Expand Then Reduce: Why This Simple Framework Solves Complex Problems
Here's the thing about solving hard problems – most people jump straight to narrowing things down. They try to cut away options before they've even explored what's possible. Big mistake Worth keeping that in mind..
What if I told you the secret isn't about cutting faster, but expanding smarter first? That's where the 1.Because of that, 5. On top of that, 3 expand then reduce framework comes in. It flips conventional thinking on its head, and honestly, it's changed how I approach everything from writing to product development.
The short version is this: expand your thinking broadly, then systematically reduce it to what actually works. But there's more to it than that And that's really what it comes down to..
What Is the 1.5.3 Expand Then Reduce Framework
At its core, the 1.5.3 expand then reduce proposition is a structured approach to problem-solving that prioritizes breadth before depth. Rather than diving deep into one solution path, you deliberately cast a wide net first, generating multiple possibilities before refining and selecting.
The numbers represent the rhythm: one clear problem statement, five potential approaches, three viable solutions. But don't get hung up on the math – the principle matters more than the specific ratios No workaround needed..
This isn't just brainstorming with extra steps. It's a disciplined method for ensuring you don't prematurely converge on suboptimal solutions. In practice, it means resisting the urge to pick favorites too early No workaround needed..
Where This Approach Came From
The framework draws from design thinking, systems theory, and cognitive psychology. Designers have long known that sketching multiple concepts leads to better final products. That said, engineers use similar principles in trade-off analysis. Even writers know that drafting freely before editing produces stronger work.
What makes 1.5.3 different is how it systematizes this intuitive process. Instead of hoping you explore enough options, you follow a deliberate sequence that forces comprehensive thinking.
Why It Matters More Than You Think
Most failed projects share a common thread: they solved the wrong problem perfectly. Teams fall in love with their first good idea and skip the hard work of exploring alternatives. They reduce too soon, missing breakthrough opportunities hiding in plain sight That's the whole idea..
When you expand first, something magical happens. That said, you find combinations nobody considered. You discover constraints you didn't know existed. You avoid the trap of local maxima – settling for good enough because you never looked beyond the obvious.
Real talk: this approach takes longer upfront. But it saves months of backtracking later. I've seen teams abandon months of work because they skipped the expansion phase and built something nobody wanted That's the whole idea..
The Hidden Cost of Premature Reduction
Companies lose billions annually to premature convergence. They invest heavily in solutions that looked great in conference rooms but fail in the real world. Why? Because they reduced their options before fully understanding the problem space.
The expand then reduce method forces you to confront uncertainty head-on. Here's the thing — it's uncomfortable at first – generating multiple viable paths feels inefficient. But efficiency without effectiveness is just expensive busywork.
How the Expand Then Reduce Process Actually Works
Let's break this down into actionable steps. The framework follows three distinct phases, each with its own mindset and techniques.
Phase 1: The One Problem Statement
Start with exactly one problem, clearly defined. Even so, this seems obvious, but most teams try to solve five problems simultaneously. Pick the core issue that, if solved, would create the most value Worth keeping that in mind..
Your problem statement should be specific enough to guide exploration but broad enough to allow creative solutions. "Increase customer satisfaction" is too vague. "Reduce checkout friction for mobile users" gives you something concrete to work with And it works..
Write it down. Make it visible to everyone involved. Every idea you generate should relate back to this single focus.
Phase 2: The Five Exploration Paths
Now comes the expansion phase. Generate five distinct approaches to your problem. These aren't five variations of the same solution – they're fundamentally different ways of thinking about the challenge Worth knowing..
Take this: if your problem is reducing customer churn, your five paths might include:
- Improving product quality
- Enhancing customer support experience
- Redesigning pricing structure
- Building community features
- Creating educational content
Each path represents a different lens through which to view the problem. Don't worry about feasibility yet – you're mapping the territory, not choosing a route Less friction, more output..
Techniques for Generating Multiple Paths
Use constraint removal to spark creativity. Ask "What if budget wasn't an issue?Worth adding: " or "What if we had to solve this in 24 hours? " These artificial limitations often reveal unexpected approaches Took long enough..
Seek inspiration from unrelated fields. How would a restaurant solve this problem? What about an airline? Cross-pollination generates novel combinations Most people skip this — try not to..
Invite diverse perspectives. People from different backgrounds will naturally gravitate toward different solution paths. That diversity is exactly what you want at this stage.
Phase 3: The Three Solution Candidates
With five paths mapped, evaluate each against your criteria: feasibility, impact, and alignment with your goals. Select the three most promising candidates for deeper development.
This reduction phase requires honest assessment. Because of that, which paths show real potential? Here's the thing — which ones excite you and your team? Which ones address root causes rather than symptoms?
Develop each candidate enough to test assumptions. Create rough prototypes, run small experiments, gather feedback. You're not building final solutions – you're validating concepts And that's really what it comes down to..
Making the Final Choice
After testing your three candidates, one typically emerges as the clear winner. But here's what most people miss: the runner-up often contains valuable insights for improving your chosen path.
Document what worked and what didn't across all three candidates. This knowledge becomes invaluable for iteration and future projects.
Common Mistakes That Derail the Process
Even smart teams screw this up regularly. Here's where things typically go wrong.
Expanding Too Narrowly
The biggest trap is generating five variations of the same basic approach. Still, you think you're being thorough, but you're just rearranging deck chairs. True expansion means exploring genuinely different dimensions of the problem.
I once watched a product team generate five "solutions" that were all minor tweaks to their existing interface. They'd expanded their thinking by about 15%, not 500%.
Reducing Too Quickly
Another common error is rushing to judgment during the expansion phase. Someone throws out an idea, and instantly the room fills with reasons why it won't work. This kills creativity and reinforces existing biases.
During expansion, every idea gets a fair hearing. You're not evaluating quality yet – you're exploring possibility.
Skipping the Documentation
Teams get excited about generating ideas but forget to capture them properly. Without clear records of your five paths and three candidates, you lose the ability to learn from the process.
Document everything. Take photos of whiteboard sessions. Record voice memos during brainstorming. The goal is creating a knowledge base for future challenges Small thing, real impact..
Practical Tips That Actually Work
Based on years of using this framework, here are the tactics that consistently deliver results The details matter here..
Set Time Boxes Ruthlessly
Give yourself strict limits for each phase. Which means spend too long expanding, and you'll never ship. Rush the reduction, and you'll miss crucial insights.
Try this timing: one hour for problem definition, two hours for generating five paths, three hours for developing three candidates. Adjust based on complexity, but maintain the ratios.
Use Visual Mapping
Draw your five paths as branches from your central problem. This visual representation helps people see the relationships and gaps in your thinking. It also makes it easier to communicate your process to
stakeholders and collaborators. A well-drawn map also surfaces hidden assumptions — if you can't clearly branch a path visually, it probably needs more definition And that's really what it comes down to..
Bring in Outside Perspectives
During expansion, invite someone who wasn't part of defining the problem. Fresh eyes consistently catch blind spots that insiders have normalized. A developer reviewing a design challenge, or a customer-facing team member weighing in on a technical constraint, often surfaces connections no one else saw It's one of those things that adds up..
You don't need formal workshops. A quick 15-minute conversation over coffee can reframe an entire path And that's really what it comes down to..
Separate Spaces for Each Phase
Physically or digitally, create distinct environments for expansion and reduction. During expansion, use large open canvases, open tabs, and flowing conversation. During reduction, switch to tables, spreadsheets, or structured templates. The shift in format signals a shift in mindset and prevents the two modes from bleeding into each other.
Why This Framework Endures
The five-to-three method isn't revolutionary. Its power lies in discipline. Most people already have the creative capacity to generate five paths and evaluate three candidates. What they lack is the structured commitment to actually do it before defaulting to the first decent idea that surfaces Worth knowing..
By forcing yourself through each phase — definition, expansion, reduction, testing, and documentation — you replace intuition-driven decisions with evidence-informed ones. You stop falling in love with your first concept and start building confidence in your final choice.
The teams that adopt this practice consistently report one surprising outcome: the process takes less total time than their old approach of iterating on a single idea until it either works or fails. Breadcrumbing three candidates through small experiments is faster than perfecting one path in isolation And that's really what it comes down to..
Start small. Also, pick a decision you're facing this week — it doesn't need to be existential. Day to day, define the problem in one sentence, sketch five distinct paths, narrow to three, test quickly, and document what you learn. The framework scales from a single product feature to an entire company strategy, but its value is proven at every level That alone is useful..
The goal was never to find the perfect answer on the first try. In practice, it's to make better choices more reliably, with less wasted effort and more shared understanding across your team. That's a framework worth keeping And that's really what it comes down to..
