In one line: How a company links people into groups for product work, by function, by project, or in a matrix of both, sets the trade-off between deep expertise and fast, coordinated delivery.
Core idea
Organization is simply the scheme by which individuals are linked into groups. The links can be reporting relationships, shared activities, financial arrangements, physical location, or informal social and political ties. For product development, the classic choice is where people report:
| Form | People report to… | Strength | Weakness |
|---|---|---|---|
| Functional | function heads (electrical, mechanical, test…) | deep expertise, efficient use of specialists | slow coordination across functions; no one owns the product |
| Project | project managers | speed, focus, clear ownership | expertise thins out; people may be stranded when projects end |
| Matrix | both a function and a project | balances depth and integration | two bosses; conflict over priorities and resources |
How it works
- Matrices come in weights.
- In a heavyweight matrix, the project manager controls budget and people’s evaluations, so it behaves almost like a project organization.
- In a lightweight matrix, the project manager mainly coordinates, and the functions hold the power.
- There is no single right answer. The best form depends on size, industry, competition, how fast products turn over, technology, capital intensity and market position.
- Speed tends to fall as size grows, which is why large organizations build supporting mechanisms, such as visible status (see Obeya) and explicit decision rights (see RACI Charting), to keep cross-functional work moving.
- Labor is the main cost of engineering. That is why organizations track time against charge numbers. Comparing your forecast hours with actual hours, even for your personal life, is a surprisingly revealing exercise in how work really gets done.
In practice
An org chart rarely tells you what someone does. A common exercise is to draw a team you have worked on, with who was on it and who owned what, and then ask three questions:
- Is there a pattern?
- What drove the team’s makeup?
- Could an outsider infer your job from the chart?
Most engineering organizations turn out to be matrices of some weight. Many of the frustrations engineers report, such as conflicting priorities, unclear ownership and slow decisions, trace back to the matrix’s two-boss tension rather than to individuals.
Questions to ask yourself
- Is my organization functional, project-based, or a matrix, and how heavy is the project side?
- Who actually decides when my functional manager and project lead disagree?
- What does my time card say about where my effort really goes?
Connections
- The process these organizations run: Product Development Process.
- Tools that ease matrix friction: RACI Charting, Obeya.
- Team-level view: High-Performing Teams. Leading inside the matrix: Leading from the Middle.
- Capabilities exercised: Connecting Across Disciplines, Interpersonal Skills, Realizing the Vision.