Organizational Design

At this stage, you're designing structure across multiple teams. That means making real decisions about team boundaries, ownership models, reporting lines, and hiring strategy at the org level. When you split a team, merge two teams, or staff a new initiative, those are organizational design decisions with consequences that last. Hiring becomes a serious lever here. You're not just filling roles on one team. You're thinking about composition across your org: where the skill gaps are, what the right senior-to-junior ratio looks like, and how to staff new work without gutting existing teams. You're also deciding when the current structure needs to change, which is one of the hardest calls at this stage.

Key Behaviors

  • Makes deliberate team structure decisions (splits, merges, new teams) based on strategy, not just convenience or history
  • Hires with org-level composition in mind, thinking about how each hire fits into the broader picture
  • Defines clear ownership boundaries between teams so work doesn't fall through the cracks or get duplicated
  • Recognizes when a team structure that used to work is now creating friction, and changes it
  • Establishes decision rights across teams so people know who has authority over what

Common Struggles

  • Keeps team structures the same for too long because restructuring feels disruptive
  • Staffs new initiatives by pulling from the same team every time, burning out the strongest group
  • Hires to fill seats rather than deliberately shaping the org's composition
  • Lets ownership boundaries stay ambiguous between teams, creating friction and duplicated work

Success Indicators

You know you're successful when you:

  • Teams are structured to match the current strategy, not just the way things were set up originally
  • Ownership boundaries between teams are clear and rarely disputed
  • Hiring decisions are made with the whole org in mind, not just the team with the open headcount
  • When you restructure, the rationale is clear and the transition is well-managed

Mindset Shift

From:

"I actively design how this team is organized, composed, and scoped for the work ahead."

To:

"I design how multiple teams are structured, staffed, and bounded to serve the org's strategy."

Questions to Ask Yourself

  • Are my teams structured for the work we need to do next, or the work we were doing six months ago?
  • Where are ownership boundaries between teams unclear, and what's that costing us?
  • Am I hiring to shape the org I need, or just backfilling the org I have?

Build These Habits

  • 1
    Review team structure against strategic priorities at least quarterly
  • 2
    When a team is struggling, ask whether it's a leadership problem or a structural one before assuming either
  • 3
    Before opening a new role, articulate how it changes the team's composition, not just its headcount
  • 4
    After any restructure, check in on how the transition landed and what you'd do differently

Seek Feedback

  • "Does the way our teams are structured make it easy or hard to get your work done?"
  • "Where are ownership boundaries between teams causing confusion or friction?"
  • "Do you feel like talent and opportunities are distributed fairly across the org?"

Signals You're Ready to Level Up

  • Your org adapts its team structure as strategy evolves instead of clinging to what worked before
  • Ownership between teams is clear enough that cross-team work doesn't require constant negotiation
  • People across your org can explain why the teams are structured the way they are

Focus Summary

  • Structure teams around strategy
  • Hire for the org, not just the role
  • Draw clear ownership boundaries

At this stage, organizational design is about building the right containers for work. The teams you create, the boundaries you draw, and the people you hire shape how dozens of engineers experience their jobs every day. Get the structure right and a lot of other problems get easier.