Dive into the transformative world of product teams and vertical slicing in our latest Engineering Strategy 101 series. Gain insights on building cross-functional teams, fostering innovation, and aligning with customer values for more efficient and agile product development. Unlock the blueprint to revolutionize your software development approach and drive success.
A matrix organization is a company structure where teams report to multiple leaders. The matrix design keeps open communication between teams and can help companies create more innovative products and services.
In my experience, in a matrix organization, the team reports to the project manager as well as each team member reports to the head of their competence (whatever is their main area of knowledge).
When a new project is going to start, there is a negotiation between the project manager and the different heads of expertise to get the people and expertise he/she needs for the project (starting time, time in the project, other details). This type of organization allows an expert to help in several projects at the same time.
It's a very interesting representation of divide and conquer. I Some companies use vertical slicing to isolate departments from one another resulting in lost communication and productivity, but your version is much cleaner.
How would this organization be different from a matrix organization?
Interesting question. What is your definition of a matrix organization?
A matrix organization is a company structure where teams report to multiple leaders. The matrix design keeps open communication between teams and can help companies create more innovative products and services.
In my experience, in a matrix organization, the team reports to the project manager as well as each team member reports to the head of their competence (whatever is their main area of knowledge).
When a new project is going to start, there is a negotiation between the project manager and the different heads of expertise to get the people and expertise he/she needs for the project (starting time, time in the project, other details). This type of organization allows an expert to help in several projects at the same time.
Great post, Alvaro. Developers should be more focused on the product, rather than the code.
If the product doesn't work well, the code doesn't matter.
And thank you for the mention!
It's a very interesting representation of divide and conquer. I Some companies use vertical slicing to isolate departments from one another resulting in lost communication and productivity, but your version is much cleaner.