About this Prototype
Goal: Test the new PMO ↔ Product ↔ Engineering process in a controlled 3-week pilot before locking it into Odoo. The prototype is a teaching aid — the real test is whether the team adopts the cadence.
Navigation
| Section | Use it for |
|---|---|
| Home (landing) | Pick your role — CS, PMO, PM, QA Lead, Conductor. Each opens a role-specific home. |
| Browse | Power-user drill-down. Lanes / Phases / All tickets with filters & search. |
| + New | Create a ticket. 5-step form with severity rubric. Drafts save in your browser only. |
| Triage | Standalone 4-dimension rubric tool — score a hypothetical item for tier & rollout. |
| About | You're here. |
Five Role Homes
| Role | Answers |
|---|---|
| 👋 CS Lead | What did I raise? What's shipping this week to brief clients on? What's at risk of escalation? |
| 📋 PMO | What did I raise? What's awaiting my input? What released this week? |
| 🎯 PM | Friday Decisions pending. This Tuesday's Dev Release. In rollout. Slipping items. |
| 🔬 QA Lead | Triage queue. Awaiting sign-off. Stability watch (3-strikes tracker). |
| 🎼 Conductor | System health — used by PM Lead, Eng Leadership, Head of Product, Sponsor. |
Anti-Rot Mechanisms
Tickets get visually flagged automatically so nothing falls through cracks:
- Traffic-light signal on every card: 🟢 on track, 🟡 attention (7+ days in same status or hot), 🔴 breaching (14+ days or past planned release).
- Age-in-status shown explicitly on every card (e.g. "3d in QA").
- Next-action sentence on every card — "Friday Decision pending", "QA sign-off needed by Tue".
- Browser tab counter:
(3) PMO Prototypewhen there are red-flagged items. - "Breaching" tile at the top of every role home — visually impossible to miss.
Source Documents
The Three Lanes
| Lane | For | Owner | Path |
|---|---|---|---|
| A PM-Routed | Features, enhancements, anything needing product judgment | PM | 3 phases (Planning → Dev Build → Rollout) |
| B QA-Routed | Defects against agreed spec, clearly fixable bug fixes | QA Lead | Triage → direct to Dev → Type 1 or 2 rollout |
| C Incident | P0 incidents only | Eng Lead | Mitigation → RCA → permanent fix back into A or B |
The Four Rollout Types
| # | Type | Use For | Time to Client | PM Effort |
|---|---|---|---|---|
| T1 | Direct | Single-client bug fix, P0 hotfix | Same day | 30 min |
| T2 | Notified | Cross-client bug, visible UX change | 1–2 days | 1–2 hours |
| T3 | Demoed | New feature, cross-client UX change | 3–5 days | Half day |
| T4 | Piloted | New module, breaking change, field-dependent | 1–3 weeks | 1–3 days |
Pilot Plan (3 Weeks)
Sponsor: Engineering Leadership
Scope: All product surfaces (LPA, TMS, VT, FleetRobo Core, WMS) with seed data covering 8 scenarios
- Week 0: Setup — visual dashboard live, sponsor + QA Lead aligned, kickoff with team
- Week 1: Soft launch — first QA triage Tuesday, first PM↔PMO sync, first Friday Decisions Day, Week 1 retro
- Week 2: Iterate — first Lane B item shipped end-to-end, first rollout-type-driven release, Week 2 retro
- Week 3: Scale decision — green light (migrate to Odoo) / yellow (SOP v2 + re-pilot) / red (rethink)
How to Update This Dashboard
The dashboard is a static site. To update:
- Edit
data/tickets.jsonin the workspace git add . && git commit -m "update tickets" && git push- Cloudflare Pages auto-deploys in ~30 seconds
No backend, no auth, no infra. Edit and refresh.