Design thinking front-end
Turn messy feedback into an evidence-backed product thesis before writing epics or tickets.
1. Discover
2. Synthesize
3. Theme
4. Epic
5. Story/Card
Build
Inputs
Customer and stakeholder feedback
Meetings / transcripts / files
AssetPro feedback: bandwidth
Kenco: 4,328 active assets
Phoenix: 5,269 active assets
Themes
Outcome-oriented problem areas
HW-T1
Useful, reliable
hardware capability
Field evidence before device roadmap
WB-T1
Trusted AssetPro
context in 3PM
Source-backed, permissioned data
WB-T2
Fleet-manager
decision workbench
One workflow, next human decision
AP-T1
Dependable AssetPro foundations
Scale, bandwidth, reliability, quality
Epics
Bodies of work under each theme
HW-E1 Inventory devices + firmware
HW-E2 Field problems + support needs
WB-E1 Inspect AssetPro read contract
WB-E2 Define approved context slice
WB-E3 Verify boundaries + failures
WB-E4 Select first manager workflow
WB-E5 Prototype decision view
AP-E1 Current-state inventory
AP-E2 Volume + bandwidth validation
Stories / Cards
Two-week sprint handoff tasks
HW-C1 Build installed inventory source list + gaps
HW-C2 Choose one field test candidate
WB01-C1 Agree read contract and source owner
WB01-C2 Connect read-only context slice
WB01-C3 Test denied/stale/ unavailable states
WB02-C1 Select first fleet manager workflow
WB02-C2 Wireframe dashboard decision view
AP01-C1 Inventory current state + usage
AP01-C2 Validate Kenco/ Phoenix-scale behavior
Governance rule:
Every story/card must trace back to a theme, epic, PRD acceptance criterion, and required test evidence before developer handoff.
1. Themes before epics Themes are customer/business problems. They prevent the roadmap from becoming a random list of features or tickets.
2. Epics before stories Epics group meaningful bodies of work under each theme and identify dependencies before Dev cards are written.
3. Stories as handoff Stories/cards are the solution-architect handoff layer: scoped, testable, and linked to PRD acceptance criteria.