Mycroft AI
  • Documentation
  • About Mycroft AI
    • Why use Mycroft AI?
    • Glossary of terms
    • Contributing
    • FAQ
  • Using Mycroft AI
    • Get Mycroft
      • Mark II
        • Mark II Dev Kit
      • Mark 1
      • Picroft
      • Linux
      • Mac OS and Windows with VirtualBox
      • Docker
      • Android
    • Pairing Your Device
    • Basic Commands
    • Installing New Skills
    • Customizations
      • Configuration Manager
      • mycroft.conf
      • Languages
        • Français (French)
        • Deutsch (German)
      • Using a Custom Wake Word
      • Speech-To-Text
      • Text-To-Speech
    • Troubleshooting
      • General Troubleshooting
      • Audio Troubleshooting
      • Wake Word Troubleshooting
      • Log Files
      • Support Skill
      • Getting more support
  • Skill Development
    • Voice User Interface Design Guidelines
      • What can a Skill do?
      • Design Process
      • Voice Assistant Personas
      • Interactions
        • Intents
        • Statements and Prompts
        • Confirmations
      • Conversations
      • Error Handling
      • Example Interaction Script
      • Prototyping
      • Design to Development
    • Development Setup
      • Python Resources
      • Your First Skill
    • Skill Structure
      • Lifecycle Methods
      • Logging
      • Skill Settings
      • Dependencies
        • Manifest.yml
        • Requirements files
      • Filesystem access
      • Skill API
    • Integration Tests
      • Test Steps
      • Scenario Outlines
      • Test Runner
      • Reviewing the Report
      • Adding Custom Steps
      • Old Test System
    • User interaction
      • Intents
        • Padatious Intents
        • Adapt Intents
      • Statements
      • Prompts
      • Parsing Utterances
      • Confirmations
      • Conversational Context
      • Converse
    • Displaying information
      • GUI Framework
      • Show Simple Content
      • Mycroft-GUI on a PC
      • Mark 1 Display
    • Advanced Skill Types
      • Fallback Skill
      • Common Play Framework
      • Common Query Framework
      • Common IoT Framework
    • Mycroft Skills Manager
      • Troubleshooting
    • Marketplace Submission
      • Skills Acceptance Process
        • Information Review Template
        • Code Review Template
        • Functional Review Template
        • Combined Template
      • Skill README.md
    • FAQ
  • Mycroft Technologies
    • Technology Overview
    • Roadmap
    • Mycroft Core
      • MessageBus
      • Message Types
      • Services
        • Enclosure
        • Voice Service
        • Audio Service
        • Skills Service
      • Plugins
        • Audioservice Plugins
        • STT Plugins
        • TTS Plugins
        • Wake Word Plugins
      • Testing
      • Legacy Repo
    • Adapt
      • Adapt Examples
      • Adapt Tutorial
    • Lingua Franca
    • Mimic TTS
      • Mimic 3
      • Mimic 2
      • Mimic 1
      • Mimic Recording Studio
    • Mycroft GUI
      • Remote STT and TTS
    • Mycroft Skills Kit
    • Mycroft Skills Manager
    • Padatious
    • Precise
    • Platforms
Powered by GitBook
On this page

Was this helpful?

  1. Skill Development
  2. Voice User Interface Design Guidelines

Prototyping

One way to prototype your skill is to get willing test participants to act as the User of the skill. These tests can be done in person or over a video conferencing tool.

PreviousExample Interaction ScriptNextDesign to Development

Last updated 5 years ago

Was this helpful?

As the skill designer you will act as the Voice Assistant and respond to the user's input with pre-written that you have created. You can think of it like a table read for a screenplay except the user is ad-libbing. Make sure you ask your participants if it is alright to record the sessions so that you can take better notes after the test is complete.

As the part of the Voice Assistant you want to stick to the script, but you are actually hoping the tester says something that you haven't thought of yet. The goal of these tests isn't to just validate your assumptions, the goal is to observe interactions that did not occur to you at first.

To begin the test give the user a task. For example, with the Moon Phase skill, we can pull the task directly from our Jobs to be done work.

Task Example:

You're thinking about taking some photos of the moon tonight, and you want to know what phase the moon will be in. What would you ask Mycroft to help you plan your photo session?

The first off the cuff responses from your test are generally the best, but it's always good to ask your testers if they can provide any variations on the way they might ask the question.

Be considerate of your tester's time. A usability test should never exceed 90 minutes, after that . We think you can get valuable feedback in a 30 to 45 minute session.

If you are creating a Skill as a hobby or as an individual you may not have the resources to provide an incentive to your testers. In that case you might be limited to friends and family for testing. If you are creating a skill for a larger organisation make sure that you think about possible incentives and check if your organisation requires a legal waiver for user testing.

Example Interations
the test subject will likely get tired