Founder Trajectory Matrix

Activate when: a founder says they're hitting a ceiling despite working harder; a founding team keeps fighting about who makes decisions; someone asks 'why do some founders progress faster than me?' or 'do I need a co-founder?'; a founder is moving from early stage to scaling and things that worked before are now breaking. Do NOT activate when: the real constraint is product-market fit, runway, or capital (use pmf-crossing-the-chasm or jobs-to-be-done instead); the founder has operated fewer than 6 months and lacks behavioral data to diagnose.

deciqAI@deciqai

Install

openclaw skills install @deciqai/founder-trajectory-matrix

Founder Trajectory Matrix

Overview

Founders diverge along two behavioral axes: (1) actively seeking mentors vs. relying on internal judgment, and (2) intellectual humility in receiving feedback. These axes predict trajectory ceiling more reliably than domain expertise, market timing, or capital. The matrix identifies five development paths — each with a failure mode, a plateau signal, and an upgrade move. All five paths have produced successful companies, but each creates blind spots that compound into structural stagnation if unaddressed.

Pairs with first-principles (strip founder narrative before running) and feedback-loops (instrument the upgrade move after). Combine with lean-startup to separate trajectory-level from execution-level questions.

When to Use

Concrete triggers: founder hits a growth ceiling that doesn't resolve despite executing harder; founding team has persistent conflict about decision-making authority; solo founder asks "do I need a co-founder?"; founder enters a new scaling phase (0→1, 1→10, 10→100) where prior approach now shows friction; investor/board notices a behavioral pattern the founder can't see; founder asks "why do peers progress faster with less effort?"

When NOT to use: market, PMF, or capital is the real constraint; goal is to assess team skill complement (use mece); founder is in acute crisis (runway < 60 days); fewer than 6 months of operating data.

Coaching Novices (Adaptive Front Door)

Engine mode: concrete case → run The Process directly. Coach mode: unfamiliar → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

One-line what-it-is: maps which of 5 founder development paths you're on and what one behavior change breaks your ceiling.
Check fit: at least 6 months operating data? Is the constraint behavioral, not market/capital?
Ask: "In the last 90 days, how many times did you change your mind on something important because of someone outside your team?" Capture before offering any framework language.

[WAIT — do not advance until user responds]

Introduce the two axes one at a time (mentor-seeking first, then humility). Ask the founder to place themselves on each using behavioral evidence. Run The Process one step at a time with their input.

[WAIT — do not advance until user responds]

Offer the trajectory name as a hypothesis. Anchor the upgrade move to one specific 30-day behavior change. Close by naming the insight they uncovered.

[WAIT — do not advance until user responds]

The Process

Stop-rule: if the founder already knows their trajectory and can articulate their ceiling, skip to Step 4.

Step 1 — Plot on two axes. X = Mentor-Seeking (Low→High), Y = Intellectual Humility (Low→High). Score 1–5 using behavioral evidence from last 90 days. Gate: need ≥3 concrete examples per axis.

Step 2 — Map to a trajectory.

Solo Executor (Low/Low): fast and convicted; ceiling = information bottleneck
Mentor-Seeker (High/High): builds wisdom infrastructure; risk = decision paralysis
Partner-Builder (High mentor-seeking → equity co-founder search): fills structural gaps; risk = warmth-over-complementarity mismatch
Humility-Grower (Low→High humility in progress): brittle under stress without maintenance systems
Network-Synthesizer (High + advisory equity structures): value from curated info flow; risk = networking crowds out building

Step 3 — Name the dominant failure mode (see table). You cannot design an upgrade move for a failure mode you haven't acknowledged.

Trajectory	Dominant Failure Mode	Upgrade Move
Solo Executor	Information bottleneck + key-person dependency	Identify one domain not top-20% → hire/partner within 60 days
Mentor-Seeker	Decision paralysis + advisor-pleasing	Decision filter: define in advance what evidence would change your mind
Partner-Builder	Co-founder mismatch + equity regret	90-day real-problem compatibility test before equity conversations
Humility-Grower	Stress-regression to old pattern	Weekly update log: one belief updated + what caused it; share with accountability partner
Network-Synthesizer	Activity substitution (networking replaces building)	70/30 rule: 70% internal building, 30% network-facing

Step 4 — Commit to the upgrade move. Must be behavioral (observable action), not attitudinal (internal resolve). Named person, named domain, named deadline.

Step 5 — Schedule a 90-day reassessment using the same behavioral evidence protocol. If no measurable behavior change, diagnose why before selecting a new move.

Output Template

→ Method in Action: Carnegie's Trajectory Shift from Solo Executor to Partner-Builder (1870s–1880s)

Founder Trajectory Packs

Domain-specific extensions adding behavioral signatures calibrated to a specific founder type. Existing packs: Technical Founder Pack (engineers-turned-founders who default to Solo Executor in product but Mentor-Seeker in commercial domains); Second-Time Founder Pack (prior success calcified a trajectory that worked in market A but fails in market B). Contribute: submit a PR to the deciqAI Knowledge Skills repo.

Applying It Well

Use behavioral evidence, not self-report — founders consistently misplace themselves on the humility axis.
Trajectory is not character — labeling it as a verdict blocks the upgrade conversation.
Stress reveals the default trajectory — design upgrade moves with stress-case protocols.
Upgrade moves have a 90-day half-life — install feedback-loops or the behavior decays.
Network-Synthesizer is the most socially legitimized failure mode — looks productive while starving the company of founder attention.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake Move	Reality
[D] "I'll bring in advisors when I have more to show them"	Advisors are most valuable before decisions are locked. Solo Executor delay tactic.
[D] "We align on vision, different styles is fine"	Style differences without a conflict resolution protocol create compounding debt.
[D] "I've heard this feedback before and disagree"	Consistent pattern-override is the strongest signal of a humility ceiling.
[D] "I'm selective about whose advice I take"	Without a stated criterion, "selectivity" is confirmation bias rationalized.
[D] "I need to move fast — no time for mentor conversations"	Solo Executors move fast in all domains, including those where they lack expertise.
[D] "We have a great advisory board"	Advisors without equity or consequence are structurally underincentivized.
[D] "My last company succeeded with this approach"	Prior success in a different market/stage is the anchor bias that makes the current plateau invisible.
[D] "Bringing in a co-founder now would dilute too much"	Dilution is financial. Trajectory ceiling is existential. Conflating them is a rationalization.
→ Add [O] entries here after each real use — paste the actual failure pattern	What went wrong and why

Red Flags / Verification

Red flags: founder names trajectory fluently but can't cite a behavioral example; upgrade move delegates to others with no change from the founder; 90-day reassessment is skipped; founder rates themselves 4–5 on humility but can't name the last time external input changed a major decision; advisory board is entirely the founder's existing social network.

Verify: both axes scored with ≥3 behavioral examples (not self-perception); trajectory label offered as hypothesis and confirmed by founder; dominant failure mode named by founder; upgrade move has named person + domain + deadline; 90-day reassessment scheduled; stop-rule applied if founder already knew their trajectory; diagnostic not run during acute crisis.

Part of deciqAI Knowledge Skills — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.