Field notes
Notes written on the way up.
Short, practical reading for anyone taking a new product from idea to launch.
From rumour to proposition
A rumour is “people would love an app for this”. A proposition is “independent bike mechanics lose time chasing parts, and would pay a small monthly fee for a log that ties each part to a customer and a date”. The second can be tested: are mechanics losing time, is it parts specifically, and would they pay? Write yours down before talking to anyone, then see how it changes.
Ten interviews, done well
Ask about the past, not the future: “tell me about the last time” rather than “would you use”. Do not pitch. Listen for workarounds, spending and emotion, which signal a real problem. Stop when you hear the same stories repeating; for a narrow audience that can happen within eight to twelve conversations.
Choosing prototype fidelity
Paper answers “does this concept make sense?” in hours. Clickable prototypes answer “can people use it?” in days. Coded spikes answer “is this technically possible?” when the risk is in the machinery. A concierge trial, where a person performs the service by hand, answers “will people actually use and pay for this?” with real behaviour. Choose by the question, not by habit.
The smallest honest release
A first release should complete one valuable journey for one kind of person, end to end, reliably and accessibly. It should not pretend to do things it cannot. Cut features before cutting quality; a small product that works builds trust, a large one that wobbles spends it.
Store review without surprises
Common causes of rejection: reviewers cannot sign in, the listing promises features the build lacks, privacy disclosures do not match what libraries collect, crashes on an untested device, and purchase rules for digital goods. Prepare a demonstration account, re-read the listing against the build, trace every SDK, and test on the oldest supported version.