Collaboration projects

This topic contains 4 replies, has 5 voices, and was last updated by 10 months, 1 week ago.

  • Author
  • #1626


    As Dr.Simon mentioned, there are several types of organizational structure which a company can function within, each having their own set of advantages and disadvantages. Consider collaboration projects, that is, two or more companies come together to develop and manufacture a product.

    In your opinion,which organizational structure would be more efficient? Why?

  • #1635

    Khemraj Singh

    For collaboration projects, I would consider a Product Organizational Structure. This structure has managers reporting to the head of the company by product type. Each division within the organization is dedicated to a particular product line. This certainly makes collaboration among two or more companies easier, especially if a company is only called by another company for one or two products. This type of organizational structure can also shorten product development cycles. A diagram of a Product Organizational Structure is shown below:

    Product Organizational Structure

    • This reply was modified 10 months, 4 weeks ago by  Khemraj Singh.
  • #1640


    I have worked on several projects like this before with some good and bad outcomes. From an engineering point of view, this can be a pain if the work culture and engineering processes are different in both companies. Also, if there are intellectual properties that one or more companies are trying to protect during this collaboration, this can make the process more cumbersome.
    So to answer your question and based on my experience, it’s not so much the org structure that has impacted efficiency during collaboration, but more so processes, working culture and skill sets.

  • #1658


    I think matrix organization structure is most ideal for collaboration projects. To break down what a matrix is, it is an organizational structure that distributes responsibilities among two or more dimensions. A matrix organization structure takes multiple perspectives into account and makes one head person to run more than one group. The quality of decesions can then be enhanced because different perspectives are taken into account. Resources are utilized more effectively since each organization have different specialists needed in various other departments. It is more expensive to have duplicates throughout the collaborated project. Therefore, using a matrix structure will give the opportunity of sharing resources.

  • #1831

    I agree with Adrian that processes are most important during collaboration. One company may utilize the waterfall method of managing projects while another may use agile. It should be up to the company organizing the collaboration to get each company to agree on a certain process. Standardization is also critical to ensure everything flows the same and everything is done the same regardless if one company thinks their process is better than the others. The point of collaboration is for everything to work together seamlessly to produce a quality product.

You must be logged in to reply to this topic.