Role Separation in the Problem and Solution Spaces
Question: Should we separate roles in the problem and the solution space?
From a methodological and functional perspective, separating roles in the problem and the solution space is imperative.
The first reason for separation is because the solution space is a bottomless pit of tactical and technical activities which will completely monopolize a person's focus.
When mixing roles from either the problem or solution spaces, the roles in the solution space will dominate because the individual often does not have enough details on the market problem, and because the solution requires documenting many details and constant interaction with the engineers.
Accordingly, crucial strategic activities in the problem space will not be adequately performed if the person is overwhelmed with intricate responsibilities in the solution space.
The second reason for separation is gravitating skills, which is a dominant occurrence when mixing any roles.
Gravitating skills is when people naturally devote more time and effort to do whatever they are more comfortable and natural with, effectively neglecting other assigned roles.
For example, a technically-minded person will prefer writing product requirements and not engage in market research or customer interviews.
The primary guideline to follow when combining roles is to have all the roles being combined belonging to one space only.
Do not mix and assign roles from both the problem and solution spaces to one person.
For example, a product planner and product marketer role combination (only the problem space) is better than a product planner and product architect role combination (both the problem and solutions spaces).
The secondary guideline to follow when combining roles is only to join roles of the same character.
For example, assigned roles are all strategic. Do not assign strategic and operational roles to one person.
For more information, see the What is Product Management? web page and view the six-minute video which explains what product management is according to the Blackblot PMTK Methodology™.