# Increasing Product Value (Glaringly Obvious)

**URL:** <https://forum.zurb.com/t/increasing-product-value-glaringly-obvious/351>\
**Category:** Open topics\
**Created:** [November 8, 2025, 5:33pm UTC](https://forum.zurb.com/t/increasing-product-value-glaringly-obvious/351 "2025-11-08T17:33:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\
**Post date:** [November 8, 2025, 5:33pm UTC](https://forum.zurb.com/t/increasing-product-value-glaringly-obvious/351/1 "2025-11-08T17:33:28Z")

</div>

My recent chat with [David Pereira](https://www.linkedin.com/in/davidavpereira/) about why so many product teams confuse speed with progress was great. David’s work focuses on helping teams shift from output to outcomes, moving past the “feature factory” mindset where shipping more is mistaken for success.

> **[Glaringly Obvious with David Pereira](https://glare.helio.app/interviews/david-pereira#making-design-measurable)**
>
> Podcast Interview: Measure, test, and refine to drive product value

Big ideas:

- **Speed isn’t progress** → More output doesn’t always mean more value.
- **Outcomes matter more than output** → Success is measured by behavior change, not ticket count.
- **Validate before you build** → Test ideas early to learn what’s worth pursuing.
- **Mindset beats methodology** → Frameworks only work when teams focus on clarity and impact.
- **Measure what matters** → Track results that show real progress, not just motion.

* * *

 ![product-value](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/87a507bfb18536e1bc9484843eddf88aed4b650c.jpeg)

David really leans into the idea that progress isn’t about doing more. When teams chase velocity, they risk piling on features that add complexity instead of value. By focusing on validation and learning, teams can shift their energy from activity to outcomes.

The goal of Glare is to align design impact with business impact so teams can create more product value.

How is your team measuring product design success…do your metrics show real progress, or just movement?

---

<div class="post-metadata">

**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\
**Post date:** [November 8, 2025, 8:53pm UTC](https://forum.zurb.com/t/increasing-product-value-glaringly-obvious/351/2 "2025-11-08T20:53:50Z")

</div>

I built on these ideas, aligning them to more of my conversations I’ve been having with design leaders recently.

Product value and design quality are two sides of the same coin, but there’s a language issue in translating these ideas between design teams and stakeholders. More process won’t get you there, and focusing on design outputs has diminishing returns.

> **[Most design leaders want design impact.

But most designers don’t wake up...](https://www.linkedin.com/posts/bryanzmijewski_most-design-leaders-want-design-impact-activity-7392996966152093697-bSU2)**
>
> Most design leaders want design impact.
> 
> But most designers don’t wake up thinking about impact. They think about making great work. The disconnect isn’t ambition. It’s language.
> 
> You don’t get design impact by chasing it. You get it by raising...

 ![creating-design-impact6](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/aafafe8738359d17c35f33a02850306a4fb5725f.png)

---

<div class="post-metadata">

**Author:** ![nathaliesmith](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/nathaliesmith/32/443_2.png) [@nathaliesmith](https://forum.zurb.com/u/nathaliesmith)\
**Post date:** [November 10, 2025, 9:57pm UTC](https://forum.zurb.com/t/increasing-product-value-glaringly-obvious/351/3 "2025-11-10T21:57:24Z")

</div>

Speed without clarity is chaos! Loved this chat a ton, great job here you two!