Derribar Ventures on User-Centric Design: 5 Pillars Every Team Needs – London Business News | London Wallet

Most products fail not because the technology is weak, but because no one stopped to ask the user what they actually needed. Derribar Ventures Limited highlights a persistent gap in product development: teams build what they can, not what they should. The result? Feature-bloated platforms that solve problems nobody has. This article breaks down a practical, repeatable framework for putting users at the centre of every product decision – from discovery to delivery.

Why user-centricity is a revenue strategy, not just a philosophy

There is a tempting misconception that user-centric design is a “nice to have” — something reserved for consumer apps, while other companies focus on specs and scalability. Derribar Ventures notes that this thinking is outdated and, frankly, expensive.

The numbers back this up. According to a 2023 Deloitte report, companies that prioritize customer-centric strategies are 60% more profitable than those that don’t. Meanwhile, research by PwC found that 73% of decision-makers say customer experience is a key factor in their purchasing decisions — regardless of industry or company size.

User-centricity is not about appearance alone. User-centricity is about removing friction, speeding up adoption, and creating products that people buy again and again. When companies take user experience as a strategic approach rather than just a design department concern, they reap the compounded rewards of retention and growth in revenue.

Five pillars of user-centric product development

Unlike the typical advice on generic principles, Derribar Ventures Limited outlines an easily adaptable approach, which is comprised of five pillars, and can be used by any product team regardless of its size or domain of operations.

Pillar 1: Discovery before assumptions

The biggest waste in product development is building confidently in the wrong direction. Derribar Ventures highlights that effective discovery involves more than a handful of customer interviews before a roadmap meeting. It requires:

• Continuous user research cadences — not one-off sprints before launches, but monthly or biweekly conversations with actual users.
• Jobs-to-be-done analysis — understanding the outcome users hire your product to achieve, not just the features they request.
• Cross-functional participation — engineers and commercial teams joining discovery calls, not just designers and product managers.

The goal is to replace internal assumptions with external evidence before a single line of code gets written.

Pillar 2: Segmented empathy mapping

Not all users are the same, and treating them as a monolith is a common trap. A product might serve administrators, everyday end-users, and executive sponsors — each with different motivations and pain points.

Derribar Ventures suggests building empathy maps segmented by user role, not just buyer persona. For each segment, teams should document:

1. What the user is trying to accomplish daily.
2. What frustrates them about current solutions.
3. What success looks like in their own words — not in your marketing language.

This granularity prevents the classic mistake of optimizing for the person who signs the check while ignoring the person who uses the product every day.

Pillar 3: Prototype and validate before you scale

Many teams skip low-fidelity validation because they feel pressure to ship “complete” features. This is a costly error. Rapid prototyping and validation cycles allow teams to:

• Test core assumptions with clickable mockups before committing engineering resources.
• Identify usability issues at a stage where changes cost hours, not quarters.
• Generate internal alignment by showing stakeholders tangible artifacts instead of slide decks.

A simple rule of thumb: if your team has not put a prototype in front of at least five real users before development begins, you are guessing.

Pillar 4: Measure behaviour, not just satisfaction

Surveys and NPS scores tell you what users say. Behavioural analytics tell you what they do. Derribar Ventures Limited believes that truly user-centric organizations track both, but weigh behaviour more heavily.

Key behavioural metrics product teams should monitor include:

• Time-to-value — how quickly a new user reaches their first meaningful outcome.
• Feature adoption depth — not just whether a feature is clicked, but whether it is used repeatedly and in the intended workflow.
• Drop-off mapping — identifying the exact moments users disengage or abandon a flow.

Teams that track what users actually do — rather than what they say in surveys — consistently make sharper product decisions and see stronger engagement over time. The lesson is clear: let user behavior guide iteration, not internal opinions.

Pillar 5: Close the feedback loop publicly

Gathering feedback means nothing if users never see the impact. Derribar Ventures suggests that companies create visible, structured feedback loops. This can look like:

• A public product changelog that connects shipped features to specific user requests.
• Quarterly “you asked, we built” communications sent directly to customers.
• In-app notifications that surface relevant new features to the users who requested them.

Closing the loop does two things: it builds trust, and it trains users to keep giving you the insights you need. Both are compounding advantages.

Common pitfalls Derribar Ventures sees in product teams

Even well-intentioned teams fall into patterns that undermine user-centricity. Derribar Ventures Limited highlights three of the most frequent:

1. Confusing stakeholder requests with user needs. Internal executives and partner demands often drown out the voice of the actual user. A feature requested by a sales team to close one deal is not the same as a validated user need.
2. Over-indexing on competitors. Watching the market is smart; copying competitor features without validating whether your users need them is not. It leads to parity, not differentiation.
3. Treating accessibility and onboarding as afterthoughts. If a powerful feature requires a training manual, it is not user-centric — it is engineering-centric with documentation attached.

Putting it into practice: Where to start

Derribar Ventures Limited recommends that teams resist the temptation to try to do a full refresh all at once. Rather, pick one of the pillars highlighted above and spend an entire quarter on it. Start with discovery if your team has not been working with an actual customer in the last 30 days. Start with behavioural measurement if you have done research, but do not have the technology in place.

Building user-centric products is not a destination — it is a discipline. Derribar Ventures’ take is simple: the companies willing to embed this discipline into their culture today will be the ones setting the standard tomorrow. The tools and frameworks exist. The data is accessible. The only remaining variable is whether your team is willing to listen before it builds.