Project to Product Organization For Executive Leaders
The Project to Product Organization is a very sensitive topic for executive leaders. While a traditional project company is designed around functional departments the product company is designed around product value streams, this article will explain the main differences from an organizational design point of view between a project vs product company.
The organizational structure is extremely important for the success of any business, and that’s why the topic of Project to Product Organization requires an entire article to explain the main concepts in detail.
Project-centric companies are designed around functional departments, therefore it’s common to build a matrix organizational structure to build the projects. On other hand, product-led companies are designed around product value streams.
ADAPT Methodology® is a unique Digital Product Development framework to change traditional project-centric companies toward product-led companies!
Society changed and leaders need support in the way how they lead and design their digital product organizations, that is the reason why the ADAPT Methodology® was created, but now let’s get a deep dive into the Project To Product Organisation.
Project to Product Organization
We believe the matrix organizational structure is a completely outdated model for companies that are creating Digital Products, but if your business model is to build projects this organizational design might not be that bad. On contrary, if you are building Digital Products you want to take a look into a different way to design your company, so let’s dig into this topic.
An organizational structure with a matrix design is bad
Spotify’s document about tribes and guilds became extremely popular in the Agile community. If you take a look into their organizational structure, you will see they are using a matrix organizational structure and in my opinion, this is not the best approach. Before I continue, I would like to explain what an organization structure based on a matrix organizational structure is, just to make sure that you fully understand what I want to say.
In simple terms, a matrix organization is an organization where vertical projects are staffed with several individuals from different parts of the company belonging to several different departments. This approach is extremely common because most companies are built like this.
Below you can find a picture that represents an organizational structure based on the matrix method:
Over the years, I have worked with many companies where this organizational structure is present; based on my experience, I will outline the following problems common to it.
Extremely Political Environment
It is not uncommon for organizations with this kind of setup to suffer from political issues. The team in this situation is a bunch of individuals from different parts of the organization that are brought together to deliver something.
My experience tells me the problem is not with team members but with line managers. If everything is going well, line managers tend to say that success is a result of their team members.
If something really bad happens, line managers tend to say the problems are due to the other departments. They enter into “save my ass” mode, trying to cover their ass instead of helping the organization to find the problem.
I believe this is partly the result of the previous problem. When something goes wrong, people from different departments try to save their asses and blame everyone other than themselves. Unfortunately, I see this happen too often.
Horizontal Line interference
Over the span of my career, I’ve seen this happen in almost every company where I worked: Moving towards Agile is something difficult for most middle managers.
There are clear roles for Product Owners, Scrum Masters, and Team Members, but nothing for Agile Managers.
Managers try to do their best to help people, but in my humble opinion, most of the time their actions in these situations cause more harm than good. They try to give “one on one” help to people regarding career development, they try to establish team events, and they try to do many other things, but in reality, all these activities remove people’s focus from their product team.
Another typical example is the practice of having all these line managers in all kinds of meetings, for example, dailies, planning, reviews, etc. Because they want to see what their guys are doing, they go to these meetings, but unfortunately, most of them cannot keep quiet, and therefore they end up sabotaging the discussion and making all these meetings quite inefficient.
Decisions take a lot of time to be made
Of course, in theory, the team should own all their decisions, but with so many “chefs in the kitchen”, I can guarantee that any decision that ought to take just a few minutes will take weeks of negotiation with this kind of organization structure—Not productive at all.
Individual Goals mess
People that follow my work know how I hate personal goals attached to individual performance. In this organizational structure, I believe we have the right setup to launch the company into chaos and drain people´s individual motivation.
Let me explain: Having several horizontal line managers implies (in most organizations) that each different person will have a different goal or goals defined by his/her manager.
Now, if you imagine that in a team of 7, everyone has two goals, for example, this means that we have a total of 14 individual goals that have nothing to do with the team goal, which is the most important one.
Of course, you can say the team as a whole will have its goal, and all the individual goals will end up aligned with the team goal, but do you believe that with so many different managers, different people, and different goals, people will be aligned with the team goals? Well, hardly, at least I do not believe.
Interference with new hirings
Several years ago I had the opportunity to be part of a sad story. At that time I was Scrum Master, and the team was recruiting a developer; of course, we all looked for senior developers. We had several interviews with several candidates, but only one guy seemed to be a perfect fit for our team. We all agreed he was our man. We communicated with everyone and said he should be hired.
A couple of days later, the head of software development informed us that HE had chosen another guy. So basically, a guy who was not part of our team, which would not work on a daily basis with the new developer, who did not have any idea about what we needed, decided the future of the whole team. Later on, we found out that he was simply trying to achieve his personal yearly goal (saving money for the department).
Our companies are full of such cases, demonstrating how the horizontal line manages without understanding their place in Agile Organisations, and how this can harm the company a great deal.
A Product Value Stream Approach
So what can be done? How can we assemble cross-functional teams that have everything needed to allow high performance?
Before I describe my approach, I want to warn you; this is quite a radical approach to traditional management.
I know this cannot be implemented in most companies (or at least, those typical managers), but I truly believe in Peter Senge’s words:
“It´s not enough to change the structures if the mindset behind does not change“
I think this is one of most companies’ biggest problems: they keep trying to solve old problems with old ways of working. If you truly want to make a difference, you truly must change the way you think—to that end; I choose to present something more radical than the norm.
We want to create teams that:
- Are small, directly communicating with each other
- Where everyone takes responsibility for their work
- Make decisions fast
- Celebrate small successes
- Are not political
- Have end to end responsibility
- Are focused on real, important things
- Can release their products several times a day if necessary
- Budget independent
- Have all the necessary people to make the product live
If you think about all these characteristics, this is exactly what a Startup is. So, why not create small Startups within our companies, meaning Product Value Streams?
Before you say this idea is ridiculous, consider the fact that there are several companies all over the world already testing this concept.
So, how can we assemble this kind of setup? To achieve this kind of setup we should create cross-functional teams that are fully independent.
Everyone reports to the same person (the Startup CEO), and this small team has all the necessary people and necessary skills to make the product live.
Below you can find a picture illustrating this setup.
Pros and Cons of this approach
Since I presented the positive aspects above, I will now focus on the negative points of this approach:
There is no space for middle management – If companies chose to implement this approach, middle managers would not have a role. Of course, they can do any other job that is necessary to release the product, but typically this will not be a manager role—it will be a specialist role, which means that middle managers must adapt to new jobs.
Communication with other Start-Ups – The ideal setup will be able to create fully independent products without requiring much communication with the rest of the organization, but we still want to share best practices with the rest of the company. Here people must be careful not to get isolated from the other parts of the organization. Typically a well-established Community of Practices will tackle this problem.
A lot of courage is needed – To implement this kind of approach, top management must have a lot of courage. This is a completely radical approach, and it requires a lot of courage to try something so new like this. Even if management can implement this, the company must have a great culture of learning from its mistakes, as this will be the only way to achieve success using this approach.
I believe if we have the courage and the vision to start building companies in this way, we will be able to create products faster and more successfully than ever.
Summary on the topic of Project To Product Organization
In a project-based organization, the project team is usually assembled for the duration of the project and then disbanded once the project is completed. The team may include a project manager, subject matter experts, and a variety of other specialists, such as designers, engineers, or developers.
In contrast, a product-based organization is focused on creating and selling a product or set of products to customers. This type of organization is often structured around product value streams that contain all the skillsets required to develop the product, such as marketing, sales, engineering, and customer support.
The movement from project to product is becoming bigger, therefore, we truly believe that we would need to write a small article on this topic: project to a product organization, we hope you enjoyed it.
Did you like this article?
We enable leaders to become highly valued and recognized by adapting their project-centric company into a product-led company, society changed and leaders need support to adapt their companies to the digital era, that is the reason why the ADAPT Methodology® was created!
If you are interested in knowing if your company is a project-centric or a product-led company simply take our Project To Product Scorecard.
If you want to know how we can help you to start your transformation please check out our: Project To Product Training.
If you are interested in doing a transformation in your company please check out our: Project To Product Consulting.