The madness in not measuring design at all

If you think measuring design is hard (it is), not measuring it is even harder—on your team, your organization, and your users. When design operates without being measured, it risks losing its voice, its influence, and its connection to the mission. Worse, the organization risks burning through resources, alienating its audience, and delivering solutions that might not actually solve anything or only solve half of something.

And while you might think, “I’m safe from the spotlight because my leadership doesn’t know how to measure my team”—think again. Sure, that might shield you from some of the brutal scrutiny that can come with data, but it’s a double-edged sword. Without measurement, you’re also excluded from the most consequential debates that shape the future of the business and how it serves its audiences. Measurement can be a burden—but it’s also a bridge to better things. Don’t fall into the trap of taking comfort in its absence.

Let’s explore. Here are the risks that emerge when design isn’t measured—or worse, when its contributions are ignored altogether.

Conflating delivery with design

Treating design as a vendor instead of a partner

Flying blind into development

Wasting resources and shortening the runway

Focusing on the wrong solution or audience

Worsening organizational silos

Veering away from audience needs

Missing critical learning opportunities

Weakening design’s role in strategy

Conflating delivery with design

One of the biggest risks of not measuring design is that it gets reduced to delivery. Think of delivery as the output—things like user interfaces, campaign materials, or prototypes. But design is so much more than that. It’s the process of solving problems, uncovering insights, and driving strategy. Design is the journey much more than it’s the destination.

When organizations only value the outputs and skip measuring the process, they miss out on the real impact of design. It shifts the focus from how we solve problems to how fast we can churn out artifacts. And that’s not just bad for design—it’s bad for the organization and it’s bad for the audience. Without recognizing the process, design becomes less about building solutions and more about ticking boxes, which leads directly to our next point.

Mitigation steps

  • Regularly share case studies or project retrospectives that highlight how the design process uncovered insights or influenced strategic decisions.

  • Shift conversations from “What did we ship?” to “What problems did we solve?” during presentations, stand-ups, and stakeholder reviews.

  • Track process-related outcomes like problem discovery, user feedback cycles, and the success rate of validated concepts to show the value beyond the artifact.


Treating design as a vendor instead of a partner

When design isn’t measured, it often gets treated like a vendor. Teams come to design with orders like a drive-thru—“We need a wireframe for this!”—instead of involving them as partners in solving the actual problem. This transactional mindset keeps design at arm’s length, which means it’s left out of key strategy conversations.

The risk? Solutions that lack the user connection design brings to the table. Teams end up building in isolation, relying on assumptions instead of insights. Worse, it perpetuates silos, making it harder for design to work cross-functionally and weakening the end-to-end experience.

Mitigation steps

  • Involve designers early in product and strategy discussions to ensure they’re partners in defining problems and solutions.

  • Encourage teams to frame requests in terms of the problem they’re trying to solve rather than what they need designed.

  • Regularly involve design leads in roadmap discussions, strategic planning, and executive meetings.


Flying blind into development

Without design measurement, organizations often dive headfirst into development armed only with ego and conjecture. Leaders guess at what users need and skip the part where they connect with actual humans.

This leads to unnecessary risks:

  • Wasted development cycles on features no one asked for.

  • Products that miss the mark entirely.

  • A culture that celebrates “gut instinct” over user connection.

When you don’t measure design, you lose the safety net of validation and iteration. Instead of building confidence, you’re just…building.

Mitigation steps

  • Advocate for lightweight research phases (e.g., user interviews, surveys) to validate assumptions before development begins.

  • Build in mechanisms (like usability testing or beta testing) to gather user input throughout development.

  • Share findings from research and testing broadly, tying them to tangible product decisions to build credibility and trust in the process.


Wasting Resources and Shortening the Runway

For early-stage startups (or really any stage organization), every dollar counts. But without measuring design, organizations risk wasting limited resources on the wrong solutions, audiences, or priorities.

Imagine burning through months of runway developing a feature for a hypothetical user, only to learn it doesn’t resonate—or worse, it’s irrelevant. Measuring design keeps teams focused on what works and what’s needed, saving time, money, and sanity.

Mitigation steps

  • Regularly connect design priorities to business KPIs, like retention, revenue, or customer satisfaction, to ensure alignment.

  • Focus on small, testable initiatives before committing to full-scale development to validate ideas quickly.

  • Track the efficiency of design efforts (e.g., reduced rework, faster validation cycles) to show how they conserve resources.


Measurement can be a burden—but it’s also a bridge to better things.

Focusing on the Wrong Solution or Audience

Without measurement, it’s incredibly easy to miss the mark entirely—solving the wrong problem, targeting the wrong audience, or both.

For example:

  • Are you optimizing an onboarding flow for new users when churn is really happening three months in?

  • Are you building features for power users while ignoring the first-time user experience?

Design measurement ensures that the team’s efforts are grounded in user insights, not gut feelings.

Mitigation steps

  • Use research to create accurate personas that guide decisions and keep teams focused on the right audience.

  • Start every project with a validated problem statement to ensure alignment before ideation begins.

  • Map user journeys to identify gaps, pain points, and opportunities that help guide focus toward the right solutions.


Worsening Organizational Silos

Design is often the bridge that connects product, marketing, engineering, and other teams. But when design isn’t measured, it’s easier for organizations to silo it.

The irony is that isolating design doesn’t just weaken design—it weakens everyone. Silos become stronger, communication breaks down, and the big picture suffers. Measuring design is a way of reinforcing its role as a connector, not just a producer.

Mitigation steps

  • Hold joint workshops, retrospectives, or ideation sessions to foster connections between design and other teams.

  • Tie design outcomes to broader team or company OKRs, ensuring all teams have a stake in the same success.

  • Define how design works with other teams (e.g., product, engineering) in partnership agreements to clarify expectations and promote collaboration.


Veering Away from Audience Needs

When design measurement is absent, it’s easier for teams to drift away from the needs of the people they’re supposed to serve. The work becomes less about solving real problems and more about checking boxes or hitting internal goals that don’t resonate with users.

This isn’t just bad for your users—it’s bad for your mission. An organization that forgets its audience loses its sense of purpose, and the work quickly becomes hollow.

Mitigation steps

  • Regularly bring user insights into team stand-ups or sprint planning to keep the audience front and center.

  • Conduct ongoing user interviews or usability tests to ensure user needs are understood and prioritized.

  • Track Key Experience Indicators (like satisfaction, effort, or task success) to evaluate how well solutions align with user needs.


Missing Critical Learning Opportunities

Every design initiative is an opportunity to learn—not just about what works, but about what doesn’t. Without measurement, those learning opportunities slip through the cracks.

  • You might miss insights that could have led to a critical pivot.

  • You might overlook feedback that could inspire an entirely new product or business line.

  • You might fail to see how one small tweak could create a massive ripple effect across the user experience.

Measuring design isn’t just about proving value—it’s about uncovering opportunities for growth and innovation.

Mitigation steps

  • Use retros to reflect on what’s been learned from both successes and failures.

  • Create a centralized repository for user research findings, testing data, and key learnings to ensure they’re accessible for future projects.

  • Promote a culture of testing and iteration, where every project includes an explicit “What did we learn?” phase.


Design is the journey much more than it’s the destination

Weakening Design’s Role in Strategy

Finally, not measuring design diminishes its role in the larger strategy. Without data to back up its impact, design becomes an afterthought in decision-making processes.

When design isn’t present in the strategy conversation, the solutions are weaker. Design isn’t just about making things look good—it’s about making things work.

Mitigation steps

  • Share success stories, metrics, and examples of design’s strategic contributions in leadership meetings.

  • Clearly articulate design’s role in driving the business forward through shared documents or team charters.

  • Ensure design leaders have a seat at the table in strategic planning and decision-making processes.


Don’t Take Comfort in the Absence of Measurement

Measurement can feel like a burden, but it’s a necessary one. It’s what gets you into the rooms where the big decisions happen. It’s what ensures your team is seen as a partner, not just a producer. And it’s what connects your work to the mission you’re all there to serve.

So, while it might be tempting to think, “They can’t measure us, so they can’t criticize us,” remember: that same comfort keeps you out of the conversations that matter most.

Previous
Previous

The challenges in measuring design

Next
Next

Your EHR Sucks