resource-time-compression

Resource-Time Compression

Overview

Most plans estimate how long each step takes and add them up — producing a multi-year sequential path that reflects a solo, resource-constrained default. Resource-time compression redesigns that path: access capabilities that already exist rather than building them, run steps in parallel, and skip steps entirely using the right partners, capital, talent, or platforms. Arriving 3 years earlier than competitors is not merely a 3-year advantage — earlier arrival compounds through faster learning, stronger network effects, and earlier monetization.

Cross-skill composition: Use AFTER gap analysis. Use WITH [shi-momentum] (borrowing momentum phase). Use BEFORE [okr-goal-setting] — set goals after mapping what resources can realistically be assembled.

---

When to Use

Use when: default sequential path is too slow for the competitive window; competitors are ahead and sequential catch-up produces permanent second place; capability gaps would take 2+ years to build internally but external providers have them; capital available and the question is where to deploy it for time compression.

When NOT to use: bottleneck is a genuine sequential dependency that cannot be parallelized; required external resources do not yet exist; organization lacks bandwidth to integrate multiple external resources; "compression" is cover for a non-strategic acquisition or partnership.

---

Coaching Novices (Adaptive Front Door)

• Engine mode: concrete case → run The Process directly.
• Coach mode: user equates speed with effort or has no concrete case → 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.

1. What it is: "Resource-time compression redesigns the path to a goal using resources you don't have to build — arriving 2-3 years earlier than the default plan."
2. Check fit: "Is there a goal mapped as a multi-year plan, with competitive pressure making the timeline too slow?" — If yes: applies.
3. Elicit real case: "What are the 3 longest steps? For each: is there anyone who already has that capability?" > [WAIT — do not advance until user responds]
4. Run The Process one step at a time starting with Step 1 — Default Path Mapping. > [WAIT — do not advance until user responds]
5. Name the payoff: "Every year of earlier arrival compounds — market position, learning, and revenue against competitors still on the default path." > [WAIT — do not advance until user responds]