Gartner Research

Applying the Gartner UX Model to Application Development Practices

Published: 25 February 2016

ID: G00281127

Analyst(s): Danny Brian

Summary

A great application user experience does not happen by chance. It requires concerted practices on the part of development teams and UX professionals. This guidance framework provides best practices to help application teams deliver a better user experience.

Table Of Contents

Problem Statement

The Gartner Approach

The Guidance Framework

  • Prework: Realize That UX Is Not (Purely) a Creative Pursuit
  • Practice: Conduct User Studies
    • The Win-Win-Win of Real User Engagement
    • Why Not Just Conduct a Survey?
    • Discovering Untapped Opportunities
    • Ongoing and Iterative
    • Distilling the Results
    • Just Do It
    • A Development Team's First User Study
    • The Relationship of User Studies to Other Framework Components
  • Practice: Define and Apply Personas and Scenarios
    • Define Early, and Refine Constantly
    • A Clear Foundation for Project Planning
    • Scenarios Fill in the Gaps
    • Utilize Personas and Scenarios in All Projects
    • A Persona Success Story
    • The Relationship of Personas and Scenarios to Other Practices
  • Practice: Scope Application Features Narrowly
    • Simpler Is Always Better
    • Limit Use Cases With Prejudice
    • Improve Use Cases
    • There Is No Downside to Narrow Scope
    • The Relationship of Narrow Scoping to Other Practices
  • Practice: Prototype Applications
    • Fail Early, Fail Often
    • Prototyping Is a Group Effort
    • Prototyping Helps Elicit and Clarify Requirements
    • State of the Art: Paper and Whiteboards
    • It's All in the Details
    • The Symptoms of Poor Prototyping
    • A Failure to Prototype
    • The Relationship of Prototyping to Other Framework Components
  • Practice: Utilize Analytics
    • Analytics Tell What, Not Why
    • A/B Testing
    • Application Intelligence
    • Expose the Data
    • The Relationship of Analytics to Other Framework Practices

Risks and Pitfalls

  • Ownership of the User Experience Is Ambiguous
  • Contributors Are Unable to Give or Receive Criticism
  • Analytics Are Safeguarded to Protect Teams
  • Requests for User Studies Get Rejected
  • Sponsors Demand Features Without a Clear Priority

Related Reading

Gartner Recommended Reading

©2020 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates. This publication may not be reproduced or distributed in any form without Gartner’s prior written permission. It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact. While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such. Your access and use of this publication are governed by Gartner’s Usage Policy. Gartner prides itself on its reputation for independence and objectivity. Its research is produced independently by its research organization without input or influence from any third party. For further information, see Guiding Principles on Independence and Objectivity.

Already have a Gartner Account?

Become a client

Learn how to access this content as a Gartner client.