TEAM
READINESS
TO SCALE.
TEAM
READINESS
TO SCALE.
Most leaders cannot say whether their team is ready to scale with anything more specific than a feeling. This diagnostic makes that feeling specific. The output maps your team across six pillars of capacity, shows where it is fixed, grinding, or flowing.
Pick what's most true, not what should be true.
Estimated time: 6 minutes.
Get started
1. Think of the most demanding push your team has been through in the last 6 months — a launch, a deadline, a crisis, a fundraise. The week after it ended, what actually happened?
People kept going at the same pace. The next thing was already on fire.
A few people took a day or two. Most did not. Work continued roughly as before.
Visible drop in output for about a week — late starts, lighter calendars — then back to normal.
A planned recovery period was scheduled in advance. People took it. Nobody felt guilty about it.
Recovery is built into the operating rhythm. The team finished the push energized, not depleted, because intensity and renewal alternate by design.
2. A major opportunity arrives tomorrow. Capturing it requires your team to operate at 130% of current load for the next 4 months. Which is the most honest response?
We would take it. We have done harder. People would figure it out.
We would take it, but I would expect 1 to 2 resignations and visible quality drops by month 3.
We would decline or renegotiate scope. Current load is already near our sustainable ceiling.
We would take it only if I could hire 2 to 3 people in the first month. With that, yes.
We would take it easily — current load runs at maybe 70 percent of what the team can sustain. The headroom is structural.
3. In the last two weeks, when you have been stressed, frustrated, or anxious about something, how would the people closest to you on the team have known?
They would have picked it up from how I behaved — shorter responses, faster meetings, more critical edits — but I would not have named it.
They would not have. I keep it pretty contained until I have processed it.
They probably caught the spillover. I might have been sharper than usual, or vented more than I meant to.
They would have known something was off, but not the specifics. I would have named it briefly (rough morning, I will be quiet) and moved on.
Difficult emotions arrive, get named, and move through me without distorting how I lead. The team is not managing my state because I am.
4. Picture yourself walking into your team working space (or opening Slack first thing) on a normal Wednesday morning, last week. Before anyone notices you are there — what is the ambient feeling?
Tense. Short messages, closed body language, people seem careful around each other.
Buzzy and a bit chaotic — lots of conversations, some about other people, some venting.
Honestly varies wildly day to day — I could not predict.
Quiet. Productive but flat. Not much energy in either direction.
Focused energy. People are heads-down, occasional laughter, generally engaged. The baseline tone is calm and active.
5. A specific time someone on your team produced something (a doc, a decision, a customer email) and you went back in and changed it after they handed it off. What actually happened?
I made the change without telling them — it was faster, and the bar matters more than their feelings.
I made the change and told them what I changed and why, so they would know for next time.
I sent it back with feedback and asked them to revise it themselves, even though I could have done it in 5 minutes.
I left it. It was not how I would have done it, but it was good enough and shipping it as theirs mattered more than the delta.
The team owns standards I no longer have to enforce. The work being theirs — sometimes better than I would have done — does not register as a threat.
6. Two outcomes: a major project your team owns succeeds visibly because of decisions you did not make, and a smaller initiative you personally drove fails publicly. What do you actually feel?
Net negative, even though the math says it should not be. The failure would weigh more.
Mixed in a way I would not fully admit. Glad for the team but quietly bothered the win was not more clearly mine.
Mostly fine, but I would find myself slightly more invested in the failure than the success.
Net positive. The team winning is the bigger story, the personal failure is annoying but localized.
The team win is the bigger event by a clear margin. The personal failure registers as data, not as identity. The asymmetry is real, not performed.
7. Think about every decision someone on your team brought to you for input or approval yesterday. What is the honest breakdown?
Honestly heavy on the small. I find myself thinking why are they asking me this, but I answer because the alternative is a longer conversation.
Mostly small approvals and what should I do here questions about things the person should already know.
Mixed. Some real ones, several I noticed mid-conversation did not really need me — but it was faster to just answer.
Most were genuinely important — strategic calls, hires, things only I have context for. Maybe one or two could have been handled lower.
Almost nothing reached me yesterday because the team operates on clear decision rights. What did reach me was genuinely strategic.
8. Reconstruct the most recent stretch — last 30 days or so — when complexity genuinely spiked. During that stretch, what happened to decision-making?
I pulled decisions back and then mostly did not give them back. The temporary centralization quietly became the new normal.
I pulled key decisions back to me — temporarily, to make sure we got it right. Things stabilized after a couple of weeks and I let go again.
Decisions distributed mostly, but I noticed myself wanting more updates, more visibility. I tightened the loop without taking decisions back.
There has not really been a stretch like that recently — things have been steady.
Decisions kept distributing the way they normally do. The team made calls in their domains and we navigated the complexity without me becoming the routing center.
9. Reconstruct the most recent meeting, last 14 days, where a real decision was being made. During that meeting, what happened with disagreement?
Mostly nodding and good points. Someone clearly had reservations from body language but did not say anything.
Open friction — but it got personal, or someone got defensive, and the decision quality did not improve from the conflict.
There was disagreement, but polite. People hedged. The real objections came out in 1 to 1s afterward, not in the room.
Someone openly disagreed, including across seniority. It got worked through, and the decision came out stronger.
Disagreement is the operating system, not the exception. People challenge each other without it being personal because the team is aligned on what we are trying to achieve, not on who is right.
10. Think about the last meaningful problem that hit your desk later than it should have — a frustrated customer, a project actually behind, a hire that was not working. How did it eventually reach you?
It came out in a postmortem with the framing of I should have told you sooner.
I noticed it myself — through a metric, a customer complaint, a stray comment — and only then did the rest of the picture come out.
Someone brought it to me, but only after it had already started visibly affecting things. The team had been aware but had not escalated.
I cannot think of a recent example — information seems to flow well.
Someone brought it to me directly, before it became a crisis, and it was clear from the framing that the team had been actively monitoring it together.
11. Reconstruct the most recent moment, last 90 days, when something unplanned hit your business — a competitor move, a regulation change, a key person leaving, a market shift. Reconstruct your first 72 hours of response.
I went into damage control. Most of the next two weeks were spent stabilizing rather than thinking about what the change opened up.
It rattled me for a couple of days. I worked through it but my response was slower and more cautious than it could have been.
I dealt with it cleanly — assessed, communicated, made the necessary adjustments. The business is roughly where it would have been.
Within 24 hours I had started reframing it in terms of what it might enable. Within 72 hours I had committed to a move that would not have happened without it.
The team brought me ideas about what the change might enable before I asked. Disruption is treated as information by default. The system gets sharper from volatility, not just through it.
12. Think about the last time something blocked progress on a real priority — a partnership fell through, a hire passed, a regulator pushed back, a key dependency failed. Reconstruct your first three actions after you understood the block was real.
I noticed myself getting demoralized for a while. Came back to it eventually but the energy around the priority took a hit and did not fully recover.
Most things I prioritize tend to either work or get quietly deprioritized when they hit friction.
I paused. Reassessed. The pause was useful in retrospect but cost time, and I noticed I was waiting for clarity that was not going to come from waiting.
I worked on getting through the hurdle directly — pushed harder, escalated, found workarounds. We got there but it took longer than the original plan.
I started looking for the second-best path almost immediately. Within a day or two I was working a different angle that, in some cases, turned out to be better than the original plan.
Company
Full name
Email
Next
Submit