CEDX Roadmap · Projects & Delivery
Roadmap holds the whole portfolio — 320 initiatives, 238 active, 1,608 eng-months of open effort — and grades it: 87 initiatives at high slip risk, a portfolio health of 33, and the worst offender named with its lag in percentage points.
The healthiest number on the Overview is the one most tools hide: 106 initiatives at risk or off track, above the 4-week portfolio median. A roadmap that cannot say that sentence is a poster.
Runs on demo data — the portfolio office and every initiative key in the captures is the seeded demo set.
What it is
Fifteen requests in seven days — eight from enterprise accounts — land in the inbox with the asker, segment and channel attached, then auto-cluster into seven themes. Ops efficiency holds four; each theme lists the initiatives it feeds.
320 initiatives as rows: horizon — Now, Next or Later — health, priority, progress, effort, value, theme, owner and target end on every one. The shipped rows stay in the ledger at 100%, so the portfolio has a memory.
Q2–Q4 2026, bar = target window, and the screen admits its own limit: 40 bars shown of 211 after filters — “cap 40 for density.” Progress sits at the end of each bar, and the at-risk count of 67 is a filter, not a footnote.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/roadmap.
01 — Overview
238 active, 89 in the now horizon, 106 at risk or off track — 30 of them blocked. The health ring reads 33 and the alerts explain it: one initiative slipping at 95% with a 48-point lag, ten teams over 100% capacity, and two P0s near ship with progress ≥ 74%.
02 — Insights
The inbox: scanners that double-scan on dock reconnect, quotes drifting by cents on EU reverse charge, an audit pack blocking a procurement. Each request maps to a theme, and each theme to the initiatives that would answer it — linked clusters currently zero, feeding value scores, shown honestly.
03 — Initiatives
The ledger is the portfolio's double-entry book: horizon, health, priority and progress against effort and value. An initiative at 100% progress with effort 9 and value 78 shipped; one at effort 12 and value 40 is a different argument — and the table lets you have it.
04 — Timeline
The Gantt-like view caps itself: top 40 of 211 bars for density, with at-risk and now-horizon as filters. Bars read as target windows, progress at the right edge — and the two red bars are the initiatives the overview is already alerting on.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the Now / Next / Later calls and can defend each one with effort, value and the requests behind the theme — not with seniority.
now horizon · 89
Reads the slip board: 87 initiatives at ≥55% slip risk and ten teams over capacity is a staffing and sequencing conversation, held early.
high slip · 87
Runs the request inbox: fifteen a week, clustered into themes, linked to initiatives so the value score has evidence under it.
requests · 15 / 7 daysThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Requests land from support, sales and customer channels with segment attached, and cluster into themes — seven this week — instead of dying in an inbox.
An initiative is written with effort and value. The themes feed the value side, so the score traces back to what the field asked for.
Horizon is a decision: Now, Next or Later, with 89 currently in flight. The ledger keeps the argument — effort 12, value 40 — on the row.
Delivery grades the plan: progress against target window, slip risk, lag in points. The overview reads 33 because the portfolio earned 33.
One record
A roadmap that floats above the tracker is fiction with good typography. Here the initiative's progress is computed from the work below it.
The epics on the delivery roadmap are initiatives on the portfolio ledger — same bars, read at portfolio altitude.
CEDX SprintsSlip is manufactured one carry at a time; the sprint's carry-out is what the initiative's lag in points is made of.
CEDX Resourcing“10 teams over 100% capacity” is the roadmap reading the resourcing grid — the alert names the practices.
CEDX FeedbackThe request inbox is where feedback becomes evidence: fifteen asks a week, clustered, and tied to the initiatives that answer them.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your portfolio, your themes
Roadmap with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/roadmap. It runs on demo data.
From the channels the field already uses — support, sales and customer success — each with the asker and segment attached. The demo inbox holds 15 from the last 7 days, 8 of them enterprise, clustered into 7 themes.
Per initiative, against its target window and progress: the top of the board reads 95% with a 48-point lag on a 10-month effort. 87 initiatives sit at ≥55%, and the score feeds the “Do this next” list weighted by value.
A risk-adjusted reading of the whole portfolio: 89 initiatives in the now horizon against a risk index of 75%. It is deliberately unflattering when the portfolio is over-committed — that is what it is for.
No, and it says so: the view caps at 40 bars for density out of 211 after filters, with now-horizon and at-risk as one-click filters. The ledger underneath always carries the full 320.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask what your own Now column would score.