Product Strategy Experience Strategy Systems Thinking
Turning complexity into shared direction.
I connect customer needs, business priorities, operational realities, and technical constraints to help teams decide what to build, where to focus, what tradeoffs to make, and how success should be measured.
Experience Strategy
Service Design
Prioritization
Cross-Functional Alignment
My Strategy Philosophy
Strategy is a system for making better decisions.
A roadmap is not a strategy. A workshop is not a strategy. A vision deck is not a strategy. Strategy is the shared logic that helps an organization decide what matters, what does not, and how to make tradeoffs when conditions change.
My role is often to bring together perspectives that naturally compete: what customers need, what the business must accomplish, what technology can realistically support, and what the organization is capable of delivering and sustaining.
When those forces are visible together, teams can move from reacting to requests toward making intentional product decisions based on outcomes, risk, evidence, and shared priorities.
What strong strategy creates
- A clear definition of the problem
- Shared customer and business outcomes
- Visible constraints and tradeoffs
- Priorities teams can explain
- Principles that guide future decisions
- Measures that show whether the strategy is working
How I Build Strategy
Frame. Align. Focus. Scale.
My approach is designed to move teams from a collection of requests and assumptions toward a shared understanding of the problem, the decisions that matter, and the outcomes we are trying to create.
01 / Frame
Define the problem before committing to the solution.
I work with teams to separate symptoms from underlying problems, identify who is affected, understand why the problem matters to the organization, and define the outcomes worth changing.
02 / Align
Create one shared view of reality.
Research, operational data, technical constraints, business priorities, policy, and stakeholder knowledge are brought together so teams are making decisions from the same context rather than competing versions of the problem.
03 / Focus
Make the tradeoffs explicit.
Strategy requires choices. I help teams identify where investment creates the most value, what can wait, what should be standardized, where flexibility matters, and which risks the organization is willing to accept.
04 / Scale
Turn decisions into systems teams can reuse.
The strongest strategies become principles, patterns, governance, measurement, and operating practices that help teams make future decisions without reopening the same debates every time.
Connecting the System
Good product decisions sit at the intersection of four realities.
I rarely see complex product problems caused by one thing. The work is usually difficult because customer needs, business goals, technology, and operational realities are pulling in different directions.
Customer Reality
What people are trying to accomplish, where they struggle, what they understand, and where the experience creates unnecessary cognitive or operational burden.
Business Reality
Growth, cost, risk, compliance, adoption, retention, delivery speed, and the broader outcomes the organization needs the product to support.
Technical Reality
Architecture, platform capability, technical debt, integration constraints, security, maintainability, and the real cost of creating and supporting a solution.
Organizational Reality
How teams actually work, who owns decisions, where handoffs occur, what capabilities exist, and whether the organization can realistically operate the solution after launch.
From Evidence to Direction
Research matters when it changes a decision.
I do not treat research as a separate phase that ends with a presentation. Its value is in how it changes prioritization, product direction, investment, and the assumptions a team is willing to carry forward.
That means connecting qualitative research with operational data, product analytics, support issues, technical constraints, stakeholder knowledge, and business goals.
The output is not simply more information. It is clearer decisions about where to invest, what risks need validation, which workflows need intervention, and what evidence would cause us to change direction.
Questions I use to drive decisions
- What problem are we actually solving?
- Who experiences the problem most?
- What happens if we do nothing?
- Which assumptions carry the most risk?
- Where can we create the greatest leverage?
- What evidence would change our direction?
Strategic Principles
Principles reduce the number of decisions that need escalation.
On large programs, leaders cannot personally resolve every product decision. I use strategic principles to give teams enough shared logic to make good decisions independently while keeping the work connected to the larger direction.
01
Automate the mechanics. Preserve judgment.
Technology should remove repetitive coordination and administrative work without hiding or replacing decisions that require human context and accountability.
This principle helped separate high-value human decisions from workflow mechanics in complex case-management environments.
02
Standardize the common. Design the exceptional.
Teams should not spend design and engineering capacity repeatedly solving mature, low-risk interaction problems.
Shared patterns and experience guardrails free teams to focus on complex workflows, new capabilities, and higher-risk decisions.
03
Design the service before the screen.
When workflows span teams, systems, policy, and handoffs, improving one interface rarely solves the underlying problem.
Service models create a shared foundation for product, operational, and technical decisions before teams optimize individual interfaces.
04
Define the outcome before the artifact.
Teams need agreement on what success means before debating the shape of the solution.
Clear outcome measures make tradeoffs easier and give leadership a stronger way to evaluate product investment.
Strategy in Practice
Shared direction should produce measurable change.
The goal of strategy is not alignment for its own sake. It is helping teams make better investments, reduce avoidable complexity, and create outcomes the organization can measure.
Faster Resolution
A shared service model simplified complex case-management workflows.
Fewer Handoff Errors
Clearer ownership and governed workflows reduced coordination failures.
Less Duplicate Work
Shared product foundations reduced redundant implementations.
System Adoption
Product teams adopted a shared design foundation at scale.
Selected Strategy Work
How this approach shows up in real product decisions.
The problems vary, but the pattern is consistent: understand the larger system, make tradeoffs visible, create shared direction, and turn that direction into a model teams can execute and extend.
Enterprise Transformation
CMS Case Management
Reframed a fragmented interface problem as a service and operating-model challenge spanning users, workflows, compliance, technology, and organizational ownership.
40% faster resolution and 60% fewer handoff errors.
Organizational Strategy
Building Design Capability
Built a design and research practice, operating model, research capability, and shared product foundations that moved Design upstream into product decision-making.
0 to 8 team members and 90% design-system adoption.
Growth Strategy
Building an Experimentation System
Connected UX, marketing, analytics, and platform capabilities into a repeatable experimentation model rather than relying on isolated campaign optimization.
Created a shared framework for learning, prioritization, and scalable experimentation.
Working With Leadership
My role is often to make complexity easier to decide against.
Executives and product leaders rarely lack ideas. The harder problem is deciding which opportunities matter most, where risk is hiding, and which investments actually move the organization toward its goals.
I help create that clarity by connecting evidence to decisions, separating strategic questions from implementation questions, surfacing tradeoffs early, and giving teams a shared framework for moving forward.
Where I create leverage
- Problem framing and opportunity definition
- Customer and stakeholder alignment
- Product and experience principles
- Portfolio and roadmap prioritization
- Service and workflow strategy
- Experience governance
- AI and automation decision frameworks
- Outcome and measurement strategy
The Principle I Come Back To
Good strategy gives teams fewer decisions to rediscover.
The goal is not to predict every future decision. It is to give people enough shared context, principles, evidence, and direction to make the next decision well.