Why we start every project with a one-page brief
The fastest way to align founders, designers and engineers before the first sketch.
Every Sampan Labs project starts with a single page. Not a 40-slide deck, not a requirements spreadsheet. One page, written together with the client in the first week.
What goes on the page
- Goal: one sentence on what changes for the business if this works.
- Users: who uses it, and in what situation. Be specific: “stall owner during lunch rush”, not “merchants”.
- Must-haves: the few things it has to do on day one.
- Not now: the things we have agreed not to build yet.
- Done when: how we’ll know it worked, ideally with a number.
Why one page
Because it fits on a wall, it gets read. When a new request appears in week four, anyone can look at the page and ask: does this serve the goal, or is it a “not now”?
The “Not now” list is the most valuable part. Writing it down is how you stop arguing about it every week.
The page changes during a project, and that’s fine. What matters is that it changes on purpose, with everyone in the room, rather than by drift.
