Short answer

Incorporate Appreciative Inquiry techniques into your user research process to uncover a broader spectrum of user needs and aspirations, moving beyond just problem-solving.

Field
User-Centred Design
Source
Academic Publication (2010)
Method
Action Research / Case Study
Evidence
Strong effect

By shifting the focus from problems to past successes and future aspirations, Appreciative Inquiry can uncover a richer and more comprehensive set of user requirements. This user-centred design research insight is drawn from a 2010 study published in Academic Publication. Using Action research / case study, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Incorporate Appreciative Inquiry techniques into your user research process to uncover a broader spectrum of user needs and aspirations, moving beyond just problem-solving.

Study
User-Centred DesignHigh ImpactStrong effect

Appreciative Inquiry enhances user requirement elicitation by focusing on success and future vision.

By shifting the focus from problems to past successes and future aspirations, Appreciative Inquiry can uncover a richer and more comprehensive set of user requirements.

Academic Publication · 2010

01

Key Findings

  • 01Appreciative Inquiry increased the number of unique requirements gathered.
  • 02It identified more quality-based (non-functional) and forward-looking requirements.
  • 03Participants reported positive attitudes towards the process.
  • 04The method showed benefits for the requirements obtained and the overall elicitation process.
02

Application

Design takeaway

Incorporate Appreciative Inquiry techniques into your user research process to uncover a broader spectrum of user needs and aspirations, moving beyond just problem-solving.

How to apply

When initiating a design project, facilitate sessions that explore past successes and collaboratively envision an ideal future state to uncover user requirements.

Project actions

  • 01When conducting user interviews, start by asking about positive experiences related to the product or service.
  • 02Use future-oriented questions to prompt users to describe their ideal scenarios.
03

Method & Evidence

AimHow can Appreciative Inquiry be effectively applied to elicit user requirements, and what are its benefits compared to traditional methods?
MethodAction Research / Case Study
ProcedureThe research involved multiple studies, including comparisons with traditional requirement elicitation methods, quasi-experiments across different development phases, and integrated case studies. Data was collected on the quantity and type of requirements, user and developer attitudes, and the effectiveness of the Appreciative Inquiry process itself, considering factors like facilitator experience and project type.
ContextSoftware development and project management

Variables

IVMethod of requirement elicitation (Appreciative Inquiry vs. Traditional)
DVNumber and type of requirements gathered, user/developer attitudes
CVProject phase, facilitator experience, team effectiveness, project type
04

Strengths & Limitations

Strengths

  • +Focuses on positive aspects, fostering engagement.
  • +Can uncover innovative solutions by exploring ideal futures.

Limitations

The success of Appreciative Inquiry can be heavily influenced by the facilitator's ability to guide the conversation positively and constructively.

Reliability & validity

The validity of the findings relies on the qualitative assessment of requirements and attitudes, which can be subjective. Reliability might be improved through standardized facilitation protocols and multiple coders for requirement analysis.

Think critically

To what extent can the positive framing of Appreciative Inquiry mask underlying critical issues that need to be addressed for successful product development?

05

Design Principles

"Focus on strengths and future possibilities to unlock innovative user requirements."

Traditional methods often highlight pain points, which can limit the scope of innovation. Appreciative Inquiry encourages a more positive and forward-looking perspective, potentially leading to more innovative and user-aligned design solutions.

06

What This Means for Your Design

Instead of just asking users what's wrong, ask them about what's worked well in the past and what their ideal future looks like. This helps find better ideas for new designs.

How to use in your project

  • 1.Describe how you used Appreciative Inquiry principles to gather user requirements, highlighting how it differed from traditional methods and the benefits observed.
07

Add to My Project

08

Quick Cite

Paragraph starter

To ensure comprehensive user requirements, an Appreciative Inquiry approach was employed. This method focused on identifying past successes and envisioning future ideal states, which yielded a greater number of unique and quality-based requirements compared to traditional problem-focused elicitation techniques.

09

Source

Academic Publication

Eliciting User Requirements Using Appreciative Inquiry

journal · 2010

View source

Questions About This Research

What does the research say about appreciative inquiry enhances user requirement elicitation by focusing on success and future vision?
Incorporate Appreciative Inquiry techniques into your user research process to uncover a broader spectrum of user needs and aspirations, moving beyond just problem-solving. Evidence: Academic Publication (2010).
Why does "Appreciative Inquiry enhances user requirement elicitation by focusing on success and future vision." matter for design?
Traditional methods often highlight pain points, which can limit the scope of innovation. Appreciative Inquiry encourages a more positive and forward-looking perspective, potentially leading to more innovative and user-aligned design solutions.
How can designers apply this research?
Incorporate Appreciative Inquiry techniques into your user research process to uncover a broader spectrum of user needs and aspirations, moving beyond just problem-solving.
What were the main findings?
Appreciative Inquiry increased the number of unique requirements gathered.. It identified more quality-based (non-functional) and forward-looking requirements.. Participants reported positive attitudes towards the process.. The method showed benefits for the requirements obtained and the overall elicitation process.
What research method was used?
Action Research / Case Study.
How strong is the evidence?
Evidence strength is rated Strong effect, based on a 2010 journal from Academic Publication.
What should I do differently in my next project?
When initiating a design project, facilitate sessions that explore past successes and collaboratively envision an ideal future state to uncover user requirements.
What are the limitations?
The effectiveness may depend on the facilitator's skill, team dynamics, and the specific project context. The research was conducted within a software development context, and generalizability to other design fields may require further investigation.