Summary: This article explores one of the biggest risks that appears when design gains more influence in product teams: making design decisions in questions that are not actually design-driven. It explains how overreach happens, how it connects to design maturity and decision ownership, and how a simple response chart can help designers choose when to lead, guide, challenge, or step back.
For a long time, one of the biggest challenges for design in many companies has been visibility. Design is often brought in too late, treated like a service function, and expected to support decisions that were already made by someone else. In that kind of environment, the main goal is usually clear: build trust, become more visible, and move from a supporter role into a collaborator role that can shape product work earlier and more meaningfully. But once that shift begins, a different challenge appears. When design starts getting invited into more discussions, asked for stronger opinions, and trusted with bigger decisions, it feels like progress, and in many ways it is. It usually means the company is starting to understand that design is not only about screens, but also about how product decisions affect people, clarity, trust, and usability. At the same time, this new influence brings a new risk, and one of the biggest is this: making design decisions in questions that are not actually design-driven.
The “Misplaced ownership” problem
As design becomes more visible, more questions begin to land on the designer’s desk. Teams ask whether a direction is right from a UX point of view, stakeholders want guidance earlier, and product teams start bringing design into decisions before things are finalized. That is usually a good sign, because it shows that design is no longer treated only as a delivery step at the end of the process, but as a discipline that can help shape direction earlier. The problem starts when that visibility grows faster than role clarity.
In that kind of environment, designers often get pulled into questions that look like design questions on the surface, while the real decision underneath is actually about product strategy, business priority, delivery trade-offs, policy, or risk. This is where overreach begins, and it usually begins quietly, because nobody plans for it and nobody names it early enough.
The overreach situation
Overreach is rarely dramatic, and most of the time it does not come from ego. It comes from good intentions. A designer sees friction, notices a weak flow, spots a usability risk, and wants to improve the experience before it creates harm. That is normal, and in many cases it is exactly what design should do.
The problem appears when the visible layer of the issue is UX, but the real decision is something else. Sometimes the real question is not whether the flow is cleaner, the screen is clearer, or the journey is easier to use. Sometimes the real question is whether the company should build something now, whether the trade-off is worth it, whether the idea supports the product goal, or whether delivery can carry the cost.
Those are not pure design questions, even if they affect the experience in a very real way. When design starts acting like the final decision maker in those cases, the role becomes blurry, and later, if the outcome is poor, design may get blamed for a decision it never truly owned, never had all the inputs for, and never should have carried alone. That is the real danger. The issue is not that design is helping too much, but that design may be taking ownership of decisions that belong in a wider cross-functional space.
Maturity is a transformation, not a jump
This issue is not only about individual behavior. Very often, it is also a sign of uneven design maturity. In more mature organizations, influence does not grow on its own. It grows together with clearer ownership, better collaboration rules, and a stronger understanding of how design fits into the wider product lifecycle. When that maturity is still developing, design can gain more visibility before the system around it is ready, which means more questions come to design even though the company still has not decided who owns what, how trade-offs are made, or who has the final word when several teams are affected.
That is why this stage often feels painful. From the outside, it looks like progress, but inside the work, design gets more influence without always getting better conditions to use that influence well.
In other words, what looks like a designer problem is often a system problem.
The decision-right framework
Product organizations have been dealing with versions of this for years, which is why decision-right frameworks such as RACI, DACI, or RAPID exist in the first place. Their purpose is not to make teams bureaucratic. Their purpose is to make clear who gives input, who shapes a recommendation, and who owns the final call. That matters here, because the real issue is not only whether design has a strong opinion. The real issue is whether design is stepping into the right role in the decision. Sometimes design should lead the recommendation. Sometimes it should bring evidence. Sometimes it should challenge the risk. Sometimes it should simply support the discussion. What creates trouble is not strong design input by itself, but strong design input delivered with the wrong level of ownership.
Seen from that angle, overreach is often not a personality problem, but a decision-structure problem.
There is no sharp line between design and product
This is where many teams get stuck, because they try to split questions into two clean groups, as if some decisions belong to design and others belong to product, when in reality most important decisions touch both.
In digital products, a lot of decisions affect more than one area at the same time. They shape the experience, but they also affect business goals, delivery effort, technical complexity, and future scalability. That is why the better question is not whether something is a design decision or a product decision. The better question is what kind of impact the decision has, what type of risk it carries, and who should own the final call.
This is also why designers need broader product understanding, not because they should become product managers, but because they need enough judgment to recognize what kind of decision they are looking at before they react to it. This is where product trio thinking becomes useful. In stronger product teams, design, product, and engineering do not work as three separate functions waiting to hand work to one another. They work more like a shared decision space, where each discipline brings a different lens and a different responsibility. Product usually carries value and business direction, engineering carries feasibility and delivery reality, and design carries usability and experience quality. That does not mean every decision is shared equally, but it does mean the best decisions are usually shaped together, with clear ownership instead of blurred ownership.
A filter for everyday decisions
Formal methods like RACI, DACI, or RAPID are useful, but day-to-day work rarely begins as a formal decision workshop. Most situations start as quick questions, Slack messages, feedback comments, or stakeholder conversations where somebody expects a fast answer. That is where designers need something lighter.
A practical way to handle this is to stop treating every incoming question the same way, because not every question deserves the same amount of design energy, the same level of ownership, or the same kind of response. A better approach is to look at the situation from three simple angles before reacting.
- Business Impact: shows how much the question matters for business goals, priorities, cost, growth, or risk.
- Experience Impact: shows how much the question affects usability, trust, clarity, flow quality, or the user’s ability to complete what they need.
- Delivery Effort: shows how hard, expensive, or risky the change is to build.
When you combine these three, you get a clearer view of what kind of decision is really in front of you, and instead of jumping straight into a design answer, you can choose the right role for design in that moment.
Sometimes design should push hard and lead the recommendation. Sometimes it should guide. Sometimes it should make the risk visible. Sometimes it should ask why the work exists in the first place. And sometimes it should simply let the issue go.
The chart below is not meant to replace formal ownership models. It is a simpler decision filter that helps designers judge how strongly they should step in before a bigger cross-functional decision is made.
The value of the chart is not that it gives a perfect answer every time. Its value is that it creates a pause before reacting too quickly. When a question comes in, the first step is not to answer it immediately, but to ask three simple things: how much does this matter for business, how much does this matter for experience, and how heavy is it from a delivery point of view? Once those three are clearer, the designer can choose the right role. That matters because the real problem in many teams is not that design says too much, but that design says the right thing with the wrong level of ownership. Instead of reacting with the same force every time, the chart helps design respond with the right amount of force for the situation.
It also makes one important thing visible: the strongest response is not always the strongest opinion. Sometimes the strongest response is to negotiate, sometimes it is to guide, and sometimes it is simply to ask why the work exists at all.
What sits underneath this model
Under the surface, this chart is built on three different layers of professional thinking.
- Design maturity: this problem usually appears only after design starts gaining more voice and visibility.
- Decision-right logic: the real question is not only what design thinks, but what role design should play in the decision.
- Cross-functional product thinking, because most important decisions sit between business value, user experience, and delivery reality rather than fully inside one function.
What the chart does is turn those bigger ideas into something lighter and easier to use in real conversations, so designers can make better judgment calls before a discussion turns into an ownership problem.
The real growth step for designers
I think this is one of the most important growth steps for designers who are becoming more influential.
Early in a career, a lot of growth is about craft, which means better flows, stronger thinking, better hierarchy, and cleaner execution. Later, the next step is not only craft, but judgment, because the designer needs to know when to lead, when to support, when to challenge, and when to step back without becoming passive. That is where maturity starts to show, because having more voice does not mean using that voice the same way in every conversation. The strongest designers are not the ones who try to own every important question. They are the ones who can read the situation well, understand what kind of decision is being made, and respond with the right amount of ownership.
Getting more influence is a good sign, and getting a seat at the table is something design should absolutely work for. But once that starts happening, designers need to become more careful about how they use that influence, because the next risk is no longer invisibility, but overreach. The best way to avoid that is not to become passive, and it is not to step back from strategic work, but to become more precise about what kind of question is in front of you, what kind of impact it has, and what role design should play in that moment.
Not every question needs a design decision. Some need a strong design recommendation, some need design input, some need design to make risk visible, and some are simply not worth fighting for. That is the shift. The goal is not only for design to have more voice. The goal is for design to use that voice with better judgment.
More articles on Medium
More articles on Linkedin
