Leadership Profile — Jordan Reyes
Synthetic illustrative example. The Leadership Profile is the private construct synthesis the AI builds before generating output documents.
| Construct | Confidence | Evidence synthesis | Developmental implication |
|---|---|---|---|
Reflection Orientation |
High | All three synthetic sources suggest convergence. Assessment: elevated Curious and Growth-Seeking. Corpus: a high proportion of product strategy conversations involve Jordan examining their own reasoning — metacognitive language appears frequently. Reflection responses are specific, include acknowledged tension, and name mechanisms over outcomes. |
Reflective capacity appears available. Development work in other constructs is likely to compound here. |
Systems Orientation |
High | Assessment: elevated conceptual structure-seeking. Corpus: Jordan consistently frames problems in terms of upstream dependencies, decision rights, and operating model constraints before feature-level questions. Reflection: peak performance example describes a turnaround by diagnosing the cross-functional operating model before changing the roadmap. |
Reliable cognitive default. The development question is whether Jordan can translate structural analysis into simpler guidance for cross-functional partners who don't share this frame. |
Learning Orientation |
Moderate | Assessment: elevated Curious and Openness. Tension in corpus: three instances where Jordan maintained a product hypothesis after contradictory customer feedback emerged. Self-report diverges from behavioral patterns specifically at the post-commitment phase. |
Strong in the information-gathering phase. A hypothesis worth exploring: once a direction has been socialized, revision costs may suppress the learning orientation that was present earlier. |
Decision Style |
High | Assessment: elevated Deliberative and Persistent. Corpus: broad input-gathering before commitment, resistance to revision after. 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. |
The mechanism is the development edge: socializing a direction before evidence is complete may convert a hypothesis into a social commitment prematurely. |
Communication Patterns |
Moderate | Corpus: precise, argument-driven, low small talk. Reflection "misread": cross-functional partners interpret Jordan's directness as impatience. Jordan experiences it as efficiency. The gap between intent and impact is consistent across multiple described situations. Corpus captures written communication only. |
The adjustment is likely not "communicate less directly" but "signal more explicitly that ambiguity and partial thinking are welcome before the argument is formed." |
Leadership Identity |
Emerging | Reflection states aspiration: develop independent decision-makers. Corpus shows high analytical investment but thin relational and coaching investment. Gap between stated identity and observed behavior is the central hypothesis — not a judgment, but a question requiring more behavioral data. |
Worth holding as a question: are the behaviors that would reflect the stated identity actually present in Jordan's day-to-day practice? |
Adaptability |
Moderate | Assessment: high Adaptable, lower Agile. Corpus: two significant product pivots in 8 months — Jordan-initiated, suggesting genuine strategic adaptability. Tactical plan revision mid-execution appears rarer and harder. |
Strategic adaptability appears present. Tactical adaptability — revising a specific execution path after commitment — appears more constrained and consistent with the Decision Style pattern. |
Self-Awareness |
Moderate | Assessment and reflection broadly aligned. One hypothesis from corpus: a pattern of reduced pushback on recurring cross-functional friction over time — possible accommodation dynamic not named in reflection. Self-awareness appears genuine within domains Jordan monitors. |
Monitoring question worth building in: "Am I adjusting to this environment or improving it?" — applied to friction that has gone quiet rather than been resolved. |
Development Readiness |
Moderate | Inferred from reflection quality, not from completing this process alone. Supporting signals: specific responses that name mechanisms over outcomes; "decision I'd make differently" doesn't attribute difficulty to external factors; evidence that prior feedback changed how Jordan operates in 1:1 conversations. |
Readiness appears present for cognitive development. Less evidence for relational or identity development work — moderate rather than high for that reason. |
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 evidence 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 evidence-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.
The mechanism: Jordan's information-gathering phase is genuinely open. Once a direction has been socialized with stakeholders, updating it becomes socially costly — and that cost suppresses revision even when new evidence would warrant it.
The trigger: Socializing a product direction before supporting evidence is complete. This converts a hypothesis into a social commitment before it has earned that status.
The practice: Before socializing any direction, designate it explicitly as a hypothesis with a stated confidence level and named condition for updating. This makes later revision feel like scientific process rather than leadership failure.
The mechanism: Jordan's default engagement mode is work-first. This is often efficient. It becomes a friction point when a direct report needs to be seen as a person before they can engage productively on the work — which is more often than Jordan currently accounts for.
The trigger: 1:1 meetings, especially when a direct report has signaled something difficult is happening. Jordan tends to miss these signals because the work frame is already active.
The practice: First two minutes of every 1:1: no agenda. The only question is some version of "how are you?" and the only rule is not immediately redirecting toward the work.
The leadership identity gap. Post-commitment anchoring is well understood and has a named practice. The more important 90-day work is closing the gap between the leader Jordan describes wanting to be and the leader the evidence suggests Jordan currently is.
The specific practice: identify one direct report operating below their ceiling and have an explicit development conversation — not about their current sprint, but about where they want to be in 18 months. Complete this before the 90-day period ends. The goal is building the habit of having it.