OREEO: A Practical Framework for Evidence-Driven Design
OREEO - A Framework for Evidence-Driven Design that is easy to remember. Nice, round and tasty.
Many organizations say they want evidence-driven design. In practice, design decisions are still often driven by opinion, hierarchy, or speed. Teams jump directly to solutions before fully understanding the problem, and launch becomes the end of the conversation rather than the beginning of learning.
Over time, I developed a simple framework to help teams move from insight to impact in a more disciplined way. I call it OREEO - It’s easy to remember and has an association with something good and circular.
OREEO describes the continuous cycle through which design ideas become validated experiences and measurable improvements. The name stands for five phases:
Observation → Reflection → Evaluation → Execution → Optimization
It’s not a rigid process. It’s a shared mental model for how design teams operate when their work is grounded in evidence rather than assumption.
Observation - Start with understanding
Every meaningful design initiative begins with observation. Before designing anything, teams need to understand the environment in which the problem exists: the customer behavior, the business objective, and the signals we can observe in data.
This phase focuses on identifying:
the problem worth solving
the customer journey and friction points
the business context and constraints
Observation forces teams to slow down just enough to ask the right questions before proposing answers.
Reflection -Turn insight into design hypotheses
Once the problem is understood, the team reflects on what they’ve learned. Reflection is where insight becomes ideas. Designers explore possible approaches and translate observations into experience concepts.
This phase is intentionally exploratory. The goal is not to produce the final answer but to generate strong design hypotheses that can later be validated. Design at this stage is thinking, not production.
Evaluation - Replace opinion with evidence
Before ideas move into production, they need to be evaluated. Evaluation introduces evidence into the design process through usability testing, concept validation, and experimentation.
This step answers critical questions:
Does the concept actually solve the problem?
Do users understand the experience?
Are we removing friction or introducing new obstacles?
Evaluation reduces risk and helps teams focus their energy on solutions that have a real chance of succeeding.
Execution - Deliver validated solutions
Execution is where validated ideas become production experiences. Designers collaborate with engineering, content teams, and business partners to translate concepts into real products and services.
Because earlier phases have clarified the direction, execution can focus on delivery rather than debate. Execution should feel like momentum, not uncertainty.
Optimization - Learning starts after launch
Most organizations treat launch as the end of a project. In reality, launch is where learning begins.
Optimization focuses on measuring real-world performance and continuously improving the experience through analytics, experimentation, and iteration. The insights generated here feed back into observation, restarting the cycle. This is how design becomes a practice of continuous improvement rather than periodic redesign.
Design as a Learning System for Revenue Growth
OREEO works because it treats design as a learning system. Each phase plays a role:
Observation creates understanding. Reflection creates hypotheses. Evaluation creates evidence. Execution creates real experiences. Optimization creates improvement.
When this cycle is working well, design becomes more than aesthetics or interface decisions. It becomes a disciplined way for organizations to discover opportunities, test ideas, and improve customer experiences over time. And there’s no business if customers don’t experience value.
That’s what evidence-driven design looks like in practice.
