MY PHILOSOPHY
The most difficult problems rarely begin where we think they do.
They begin where understanding ends. Throughout my career, one question has shaped nearly every engagement.
What problem are we actually trying to solve?
Everything that follows explores how I answer that question.
Better Questions Lead to Better Systems
People often ask what I do. The better question is how I think. I don't begin with solutions. I begin with curiosity. I look for:
- People
- Behaviors
- Decisions
- Knowledge
- Friction
- Assumptions
When we change the question... we often change the solution.
Good design rarely begins with better answers. It begins with better questions.
Understanding Before Designing
Research isn't a phase. It's the starting point. Understanding people reveals behaviors. Understanding behaviors reveal systems. Understanding systems reveal opportunities. Only then does design become meaningful.
Better alignment.
Better capability.
Better systems.
A Consistent Way of Thinking
Every engagement is different.
My approach isn't.
It always begins here.
Observe.
Understand.
Reframe.
Design.
Strengthen capability.
Those five ideas describe how I move through complexity.
Better understanding creates better decisions. Better decisions create better systems.
An Evolution of Thinking
My career isn't a collection of different jobs. It's an expansion of perspective.
The industries changed. The technology evolved. The questions became larger. The philosophy remained remarkably consistent.
Why These Projects
This portfolio isn't organized chronologically. It's organized intentionally. Every chapter explores a different organizational challenge. Together they tell one connected story.
Recurring themes:
- Understanding before designing.
- Research before assumptions.
- Knowledge before execution.
- Capability over deliverables.
- Systems over isolated solutions.
One philosophy. Seven different organizational challenges.
Looking Across the Work
These aren't seven separate projects. They're one continuous pattern.
- Organizations reducing complexity.
- Teams building shared understanding.
- Knowledge becoming structured.
- Communities becoming stronger.
Understanding should always come before deciding what to build next.
The projects become more complex. The thinking remains remarkably consistent.
The Projects Changed. The Philosophy Did Not.
Every project was different. The philosophy wasn't.
The strongest solutions rarely come from designing faster. They come from understanding better.
That's the thread connecting every chapter that follows. Not a methodology. Not an industry. A way of thinking.
Continue the Journey
The remaining pages aren't project summaries. They're chapters. Each one explores a larger organizational question than the one before it. If this philosophy resonates with you... the best way to understand it is to see it applied.
Follow the progression through seven connected case studies demonstrating how one philosophy adapts across healthcare, enterprise transformation, organizational learning, workforce development, and community systems.