Example · Coach

Everything below is invented for illustration — the people, the situations and the wording. The layout, structure and privacy rules are exactly those of a real report.

This is everything a coach can see: the final report, shared by the client's explicit permission. Transcripts, reviewer identities and per-reviewer data are never available to a coach.

Professional / Leadership report · synthesized August 21, 2026

Delivers under pressure; harder to follow when the pressure is off

Nine conversations describe a client who is decisive and clear when stakes are high, and whose reasoning becomes invisible in ordinary weeks. The shared report below is the only material available for this engagement: transcripts, reviewer identities and per-reviewer data are not accessible to a coach at any point.

Adequate evidence base. Nine external conversations across three relationship groups, shared with the coach by the client's explicit permission. 9 external interviews + self · 71 behavioral observations.

What makes you effective

Best supported first

  1. 01

    Steadies the room under pressure

    Strong evidence

    People consistently described incidents where escalating problems became workable once you joined. The pattern is behavioral and specific: naming the actual decision, cutting the scope of what must be solved now, and saying out loud what will be handled later.

    • ·Several people described a launch weekend where the work was re-sequenced into two tracks within an hour, and said the change removed the argument rather than settling it.
    • ·Colleagues in different groups independently described the habit of stating what will not be fixed today as the moment tension dropped.

    Independently described by seven people across three relationship groups, with concrete situations rather than general praise. · Relates to Decision-making under pressure, Prioritization

  2. 02

    Direct feedback that people can act on

    Strong evidence

    Feedback is described as specific, timely and unembellished. Several people said they knew where they stood without having to interpret tone, and contrasted this with previous managers.

    • ·People described receiving correction within a day of the work rather than at a review cycle.
    • ·More than one person described asking for a second opinion on their own work because the answer would be usable.

    Corroborated across two independent relationship groups with situation-level detail. · Relates to Developing others, Candor

  3. 03

    Protects the team's attention

    Moderate evidence

    A recurring description is of work being declined, deferred or absorbed before it reached the team, with the reasoning made explicit to whoever asked.

    • ·Colleagues described requests being turned down in the meeting rather than passed along quietly.

    Described by four people, mostly from one vantage point, so treated as moderate rather than strong. · Relates to Prioritization, Stakeholder management

Where you may be getting in your own way

Patterns, not verdicts

  1. 01

    Reasoning stays in your head

    Strong evidence

    The most frequently described friction is decisions arriving as conclusions. People said they can usually reconstruct the logic afterwards and generally agree with it — but reconstructing it costs them a week of guessing, and in that week they hedge.

    • ·Several people described a re-prioritization that they only understood after asking a third party.
    • ·People in two groups described preparing work they suspected was already deprioritized because no one had said so.

    Independently described in three relationship groups, with distinct situations each time. · Relates to Communication, Prioritization

  2. 02

    Quiet periods read as disengagement

    Moderate evidence

    When nothing is on fire, your attention visibly moves elsewhere. People described this as neutral for experienced colleagues and costly for newer ones, who read the absence as a verdict on their work.

    • ·Newer colleagues described interpreting a lack of response as a signal that their project no longer mattered.
    • ·More experienced colleagues described the same behavior as unremarkable, which is itself part of the pattern.

    Consistently described, but with meaningfully different interpretations depending on tenure. · Relates to Developing others, Presence

  3. 03

    Disagreement closes early

    Moderate evidence

    Several people described raising an objection once and then dropping it, not because they were overruled harshly, but because the conversation moved on quickly enough that a second attempt felt like obstruction.

    • ·People described holding back a concern that later turned out to be the actual problem.

    Four independent descriptions, one of them a mixed account that also credited you with reversing a decision when pushed. · Relates to Candor, Decision-making under pressure

How you see yourself vs. how others experience you

From your self interview vs everyone else

  • Communication

    Others see this differently

    You said

    You described yourself as over-explaining and worried about repeating context people already have.

    Others described

    Others described conclusions arriving without the reasoning, especially outside a crisis.

    The explaining you do happens under pressure, when people are already paying attention. In calm weeks, the same explanation does not happen.

  • Developing others

    Others rate this higher than you do

    You said

    You described this as the part of the role you are least confident in.

    Others described

    This is one of the two most strongly evidenced strengths in the whole set.

    The feedback habit you treat as routine is what people named when asked what they would keep.

  • Decision-making under pressure

    Broadly aligned

    You said

    You described this as your most reliable capability.

    Others described

    Others described the same, in the same terms.

    No meaningful divergence.

Different vantage points

Only groups with 3+ completed interviews

  • Direct reports · 3 voices

    Value the directness; want the reasoning behind priority changes.

  • Peers · 3 voices

    Describe you as the person to bring a stuck problem to.

  • Customer / partners · 3 voices

    Describe a candid account of what will and will not be delivered.

Tensions worth sitting with

Where the evidence disagrees with itself

  • The same directness is described as the best and the hardest thing

    People who have worked with you longest describe directness as respect. People newer to the team describe the same behavior as difficult to read. Both accounts are specific and neither is a misunderstanding — the difference is the amount of context each group has.

If you change one thing

Say the reasoning out loud when nothing is urgent

Every development theme in this report traces back to the same cause: your thinking is visible under pressure and invisible otherwise. This is the smallest change that touches all three.

Instead of

Announcing a new priority order and letting people infer why it changed.

Start doing

Two sentences with every priority change: what moved, and what you traded away to move it. In writing, where people can re-read it.

You'll know it's working when

  • ·People stop asking a third party what a change meant.
  • ·A concern raised once gets raised a second time in the same meeting.
  • ·Newer colleagues describe a quiet week as a quiet week.

Your next 90 days

Three experiments, one question

  1. Start

    Two-sentence reasoning note

    Whenever priorities change, post what moved and what it cost.

    Measure: Count how often someone asks a third party to interpret the change.

  2. Stop

    Closing a disagreement on the first pass

    When someone objects, ask a second question before moving on.

    Measure: Track how many objections get a second turn.

  3. Continue

    Same-day feedback

    Keep giving correction within a day of the work.

    Measure: Ask newer colleagues whether the feedback arrives soon enough to use.

One question to ask your team

When I change what matters, what do you have to guess?

Prepared for A. Client. Themes paraphrase anonymized evidence; no individual interview is quoted or identifiable.

Other examples

Build 2026.09.05 · v0.3.2