TinkerYesterday’s failed traces on the wall. Focus a note to light its trace.
Chapter 3 of 7
Open coding
Yesterday’s traffic left 18 failed traces. Nobody has a list of what goes wrong yet, so there is nothing to tick.
This chapter: How do you start making sense of failures before you know what kinds there are?
You will learn
- Open coding: a short note per failed trace, in your own words
- Why you write notes before you choose categories
- Why a person who knows the business does it
Words you’ll meet (2)
- Open coding
- Reading traces one by one and writing a free note on what went wrong in each.
- Note
- A line in your own words about one trace’s failure. Notes are never graded.
The picture on the left is live. Each step below asks you to do one thing in it; the story continues here as you go.
Step 1 of 3
You found where two traces went wrong. 18 failed yesterday. Nobody has a list of what goes wrong yet, so there is nothing to tick: you read each trace and write a short note in your own words. That is open coding. Before you start: