🏫
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️⃣ How to create artefacts
  • 2️⃣ Further reading
  1. Strategy
  2. Research

How to create artefacts

👋🏼 Introduction

Creating an artefact allows you to go in with a hypothesis and get a yes or a no to it. It also helps the participant imagine what you’re talking about. This way you get to see their honest reactions to your product.

1️⃣ How to create artefacts

Decide what kind of artefact

Depending on what you’re testing, pick the artefact you need to show to users.

  • It can be a clickable prototype if you’re testing the product. Use Figma.

  • It can be a product demo video if you’re testing a product construct. Create a clickthrough prototype on Figma and record it as a demo / walkthrough using Loom

  • It can be a landing page if you’re testing a positioning or marketing pitch. Use Framer

  • It can be a card sorting exercise if you’re trying to understand mental models.

Limit to 1-3 critical user flows or screens for testing

Anything more than that is going to be overwhelming and leave no time for any explorative conversation.

  • Limit to testing 1-2 broad areas like new product innovation (15 min per area)

  • Or 2-4 specific areas like in usability of interaction patterns / narratives (7 min per area)

Aim for a realistic artefact

Get close to the real product to simulate a realistic user experience and gather authentic feedback. Get details like transitions, copy, and pressed states right. Remove the blue hotspots if you’re using Figma.

At the same time trying to make the prototype too real can overengineer it and take too long to put together with diminishing returns on learnings. Skip adjacent flows and error states that you’re not testing. Focus on getting the flows you’re testing right. If users encounter one of the adjacent flows, gently move them back to the core task.

2️⃣ Further reading

PreviousHow to throw a watch partyNextBuilding with AI

Last updated 1 year ago

7️⃣
Sprint: Thursday
The Prototyping Tools We Use in our Design Sprint
DESIGN SPRINT 2.0 - Prototyping Day Tips by AJ&Smart