Strategic Map Framework - Value Drivers vs Internal Efficiency Separation
Situation
Established new H1 strategic planning framework that separates customer-facing Value Drivers from Internal Efficiency Drivers. Framework uses three lanes: middle lane for Value Drivers (the WHY), top lane for GTM activities, bottom lane for engineering deliverables. Also established phased estimation process: low-confidence ballpark dates first, then engineering-only session to raise confidence.
Reasoning
Engineers have scar tissue from being held to early, speculative dates - phased approach protects them while still giving leadership visibility. Conflating internal efficiency work (NARF, CVE automation) with customer value created confusion about what GTM can talk about. Board needs clear narrative, but engineering needs protected space to refine estimates. Separation enables two distinct stories: customer/board value narrative and engineering execution narrative.
Additional Context
Developed during LA Onsite Day 1 and refined in Impromptu Zoom Meeting. Team used Google Doc for rapid capture, Chris and Brady migrating to Miro. Dry run scheduled for department heads tomorrow at 9 AM. Board meeting is Tuesday.
People Involved
Source
reflection
AI Confidence
85%
Related Context
Sub-decision · Jan 16, 2026 · Resolved
fathom
The team adopted a Miro board to map the H1 roadmap, prioritizing the middle lane to define the why before detailing the how.
fathom
The map now separates value drivers (customer-facing) from internal efficiency drivers. This clarifies the why for all work, enabling distinct GTM and engineering narratives.
Outcome
Structure is the center of our release planning efforts now. Has brought a lot of clarity to how we plan work for the future.
Rating: 5/5
Decision ID: ae799985-9006-4f46-83fe-bbb5be952c1c