Organizational Design

At this stage, you're not designing the org. But you're starting to notice how structure affects your team's work. Who owns what decision, which meetings actually matter, where handoffs break down, why some things fall through the cracks. Most of these problems feel like people problems at first, but they're often structural ones. The skill here is learning to see the system. When something is confusing or slow, ask whether it's because someone dropped the ball or because the way things are set up makes it hard to succeed. That distinction matters more than you think.

Key Behaviors

  • Clarifies roles and responsibilities within the team so people know who owns what
  • Notices when confusion or friction is caused by unclear ownership, not individual failure
  • Defines how decisions get made on the team instead of letting it happen implicitly
  • Flags structural problems to their manager instead of just working around them
  • Keeps the team's scope and boundaries clear so people aren't pulled in too many directions

Common Struggles

  • Treats every problem as a people problem without considering whether the structure is broken
  • Lets roles and ownership stay vague because defining them feels overly formal
  • Works around structural issues instead of naming them
  • Doesn't push back when the team's scope creeps beyond what they can reasonably own

Success Indicators

You know you're successful when you:

  • Everyone on the team knows what they own and where the boundaries are
  • When something falls through the cracks, you can tell whether it's a structural gap or a performance issue
  • Decision-making on the team is clear enough that people don't need to check with you on everything
  • You've identified at least one problem that looked personal but was actually structural, and named it

Mindset Shift

From:

"I manage the people on my team."

To:

"I'm responsible for whether the way this team is set up actually works."

Questions to Ask Yourself

  • Where does work get stuck or confused, and is it because of people or because of how things are organized?
  • Does everyone on my team know what they own and what they don't?
  • Are there decisions that take too long because no one knows who gets to make the call?

Build These Habits

  • 1
    When something falls through the cracks, ask whether it's an ownership gap before assuming someone dropped the ball
  • 2
    Write down who owns what on your team, even informally, and revisit it when the work changes
  • 3
    When a new responsibility lands on the team, explicitly assign it instead of letting it float
  • 4
    Pay attention to which meetings and handoffs cause the most friction and ask why

Seek Feedback

  • "Is it clear what you own and what's outside your scope?"
  • "Are there decisions on this team where you're not sure who gets to make the call?"
  • "Where do handoffs or transitions cause the most confusion for you?"

Signals You're Ready to Level Up

  • The team operates with clear ownership and people rarely step on each other's toes
  • You can distinguish between a person struggling and a role that's poorly defined
  • Your manager hears from you about structural issues before they become crises

Focus Summary

  • Clarify ownership and roles
  • See structural problems, not just people problems
  • Define how decisions get made

At this stage, organizational design is about seeing the system your team operates in. You can't redesign the org, but you can make sure your corner of it is clear, well-defined, and set up for people to succeed. That starts with noticing when the structure is the problem.