Home / Resources
Things worth knowing before you hire anyone.
Short guides for owners, operations leads and product sponsors. Use them with us, with another team, or on your own.
Writing a one-page product brief
Before you speak to any developer, try answering these six questions on a single page. Gaps are useful: they show where discovery should start.
- Who has the problem? Describe a real person or role, not a market segment.
- What do they do today? The current workaround is your real competitor.
- What would be better? In their terms: faster, fewer mistakes, less chasing.
- What must the first release do? One sentence. If it needs "and", it may be two releases.
- What will it not do? Exclusions prevent most scope arguments.
- How will you know it worked? Something observable within a few weeks of launch.
When a spreadsheet should become software
Spreadsheets are wonderful until they are not. Consider a purpose-built tool when several of these are true:
- More than one person edits it at once and changes get lost.
- Only one colleague understands the formulas, and they want a holiday.
- You copy data between sheets by hand every week.
- Mistakes have real cost: missed bookings, wrong orders, repeated work.
- You need a history of who changed what.
Two reasons to wait: if the process itself is still changing monthly, or if a well-configured off-the-shelf tool would cover it. Software freezes a process; make sure it is the right one.
Running user interviews that do not lie to you
People are kind and optimistic about the future. Ask about the past instead. Good prompts: "Walk me through the last time this happened." "What did you do next?" "What did that cost you?" Avoid describing your idea until the end, and never ask whether they would buy it; watch what they do when offered something real.
Five interviews with the right people usually reveal the main patterns. Write notes straight afterwards, separating what was said from what you think it means.
Reading a software estimate
A trustworthy estimate is a range with its assumptions listed. Be wary of a single precise number given before anyone has examined the problem. Ask what would move the figure up, what is excluded, and how changes will be handled. A good supplier will be comfortable with those questions.
What a proper handover includes
- Source code in a repository owned by your organisation
- Hosting, domain and third-party service accounts in your name
- Instructions to deploy, roll back and restore from backup
- A record of significant technical decisions
- A list of known issues and outstanding work
- Credentials transferred securely, never by plain email
A short glossary
- Discovery: research and testing to decide what to build.
- First release: the smallest product that lets real users complete a real task.
- Prototype: a disposable experiment built to answer one question.
- Spike: a short technical test of an uncertain approach.
- Rollback: returning to the previous working version after a faulty release.
- Backlog: the ordered list of possible future work. Order matters more than length.
Want a second opinion on your brief?
Send it over. We will reply with questions, not a sales pitch.
Contact WHATNXT