Case Studies
Every engagement maps to one or more layers of the Viewpoint Stack™ — the framework I use to design organizations the way you'd design a product. Each case study below shows the layer it primarily addressed and the sublayer that produced the result.
$27M contracted in four months.
From PMF pressure to new revenue by building a repeatable delivery operating model and the cadence to run it across five clients in parallel.
Read Case Study →10-hour decision → 1-hour self-service workflow.
Built a feature catalog with role-specific views and decision rights so Sales and Service Delivery could search, configure, and price features themselves — without looping in Product.
Read Case Study →100% alignment on strategy for the first time.
A 3-day facilitated off-site that moved a fractured cross-functional team from competing priorities to a shared diagnosis, prioritized opportunities, and clear ownership.
Read Case Study →Three 2026 Outcomes. One shared direction.
Facilitated a post-layoff leadership team through 2026 strategic planning — from refined Mission and 5-year Vision down to a clear accountability model that connects annual goals to weekly execution.
Read Case Study →Project cycle time cut from 14 days to 6.
Diagnosed the real cycle-time friction with team brainstorms and a Value Stream Map, piloted a "pull" system on the biggest waste source first, then scaled VFQ + cross-functional squads across Product Design — cycle time cut nearly in half without changing the team.
Read Case Study →New engagement writeups are in progress. If you'd like to see work at a particular layer of the stack — Vision, Alignment, Clarity, or Infrastructure — let's talk.
Ask About Relevant Work →Outcomes are measured against business-critical baselines: revenue conversion, cycle-time reduction, delivery predictability, and operating capacity. Each engagement defines explicit before-and-after conditions so impact can be traced to intervention choices.
They are both. The work starts with strategic clarity and then moves into operating mechanics: role architecture, governance, process design, and team execution cadence. Strategy is treated as a system design problem, not a slide deck output.
Growth-stage organizations scaling quickly, cross-functional teams with high dependency risk, and leadership groups trying to convert product or AI potential into repeatable delivery outcomes.