Bhuvan Sarupuri Ph.D.

Standardising Feature Releases

Transforming ad-hoc processes into strategic, repeatable systems

Methods
Interviews, Workshops, Affinity Mapping
Output
Recommendations for 4 departments

Note: Collaborative research and design work completed with TOPdesk team members.

The Challenge

TOPdesk's feature releases lacked standardisation, creating inconsistent user experiences, burdened UX teams, and development efforts that failed to generate expected adoption.

Our product's feature releases lack a standardised approach

This operational inefficiency was actively undermining product value, team productivity, and customer satisfaction.

Why This Matters

🎯 User Adoption at Risk

Without consistent communication and onboarding, users struggle to discover and adopt new features, reducing ROI on development investments.

⚙️ Team Efficiency Compromised

UX designers and researchers spend excessive time reinventing release processes instead of focusing on innovation.

🚀 Development Velocity Slowed

Product teams face significant bottlenecks from lack of standardised workflows, delaying time-to-market.

👥 Customer Insights Missing

Without standardised approaches, teams lack mechanisms to address perception issues, measure communication effectiveness, track feature adoption, or collect post-release feedback systematically.

Research Approach

1

Discovery Workshop

Collaborative session with UX researchers across product teams to map current practices, decision factors, and identify gaps in existing processes.

2

Stakeholder Interviews

In-depth conversations with 7 key stakeholders: 4 Product Owners/Managers, 2 User Guidance team members, and 1 Copywriter.

3

Affinity Mapping

Systematic synthesis of research data, clustering insights into actionable categories and identifying patterns across teams.

Research Questions

From Raw Data to Insights

Our affinity mapping process transformed hundreds of interview notes into structured, actionable insights:

Miro board of the affinity mapping session: clustered sticky notes covering release communication channels, how teams decide a release approach, the roles involved, and what did not work
Affinity Mapping Session: The working board — interview notes and workshop output from 7 stakeholders, before clustering

Key Findings

Through affinity mapping, insights emerged across four critical categories:

Workshop output grouped into solutions, communication, small tags and workshop findings, each cluster listing detailed notes on release practice
Categorised Findings: The same material clustered into four groups: Solutions, Communication, Small tags, and Workshop findings

1. Communication Fragmentation

2. Process Standardisation Gaps

3. Documentation Challenges

4. Measurement & Feedback

Mapping the Existing Process

We documented the current release strategy and journey to understand the existing state and identify opportunities for improvement:

How Might We...

Transforming insights into actionable opportunities across stakeholder groups

User Guidance Teams

  • Content Timing: Get content out on time
  • Visibility: Know features releasing soon
  • Capacity: Maximize small team capacity
  • Documentation: Update portal on time
  • Collaboration: Connect dev-teams with UG
  • Info Gathering: Collect all necessary input

Development Teams

  • Standardisation: Shared efficient approach
  • Consistency: Efficient release process
  • Speed: Deliver features quickly
  • User Delight: Design enjoyable solutions
  • Engagement: Maintain feedback flow
  • Measurement: Measure user satisfaction

End Users

  • Usability Testing: Involve users effectively
  • Feature Flags: Standardise implementation
  • Feedback Loops: Create standard loops
  • Transparency: Set realistic expectations
  • Communication: Map efficient channels
  • Alignment: Standardise feedback process

Customers

  • Perception: Address update concerns
  • Measurement: Track communication effectiveness
  • Adoption: Measure feature adoption
  • Feedback: Standard post-release loops

Deliverables & Impact

This research produced actionable recommendations across the organisation:

📋

Product Management

Standardised decision frameworks for release approaches

🎨

UX Guild

Reusable solution patterns and templates

📚

User Guidance

Earlier integration and clearer content requirements

📢

Marketing

Aligned communication strategies across channels

Further down, we aim to align with the departments above and create a release strategy for the entire product.

The Case for Standardising

This is the argument the research supports, not a set of results. Nothing below was measured — the study produced recommendations, and instrumenting the release process to test them is the next step rather than something already done.

↑
User Adoption Rate

Clear communication helps users discover and adopt features faster

⚡
Team Velocity

Standardised processes free teams to innovate rather than reinvent

💰
Development ROI

Features users actually use justify resources spent building them

🎯
Competitive Edge

Consistent improvements demonstrate active product evolution

The Bottom Line

By standardising the feature release process, TOPdesk can transform from ad-hoc release management to a strategic, repeatable system. This research provides the foundation for improving customer satisfaction, team efficiency, and product competitiveness—turning internal process improvement into measurable business value.