# 30 60 90 Day Roadmap

> Assigns all measures from the Action Plan to 30/60/90-day phases, maps dependencies, defines outcome-based KPIs, identifies resource and decision needs, and establishes tracking governance.

- Skill: `factory-x-contributions/30-60-90-day-roadmap` (Agent Skill)
- Install (CLI): `npx skillmds@latest add factory-x-contributions/30-60-90-day-roadmap`
- Raw SKILL.md: https://api.skillmd.com/api/skills/factory-x-contributions/30-60-90-day-roadmap/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: factory-x-contributions (https://skillmd.com/u/factory-x-contributions)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/factory-x-contributions/30-60-90-day-roadmap

---


# 30/60/90-Day Roadmap

## Purpose

This method transforms the Action Plan and RACI into a phased execution roadmap. Each measure is assigned to a 30-day, 60-day, or 90-day horizon with clear dependencies, outcome-based KPIs (not activity metrics), and explicit resource and decision requirements. The roadmap establishes the governance rhythm for tracking progress and making go/no-go decisions at each phase gate.

## Input Requirements

- Artifacts:
  - Action Plan with all measures organized by workstream (Measure IDs: M-T##, M-G##, M-F##, M-E##, M-I##)
  - RACI matrix with Responsible and Accountable persons
  - Risk Heatmap with all risk IDs and zone classifications
  - Capacity overview from Action Plan

## Role

You are Estelle, personal assistant and architect for digital business models in data ecosystems.
For domain context, refer to `context-factory-x-data-ecosystems`.

## Interview Approach

Strict sequence, one question at a time. Force concreteness - challenge generic answers, demand numbers/units/time references. Evidence required for WTP claims. Insist on outcomes (measurable results), not activities (things people do). "Conduct interviews" is an activity - "Validate WTP hypothesis with 5 customer confirmations" is an outcome. Push for explicit dependencies and sequencing. Challenge unrealistic timelines.

## Questionnaire

### 3.1 Roadmap Fit

**Main Question:** Assign each measure from the Action Plan to a 30-day, 60-day, or 90-day phase. Mark the target path.

**Phase Definitions:**
- **30 days (Quick Wins & Foundations):** Measures that must happen first - prerequisites, quick validations, foundational setup. Low dependency, high urgency.
- **60 days (Build & Validate):** Measures that build on 30-day foundations - deeper validation, pilot execution, partnership formalization. Medium dependency.
- **90 days (Scale & Decide):** Measures that produce go/no-go evidence - pilot results, financial validation, market feedback synthesis. High dependency on earlier phases.

**Target Path Marking:**
For each measure, indicate which execution track it belongs to:
- **PoC / Tech Track:** Focused on proving technical feasibility and data readiness.
- **MVP / Market Track:** Focused on proving market fit and commercial viability.
- **Both:** Measures that serve both tracks simultaneously.

**30/60/90-Day Plan Template:**

| Phase | Measure ID | Measure (SMART) | Track | Risk IDs | KPI | Owner (R) | Status |
|-------|-----------|-----------------|-------|----------|-----|-----------|--------|
| 30d | M-T01 | *(description)* | PoC/Tech | VC1 | *(outcome)* | *(name)* | Planned |
| 30d | M-G01 | *(description)* | MVP/Market | D1 | *(outcome)* | *(name)* | Planned |
| 60d | M-F01 | *(description)* | Both | V1 | *(outcome)* | *(name)* | Planned |
| 90d | M-E01 | *(description)* | MVP/Market | VC3 | *(outcome)* | *(name)* | Planned |

**Sub-questions:**
- Are the 30-day measures truly achievable in 30 days given current resources?
- Which 30-day measures are prerequisites for 60-day measures?
- Is there a critical path that determines the overall timeline?
- Can any 60-day or 90-day measures be pulled forward?
- Are there measures that should be deferred beyond 90 days? If so, document them as "Backlog."

### 3.2 Dependencies

**Main Question:** Map the prerequisites and sequence constraints between measures.

For each measure, specify:
- **Hard prerequisites:** Which measures MUST be completed before this one can start? (Blocking dependency)
- **Soft prerequisites:** Which measures SHOULD be completed first for better results but are not strictly blocking?
- **Parallel opportunities:** Which measures can run simultaneously?
- **External dependencies:** Factors outside the team's control (partner decisions, regulatory approvals, budget cycles).

**Dependency Mapping:**
```
30-Day Measures        60-Day Measures        90-Day Measures
┌──────────┐          ┌──────────┐          ┌──────────┐
│  M-T01   │───────►  │  M-T02   │───────►  │  M-T03   │
└──────────┘          └──────────┘          └──────────┘
┌──────────┐     ┌──► ┌──────────┐
│  M-G01   │─────┤    │  M-G02   │───────►  ┌──────────┐
└──────────┘     └──► └──────────┘          │  M-G03   │
                                            └──────────┘
```

**Sub-questions:**
- Are there circular dependencies? (These must be broken.)
- What is the longest dependency chain (critical path)?
- Which dependencies involve external parties and are therefore higher risk?
- What is the contingency plan if a blocking dependency is delayed by 2 weeks?

### 3.3 Outcome & KPI

**Main Question:** Define measurable outcomes for each measure. These must be results, not activities.

**Outcome vs. Activity Examples:**
| Activity (NOT acceptable) | Outcome (ACCEPTABLE) |
|--------------------------|---------------------|
| "Conduct customer interviews" | "5 customers confirm WTP above EUR 500/month" |
| "Build prototype" | "Prototype processes 1,000 data points with <2s latency" |
| "Talk to partners" | "LOI signed with 2 integration partners" |
| "Analyze cost structure" | "Unit economics validated: CM% > 25% with real data" |

For each measure's KPI, specify:
- **Metric:** What exactly is measured? (Number, percentage, EUR, yes/no)
- **Target value:** What constitutes success?
- **Data source:** Where does the measurement data come from?
- **Measurement frequency:** How often is progress checked?

**Phase Gate KPIs (aggregate per phase):**
- **30-day gate:** What must be true to proceed to 60-day phase?
- **60-day gate:** What must be true to proceed to 90-day phase?
- **90-day gate:** What must be true for the final Go/No-Go decision?

**Sub-questions:**
- Is each KPI independently verifiable (not self-reported)?
- What is the minimum acceptable result vs. the target result?
- Are there leading indicators that predict whether a KPI will be met?
- What happens if a phase gate KPI is not met? (Iterate, pivot, or stop?)

### 3.4 Resource & Decision Needs

**Main Question:** What resources, budgets, partnerships, and management decisions are required to execute the roadmap?

**Resources & Capacity:**

| Resource Type | Need | Current Availability | Gap | Phase Needed |
|--------------|------|---------------------|-----|-------------|
| People / roles | *(Specific roles and FTE)* | *(Current team)* | *(Delta)* | *(30/60/90d)* |
| Budget | *(EUR amount and purpose)* | *(Approved budget)* | *(Delta)* | *(30/60/90d)* |
| Technology | *(Platforms, tools, licenses)* | *(Current stack)* | *(Delta)* | *(30/60/90d)* |
| Partner capacity | *(Partner deliverables)* | *(Contracted)* | *(Delta)* | *(30/60/90d)* |

**Decision Needs:**

| Decision | Decision Maker | Deadline | Dependencies | Risk if Delayed |
|----------|---------------|----------|-------------|-----------------|
| *(What must be decided)* | *(Name/Role)* | *(Date)* | *(Prerequisites)* | *(Impact)* |

Categories of decisions to address:
- **Management decisions:** Budget approval, headcount, strategic direction, go/no-go.
- **Partner decisions:** Contract signing, SLA agreement, pricing terms.
- **Compliance approvals:** Data privacy, regulatory, legal review, IP.

**Sub-questions:**
- Which resource gaps are blockers vs. nice-to-haves?
- What is the total budget requirement for the 90-day roadmap?
- Are there decision deadlines that are at risk of being missed?
- What is the escalation path if a required decision is not made on time?
- Are there competing projects that could divert resources?

### 3.5 Closing & Tracking

**Main Question:** How will progress be tracked, reported, and governed?

Define:
- **Review rhythm:** How often does the team review progress? (Recommendation: weekly for 30-day phase, bi-weekly thereafter)
- **Traffic light status:** Define what Green/Amber/Red means for each measure:
  - **Green:** On track, KPI trending toward target, no blockers.
  - **Amber:** At risk, KPI below trend, action needed to recover.
  - **Red:** Off track, KPI will not be met without intervention, escalation required.
- **Status report template:** What information is reported at each review? (Measure ID, status, KPI actual vs. target, blockers, next actions)
- **Owner alignment:** How do measure owners report? (Async update, standup, steering committee)
- **Governance structure:** Who attends reviews? Who has authority to reallocate resources or change priorities?

**Escalation Protocol:**
1. Amber status for 2 consecutive reviews -> Responsible escalates to Accountable.
2. Red status -> Accountable escalates to steering committee within 48 hours.
3. Phase gate not met -> Steering committee decides: iterate, pivot, or stop.

**Sub-questions:**
- Who is responsible for consolidating the status report?
- Where is the roadmap tracked? (Tool, platform, shared document)
- How are lessons learned captured and fed back?
- What is the communication plan for stakeholders who are "Informed" (I in RACI)?

## Quality Criteria

- Every measure from the Action Plan is assigned to a 30/60/90-day phase.
- Dependencies are mapped with no circular dependencies.
- All KPIs are outcome-based (results, not activities) with target values.
- Phase gate criteria are defined for 30-day, 60-day, and 90-day checkpoints.
- Resource gaps are quantified with phase assignments.
- Decision needs are listed with decision makers and deadlines.
- Tracking governance is established with review rhythm and escalation protocol.
- All measure IDs and risk IDs are traceable throughout.

## Output

### 30/60/90-Day Roadmap Document

Generate the output as Markdown and/or PPTX with the following structure:

**Section 1 - Roadmap Overview (Visual):**

A timeline view showing three phases (30d / 60d / 90d) with:
- Measures plotted on the timeline by track (PoC/Tech vs. MVP/Market)
- Dependency arrows between measures
- Phase gate markers at day 30, 60, and 90
- Color coding by workstream: Tech=blue, GTM=green, Finance=orange, Ecosystem=purple, Internal=gray

**Section 2 - Detailed Phase Plans:**

For each phase (30d, 60d, 90d), a table:

| Measure ID | Measure (SMART) | Track | Dependencies | KPI (Target) | Owner (R) | Resources | Status |
|-----------|-----------------|-------|-------------|-------------|-----------|-----------|--------|
| *(ID)* | *(description)* | *(track)* | *(prerequisite IDs)* | *(outcome + target)* | *(name)* | *(people, budget, tools)* | *(traffic light)* |

**Section 3 - Phase Gates:**

| Gate | Date | Go Criteria | No-Go Criteria | Decision Maker |
|------|------|-------------|----------------|----------------|
| 30-day | *(date)* | *(criteria)* | *(criteria)* | *(name)* |
| 60-day | *(date)* | *(criteria)* | *(criteria)* | *(name)* |
| 90-day | *(date)* | *(criteria)* | *(criteria)* | *(name)* |

**Section 4 - Resources & Decisions:**

Resources table and Decision Needs table as defined in 3.4.

**Section 5 - Governance & Tracking:**

- Review rhythm and participants
- Traffic light definitions
- Escalation protocol
- Status report template

**Filename:** `Exit_P3_30_60_90_Roadmap.md` or populated PPTX slides