Convivio Cookbook
  • Introduction
  • Our Business
    • The Convivio brand
    • What do we do?
    • Our work for clients
    • Our Purpose
    • Our Pulse
      • Big Rocks
      • Problems
    • Company Policies
      • Environmental Policy
      • Anti-Bribery Policy
      • Fair Tax Policy
        • Dividends policy
        • 2020 Results and Tax
        • 2019 Results and Tax
        • 2018 Results and Tax
        • 2017 Results and Tax
  • Our Team
    • Help! I'm new. How do I get started?
    • Starting at Convivio
    • Staff Benefits
    • Being a buddy
    • Having a buddy
    • Free-Range Working
    • Convivio Fridays
    • Notes: give & receive feedback
    • Security Screening
    • Submit Expenses
    • Purchases
    • Your home working environment
    • People Analytics
    • Recruitment
      • Help Card: Writing a Person Profile
      • Help Card: Writing a Job Description and Advert
      • Help Card: Publishing a Job Advert
      • Help Card: Reviewing CVs
      • Help Card: Preparing and Conducting Structured Interviews
      • Help Card: Preparing and Conducting Remote Working Interviews
    • Team Policies
      • Security Policy
        • Acceptable Use Policy
        • Business Continuity Management
        • Data Usage Policy
        • Document Access Policy
        • Mobile Equipment Policy
        • Two-Factor Authentication (2FA)
        • VPN Guide
      • Equal Opportunities
      • Grievance Procedure
      • Disciplinary Procedure
    • Taking time off work
      • Holiday
      • Sickness
    • Peer reviews
    • Mental Health
      • Mental Health Training
      • Mental Health First Aid
      • Returning to work
      • Resources
    • Continuing Professional Development
      • CPD Annual Planning
      • CPD Sprints & Scrums
      • CPD Annual Review
      • CPD Annual Retrospective
  • Our Clients
    • Principles For Building New Client Relationships
    • Researching
    • Connecting
    • Nurturing
    • Assessing
    • Learning and Thinking
    • Pre-qualification questionnaires
    • Proposing
    • Agreeing
    • Beginning
    • Inspiration
  • Our Marketing
    • Content Publishing
      • Git Repository Conventions
      • Help Card: Writing a Case Study
    • Brand Guidelines
      • Content Guidelines
      • Branded Documents and Reports
  • Our Tools
    • Infrastructure
      • External Firewalls
  • Internal Projects
    • How we improve our business
  • Client Projects
    • Delivery Launch
    • Delivery Team
      • Convivio People
      • The Coach
      • User Researcher
      • Other Team Members
    • Digital Strategy
    • Discovery
      • Discovery Briefing
      • Discovery Planning
      • Discovery Modules
      • Discovery Findings
      • Discovery Principles
      • Prepare for prototyping
    • Prototyping
      • Inputs to Prototyping
      • Prototyping Objectives
      • Prototyping Inception
      • Prototyping Sprints
      • Prototyping Outputs
    • Build
      • Inputs to Build
      • Build Kickoff
      • User Stories
      • Backlog Management
      • Backlog Scouting
      • Sprint Planning
      • Sprinting
        • Daily Standup
        • Story Lifecycle
        • Design in Sprints
        • User Testing in Sprints
        • Quality Control in Sprints
      • Sprint Review
      • Sprint Retrospective
    • Service Management
    • Digital Service Standards
      • Delivery Methodologies
        • Scrum
        • Kanban
        • Lean
          • Technical Standards
        • Code Quality
        • Testing
        • Automation
          • Security Standards
          • Quality Standards
          • Risk Standards
    • Delivery Governance
      • Steering Group
      • Risk Management
        • Risk Attitude
        • Assessing Risks
    • Delivery Help Cards
      • Help Card - Sprint Planning
      • Help Card - Sprint Review
      • Help Card - Sprint Retrospective
      • Help Card - Product Owner Feedback
      • Help Card - Common Issues
      • Help Card - Slack
      • Help Card - Github
      • Help Card - Trello
  • Our Recipes
    • Convivio Classic Cocktails
      • Ingredients
      • Tips and Techniques
      • Martini
      • Negroni
      • Manhattan
      • Old Fashioned
    • Potage Dubarry (or, creamy cauliflower soup) with spiced green pepper
    • Roasted Sweet Potato in a Herb and Nut Salad, with Maple Chilli Dressing
    • Aubergine Curry
    • Vegetarian Paella
    • Easy Ice Cream
Powered by GitBook
On this page
  • Retrospective
  • Planning
  • Sprint activities
  • Building prototypes
  • Testing prototypes
  • Analysing test results
  1. Client Projects
  2. Prototyping

Prototyping Sprints

The aim of the prototyping phase is to find a direction to move forward in. We need to quickly find out which directions or aspects of the service work or don't work.

PreviousPrototyping InceptionNextPrototyping Outputs

Last updated 6 years ago

Retrospective

Planning

Sprint activities

  1. Building prototypes

  2. Testing prototypes

  3. Analysing test results

Building prototypes

What you build and how you build it depends on what you need to find out. Always aim to pick the quickest and cheapest option for building what you need.

For example:

  • If you want to test the information architecture of a site, you can build a tree test

  • If you want to test the usability of a form, use a form-building tool like Google Forms or Typeform

  • If you want to test the usability of an interface, try paper sketches, wireframes, or mock ups

  • If you want to try testing a service with live data, build an HTML prototype that pulls from a live feed

  • If you want to test an end-to-end transactional service, build an HTML prototype with a (potentially mock-up) backend service that can react to and persist the choices of users

Testing prototypes

Common activities when testing prototypes include:

  • Interviews with users to better understand their needs

  • Showing design concepts to users to understand if the concept fits their needs

  • Testing the usability of an interactive prototype in a moderated session

You must do research with a broad range of users, including:

  • those with limited digital access and confidence

  • people with a range of visual, hearing, motor and cognitive impairments

Analysing test results

The aim of the analysis stage is to go from raw observations (this user said this, this user did that) to insights (this does not fulfil the user need, that is hard to use)

The raw outputs from the tests might include:

  • written and digital notes

  • sketches and photos

  • audio and video recordings

The best way of doing this is by getting all the useful observations up on the wall on post-it notes. It's best to do this together as a team going through the raw test output.

Once you've done that, you can begin grouping the observations into themes. For example:

  • common topics

  • stages in a user journey

  • individual pages or steps in a transaction

  • types of user

Decide on a for name each group together. Then generate problem statement that concisely covered everything you've learned.

Ta-da! Now you have insights!

Also see:

Also see:

See: Sprint Retrospective
See: Sprint Planning
User research in alpha
Analyse a research session