Beyond the Build: Designing for Impactful Digital Experiences

Originally recorded: May 21, 2025 Guest: Calvin Chopp, Creative Director, BlueModus

Technology is often what gets the credit when a digital project succeeds: the CMS, the integrations, the platform. But the decisions that most directly shape whether users actually succeed on a site are design decisions. They're just less visible.

In Episode 3 of our Beyond the Build webinar series, I sat down with BlueModus Creative Director Calvin Chopp to talk about what design-led innovation actually looks like in practice, how design shapes technical choices (not just aesthetics), and why proof-of-concept work is becoming one of the most valuable things a design team can offer. You can watch the full recording here or read on for a recap of our conversation.

What Design-Led Innovation Actually Means

Calvin started by drawing a distinction most teams don't make explicit enough. Traditional innovation asks: how is this product performing? Design-led innovation asks: who is using this product, and why should they care?

The shift sounds subtle, but the implications aren't. Traditional innovation tends toward incremental improvements: data-driven tweaks to what already exists. Design-led innovation opens the door to bigger questions: Are we solving the right problem? Are we missing an entire segment of users because we've been too focused on the existing experience?

"It's more than thinking about the user interface," Calvin said. "It's thinking user-centric and having that drive the decisions we make."

That mindset also changes the scope of what's on the table. When all decisions flow from existing analytics, the ceiling is the site as it exists today, plus or minus a few improvements. When you step back and ask what users are actually trying to accomplish, before they arrive, while they're on the site, and after they leave, you create room for solutions that would never surface in a heatmap.

How Design Shapes Technical Decisions

One of the more practical parts of the conversation was Calvin's description of how BlueModus runs UX and design discovery in parallel at the start of a project and what that process tends to uncover.

The UX discovery focuses on technical frameworks, business requirements, content models, information architecture, and site maps. The design discovery runs alongside it, asking questions like: if your site could do only three things, what would they be? What sites do you find compelling? What functionality have you always wished you had?

These aren't just strategic exercises. They consistently produce clearer requirements and often lead to those requirements being reframed entirely before development begins. "There have been multiple times where we've helped our clients reframe the issue they were looking to solve and changed the original requirements based on what was uncovered during discovery," Calvin noted.

The other outcome Calvin emphasized was simplicity. He described the goal as "invisible design" — interfaces that feel intuitive because they've been carefully considered, not because they're simple-looking. His example: a storefront door with a pull handle that was meant to be pushed. It's a small moment of friction, but it's the kind of thing good design eliminates. Users shouldn't have to think about how to use the sites we build.

That same discipline extends to architecture. Design decisions made early, reusable components, well-structured content models, modular systems, determine whether a site can grow alongside a client's needs or becomes a constraint the moment they want to do something new.

The Value of Outside Perspective

A recurring theme in the conversation was the underrated value of an outside perspective in design and how often internal teams are limited precisely because they know their product too well.

Stakeholders who have lived with a site for years naturally think in terms of that site. Their mental model is the current experience, with some small improvements. Designers coming in from outside don't carry that constraint. They ask questions internal teams stopped asking years ago.

Calvin was right to note that this only works when trust is established: "It's only as effective as the trust we have between us and our clients," he said. The outside perspective isn't valuable if clients are just handing over a list of tickets and expecting them to be executed. The real opportunity is in an open conversation where expertise is genuinely brought to the table and honestly applied, including having the harder conversations about whether a requested approach is actually the right one.

Proof-of-Concept Work: Making Bold Ideas Tangible

Calvin also talked through something BlueModus has invested in significantly: proof-of-concept exercises. These are clickable prototypes and demos of ambitious ideas. Not work clients have asked for, but work the team believes could benefit them based on what they're hearing and what they're watching in the market.

The value runs in a few directions:

• It de-risks bold ideas. Clients don't have to commit full resources to explore something ambitious. They can react to a tangible prototype before deciding whether to invest.

• It accelerates the conversation. Rather than describing an abstract idea, teams can put something in front of stakeholders that makes the vision concrete and shareable.

• It builds internal momentum. When a client can show a clickable prototype to leadership — "here's what we're thinking" — it's far more effective than a written proposal. It answers the question of whether something is worth pursuing before significant resources are committed.

Calvin described presenting these to clients and watching their reaction shift from "this is interesting" to "how soon can we actually build this?" And then being able to answer: we're already doing this. The proof-of-concept work, especially around user-facing AI integrations, often shows clients what's possible before they've seen it anywhere else in their industry.

That's the agency advantage in a sentence: cross-industry exposure means ideas that haven't been tried in one sector can be adapted from another. In-house teams, no matter how talented, are working within one context. An agency working across dozens of clients and industries brings a much wider surface area of what's been tried, what's worked, and what's next.

Where to Start

Calvin's closing advice was direct: design for user goals, not internal priorities. Stop asking what the team wants to say and start asking what users are trying to do.

That reframe alone surfaces the right questions. And once you're asking the right questions, it becomes much easier to spot where the current experience is falling short and where the real opportunity is.

"Don't be afraid to be the different voice in your internal conversation," Calvin said. "Are we designing for today, or are we designing for something that can change and adapt in the future?"

Interested in what a design-led approach could look like for your next project? Let us walk you through our UX and design discovery process and think through what's possible. Contact us to start the conversation.