usourcecontrol

3.4Voice capture

Say what needs doing, read the transcript, tick the cards you want. Paid plans.

Section 4 of 5 in this chapter

Playtests generate notes faster than anyone can type them. You are watching someone play, things are going wrong in real time, and the choice is between looking at the player and writing it down.

Voice capture lets you talk and get task cards back.

The reviewed path

  1. 1

    Record

    Press the microphone on the board and say what needs doing. One long take is fine — it is better, actually, than trying to speak in discrete items.

  2. 2

    Read the transcript

    You get the text back before anything else happens. Fix it, trim it, or throw it away.

  3. 3

    Tick the cards you want

    The approved text becomes proposed cards. Nothing reaches the board until you accept it, and you can edit a proposal before you do.

The two gates are load-bearing. Transcription and extraction are separate steps with a person in between, so a bad recording costs one call to discover rather than two, and the text that reaches extraction is text you have read. The output is always proposals — nothing appears on a shared board because a model thought it should.

  🎙  audio
       │
       ▼  transcribe
    transcript ──► YOU read / edit / discard
       │
       ▼  extract
    proposals  ──► YOU tick the ones you want
       │
       ▼
     board
Figure 3-3. Two automated steps, two human gates, then the board.

The global shortcut

The desktop app can also register a system-wide shortcut: press it, talk, press it again, and cards appear on the active project's board with no review step at all. It is off by default.

Skipping the review is the whole value during a playtest, so the trade is paid on the way out instead: the overlay names every card it created and offers Undo.

Was this helpful?

Back to top