Short answer

Designers and product managers must move beyond simply collecting data to actively integrating it into a structured process for feature ideation, validation, and prioritization.

Field
User-Centred Design
Source
Malmö University Publications (Malmö University) (2016)
Method
Longitudinal multiple-case study and systematic literature review
Evidence
Strong effect

Effectively collecting and utilizing customer feedback and product data is crucial for software companies to ensure new features deliver genuine value, rather than risking development on features that do not meet user needs. This user-centred design research insight is drawn from a 2016 study published in Malmö University Publications (Malmö University). Using Longitudinal multiple-case study and systematic literature review, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Designers and product managers must move beyond simply collecting data to actively integrating it into a structured process for feature ideation, validation, and prioritization.

Study
User-Centred DesignHigh ImpactStrong effect

Leveraging Customer Data for Value-Driven Software Feature Development

Effectively collecting and utilizing customer feedback and product data is crucial for software companies to ensure new features deliver genuine value, rather than risking development on features that do not meet user needs.

Malmö University Publications (Malmö University) · 2016

01

Key Findings

  • 01Software companies collect substantial amounts of customer feedback and product data.
  • 02Companies often struggle to effectively use the collected data in their development processes.
  • 03The impact of customer feedback changes over the product lifecycle.
  • 04Lack of data sharing hinders companies from fully benefiting from customer feedback.
  • 05There is a risk of prioritizing features that do not provide customer value due to ineffective data utilization.
02

Application

Design takeaway

Designers and product managers must move beyond simply collecting data to actively integrating it into a structured process for feature ideation, validation, and prioritization.

How to apply

Establish a feedback loop where customer insights are continuously gathered, analyzed, and directly inform the design and iteration of software features.

Project actions

  • 01When researching user needs, think about how you will collect and use the data you gather.
  • 02Consider how different types of user feedback (e.g., surveys, interviews, analytics) can be combined for a richer understanding.
03

Method & Evidence

AimHow can software development companies systematically collect and effectively utilize customer feedback and product data to drive the development of valuable features throughout a product's lifecycle?
MethodLongitudinal multiple-case study and systematic literature review
ProcedureThe research involved a two-year longitudinal study across multiple software companies, complemented by a comprehensive review of existing literature on customer feedback collection and utilization in software development.
ContextSoftware product development

Variables

IV["Collection of customer feedback and product data","Sharing of collected data"]
DV["Development of features that deliver value","Prioritization of features"]
CV["Company size","Type of software product","Product lifecycle stage"]
04

Strengths & Limitations

Strengths

  • +Longitudinal study design provides insights into evolving data impact.
  • +Multiple-case study approach offers broader applicability within the software domain.

Limitations

It can be difficult to get access to real customer data from companies for a design project. You might have to rely on simulated data or user testing feedback.

Reliability & validity

The reliability of findings is supported by the longitudinal nature of the case study and the systematic literature review. Validity is enhanced by the multiple-case approach, though generalizability to all software contexts may be limited.

Think critically

To what extent can 'data-driven' decision-making truly replace qualitative user empathy and intuition in software development?

05

Design Principles

"Data-informed feature development prioritizes user value by systematically analyzing and acting upon customer feedback and product usage patterns."

In today's connected product landscape, vast amounts of user data are available. However, the challenge lies in systematically processing this information to inform design decisions. Failing to do so can lead to wasted development resources on features that ultimately do not resonate with the target audience, impacting user satisfaction and market success.

06

What This Means for Your Design

Companies get lots of information from customers, but they don't always use it well, which can lead to making features that people don't actually want or need.

How to use in your project

  • 1.Reference this study when discussing the importance of user research and data analysis in justifying design choices or identifying user needs.
07

Add to My Project

08

Quick Cite

Paragraph starter

This research highlights the critical need for effective data utilization in product development. By systematically collecting and analyzing customer feedback and product data, design teams can ensure that developed features align with user needs and deliver tangible value, thereby mitigating the risk of investing in features that do not resonate with the target market.

09

Source

Malmö University Publications (Malmö University)

Developing the right features: the role and impact of customer and product data in software product development

journal · 2016

View source

Questions About This Research

What does the research say about leveraging customer data for value-driven software feature development?
Designers and product managers must move beyond simply collecting data to actively integrating it into a structured process for feature ideation, validation, and prioritization. Evidence: Malmö University Publications (Malmö University) (2016).
Why does "Leveraging Customer Data for Value-Driven Software Feature Development" matter for design?
In today's connected product landscape, vast amounts of user data are available. However, the challenge lies in systematically processing this information to inform design decisions. Failing to do so can lead to wasted development resources on features that ultimately do not resonate with the target audience, impacting user satisfaction and market success.
How can designers apply this research?
Designers and product managers must move beyond simply collecting data to actively integrating it into a structured process for feature ideation, validation, and prioritization.
What were the main findings?
Software companies collect substantial amounts of customer feedback and product data.. Companies often struggle to effectively use the collected data in their development processes.. The impact of customer feedback changes over the product lifecycle.. Lack of data sharing hinders companies from fully benefiting from customer feedback.
What research method was used?
Longitudinal multiple-case study and systematic literature review.
How strong is the evidence?
Evidence strength is rated Strong effect, based on a 2016 journal from Malmö University Publications (Malmö University).
What should I do differently in my next project?
Establish a feedback loop where customer insights are continuously gathered, analyzed, and directly inform the design and iteration of software features.
What are the limitations?
The study focused on large software companies, and findings may not be directly generalizable to smaller organizations or different industries. The effectiveness of the proposed framework may vary depending on company culture and existing processes.