🏫
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️⃣ Vote on solutions
  • 2️⃣ Pick the core concept
  • 3️⃣ Create a Storyboard
  1. Strategy
  2. Sprints

Decide

PreviousSketchNextPrototype

Last updated 1 year ago

👋 Introduction

Day 3 is all about picking a direction. With a stack of solutions in hand, it's time to narrow them down and pick a focus for the prototype. Reshape open-ended discussions into efficient critiquing and quick decision-making.

1️⃣ Vote on solutions

First, review the sketches from Day 2 and discuss their strengths and weaknesses. Then vote on our favourite sketches, and decide which ones to take forward. This discussion will help everyone think on their feet, and create a record of promising ideas.

Giving the solutions enough space will let the team put more time and thought into examining each sketch, before placing their votes.

Capture specifics about the solution sketches and opinions on sticky notes. This will help build on ideas that people have put thought into.

Don’t digress into discussions on abstract new ideas. Its unlikely that a new idea will make sense to take forward at this point in time. Work with the ideas you already have.

Don’t worry about what the group thinks. Stay unbiased, and true to your decision by keeping the product goals in mind.

2️⃣ Pick the core concept

The decider gets super-votes, which will be the ultimate decision maker. The ideas with super-votes on them will be taken forward in the prototype, and will be tested for the sprint.

Don’t worry about what the group thinks. Stay unbiased, and true to your decision by keeping the product goals in mind.

3️⃣ Create a Storyboard

Think of how customers would interact with your product or service. Include just enough detail to help the team prototype on Thursday. This will help imagine the finished prototype, so you can spot problems and points of confusion before its built.

Take the winning sketches and string them together - tightly connected into one cohesive story.

Quick Tip: If the team is stuck discussing one idea, or when tough decisions appear, defer to the Decider. For smaller decisions, defer until tomorrow.

3️⃣