The nine behaviors

The observable moves that separate the people who drive decisions from the people who wait to be told. Three per motion of the Seek-Sense-Ship loop, each one small enough to spot in a meeting.

Why behaviors, not frameworks

Every program we have run teaches frameworks. What people keep is smaller than a framework: a move they make without thinking, years later, often without remembering the name of the tool it came from. One alum, two years out, put it this way: “I’m not going to remember the name of the framework, but I think about that a lot: who am I framing my message for?” The label decays. The behavior persists.

So we went back through seven cohorts of one program and asked a single question: which specific, observable behaviors separate the participants who started driving decisions from the ones who stayed order takers? The answer was nine, three per motion of the loop we teach.

Seek

Get the full picture before you form a view. Who is missing, what do they know, did you hear them right.

Sense

Turn the picture into a tested recommendation. Hold the obvious answer, cut what does not matter, find out fast if you are wrong.

Ship

Land the decision with the people who have to act on it. Say it first, shape it for each receiver, make it travel without you.

The behaviors

Seek Get the full picture

1Go where your view is weakest

Before concluding, deliberately collect the perspective you are missing: the other function, the disconfirming voice, the person who already knows. Asking for help counts as this behavior, not as weakness.

What it looks like

“I realized pretty quickly that I would have to go deep into the legal area, into the technical accounting area, just so I had a deeper understanding of what the pain points actually were across the orgs.”Vrinda, finance
A year into a new company, Brad interviewed the person who had built the existing solution before proposing his own (“you have this solution, tell me about it, does it do this, does it do that”). His proposal landed with no dissent.Brad, engineering

2Open with how and what, delay why

In any conversation meant to surface information, the first few questions start with “how” or “what.” “Why” waits. “Why” demands a defense; “how did that come about?” invites the specific memory of what happened, which is where the usable detail lives.

What it looks like

“Not ‘why don’t you do more to track things post launch’ but ‘how are you tracking the success of your project post launch.'”Evan, now an engineering manager
“Asking how/what questions instead of whys makes people more comfortable sharing and more likely to provide contextual, specific responses than generic, synthesized attitudes.”Yuqian, UX research

3Loop it back

Paraphrase what you heard and ask “did I get that right?” before moving on. A slightly wrong paraphrase is a feature: people cannot help correcting information about themselves.

What it looks like

Martina replaced solution-jumping with a deliberate pause: “I was trying to jump and find the solution right away. Now I’m like, okay, please say more.”Martina
“The how/what questions and the feedback loop has helped me broadly in life and work. Loop for understanding keeps me engaged in the convos.” Said in the survey, and again nine months later.Evan
Sense Turn it into a tested recommendation

4Hold the verdict

When the answer feels obvious, name what you would need to know for it to be wrong before acting on it. Questions before conclusions, held deliberately under pressure.

What it looks like

“My first instinct was to jump to ‘these are stolen identities.’ Instead, I forced myself through how/what questions before concluding anything: What exactly changed in the data? How were these accounts onboarded? What would have to be true for this to be organic growth rather than fraud? Walking through the questions before the answers stopped me from writing a rule that would have blocked a batch of real, if unusual, new sellers, and pointed me instead toward the actual shared signal.”Michele, risk

5Sort and drop

Put the mess into a small set of non-overlapping buckets, then deliberately drop what will not change the decision. The drop is the skill.

What it looks like

“These are the top four issues. These next 22 issues, we can spend a day of legal’s time on each. I just don’t think that it’s worth chasing them down.”Vrinda, finance
“There were one, two, three main aspects that I used to classify the problems we were seeing. I intentionally left many minor things out of the scope because it was not important, wouldn’t move and it wouldn’t lead to any meaningful impact.”Marcos, product, two years out

6Pressure-test before the room

Before any high-stakes delivery, run the draft past a thought partner chosen to poke holes, and revise from what comes back. The recommendation gets tested as a draft before it becomes a verdict.

What it looks like

“I did practice it a lot with our CFO. I would run past him how I was approaching different teams. Even just having a buddy or mentor who can reflect back to you or pressure test how you plan to communicate things is helpful.”Vrinda, finance
“I use AI as a draft, but I use a human for fidelity.”Etienne, engineering
Ship Land the decision

7Lead with the answer

State the recommendation in the first sentence, then let the audience pull you down into the support. Problem, causes, options, and a committed recommendation together. Build bottom-up, communicate top-down.

What it looks like

The same engineer, the same technical issue, six months apart. First attempt: “just raising the issue and seeing if there’s a discussion that occurs or not.” Nothing happened. Second attempt: “communicate this better as an action instead of just raising an issue. ‘This is what I’m going to be doing,’ and then just acknowledgment on it.” It shipped.Nathan, engineering
“Leading with the headline. Cut the preamble, cut the ‘how did we get here,’ A, B, C and therefore D. Just lead with the D.” Now taught to his own team.Gordon, engineering

8Map the room

Before any consequential message, name who will receive it, how each receiver thinks, and what each cares about. Then build the versions.

What it looks like

Kyle wrote three versions of a budget ask for three stakeholders (an analytical manager, a big-picture skip-level, a relational events lead) and never pitched the executive directly. The intermediaries carried it, and it was funded.Kyle, sales
“Here are the people attending, this is the perspective they’re going to bring, these are the things I already know they’re worried about or going to push back on. So we should narrow our agenda to just hit these three things.”Annie, marketing
“It definitely didn’t feel natural in the beginning. The more I practiced it, the easier it got. I would still have to prompt myself to switch into that mode every single time.”Vrinda, on whether it feels authentic

9Make it carryable

Compress the ask into a form the receiver can repeat without you in the room: why now, the action, the benefit they care about, and the cost of doing nothing. Equip the intermediaries. Make it easy to say yes.

What it looks like

Coordinating executives across two regions for a sales kickoff, Sara used “here’s the decision I need, here’s what happens if it’s not made by this time,” and got “surprisingly quick alignment across those leaders without much actual pushback. It allowed me to move really fast.” She now spots the counter-pattern in others: asks with no timeline attached.Sara, marketing
“We could spend it on a new happy hour and hope that people come, or we could sponsor this event that’s already happening.” Two colleagues carried that line to an executive Kyle never met.Kyle, sales

How we use them

  • As the map. We lay an organization’s own role expectations against the nine behaviors, in its language rather than ours, and show which ones already have proven practice behind them.
  • As the practice. Every scenario in a program gets a behavior to run it with. The senior leader who wants it done their way becomes a rep in holding the verdict and mapping the room.
  • As the measure. A 360 built on the nine behaviors, rated by self, manager, and cross-functional colleagues, because each behavior is observable: it happened or it did not. Run before a program for a baseline, and again months later to see which behaviors moved.
  • As the mastery test. Fluency is not the bar. The bar is whether someone can teach the behavior to a colleague who never took the program. A dozen alumni of one program now do.

The behaviors compound in sequence. Every large outcome story on record chains them in loop order: a missing voice sought, a mess sorted, a draft tested, an answer led with, a room mapped, an ask that traveled. Individual behaviors give depth. The loop gives coherence.

Where they come from

Seven cohorts of one leadership program for individual contributors at a fast-growing technology company, 2024 to 2026. We read every participant survey, three alumni forums, and one-to-one interviews recorded months and years after the program ended, and kept only the moves that an observer can confirm happened, that show up outside work as well as in it, and that a person can learn in a short practice session.

The before-state sounds the same across cohorts. “To get to my current role I just had to get better and faster at doing what was asked of me. To get to the next level I have to start becoming the one who is identifying opportunities and guiding others to work on them.” The after-state has a consistent shape too: question-led discovery, deliberate elimination, a tested draft, a committed recommendation, receiver-first packaging, and a named cost of inaction. The nine behaviors are the moves that carry someone from the first state to the second.