Practice judgment under pressure

Most feedback a Chief of Staff gets is about output. Did the deck land, did the offsite run, did the board get what it needed. Almost nobody tells you whether the calls you made along the way were any good. CoS Signal Lab reads the decisions themselves: what you chose, what it cost, and what you tend to do when the pressure is on.

12 scenarios from inside the Chief of Staff role, each a realistic bind with no clean answer. You make a handful of one-click calls under pressure, and at the end you get a private report on how you operate. About 45 minutes, no timer, and it saves as you go.

The move you make under pressure without deciding to make it. They are invisible from the inside, which is exactly why they compound. These are the ones the Lab is built to catch:

• Over-functioning. Quietly absorbing work that belongs to other people until you become the bottleneck you were hired to remove.
• Rescue mode. Stepping in to fix it because that's faster than letting someone learn to, so the same problem comes back next quarter.
• Over-control. Holding the reins tighter as pressure rises, in the moment that called for handing something off.
• Deference over candor. Softening the truth your principal needed at full strength, usually with good intentions and usually a beat too late.
• Borrowed certainty. Sounding more sure than you are, because “I don’t know yet” feels like a bad look in a room full of decisions.
• Authority substitution. Reaching for your principal’s authority because it moves faster than building your own, and spending their credibility to do it.
• Political avoidance. Routing around the hard conversation, the difficult stakeholder, the person who actually decides, and calling it diplomacy.
• Identity erosion. Becoming whatever the room needs this week until the role has no shape, and neither do you.
• Discretion under pressure. What you do with information that isn't yours, when saying nothing costs something and saying something costs more.
• Reactivity. Firefighting because it feels like the job, when the job was to see the fire coming.

Your report names one only when it turns up in more than one scenario. Which ones are yours, and what they have been costing you, is the read.

It opens with a profile of how you tend to operate, in plain language. Then your real strengths, each tied to the specific moment in your run where it showed. Then 1 to 3 patterns worth watching, with a practice for each. Then where to focus next. There is a score, but it sits in a footnote on purpose. The grade is the least useful part.

Judgment across the 6 areas the Chief of Staff role turns on. Every scenario sits in one, so a full run touches all 6.

• Role and identity clarity. Knowing what the job is when nobody ever wrote it down, and holding that line when it drifts.
• Trust and discretion. Handling what you know without leaking it or overreacting to it.
• Managing up and candor. Telling a principal the thing they need to hear while it's still useful to hear it.
• Influence without authority. Moving people who don't report to you and don't have to say yes.
• Execution under pressure. Making the call when the information is incomplete and everything is urgent.
• Self-management and reflection. Catching your own patterns before they cost you something.

Every decision is read on 4 things.

• Decision Quality. The call itself, on its merits.
• Trust Impact. What it did to your standing with the people watching, which moves independently of whether the work landed.
• Outcome Quality. Whether it worked.
• Hidden Cost Avoidance. The price a move carries later that you could not see at the time, so a high score means you saw it coming and did not pay it.

You can score well on the call and still have paid a cost you never noticed. That gap is usually the most useful thing in the report.

Every option was scored before anyone took it, by a practicing Chief of Staff. Nothing is graded on the fly, so 2 people who make the same calls get the same result. The scenarios are written so the best answer is not given away by its phrasing, and the confident move is often the one that quietly costs you. One tester who builds a competing assessment said the thing he valued most was that he could not game it. AI writes the report in plain English from those scores and never sets them.

Because there usually is not one, and saying otherwise would make the whole thing easier to game. Most scenarios have 2 defensible moves with different costs. What you get instead is what your choice actually cost: who it moved, what it bought, what it spent. The scenarios that feel hardest are the ones where both options are right and you have to pick which price to pay.

Your report names a tendency only when it shows up in more than one scenario. A single weak call on a Tuesday is a bad afternoon. The same instinct 3 times across different kinds of pressure is how you operate, and that is the only thing worth putting a name to.

It is what makes the read comparable. Everyone meets the same binds and the same choices, which is what lets the report say a tendency repeats instead of guessing at what you meant. With free text, every result is a one-off and nothing can be corroborated.

About 45 minutes at a steady pace. Testers who sat with each one have taken closer to 90, and that is a fine way to do it. It saves after every decision, so you can close the tab and come back.

Both, for different reasons. Newer Chiefs of Staff use it to find where their instincts are still forming. Experienced operators use it to check the habits they have stopped noticing, which is the harder problem. Testers so far run from people growing into the role through VPs and founders.

Your report belongs to you and is saved to your account. Nothing goes to your employer, nothing is sold, and your answers never reach an analytics tool. This is a development tool, so nobody uses it to hire, screen, or rank. While the Lab is in pilot I read results myself to sharpen the scenarios.

A course teaches you the frameworks. This watches you use them. There is no cohort and no schedule, because the point is not curriculum. Most Chief of Staff training tells you what good looks like. This tells you what you do when it is 4pm and 2 people need incompatible things.

The pilot is free for invited testers. Pricing for general access is not set yet, and the waitlist is how you hear first.