Teams asking for innovation frequently don't have an innovation problem. They have a decision problem.
A client says they want a breakthrough campaign, a disruptive product, or a new category idea. Then you look at the brief and the issue is obvious. The offer is unclear, the user journey leaks trust, the proposition is weak, and the team hasn't tested the basics. In that situation, chasing novelty is often expensive avoidance. Better design would do more than a workshop on bold thinking.
That doesn't mean innovation is overrated. It means it's often misdiagnosed. Agencies and product teams lose time when they treat design vs innovation as a branding choice instead of an operating choice. One is usually better for the current challenge. The trick is knowing which one to lead with, and who in the team should own each move. If you need a practical way to judge whether your team is improving the right thing, this guide on how to measure innovation is a useful companion.
Table of Contents
- The Innovation Myth Your Agency Needs to Unlearn
- Defining Design and Innovation Beyond Buzzwords
- Comparing Goals Process and Mindset
- The Powerful Overlap Where Value Is Created
- Who Owns What Structuring Teams for Success
- A Framework for Prioritizing Your Efforts
- Practical Exercises for Your Team with Bulby
The Innovation Myth Your Agency Needs to Unlearn
The most common bad advice in agencies is simple. Prioritize innovation first, then figure out execution.
That sounds ambitious. It also causes a lot of weak work. Teams jump to category-changing ideas before they've defined the customer tension, mapped constraints, or improved the current experience. They confuse freshness with usefulness.
What clients usually need first
In practice, many briefs sit in one of these buckets:
- A broken experience: The product, message, or journey already exists, but people don't understand it or don't trust it.
- A fuzzy proposition: The team wants something new because the current value story is weak.
- An internal alignment problem: Strategy, creative, product, and account teams are using different definitions of success.
Those are usually design problems first. They require framing, prioritization, prototyping, and testing.
Practical rule: If the customer problem is already visible, start with design before you start hunting for invention.
Why the myth persists
Innovation sounds senior. It signals ambition. It also gives teams permission to avoid the harder discipline of making choices inside constraints.
Design has the opposite reputation. Some people still hear the word and think layout, polish, or presentation. That view misses the point. Strong design is operational. It turns ambiguity into a usable direction. It helps a team decide what the idea is, who it serves, and what gets cut.
The better question isn't "Which matters more?" It's "What kind of uncertainty are we dealing with right now?" If the uncertainty is about fit, usability, clarity, or adoption, design should lead. If the uncertainty is about unmet demand, new behavior, or emerging opportunity, innovation should lead.
Defining Design and Innovation Beyond Buzzwords
Design is the disciplined act of solving a problem within real constraints. Those constraints might be budget, brand, regulation, timing, customer behavior, channel limits, or technical feasibility. Good design doesn't remove constraints. It uses them to shape a better answer.
Innovation is the act of creating new value. Sometimes that means a new offer. Sometimes it means a new business model, a new workflow, a new audience entry point, or a new way to combine existing capabilities. Innovation asks what could exist that doesn't yet.
Design gets stronger as it moves up the ladder
A useful way to separate design from decoration is the OECD-inspired Design Ladder. It describes four levels of maturity, from no systematic approach, to styling, to functional integration, to design as core business strategy. In U.S. data, 39.8% of design-active firms use a functional approach, while only 16.1% treat design as a fully structured creative process according to the NSF's Annual Business Survey summarized at the National Center for Science and Engineering Statistics.
That gap matters. It shows how many organizations still use design late, narrowly, or cosmetically.
A practical distinction teams can use
When I brief teams on design vs innovation, I simplify it like this:
- Design asks: what is the right solution to this defined problem?
- Innovation asks: what new opportunity should we pursue at all?
- Design improves fitness for use.
- Innovation expands the field of possible value.
Both can involve research, workshops, prototypes, and testing. The difference is where each starts and what each is trying to prove.
If your team is building systems that support repeatable creative work, this piece on AI in design automation is worth reading because it focuses on how process support changes execution quality without pretending automation replaces judgment.
A lot of confusion also comes from turning design thinking into a slogan instead of a working method. Teams benefit more when they treat it as a sequence of moves tied to real decisions, which is why a grounded breakdown of the design thinking process steps can be more useful than broad definitions.
Design becomes strategic when it shapes what gets built, not just how it looks at the end.
Comparing Goals Process and Mindset
The cleanest way to understand design vs innovation is to compare what each is trying to do under pressure.
A quick comparison
| Dimension | Design | Innovation |
|---|---|---|
| Goal | Solve a defined problem well | Find or create new value |
| Starting point | Existing need, friction, or brief | Unmet need, emerging behavior, or market opening |
| Core question | What works best for people within constraints? | What should exist that doesn't yet? |
| Process style | Iterative refinement | Exploratory experimentation |
| Relationship to constraints | Works inside them | Sometimes reframes them |
| Success signal | Clarity, usability, fit, adoption | Novelty with a credible path to value |
| Common failure mode | Polished but incremental | Exciting but unusable |
| Typical owners | Product design, UX, service design, delivery leads | Strategy, innovation, venture, R&D, senior leadership |
A team doing design well usually narrows choices over time. A team doing innovation well expands the option space before narrowing it.
How experienced designers actually work
One reason design is often underestimated is that outsiders mistake rigor for caution. In reality, good designers don't move in a straight line. They loop.
A study of design activities found that experts made backward transitions between process phases 15 to 20% more often than novices and spent 40% more time on early-stage problem analysis, according to the International Journal of Design study. That behavior matters. Experienced designers revisit assumptions before they commit.
That pattern shows up in agency work all the time. Strong teams don't just produce more concepts. They stop, test framing, revisit the brief, and kill weak directions before those directions become expensive.
Different mindsets, different tools
The mindset split is just as important as the process split.
- Design mindset: user-centered, constraint-aware, detail-sensitive. Tools often include Figma, Miro, prototypes, user flows, service blueprints, and testing scripts.
- Innovation mindset: possibility-driven, ambiguity-tolerant, future-facing. Tools often include opportunity maps, trend synthesis, venture hypotheses, stimulus prompts, and concept experiments.
- Shared ground: both need evidence, but they use evidence differently. Design uses it to refine. Innovation uses it to decide where to explore.
The fastest way to weaken a project is to ask one process to do the other's job.
If you want a broader operational view of how organizations move ideas from uncertainty to execution, this guide to processes of innovation is useful because it shows the work beyond the brainstorm itself.
The Powerful Overlap Where Value Is Created
Winning isn't choosing design over innovation forever. It's knowing how they feed each other.
A new idea without design discipline usually dies in translation. It may sound original in the workshop and fail in the market because nobody made it understandable, usable, or believable. The reverse is just as common. Strong design without innovation creates cleaner versions of familiar work. That can improve conversion or loyalty, but it rarely opens new ground by itself.
This is why the best agencies don't treat design and innovation as competing tribes. They run them as connected loops. Innovation opens territory. Design turns that territory into something people can adopt.
What breaks when one side dominates
You can usually diagnose the imbalance fast.
- Innovation-heavy teams often overproduce concepts and under-prove them.
- Design-heavy teams often optimize the existing offer long after the growth ceiling is visible.
- Leadership teams often ask for both at once without sequencing the work.
That sequencing matters because design-led companies don't just make better-looking outputs. They tend to embed design in core decisions. The Design Management Institute's Design Value Index, cited in Adobe's analysis, found that design-driven firms outperformed the S&P 500 by over 219% across a decade in Adobe's write-up on design-led businesses.
That figure doesn't mean every workshop needs to become a design sprint. It means disciplined design compounds when leadership treats it as a business capability, not a final layer.
How the loop works in practice
The overlap becomes practical when teams do three things in order:
- Explore new possibility spaces. Innovation earns its keep through this exploration.
- Reduce risk through user contact. Strong teams use interviews, prototype feedback, and concept testing early. If your team needs a sharper toolkit here, these methods for user research are a good starting point.
- Refine the chosen path hard. Design then takes over, making the idea coherent.
A short explainer helps here:
For agency leaders, the operating question is simple. Are we trying to discover a better opportunity, or are we trying to make an opportunity real? If the answer is both, don't blend the stages into one messy session. Sequence them. This is especially true when the work also affects proposition, pricing, or service structure, where business model and innovation have to move together.
Who Owns What Structuring Teams for Success
One of the most expensive mistakes in agencies is role blur. The team says everyone should innovate and everyone should design. That sounds collaborative, but in practice it often means nobody owns discovery properly and nobody owns translation properly.
Research on this split makes the distinction clearer. Innovators are primarily discoverers driven by inquisitiveness, while designers create methods, processes, and functionality through applied creativity, as discussed in Jon Kolko's piece on the relationship between design and innovation.
Stop giving one team both jobs by default
A strategist may be excellent at identifying whitespace and weak at turning that into a usable product experience. A senior designer may be excellent at shaping systems and less suited to hunting for adjacent market plays. Both are valuable. They are not interchangeable.
This matters in agencies because most projects cross at least four functions:
- Strategy: frames the market, audience tension, and opportunity space.
- Creative or design: shapes the expression, structure, and experience.
- Account leadership: protects commercial reality, scope, and stakeholder alignment.
- Product or delivery: translates direction into testable and shippable decisions.
When all four functions try to own innovation at the same time, workshops get noisy. When all four functions defer design decisions until late, the work gets abstract.
A workable split inside agency teams
A better model is to assign ownership by phase, not title.
Let discovery-heavy people own the open questions. They should lead category mapping, customer tensions, adjacent behaviors, concept territories, and opportunity framing. Then hand the strongest directions to design-heavy people who can turn rough possibility into flows, interfaces, service moments, messaging structures, or campaign systems.
Don't ask the same room to be wildly divergent and brutally selective at the same moment.
That doesn't mean a rigid handoff. It means distinct accountability. One group expands and challenges assumptions. Another group structures, prioritizes, and resolves.
Teams also need operating habits that support this split. If you're modernizing the way people work with AI alongside human judgment, this article on creating AI-native operations is useful because it focuses on workflow design, not tool hype.
A simple test helps. Ask who owns each of these decisions: What problem are we pursuing? What new value might exist here? Which concept deserves proof? What exactly are we putting in front of users? If the same person owns all four on every project, your team is probably over-centralized.
A Framework for Prioritizing Your Efforts
You don't need a complicated model to decide between a design-led or innovation-led approach. Two questions are usually enough.
Use two questions first
Ask these at the start of a project:
- How clear is the problem?
- How familiar is the market or context?
Those two answers tell you where to place your effort.
| Problem clarity | Market familiarity | Priority |
|---|---|---|
| High | High | Design first |
| High | Low | Design with selective innovation |
| Low | High | Innovation to reframe the problem |
| Low | Low | Innovation first, then design quickly |
The four situations that matter
Clear problem, familiar market
This is the classic design brief. The audience is known, the friction is visible, and the offer exists. Prioritize service design, UX, messaging structure, customer journey cleanup, and fast prototyping.
Clear problem, unfamiliar market
You still need design discipline, but the team should reserve room for exploration. Maybe the need is obvious but the channel, audience behavior, or category expectation isn't. Here, use design to anchor the work and innovation to test edge cases.
Unclear problem, familiar market
Many teams waste months polishing the wrong answer. The category is known, but the problem is fuzzy. Prioritize research synthesis, opportunity framing, and concept exploration before you commit to execution.
Unclear problem, unfamiliar market
This is the highest-ambiguity case. Start with innovation. Explore unmet demand, adjacent behavior, weak signals, and future scenarios. Then move into design as soon as one direction earns evidence.
Field note: Teams get faster when they stop debating labels and start locating the problem on this grid.
This framework also prevents a common executive mistake. Leaders often fund innovation when they should fund better problem definition. Or they demand refined design when the team hasn't earned a direction yet.
Practical Exercises for Your Team with Bulby
A team doesn't need a huge transformation program to work better across design vs innovation. It needs a repeatable session structure.
One of the most practical models is Double Diamond. In real deployments, teams using it achieved 25 to 35% higher market fit for prototypes, and the divergent phases generated 2.5x more initial concepts than linear methods, according to this overview of the Double Diamond innovation framework.
A simple session structure
A useful team exercise maps directly to the four phases:
- Discover
Start wide. Gather tensions, customer signals, competitor patterns, and internal assumptions. - Define
Narrow to the most important problem statement. Here, many teams improve immediately as they stop solving five issues at once. - Develop
Generate and combine directions. Push for range before critique. - Deliver
Turn the best option into something testable. That could be a storyboard, a messaging route, a landing page concept, a service flow, or a prototype.
Tools matter here because facilitation quality often determines idea quality. Teams working remotely or across functions usually need stronger structure than a blank whiteboard provides. This guide to virtual brainstorming techniques is useful for tightening the mechanics.
What teams usually get wrong
The most common failure isn't lack of creativity. It's premature convergence.
A team jumps from one decent insight to one familiar idea and calls that efficiency. Good facilitation slows that moment down. It separates exploration from evaluation, captures weak signals before they vanish, and forces the room to test assumptions instead of defending instincts.
Bulby fits this kind of work well because it gives teams a structured way to run both divergent and convergent exercises without defaulting to the loudest voice in the room. For agencies, that's often the difference between a workshop that feels productive and one that actually produces a direction worth selling.
Bulby is built for the part of creative work where teams usually stall. Turning scattered input into strong concepts with a clear process. If your agency wants a better way to run structured brainstorming across strategy, creative, and account teams, explore Bulby.