Results for “process-over-outcome”

Translates stakeholder feature requests into validated outcome statements before any work is committed. Use this skill — proactively and without waiting to be asked — whenever a stakeholder, exec, or customer arrives with a pre-packaged solution: "we need a dashboard", "add a Slack notification", "build an export feature", "create a report", "let's add a filter", "can we just add X". Also triggers for: "how do I push back on this request", "what outcome does this feature solve", "outcome vs output", "outcomes not features", "what are we really trying to achieve", "we're being a feature factory", "I need to reframe this as a problem", "the stakeholder is pushing a specific solution", "discovery before delivery", "assumption testing", "translate this request into an outcome", "ship outcomes not features". Runs the 'One Framework. Four Questions.' protocol (Liatti + Cagan + Torres): Behavior Change → Assumption Test → Cheapest Test → Success Metric. Produces an Outcome Brief with embedded AI prompts ready to pas

Transform output-focused roadmaps into outcome-focused ones that communicate strategic intent, rewriting initiatives as outcome statements reflecting user and business impacts.

Manage teams using Andy Grove's principles: production thinking for knowledge work, output indicators, managerial leverage, effective meetings, clean decisions, OKRs, and task-relevant maturity.

Document end-to-end business processes in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time.

Replace heavy UX deliverables with hypothesis-driven design, collaborative sketching, and rapid experiments to learn what users actually need.

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

Build empowered product teams that own continuous discovery and delivery, shifting from feature factories to outcome-driven innovation.

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.