Why Is Tying Business Impact to Design Work So Hard?

I ran a survey that captured people with similar product careers (e.g., product leaders, UX designers) and filtered it down to design leads.

Most of them highlighted that their worst pain point was being unable to create business impact.

Designers themselves had a somewhat similar perspective. Their worst pain points were building the wrong thing and building products that don’t convert (thus, business impact).

This leads me to the question of:

What makes tying business impact to design so difficult? And what fields have an advantage- who could designers could take inspiration from?

1 Like

Love this @ben! Can you drop the link to that survey?

1 Like

Building on your thinking Ben, I reviewed 10 recent LinkedIn posts and Reddit threads to understand where design struggles to create impact. Here are the patterns that stood out.

  • Design is framed as execution, not risk detection
    Appears most often. Design is treated as delivery work rather than as a way to surface risk and problems early.

  • Early warnings are discounted because they arrive before data
    Problems based in intuition are ignored because they show up before metrics, making them easier to dismiss.

  • Qualitative feedback is mistaken for subjectivity
    Designer input is treated as opinion rather than informed signal grounded in system knowledge.

  • Design intuition lacks a shared language of proof
    Designers see problems but cannot translate them into evidence others trust early enough to act.

  • Teams optimize for launch, not durability
    Work is approved based on shipping, not whether it will scale, convert, or hold up over time.

  • Risk is discovered too late in the process
    Issues surface after launch, when fixes are more expensive and politically harder.

  • Design feedback creates discomfort without protection
    Designers raise concerns before failure is visible, leaving them exposed without backing.

  • Designers see system-level problems others cannot
    Designers notice breakdowns across flows and systems that are invisible in output reviews.

  • Teams lack an early-warning mechanism
    There is no shared way to capture, validate, and act on early signals, so warnings rely on personal credibility.

  • Design value is misunderstood as polish, not foresight
    Design is judged on surface quality instead of its ability to prevent failure and reduce downstream risk

Which translates into something that might sound familiar:

“Why are we finding this out now?”
“I don’t want to reopen this unless there’s clear data.”
“I get the concern, but I don’t know how to justify acting on it.”
“We hit the date. We’ll deal with issues after it’s live.”
“That feels like an opinion. Do we have anything more concrete?”
“No one flagged this earlier. Where did this come from?”

3 Likes

Here’s the survey Helio | Hooks Report

1 Like

Used this as a prompt to write a post on the topic- expanded on the idea of Intuition and how this needs to play with UX metrics for business impact.

LOOOOOVE! I don’t think the problem is that designers aren’t trying or aren’t measuring things. It’s that design signals and business outcomes rarely get talked about in the same language.

Designers look at clarity, usability, confidence. The business looks at conversion, revenue, retention. The gap shows up when no one clearly meshes these two worlds. Granted, its hard, and I think acknowledging that its a challenge is the first place to start.

1 Like

I honestly think that it’s just really hard, and not in the standard design culture.

Business is brutal, users are stubborn, and everyone is a bit narcissistic (all humans are).

It takes a bit of extra pressure and dedication to get there, and it’s hard to know if it’s even worth the push (from their perspective).

All of these feel like output vs outcome problems.

Communication and trust are super key to influencing most of these areas.

Great finds @Bryan !

This is a great observation. It’s the reason so much of what we create fails. Aligning design impact with business results isn’t a straight shot and requires understanding human behavior.

I love this stuff, so I thought it would be interesting to dive into more research. Here are five areas that Glare needs to address:

1. Humans overtrust intuition in complex systems

Daniel Kahneman and Gary Klein have great research on intuition (a core strength of design).

rainbow-spongebob

Daniel Kahneman

  • Describes intuition as fast, automatic thinking built from pattern recognition. It feels confident, but it only works well when the environment is consistent, practice is repeated, and feedback is immediate.
  • He draws a line between high-validity and low-validity environments. UX, product strategy, and markets are low-validity by default. Patterns shift, feedback arrives late, and signals are noisy.
  • In low-validity environments, intuition drifts toward overconfidence unless it is corrected by real feedback.

Gary Klein

  • Has shown that strong intuition is not about comparing options. Experienced people act quickly by recognizing patterns and mentally simulating outcomes.
  • His Recognition-Primed Decision model explains why good decisions often look instinctive. They are built from repeated exposure to real situations and clear feedback.
  • The overlap is simple. Intuition works when it is trained. Without feedback, it feels strong but stays unreliable.
  • Here is his book on intuition, The Power of Intuition

Basically, intuition becomes reliable only after repeated exposure to valid feedback. UX metrics supply that missing feedback loop.

2. Ego and motivated reasoning distort judgment

Lots of research on “motivated reasoning” shows people favor information that supports their prior beliefs, status, or identity (aka cognitive bias)

homer

This shows up in business as:

  • Executives defending sunk costs
  • Teams overvaluing their own ideas
  • Stakeholders dismissing early warnings as “subjective”

Organizational psychology has shown that externalized evidence reduces defensive reasoning (need to find sources here). Metrics work not because they are perfect, but because they shift debates away from identity and toward shared reference points.

3. Users are predictably inconsistent

bad-decisions

Behavioral science repeatedly shows that users:

  • Say one thing and do another
  • Rely on heuristics
  • Resist change even when alternatives are better

Richard Thaler argues that people are not perfectly rational. We are biased, impulsive, and often favor short-term comfort over long-term benefit.

Because of that, single user observations are noisy and easy to misread. Real understanding comes from patterns across many small signals. That is why aggregated UX metrics beat anecdotes, without replacing qualitative insight.

4. Measurement improves intuition over time

There is strong evidence that measured feedback trains intuition.

Psychologist K. Anders Ericsson studied elite performers across domains like medicine, chess, music, and sports. His core finding was simple.

measure

Expert intuition is built through deliberate practice, which always includes:

  • Clear goals
  • Repeated exposure
  • Immediate, measurable feedback
  • Correction over time

Which translates to:

  • Novices rely on rules
  • Experts rely on intuition
  • Experts only become experts through tight feedback loops

UX metrics act as a feedback loop.

Over time, teams make better decisions AND they develop better instincts. I hypothesize that UX metrics reveal where intuition actually works, and show where new patterns can emerge.

Without feedback, people repeat mistakes while becoming more confident. With feedback, intuition becomes calibrated.

5. Systems thinking backs this up

In systems, intuition without measurement creates unstable loops. Small biases compound. Errors hide until they are expensive. Hard to see early in the process.

systems

Measurement introduces a type of damping (which designers potentially dislike). However, it does not remove human judgment… this type of constraint stabilizes it.


So… back to your assertion @ben. Love @Helge’s thoughts!

  • Business is adversarial
  • Humans are biased
  • Users are inconsistent

In my experience, UX metrics succeed not because people are rational on teams, but because they are not.

1 Like

Wow, amazing breakdown @Bryan !

Love this specific part. Growth without measurement isn’t growth (if that makes sense). You could be growing in the wrong direction!

That’s mostly wandering, lol.

wandering

1 Like

Love what @Bryan said about design being seen as execution, not risk detection. I see the same thing all the time where we spot issues early through user feedback, but it’s waved off as opinion until live analytics prove the direction.

Absolutely love all of these @Bryan. A lot of these feed into the idea that understanding the user is key here, and doing everything that you possibly can (which I think all of the patterns that you highlighted touch on somewhat abstractly).

All of these feel like they come from not understanding the user well enough, or at least not doing the amount of work required to get there.

Gracias, my friend. I think with AI workflows, it’s about understanding how users fit into different parts of the process.

Our recent Helio post starts to touch on these ideas:

In my experience, there are different patterns to figuring out what users truly need… which is the foundation of design impact.

  • Without context or broader conversations, you’ll hear users say a lot of things. That feedback is helpful, but it still takes work to figure out what actually matters.

  • Watching people use products or services can be eye-opening. You start to see how people naturally try to accomplish things, where they struggle, and what they actually value. @Helge says that context and environment are key to understanding the situation here.

  • And while simply putting ideas out into the world can be expensive, the right learning cycles help teams learn quickly and reduce the risk of building the wrong thing.

2 Likes