Cultural transformation in a data-driven organisation

[Hero image: workshop wall covered in sticky notes]

Recognising the need for change

Our organisation had built its reputation on technical expertise and analytical capabilities in the banking and data sector. While our data provided valuable insights, the company's strong expert identity had inadvertently created barriers to delivering accessible solutions. As the sole designer, I identified that our products were becoming increasingly complex, requiring extensive explanation for customers to derive value. The prevailing mindset was that as experts, we should tell customers what they need rather than asking them what would be valuable.

Strategic approach to transformation

Changing culture in a risk-averse environment required thoughtful strategy. I developed several approaches to shift the organisation's perspective:

• Creating frameworks that acknowledged different user needs
• Regularly facilitating workshops to bring stakeholders into the design process
• Bringing customer voices directly into the organisation through research
• Demonstrating the business value of simplified, insight-focused solutions
• Applying the CBAIQ Design Excellence Framework to guide our approach

The goal was to complement our analytical strengths with user-centred thinking—showing how human-centred approaches could amplify existing expertise.

User archetypes transform product thinking

One of the most effective methods I used in this transformation was introducing user archetypes based on data proficiency. This framework represented a significant shift in how we viewed our customers and their needs. The framework included three primary archetypes:

• Experts: Users who prefer raw data to conduct their own analyses
• Explorers: Users who like to manipulate visualisations to discover trends
• So Whaters: Users who need clear, actionable insights without complexity

This provided a shared language for discussing user needs and helped the organisation understand the diverse ways customers interact with our products.

The insight that changed everything

The most significant breakthrough came from helping the organisation recognise that even the most technical users eventually need to communicate findings to stakeholders who want clear, actionable insights. I shared this perspective in various forums across the organisation. The insight resonated deeply with leadership, who quickly adopted both the language and concept in their own communications. This perspective shift made user-centred design relevant to everyone. It wasn't just about serving non-technical users—it was about ensuring all data analysis ultimately delivers meaningful insights.

Breaking the expert feedback loop

I identified a self-reinforcing cycle that limited our perspective:

• Products were optimised for technically proficient users
• Only those users engaged with our solutions
• We received feedback exclusively from this group
• Less technically proficient users were increasingly alienated

Presenting this analysis helped leadership recognise the business opportunity in designing more accessible solutions. It positioned human-centred design not as a nice-to-have but as a strategic business imperative.

From resistance to enthusiasm for user research

Initially, there was hesitation around conducting user research. The attitude reflected our identity as experts—we shouldn't need to ask customers what they wanted; we should already know. To address this, I began attending customer calls and help sessions to observe firsthand where friction occurred. These experiences provided compelling stories that I could bring back to the team, making user challenges concrete rather than theoretical. As the archetypes framework gained traction, resistance to research began to dissolve. The team became more comfortable with asking questions, showing early iterations, and prototyping with user feedback. Research was increasingly seen as a precision tool rather than an admission of uncertainty.

Workshop-driven collaboration builds momentum

Facilitating workshops became a key method for bringing diverse stakeholders together around user needs. These collaborative sessions, which I regularly conducted throughout projects, helped align teams around a common understanding of user journeys and pain points. For example, during one project, I facilitated sessions where stakeholders participated in mapping customer journeys and identifying pain points. This approach created shared ownership of the user experience, with participants becoming invested in addressing the challenges they helped identify. These workshops broke down silos between technical, business, and customer-facing teams, helping everyone see how their role contributed to the overall user experience.

Evidence of cultural transformation

As the shift gained momentum, several indicators showed the transformation was taking hold:

• Leadership consistently used the archetype language in product strategy discussions
• Other business units began using the framework in their own work
• Team members started initiating their own user research activities
• Products were increasingly evaluated based on insight accessibility
• Simplified solutions emerged that reduced both development costs and support needs

The approach evolved from being design-driven to design-supported, with teams across the organisation adopting user-centred principles in their work.

Impact on product development

The cultural transformation had tangible effects on how products were conceived and delivered:

• Simplified solutions: Products became significantly less complex and more focused on delivering clear insights.
• Reduced delivery costs: More straightforward products required less development effort and support.
• Faster delivery cycles: With clearer priorities based on user needs, teams could build and ship more efficiently.
• Evidence-based decisions: User feedback began actively shaping product decisions, often challenging internal assumptions.

Key learnings for cultural transformation

This journey revealed several principles that continue to guide our approach to design leadership:

• Give people language they didn't have: Creating frameworks and shared vocabulary makes invisible concepts discussible and actionable.
• Show rather than tell: Bringing stakeholders into direct contact with user challenges is more powerful than theoretical arguments.
• Position design as business strategy: Connecting human-centred approaches to business outcomes secures leadership buy-in and sustains change.
• Embrace small wins: Cultural change happens gradually through consistent reinforcement and visible successes.
• Empower others to lead: True transformation occurs when team members begin initiating human-centred practices themselves.

The transformation to a user-centred culture has fundamentally changed how the organisation approaches product development and customer engagement. What began as a design initiative has become an organisational advantage, enabling us to deliver more value to more customers with greater efficiency.