Threshold is centered on you, your leadership, and the impact you want to have.
Select the level that best reflects your current role. This is your starting point, not a judgment.
Months One through Three built your leadership foundation. Month One asked you to clarify who you are and how you show up. Month Two taught you to see systems accurately and diagnose root causes. Month Three taught you to turn diagnosis into disciplined design.
Month Four integrates all of it. This is where individual effectiveness becomes organizational scalability.
The central shift this month: stop being the Star Player who does everything, and become the Head Coach who wins through others. Systems do not improve when leaders hoard responsibility. Organizations scale when leaders build the people around them rather than protecting the work for themselves.
This month you will learn to delegate not as offloading, but as development. You will use your Month Three charter as a live delegation instrument. You will build the frameworks, coaching habits, and accountability structures that turn your team from executors into owners.
The goal is simple to name and hard to do: shift from doing the work to building the people who do the work. That shift is what makes everything else you have built this year sustainable.
Before we begin, take a few minutes to honestly assess where you are with delegation today. No one sees these results. Rate yourself as you actually are, not as you aspire to be.
I delegate tasks based on each person's actual readiness and development needs, not just convenience or availability.
When I delegate, I define the outcome I need rather than the specific steps to get there. I give people the destination, not the GPS directions.
After I delegate, one person clearly owns the result. I do not let accountability sit in a gray zone between multiple people.
When a team member gets stuck, my first instinct is to ask a question rather than take the work back.
I consciously use real work as a development tool. I think about what each assignment builds in the person doing it, not just whether the task gets done.
I can accept work done at 70-80% of my standard when the gap represents growth, not negligence. I do not let perfectionism become a bottleneck.
The most common leadership trap at every level: the habits that made you successful as an individual contributor become the habits that cap your team's ceiling as a leader.
The Star Player is not lazy. They are often the hardest worker in the room. That is the problem. Their work ethic becomes the team's ceiling. Every hour a leader spends doing work their team could do is an hour not invested in building the team's ability to do it.
The Month Three charter you built is not a solo execution plan. It is a delegation map. Every deliverable on that charter is an opportunity to assign ownership to someone on your team and build their capability through executing it.
Look at your Month Three charter. Name one deliverable you are currently planning to own yourself that a team member could own instead. What is the 30% growth gap that makes it a stretch for them?
One of the most paralyzing beliefs in leadership: wait until someone is fully ready before giving them more responsibility. That belief guarantees they never become ready.
Hersey and Blanchard's Situational Leadership model holds that the right leadership approach depends on the readiness of the person being led. There is no single right style. There is only the right fit.
| Readiness Level | What the Person Needs | Leadership Response |
|---|---|---|
| Low readiness | Direction and structure | Directing: high task, low relationship |
| Some readiness | Guidance and encouragement | Coaching: high task, high relationship |
| Moderate readiness | Support and collaboration | Supporting: low task, high relationship |
| High readiness | Autonomy and trust | Delegating: low task, low relationship |
Task delegation creates executors. Outcome delegation creates owners. The difference is not semantics. It is the single most important shift in how you hand off work.
Unclear ownership is the most common reason delegated work fails. RASCI is the tool that makes ownership explicit before execution begins.
| Role | Definition | Key Rule |
|---|---|---|
| Responsible | Does the actual work | Can be multiple people |
| Accountable | Owns the outcome and answers for it | Only one per deliverable — always |
| Support | Provides resources, removes obstacles | The S distinguishes RASCI from RACI |
| Consulted | Provides input before decisions | Two-way communication; must be done before |
| Informed | Receives updates after decisions | One-way communication; after the fact |
The accountability rule: If two people are listed as Accountable for the same deliverable, neither is truly accountable. The moment you cannot point to one person and say "this is yours," the deliverable is at risk. Shared accountability is diffused accountability.
Take the deliverables from your Month Three charter and assign RASCI roles for each. This is the moment where delegation becomes concrete.
For each of your charter deliverables, assign one person as Accountable. Then fill in Responsible, Support, Consulted, and Informed. If you cannot name one Accountable person, the ownership structure is not yet ready.
When a team member gets stuck, the leader's instinct is to rescue them. Rescue feels helpful. It is not. Every time you solve their problem, you confirm that they cannot solve it themselves.
Most plans fail their timelines not because the work was underestimated but because the plan had no buffer for the unexpected. Reality always fills the white space.
A Gantt chart maps milestones against time. For delegation purposes, the most important discipline is not the timeline itself. It is the buffer zones built into it.
Name three things that would stop if you were gone for 48 hours. For each one, name the specific delegation or ownership change that would prevent it from stopping.
Liz Wiseman's research found that some leaders amplify the intelligence around them and some leaders diminish it. The behaviors that separate them are specific, learnable, and visible to everyone except the leader themselves.
| Multiplier Behavior | Diminisher Behavior |
|---|---|
| Asks questions that open thinking | Provides answers that close it |
| Delegates whole challenges | Delegates broken-up tasks |
| Holds people to their own ideas | Substitutes their own ideas |
| Creates space for debate and challenge | Resolves tension by deciding |
| Expects people to figure it out | Assumes people need help to think |
Think of a recent interaction with a team member. Were you acting more as a Multiplier or Diminisher in that moment? What specifically would a Multiplier have done differently?
Not every delegation breakdown has the same cause. Knowing whether the problem is structural or behavioral determines whether the right response is a tool or a conversation.
| Problem | The Fix |
|---|---|
| Unclear ownership | RASCI assignment |
| Bottlenecks from leader hoarding work | 70% rule + deliberate delegation |
| Poor handoffs between people | Gantt timeline + back-brief |
| No accountability after delegation | 1:3:1 coaching cadence |
This is the applied work for Month Four. You are building the delegation and coaching infrastructure for your Month Three charter. Work through each section using your actual team and real deliverables.
Go through your current responsibilities and sort them into three categories.
Choose two people on your team. For each, identify a stretch assignment from your charter and the coaching support you will provide.
Name each charter deliverable, who owns it, and what decisions they can make independently versus what requires escalation.
Define how and when you will use 1:3:1 check-ins with each person you are delegating to. Name the specific day, format, and what you will do when someone gets stuck.
These five deliverables represent the full delegation infrastructure for your charter. Review each, confirm it is complete, and bring everything to your one-on-one coaching session.
Month Four is where the work you designed in Month Three becomes work your team owns. The systems you have built this month are what make that possible.
“What is the single biggest thing I have been holding onto that belongs to someone on my team?”
“What would change for my team if I was truly operating as a Head Coach instead of a Star Player?”