Building For Customers
a deep dive into customer-first design
Welcome back, folks! Hope you’ve all been keeping warm with the recent snowy days we’ve been experiencing on the East Coast of North America.
I’m very excited to share this week’s post with you all for two reasons: (a) it’s something I’ve been learning more about and (b) I’ve written about customer-first design before, and this post feels like a deeper dive.
If you’re interested in customer-first design and building products around sustainable design principles, this might be a fun read for you.
Happy reading!
Where Customer-First Design Starts to Slip
Early in a product’s life, customer-first design happens almost by default. Feedback is immediate, consequences are visible, and PMs feel the impact of decisions quickly.
As products mature, that proximity fades. Customer insight starts arriving through summaries and dashboards rather than direct interaction, while decisions involve more stakeholders operating under tighter timelines. In that environment, customer impact is acknowledged, but it no longer anchors the conversation.
At this point, customer-first design stops functioning as a constraint and begins to behave like a preference, which makes it vulnerable during roadmap negotiations and prioritization discussions.
Abstraction Is the Real Risk
One of the quiet ways customer-first design erodes is through abstraction.
As customers are represented through segments and averages, decision-making becomes more efficient but less precise.
Experiences with the greatest emotional weight are often treated as edge cases, even though they are the moments that shape trust and long-term loyalty.
PMs who stay customer-first work deliberately against this drift. They keep real customer context present long after discovery phases are complete, often by engaging directly with support conversations, onboarding sessions, and churn explanations. This isn’t about staying close to the customer out of principle; it’s about maintaining high-quality inputs into product decisions as scale increases.
Efficiency Quietly Changes Who Does the Work
Efficiency is necessary for scale, but when it becomes the dominant design driver, effort begins to move outward. Processes get optimized for internal flow, and the resulting complexity shows up in the customer experience through longer paths to resolution and inflexible workflows.
Customer-first PMs pay close attention to where this shift occurs. They are explicit about which moments in the customer journey deserve protection, even when doing so introduces operational complexity internally. These decisions rarely surface as roadmap items, but they play a significant role in how customers experience the product over time.
Customer-First Design Requires a Longer View
Another reason customer-first design is difficult to sustain is that its benefits rarely appear immediately.
Trust compounds slowly, while delivery metrics and revenue signals move quickly. In short planning cycles, it becomes easy to favor outcomes that are visible now over those that matter later.
PMs who maintain a customer-first approach counter this by tracking longer-horizon signals alongside near-term performance indicators. Patterns in repeat usage, changes in support sentiment, and customer behavior during failure moments provide important context that helps teams avoid mistaking speed for progress.
Failure Is Where Customer-First Design Becomes Obvious
Customers rarely evaluate products based on ideal scenarios. Their judgment is shaped by how systems behave when something goes wrong.
Moments involving errors, recovery, and escalation reveal whether a product respects the user’s time and attention. These experiences are often under-designed because they don’t align cleanly with success metrics, yet they carry disproportionate weight in shaping perception.
PMs who stay customer-first treat failure as a core part of the product experience, designing recovery paths that feel clear and supportive rather than procedural.
What Customer-First Design Looks Like in Practice for PMs
For PMs, staying customer-first is less about intention and more about how you structure your day-to-day decisions.
✅ One of the most effective moves is to treat customer impact as a required input rather than supporting context. Before prioritization discussions, strong PMs explicitly articulate how each option changes customer behavior, not just metrics. Framing decisions in terms of what customers will now do more easily, do less often, or stop doing altogether forces trade-offs into the open and prevents the conversation from drifting toward internal convenience.
✅ Another critical practice is maintaining direct exposure to customer friction long after discovery phases end. PMs who stay customer-first create recurring touchpoints with real customer signals, whether that’s regularly reviewing support conversations, listening to sales calls, or reading churn explanations firsthand. This keeps decision inputs grounded even as products scale and teams specialize.
✅ Customer-first PMs also design with failure in mind. Instead of treating errors and edge cases as secondary concerns, they ask early how recovery should work and who carries the burden when something breaks. This shifts design conversations away from ideal flows and toward realistic experiences, where trust is most easily gained or lost.
✅ Finally, customer-first PMs are deliberate about where efficiency is allowed to win. They identify moments in the customer journey that shape perception and actively protect them, even when doing so introduces internal complexity. This clarity makes trade-offs easier to defend and prevents gradual erosion of the experience.
None of these practices require new tools. They require discipline and consistency.
Final Thoughts
Customer-first design is not something PMs lose because they stop caring. It fades when systems reward speed, efficiency, and scale without equally rewarding judgment.
The PMs who sustain customer-first design understand that their real job is not feature prioritization. It is decision quality. That quality depends on whether customer reality is present, concrete, and influential when trade-offs are made.
Over time, products reflect the decisions that shaped them. When customers are structurally present in those decisions, trust compounds. When they aren’t, no amount of intention can compensate.
Customer-first design survives when PMs build it into how decisions are made, not just how strategies are described.