The Inputs — Jordan Reyes
Synthetic illustrative example. A VP of Product, ~12 years' experience, two companies. Provided one assessment, a corpus drawn from ~9 months of AI working sessions, and a structured reflection. Deliberately imperfect — the tensions between these three are where the analysis gets interesting.
A validated trait inventory. Shown as relative standing, not a score to optimize.
Patterns drawn from ~9 months of real working sessions with an AI — not self-report, but observed behavior in how he actually reasons, writes, and decides.
A few representative moments, in Jordan's own words from the working sessions:
"Before we touch the roadmap, I want to know who actually owns this decision. Half our churn is because Product and Eng think they're each waiting on the other."
→ Frames problems as operating-model failures before feature gaps
"Don't give me the bullet summary. I want to see why each conclusion follows from the last — if I can't trace the reasoning I don't trust the recommendation."
→ Argument-driven; low tolerance for unsupported conclusions
"I think we should hold the current direction one more cycle. I know the data's pointing the other way, but I already told the leadership team we were committed."
→ A gap between when the reasoning resolves and when he commits — twice, after socializing
"I'll just rewrite this part myself, it's faster. The structure isn't quite where it needs to be."
→ Reclaims delegated work; edits cluster on quality standards, not trust
"Okay — that customer interview actually changes my read. Let me redo the prioritization."
→ Genuinely updates when shown specifics, though it tends to take a concrete trigger
Structured written responses to the reflection prompts. This is where Jordan interprets his own experience.
On a decision he'd revisit:
"I delayed sunsetting a feature for a quarter because I'd told three stakeholders we were committed. I knew earlier. I just didn't want to be the person who reversed course in public."
On being misunderstood:
"People sometimes read my directness as disapproval. Under time pressure especially — I get terse and skip the warmth, and it lands worse than I mean it to."
On how he works with his team:
"I'd describe myself as pretty collaborative. I bring the team into most decisions and I'm genuinely open to being wrong — I don't think people experience me as controlling."
On what he wants to build:
"I want a team that makes good independent decisions without me in the room. But honestly, I'm not sure I've built the conditions for that — I think I'm still the bottleneck."
The assessment says "Curious"; the corpus shows openness arrives slowly. The reflection names a desire to build independent decision-makers; the corpus shows him holding work close. Those gaps — not the agreements — are what the analysis pays attention to. See how they synthesize into a profile →
Signal Tensions — Jordan Reyes
Synthetic illustrative example. Leadership OS isn't looking for a clean, consistent picture. The gaps between how Jordan describes himself, how he appears to operate, and how he interprets his own experience are the most developmentally interesting part of the whole analysis.
| Area | Assessment says | Corpus shows | Reflection says | What the tension means |
|---|---|---|---|---|
| Delegation & control | Doesn't measure directly; high Persistent + Conceptual | Reclaims delegated work — "I'll just rewrite this part myself" | "I'm pretty collaborative… I don't think people experience me as controlling" | The sharpest gap. Jordan's self-story (collaborative, hands-off) doesn't match the observed pattern (holds work close). He half-sees it — he names the "bottleneck" worry himself — which makes this workable, not a blind spot. |
| Learning & openness | Elevated Curious / Openness | Updates genuinely, but usually needs a concrete trigger; three slow revisions | Frames himself as open to being wrong | Not a contradiction so much as a texture: the openness is real but reactive. He revises when shown specific evidence, less so from open-ended challenge. Useful to know how to actually move him. |
| Decision-making | High Deliberative + Persistent | Reasoning resolves days before he commits — twice, after socializing a direction | Names it directly: held a call because he'd "already told the leadership team" | All three converge here, which raises confidence: the delay isn't analysis, it's the social cost of visibly reversing. The clearest, best-supported developmental thread. |
| Communication | Lower Sociability | Precise, argument-driven, low small talk | "People read my directness as disapproval… under time pressure I skip the warmth" | Assessment and corpus agree on the style; the reflection adds the missing piece — Jordan knows the cost and when it spikes. Awareness is present, so this is a calibration issue, not a discovery. |
| Adaptability | High Adaptable, notably lower Agile | Adjusts thoughtfully but not quickly; two slow product pivots | Doesn't address directly | Assessment and corpus align, reflection is silent — so this is held as a quieter hypothesis. Jordan adapts well given time; speed under ambiguity is the open question worth watching. |
| Influence & identity | Doesn't measure | Builds authority through structure and traceable reasoning | Aspires to develop independent decision-makers | An aspiration ahead of the evidence. Jordan wants to build independent operators, but the corpus doesn't yet show him creating the room for it. Held as "Emerging" — a direction, not a finding. |
A personality test would flatten these into scores. Leadership OS keeps the disagreements visible on purpose — they're where a coach would actually start. The strongest developmental priority (post-commitment anchoring) is the one where all three inputs converge; the most human one (delegation) is where they pull apart. See how these become a development plan →
Analyst Workspace — Jordan Reyes
Synthetic illustrative example. A demonstration artifact showing how the analysis weighs, converges, and holds back — not the prompts that produce it, but the logic they enforce.
Confidence tracks how many of the three inputs point the same way — never how strong any single one is. One vivid corpus moment doesn't earn "High." Convergence does.
All three inputs converge. Decision Style — assessment (Deliberative), corpus (delayed commitment), and reflection (names it outright) all agree.
Two inputs align, one is silent or mixed. Communication — assessment and corpus agree on style; reflection adds nuance but doesn't contradict.
Mostly one input, usually an aspiration. Leadership Identity — reflection states a goal the corpus doesn't yet show. Held as a direction.
Inputs can't speak to it. Reported as a gap, not guessed. The analysis is allowed — required — to say "not enough here."
Tracing Decision Style from raw input to the conclusion that became the #1 development priority:
Deliberative 88th, Persistent 82nd — thorough, and resistant to revising once set.
"I know the data's pointing the other way, but I already told the leadership team we were committed." Pattern recurs across two decisions.
"I delayed sunsetting a feature… I knew earlier. I just didn't want to be the person who reversed course in public."
All three point the same way. The mechanism isn't slow analysis — it's the social cost of visibly reversing after socializing. Confidence: High.
Development Roadmap, Priority 1: "Post-commitment anchoring." Recommendation targets the mechanism (separate the decision from the audience), not the symptom ("decide faster").
Two examples of restraint — places a less disciplined read would have overclaimed:
- Self-Awareness stayed Moderate, not High. Jordan is articulate and reflective, which is easy to mistake for deep self-knowledge. But articulateness isn't self-awareness — and the delegation gap shows a real blind spot. The fluency was explicitly not allowed to inflate the rating.
- Adaptability was held as a quiet hypothesis. Assessment and corpus agreed, but the reflection never addressed it. Rather than infer, the analysis flagged it as worth watching and moved on.
Every conclusion in the participant-facing documents traces back through a chain like the one above. Nothing is asserted that can't be walked back to a specific input. See the full traceability methodology →
Leadership Profile — Jordan Reyes
Synthetic illustrative example. The Leadership Profile is the private construct synthesis the AI builds before generating output documents.
Reflection Orientation
HighHow deliberately a leader examines their own experience and draws developmental insight from it.
Systems Orientation
HighThe tendency to frame problems as structures and root causes rather than isolated events.
Learning Orientation
ModerateOpenness to revising a position when new information arrives.
Decision Style
HighHow a leader gathers input, weighs it, and commits.
Communication Patterns
ModerateHow a leader's intent translates into how others actually experience them.
Leadership Identity
Emerging HypothesisThe leader a person is actively trying to become, and whether their behavior is moving toward it.
Adaptability
ModerateHow readily a leader adjusts course as conditions change.
Self-Awareness
ModerateThe accuracy of a leader's read on their own impact — not how articulate they are about it.
Development Readiness
ModerateHow prepared a leader is to act on developmental insight — inferred, not assumed from participation.
Jordan's synthetic profile suggests a leader who operates through systems framing, structured communication, and strong analytical investment in product decisions. Highest-confidence patterns: structural diagnosis before intervention, broad information-gathering before commitment, and a communication gap between the precision Jordan intends and the impatience others sometimes experience.
Most generative development territory: the intersection of post-commitment anchoring in decisions and the Leadership Identity gap between stated aspiration and observed behavioral emphasis. These may be related — a leader who anchors to product hypotheses may similarly anchor to a leadership model that doesn't yet include the relational behaviors the identity aspires to.
Insufficient signal for confident hypothesis: Leadership Identity requires more relational behavioral data. Communication under verbal and high-stakes conditions unobservable from written corpus alone.
Leadership User Manual — Jordan Reyes
Excerpt — three of six sections. Full document is 3–4 pages, first person, designed to be shared with a manager, team member, or collaborator.
I think in structures. My first instinct when encountering a product problem is to look for the operating model failure before I look at the feature gap. A roadmap that keeps churning usually isn't a prioritization problem — it's a signal that decision rights between Product, Engineering, and the business aren't clear enough to hold.
I form hypotheses quickly and commit to them with energy. This helps me move a team toward a direction when ambiguity is high. It creates friction when the hypothesis is wrong and I've already aligned people to it. I'm working on naming hypotheses explicitly before socializing them.
Post-commitment anchoring. Once I've socialized a product direction, I revise reluctantly. The cost of reversal feels higher than it actually is. The practice I'm building: label a direction as a hypothesis with an explicit confidence level before sharing it, so revision later reads as scientific process rather than failure.
Cross-functional communication gap. I write and present in complete, structured arguments. Partners in Sales and CS have told me this reads as impatience. I experience it as efficiency. I'm working on making space for partial thinking earlier in a conversation.
"Does this roadmap reflect what customers actually need, or what we find technically interesting?" I use this to interrupt the pull toward elegant architecture over useful product.
"Who needs to make this decision, and am I helping them make it or making it for them?" I apply this when I've been the decision-maker on something that should have been someone else's call to build.
"What would have to be true for this hypothesis to be wrong — and have I actually checked?" This is the question I'm trying to ask before committing to a direction, not after.
Working-With-Me Guide — Jordan Reyes
Synthetic illustrative example. Full document. Readable in under 3 minutes.
AI Calibration Document — Jordan Reyes
Synthetic illustrative example. Full document. Paste at the start of any new AI conversation.
"Does this roadmap reflect what customers actually need, or what we find technically interesting?" Apply this when evaluating product options, framing tradeoffs, or assessing whether a direction is input-led. I'm more interested in what the data shows than in confirming a direction I've already taken.
Development Roadmap — Jordan Reyes
Synthetic illustrative example. Private — not for sharing. Excerpt: two priorities and 90-day focus. Demonstrates current traceability format.
Development priority: Post-commitment anchoring — the suppression of input-based revision after a product direction has been socialized with stakeholders.
Originating constructs: Decision Style (High Confidence) · Learning Orientation (Moderate Confidence)
Confidence: High — convergent across all three inputs.
Input basis
Assessment: Elevated Deliberative and Persistent indicators suggest both thorough information-gathering and resistance to revision after commitment.
Corpus: Three instances of maintaining a product hypothesis after contradictory customer feedback emerged; commitment held past the point where the signals had shifted.
Reflection: The "decision I'd make differently" response names the mechanism directly — holding a roadmap prioritization after engineers flagged structural risks, attributing it to sunk-cost reasoning.
Theoretical framing: Argyris — espoused vs. enacted theory gap. Jordan espouses input-based decision-making; behavioral signals reveals a theory-in-use where social commitment suppresses updating. Mezirow — the assumption beneath the pattern is that revision signals failure rather than learning. Naming hypotheses explicitly before socialization disrupts this assumption.
Mechanism: Socializing a product direction converts a working hypothesis into a social commitment — before the input is complete. The subsequent revision cost (perceived loss of credibility) suppresses updating even when the input warrants it.
Condition: Any product direction shared with the broader team or leadership before supporting input is fully assembled.
Practice: Before socializing any direction, designate it explicitly as a hypothesis with a stated confidence level and a named update condition: "I think X — I'm at 65% confidence, and I'd revise if we saw Y." This makes later revision feel like scientific process rather than leadership failure.
Question for reflection: Before I share this direction — is it a hypothesis or a commitment? What would have to be true for this to be wrong, and have I checked?
Development priority: Relational investment gap — high analytical investment in product leadership with thin behavioral investment in the relational and developmental dimensions of the leadership identity Jordan describes aspiring to.
Originating constructs: Leadership Identity (Emerging Hypothesis) · Communication Patterns (Moderate Confidence)
Confidence: Moderate — strong from corpus; limited reflection input about relational contexts specifically.
Input basis
Assessment: PrinciplesYou profile suggests engagement and person-orientation as traits; behavioral investment in relational development is not confirmed.
Corpus: High frequency of analytical and structural engagement; relational investment (developmental conversations, explicit career discussions, interpersonal checking-in) appears infrequently.
Reflection: States aspiration to develop independent decision-makers; does not describe specific relational practices that would enact this.
Theoretical framing: Kegan — subject-object gap. The stated leadership identity (developer of people) is espoused but not yet object — Jordan is still subject to the dominant mode (analytical investment), which makes it hard to see or change. Ibarra — identity transitions require behavioral experimentation before the new identity solidifies. The practice below is an identity experiment, not just a behavior change.
Mechanism: The default engagement mode is work-first. This is efficient and often appropriate. It becomes a development edge in contexts where a direct report needs to be seen as a person before they can engage productively on the work — which is more frequent than the current pattern accounts for.
Condition: 1:1 meetings, especially when a direct report has given a quiet signal that something is off. The work frame is typically active before the conversation starts.
Practice: In the first two minutes of every 1:1, no agenda. The only question is some version of "how are you?" and the only constraint is not immediately redirecting toward the work. Small behavioral experiment; larger identity signal.
Question for reflection: In my last five 1:1s — did I lead with the work or with the person? What did I learn about each direct report that I wouldn't have known from the work deliverables alone?
Why this, not another priority: Post-commitment anchoring is well understood intellectually and has a named practice. The relational investment gap is more resistant to insight because it is invisible from inside the dominant analytical frame. The 90-day work is not adding a new skill; it is beginning to make the subject-object shift that would allow Jordan to see the gap at all.
Connection to intrinsic motivation: Jordan's stated leadership identity — developing independent decision-makers — is the intrinsic motivation already present. The 90-day work is closing the gap between what Jordan already cares about and what the behavioral signals shows Jordan actually invests in. This is the kind of development that sustains because it resolves internal contradiction rather than adding external obligation.
The specific action: Before the 90-day period ends: identify one direct report who appears to be operating below their potential ceiling and initiate an explicit development conversation — not about their current sprint, but about where they want to be in 18 months and what Jordan could do to support that trajectory. The goal is not the outcome of the conversation. The goal is building the cognitive and relational habit of having it.
What success looks like: Not a behavior count. A shift in what Jordan notices in 1:1 conversations — from deliverable status to the person's experience of the work. That shift in noticing is the leading indicator that the identity experiment is working.