Tools · Startup & strategy
Prioritization Matrices
Drop in a task list (and roles) — get a validated RACI plus impact/effort priority grids and a sequenced plan.
How it works
Corpus-grounded matrices with a code safety net: the model drafts the RACI assignments and the Complexity-Impact / Action-Priority quadrant placements grounded in the decision/management canon, then code VALIDATES the RACI rules (exactly one Accountable per task; RAPID mode: exactly-one-Decide, veto-count and R-capacity failure-mode checks for a single decision; flags zero/multiple owners, the every-role-Responsible smell, and over-consultation) and RE-DERIVES every quadrant from effort/impact — so placements are checked, not trusted. Returns a quick-wins-first sequenced plan. Complements the EOS Accountability Chart (MF-176): RACI is task/decision-level responsibility; EOS seats are org-structure roles.
You bring
{ tasks?: string[], roles?: string[], decision?, mode?: raci|prioritization|rapid|both }
You get
{ mode, raci?{roles, rows[], validation[], valid}, rapid?{decision, assignments[], validation, valid, failure_modes[]}, prioritization?{action_priority[], complexity_impact[], sequenced_actions[]}, grounded_in, provenance }
Use it for
- →Messy backlog with no owners: tasks + roles → a rule-validated RACI (every task gets exactly one Accountable) + a sequenced plan
- →Decide what to do first: drop initiatives in → quick-wins / major-projects / fill-ins / thankless quadrants with a so-what order
- →Audit an existing RACI: paste it in → the validator flags the no-owner, two-owner, and everyone-Responsible smells
See it work
example outputTasks: a 5-item Q3 launch backlog (pricing page, data migration, SOC 2 evidence, onboarding emails, churn dashboard) across roles PM, Eng, Design, Marketing — mode: both.
Prioritization & Responsibility Matrices — Q3 launch backlog
Mode: both (RACI + prioritization) · RACI rules: PASS ✅
RACI
| Task | PM | Eng | Design | Marketing |
|---|---|---|---|---|
| Pricing-page redesign | A | C | R | C |
| Customer data migration | C | A/R | – | I |
| SOC 2 evidence collection | A | R | – | I |
| Onboarding email series | C | I | C | A/R |
| Churn dashboard | A | R | C | I |
A = Accountable · R = Responsible · C = Consulted · I = Informed
Validation (code, not the model): every task has exactly one Accountable. No no-owner rows, no two-owner rows, no every-role-Responsible smell. valid: true.
Action-Priority (effort × impact)
- Quick wins — Onboarding email series (low effort / high impact): activation lift for little build cost.
- Major projects — Customer data migration (high / high): unblocks the launch but it's the riskiest line.
- Major projects — Pricing-page redesign (high / high): revenue-facing; worth the effort.
- Fill-ins — Churn dashboard (low / low-ish): useful, not launch-blocking.
- Thankless — SOC 2 evidence collection (high effort / low near-term impact): mandatory, no glory — staff it but don't let it eat the sprint.
Quadrants were re-derived from effort/impact in code, so placements are checked, not trusted.
Sequenced plan (quick wins first)
- Ship the onboarding email series — fastest payback.
- Start the data migration now — longest pole, highest risk.
- Run pricing-page redesign in parallel.
- Slot SOC 2 evidence as steady background work toward the audit window.
- Stand up the churn dashboard once launch data is flowing.
Grounded in the decision/management canon. Complements an EOS Accountability Chart: RACI is task-level responsibility; EOS seats are org roles.
Run it now
Prioritize the work & assign ownership
Drop a list of tasks into an Action-Priority and Complexity-Impact matrix, get a quick-wins-first sequence, and (with roles) a rule-checked RACI matrix.
One per line.
Optional — add roles to also get a RACI matrix.
Prefer code? Call it over the API or hand it to your AI agent via MCP — POST /api/bicycle/prioritization-matrices · build_prioritization_matrices. API & agent access →