Roadmap Contributions
Engineering roadmap input translates Rust reality into planning language: edition cliffs, reliability investments, and platform work that unlocks product bets. A quarterly one-pager beats surprise "we need a month for toolchain" mid-quarter.
Recipe
Quick-reference recipe card - copy-paste ready.
# Engineering input Q3 (orders platform)
## Outcomes we enable
- EU launch (GDPR export path, audit logging)
- 99.9% checkout SLO (pool + tracing investment)
## Investments requested (20% capacity)
1. sqlx migration expand phase - blocks EU schema
2. cargo-vet + SBOM - enterprise deal #442
3. Worker/API deploy coupling automation - CFR reduction
## Defer with trigger
- Workspace split into 5 binaries - revisit when team >= 12
## Risks if ignored
- Edition 2024 drift blocks hiring playbook
- INC-9011 recurrence on pool configWhen to reach for this:
- Quarterly business planning
- Annual product strategy offsite
- Executive asks "what does eng need?"
- Competing launches vs reliability
Working Example
| Roadmap row (product language) | Engineering work | Size |
|--------------------------------|------------------|------|
| Faster invoice export | Polars lazy pipeline + worker memory caps | M |
| Enterprise security questionnaire | cargo-audit, vet, SBOM in CI | S |
| Reduce checkout incidents | sqlx pool alerts + runbook (post INC-8812) | S |PM owns priority order; engineering owns feasibility and dependency links.
Deep Dive
One-Pager Sections
- Outcomes - What product goals engineering enables.
- Investments - Platform/debt with capacity ask.
- Risks - Incidents, EOL, compliance deadlines.
- Dependencies - DBA, security, other squads.
- Deferred - With numeric revisit trigger.
Data to Bring
DORA trends, top incidents, support themes, security audit gaps, compile CI duration, hiring/onboarding friction.
Collaboration Rhythm
- Week -3: draft one-pager
- Week -2: PM negotiation on capacity
- Week -1: exec summary slide if needed
- Mid-quarter: adjust if launch slips or incident changes priorities
Gotchas
- Jargon roadmap - "Tokio refactor" means nothing to exec. Fix: "Reduce checkout outage minutes."
- No capacity ask - Items never scheduled. Fix: Percentage or sprint count explicit.
- Surprise EOL - Fix: Edition/MSRV on roadmap 2 quarters ahead.
- Everything P0 - Fix: PM ranks; engineering flags impossible combos.
- Ignoring product dates - Fix: Propose scope cut, not silent slip.
Alternatives
| Alternative | Use When | Don't Use When |
|---|---|---|
| OKRs linking eng KPIs | Mature planning | Team <5 without OKR culture |
| Tech radar slide | Educate leadership on Rust ecosystem | Sole planning artifact |
| RFC portfolio review | Many parallel migrations | Simple single-service squad |
| Joint eng/product roadmap doc | Strong partnership | Weak PM engagement |
FAQs
How much detail for exec?
Three bullets: outcome, risk $, capacity % - appendix for engineers.
Who presents?
EM + tech lead together; PM owns business priority narrative.
Roadmap vs backlog?
Roadmap themes; backlog tickets execute - link each theme to epics.
Mid-quarter reprioritize?
Yes with trade-off explicit: what drops if new item enters.
Multi-team Rust platform?
Central platform roadmap + squad overlays for product-specific work.
Include hiring plan?
Yes if Rust hiring is bottleneck for roadmap commitments.
Customer commitments on roadmap?
Flag as fixed-date; engineering marks dependency risks early.
Open source maintenance?
Include if product depends on crate releases; security tie-in.
Measure roadmap accuracy?
Compare planned vs delivered outcomes quarterly; not story points vanity.
Decline roadmap item?
Feasibility veto with alternatives and dates - document in one-pager.
Related
- Prioritizing Platform & Tech Debt - debt framing
- Stakeholder Communication - exec updates
- DORA Metrics - evidence
- Edition & Toolchain Upgrades - cliffs
- Technical Decision-Making - options
Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.