🏫
Obvious University
Website
  • 👋Welcome to Obvious University!
  • Strategy
    • Sprints
      • 1️⃣Map
      • 2️⃣Sketch
      • 3️⃣Decide
      • 4️⃣Prototype
      • 5️⃣Test
    • Benchmarking
    • Research
      • 1️⃣Research guide
      • 2️⃣How to recruit users
      • 3️⃣How to conduct an interview well
      • 4️⃣How to take notes
      • 5️⃣How to prep for remote research
      • 6️⃣How to throw a watch party
      • 7️⃣How to create artefacts
  • Working with Features
    • Building with AI
      • 1️⃣Understand the tech
      • 2️⃣Map your product
      • 3️⃣Build a proof of concept
      • 4️⃣LLM Inputs
      • 5️⃣LLM Responses
    • Building Help and Support
      • 1️⃣How to scope a support experience
      • 2️⃣How to design discovery for support
      • 3️⃣How to design a support centre
      • 4️⃣How to write good support articles
  • Product Design
    • Microcopy
      • 1️⃣How to write well
      • 2️⃣How to write phrases
      • 3️⃣How to write messages
      • 4️⃣How to create a voice
    • Typography
      • 1️⃣How to compose type
      • 2️⃣How to create a type scale
      • 3️⃣How to pick typefaces
      • 4️⃣How to pair typefaces
    • Design System
      • 1️⃣Introduction to design systems
      • 2️⃣How to audit a design system
      • 3️⃣How to run a design system pilot
      • 4️⃣How to set up a design foundation
      • 5️⃣How to build components
      • 6️⃣How to document a design system
      • 7️⃣How to enable adoption and govern a design system
    • Mobile Engineering
      • 1️⃣Trunk based development
      • 2️⃣Agile development terminology
      • 3️⃣Git commit messages
      • 4️⃣Code review and pull requests
      • 5️⃣Readings
  • Delivery
    • Project Management
    • Collaboration
  • Hiring and Growth
    • Growth
      • 1️⃣Design growth framework
      • 2️⃣How to give ongoing feedback
      • 3️⃣How to check-in every quarter
      • 4️⃣How to address underperformance
      • 5️⃣FAQs
    • Hiring and careers
      • 1️⃣The Hiring Process
      • 2️⃣Diverse and Inclusive Hiring
  • PEOPLE EXPERIENCE
    • Benefits and Perks
      • 1️⃣Paid time off
      • 2️⃣Insurance and healthcare
      • 3️⃣Continuing education
      • 4️⃣Speaking at conferences
    • Starting at Obvious
      • 1️⃣Introducing Obvious
      • 2️⃣Set up your workspace
      • 3️⃣Onboarding
      • 4️⃣Finances
      • 5️⃣Code of Conduct
    • Employment policies
      • 1️⃣Equal opportunity employment
      • 2️⃣At-will employment
      • 3️⃣Employee records and privacy
      • 4️⃣Prevention of sexual harassment
      • 5️⃣Drugs and alcohol
      • 6️⃣Fraternisation
      • 7️⃣Non-compete and non-solicitation
      • 8️⃣Non-disclosure
Powered by GitBook
On this page
  • 👋 Introduction
  • 1️⃣ Understand the domain
  • 2️⃣ Understand features
  • 3️⃣ Understand JTBD
  • 4️⃣ Evaluate apps
  • Conclusion
  1. Strategy

Benchmarking

PreviousTestNextResearch

Last updated 1 year ago

👋 Introduction

Benchmarking is a way to rapidly build context about the domain we’re designing for. It helps us understand the needs of users and features that are table-stakes. Benchmarking also helps us build on top of well resolved solutions for validated user needs.


1️⃣ Understand the domain

  1. Identify competitors. Identify 5-8 competitors. Ensure a variety in selection from immediate competitors in your geography and adjacent geographies, to competitors that build for a similar user persona and the best products in this category worldwide.

  2. Identify target audience for each competitor. They may or may not be the same across the products you’ve chosen. Understand the objectives of the audience of each competitor. Identify their attributes and qualities.

  3. Create domain framework. Turn attributes and qualities into axes of a 2x2 matrix to create a framework. Find your product’s placement or positioning in the domain. This clarity will help tremendously in making product decisions.

2️⃣ Understand features

  1. Start with the product architecture of each competitor. The architecture will reveal key features. These are typically areas such as onboarding, support, home page, and any features in the bottom navigation of your app. This will give you a good overview of all kinds of capabilities being provided to users in your domain.

  2. Identify the goal of each feature and qualities of an ideal experience. As you look at the same features being provided in each of the competitors, look for attributes of the flows and designs that make for good and poor experiences for users. You are likely to discover a lot of interesting ideas this way.


3️⃣ Understand JTBD

  1. Identify superset of JTBD for each feature across competitors. Create a matrix of availability. This matrix will help you quickly separate the feature leaders and feature laggards in the domain. It will also reveal if there is a agreed set of features that are table-stakes.

  1. Collect screens for each JTBD for each app and make note of what is and isn’t working well. The best way to do this is to use the app yourself and take screenshots or screen record flows end to end.

Sometimes the app may not be available in your region or you may not be eligible to use it. Youtube walkthroughs are a reliable back up.


4️⃣ Evaluate apps

  1. Create a feature rating matrix for the persona in focus based on notes, comparison and ideal experience. This will help you form an opinion of how well key problems in your domain have been solved by competitors.

  2. Give apps an average overall rating as a simple average of the rating of all the individual features rounded up or down as needed. Make sure that each of the features are defined and grouped in a way so that they are equally important to the product. Doing so will help the average rating be an accurate representation of the overall product.


Conclusion

Through the benchmarking exercise, you will have built a deep understanding of the product space, broadened your idea of various solutions for the same problem, understood tradeoffs that competitors have made, and identified what constitutes as table stakes in your domain.

This learning should help you with more informed usefulness research, defining product strategy for an MVP feature or Product, identifying the USP for your product, and area for innovation in your product.


Key features for trading apps across the domain
Comparison list of all JTBD in the registration process of trading apps
Comparison of scrip details page of trading apps
Comparison of trading apps by feature