Org Design Should Follow Strategy, Not Titles
There is a quiet moment in many growing companies when the org chart starts taking on a life of its own. The structure of the company drifts away from the strategy. This drift is invisible until the company tries to do something hard.
Summary
- In many growing companies the order is reversed: titles are assigned first, reporting lines second, and strategy is later adjusted to fit the resulting structure.
- Title-driven design produces senior roles with unclear ownership, functional silos where strategy needs cross-functional work, and decision rights allocated by seniority.
- Structure should be derived from what the strategy requires, since winning a segment, expanding geographically or leading with product each imply a different organisation.
There is a quiet moment in many growing companies when the org chart starts taking on a life of its own. New roles get created because the founder feels the team needs more "leadership coverage." Titles get inflated because hiring is competitive. Reporting lines get reorganized because someone complained. And, slowly, the structure of the company drifts away from the strategy.
This drift is invisible until the company tries to do something hard, and discovers that the structure does not support the bet.
Org design should follow strategy. That sounds like an obvious statement, and yet in almost every growing company, the order gets reversed. Titles get assigned first. Reporting relationships get drawn second. Strategy gets adjusted, much later, to fit whatever shape the org has ended up in.
This is one of the most expensive forms of organizational debt a company can accumulate.
When Titles Drive Org Design
When titles drive org design, the patterns are recognizable:
- Senior hires get titled "Head of X" with no clarity on what X actually owns or what success means.
- Functional silos form where the strategy requires cross-functional execution.
- Promotions create reporting lines that look reasonable on paper but produce no operational change.
- The leadership layer grows faster than the company's complexity, creating coordination overhead.
- Decision rights get distributed by seniority, not by where the company needs decision-making concentration.
Each of these is a symptom of treating org design as an HR exercise rather than a strategic one.
A company that designs structure to serve strategy operates differently. The first question is not "who reports to whom" but "what does the strategy require?"
If the strategy is to win a specific market segment, the org needs concentrated decision-making and a tight feedback loop between the people who serve that segment. If the strategy is geographic expansion, the org needs distributed authority with clear accountability for each region. If the strategy is product-led, the org needs deep ownership of product surface area, with revenue and engineering coordinated tightly. Different strategies imply different structures, and the structure is meant to make the strategy easier to execute, not harder.
What to ask before you redraw the org chart
A founder thinking about org design from strategy backward can ask:
- What does our strategy require the company to be good at over the next eighteen months?
- Which decisions need to be made faster, and where in the org are those decisions currently slowing down?
- What capabilities are we missing, and is the answer to add roles or to redesign existing ones?
- Where are the seams between functions where the strategy is leaking?
- If we drew the org chart from scratch to fit our current strategy, what would change?
These questions are uncomfortable in most companies because they imply that the current structure may be a remnant of an older strategy. That is usually the case.
Companies grow in phases, and the structure that worked at one phase rarely survives the next without redesign.
Why a company is its decisions, not its titles
At SRF Capital Studio, the work we do in HR business partnering is built on this idea. People decisions and capital decisions are the same kind of decision: bets on what the company is becoming. The structure of the company is the largest commitment to that future. When we work with founders on workforce planning, we start by mapping the strategy and its operating implications, and only then work down to roles and reporting lines. The point is to make sure each hire and each structural choice survives contact with what the company is actually trying to do.
A company is not its titles. A company is the set of decisions it can make quickly, and the set of capabilities it can deploy at scale.
The org chart is supposed to make those decisions and capabilities visible.
If your org chart describes who is senior, not what the company is good at, you have an HR document, not a strategic asset.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
Related reading
The services behind this article
What we do about it, for founders and finance teams. Each has its own page.
HR Business Partnering
Strategic people operations that align org design and hiring with what the business is actually trying to do.
