Perla › Manifest › a great team
Manifesting A Great Team caught it before i did
It's an ordinary Tuesday and someone on the team flags a pricing error in the new listing before a single customer sees it. This isn't measured by headcount; it's the ordinary moment someone catches something you missed and fixes it without making it a whole conversation.
- A full script for a great team, written in the present tense and ready to read tonight.
- Shorter versions — one for falling asleep, one for the morning, and one line to carry with you.
- How to use it: Trust between people who already work together doesn't build because a script asked it to, and headcount alone never made a team good.
- The common mistake: Counting how many people are on the team, or comparing headcount to a competitor's, says nothing about whether the people already there actually trust and cover for each other.
The script
Read it slowly, in the present tense, as though it has already happened. It is written to be spoken aloud, but silently is fine.
I'm halfway through the Tuesday standup when someone mentions, almost in passing, that they noticed a pricing error in Friday's new listing and already fixed it before anyone bought at the wrong number. I hadn't caught it myself, and they don't make a thing of telling me, just a line in the update before moving on to their own tasks for the day. Later that morning another person on the team asks a genuinely useful question about a decision I made last week, not challenging it, just checking they understand the reasoning before they build on top of it, which makes me explain my own thinking properly for the first time. By the afternoon a third person has quietly picked up a task that fell between two people's job descriptions, the kind of gap that used to sit unclaimed for days, and just does it without waiting to be asked. I don't sit down and calculate how many people are on payroll before I close my laptop that evening. I think about the pricing error caught in time, the honest question, the task nobody had to be told to pick up, and about a business that runs a little more smoothly today because three separate people paid attention without being asked to.
Shorter versions
Two for the ends of the day, and one line to carry through the middle of it.
The pricing error's fixed, the gap task's done, headcount unchecked tonight because it was never the point. Someone caught a mistake I made and quietly corrected it without turning it into a conversation, and that's worth resting on more than any number of people on the payroll. The office is dark now, the laptop's shut. Three people paid attention today without being asked to. That's what a good team actually looks like.
Yesterday's gap task gets checked first, the one nobody was assigned that got done anyway, because whoever picked it up deserves a proper thank you before the day gets busy. I write it, specific to what they actually did, then open the week's task list. The usual work takes over after that, a little steadier today knowing a pricing error gets caught before a customer sees it, not because I checked, but because someone else did.
Someone caught a pricing error before a customer saw it, fixed it, barely mentioned it.
How to use it
Trust between people who already work together doesn't build because a script asked it to, and headcount alone never made a team good. Right after a standup or a check-in where something quietly went right because someone paid attention, notice it properly rather than assuming it. Thank the person specifically for what they actually did. That matters more than how many names sit on the payroll.
The mistake to avoid
Counting how many people are on the team, or comparing headcount to a competitor's, says nothing about whether the people already there actually trust and cover for each other. A team that catches each other's mistakes quietly, without making it a performance, is doing something a bigger team without that trust can't match. Notice the quiet catch, the honest question, the gap task nobody had to be told to pick up. That's the actual measure.
Questions
What makes a team great beyond just hiring good people?
Trust that shows up in small moments, someone catching a mistake and fixing it quietly, someone asking a genuine question rather than assuming, tends to matter more than individual talent alone.
How many people does a great team need?
There's no minimum; a two-person team that genuinely covers for each other can outperform a much larger group that doesn't, and size alone doesn't build that kind of trust.
How do you build trust on a small team quickly?
Noticing and naming the small moments it already shows up in, rather than only addressing problems, tends to reinforce the behaviour more than any formal exercise does.
Have this written about you
The script above is written for anyone. Perla asks about your actual situation, writes it as a present-tense narrative and reads it back to you — in a calm voice or your own, recorded once. One ritual instead of ten apps.