The Matrix That Slowed Decisions
A 600-person software firm moved from functional departments to a matrix 14 months ago. Product managers own release scope and schedule; functional engineering managers own staff, technical standards, and performance reviews. Release 7.2 slipped from six weeks to eleven. Decisions that should take one meeting now take three, and 14 people attend a weekly alignment meeting. Engineers receive conflicting priorities from product and functional managers. Escalations to the vice president of engineering have doubled. The vice president wants to fix the culture with a collaboration workshop. You are asked to diagnose the structure before agreeing to training. The firm has nine product lines and six functional groups; product managers have no formal authority over engineers' reviews, and there is no documented decision-rights map. The chief executive has asked for a plan that does not add another layer of management.
1. Diagnose the problem using organizational structure and decision-rights concepts, and explain why a culture workshop is unlikely to help.
Read the worked answer
The symptoms point to structural ambiguity, not a deficient culture. In a matrix, two bosses can be legitimate, but the firm has not defined which boss decides what. Product managers own scope and schedule but lack authority over performance reviews, while functional managers own staff and standards but not release commitments. Engineers therefore receive conflicting priorities, and the only way to resolve them is escalation. The 14-person alignment meeting and the tripled decision time are symptoms of unclear decision rights and weak integrating mechanisms, not of people being uncooperative. A culture workshop may improve goodwill, but it does not tell an engineer whose priority wins when product wants a feature and the functional manager wants a refactor. Without a decision-rights map and a smaller decision forum, the same conflicts will recur after the workshop. The diagnosis should be tested by mapping recent decisions: who proposed, who decided, who was consulted, and where the decision stalled.
2. Propose two structural changes and the metrics you would use to judge whether they worked.
Read the worked answer
First, publish a decision-rights charter. Product managers decide release scope and sequence, subject to an engineering veto only for architecture, security, or capacity constraints; functional managers decide technical standards and staffing, not release content. Escalation should occur only when a decision crosses a stated threshold, such as a delay over five days or a cost over a set amount. Second, replace the 14-person alignment meeting with a five-person release decision forum: product lead, engineering lead, quality lead, operations lead, and one functional representative. The forum decides within 48 hours and publishes the rationale. Metrics should include median decision cycle time, escalation rate per release, number of attendees in decision meetings, and schedule-slip variance. A culture survey can be a secondary check, but it should not be the primary outcome. If decision cycle time falls while escalation and slip variance fall, the structural changes are working.