Appetite
Instead of asking "how long will this take?", ask "how much time is this worth to us?". Set that budget first, then design a solution that fits it. It stops projects from growing without limit.
by Ryan Singer ยท 10 ideas
Instead of asking "how long will this take?", ask "how much time is this worth to us?". Set that budget first, then design a solution that fits it. It stops projects from growing without limit.
Before handing work to a team, a senior person defines it at the right level: rough enough to leave room, solved enough to show the path, bounded enough to say what's out. Too vague and teams flounder. Too detailed and they can't adapt.
Sketch ideas with a thick marker, or as boxes and arrows, so you can't add fine detail. This keeps the conversation on flow and structure, not pixels. Leave the visual design to the people who build it.
Before a project starts, look for the hidden unknowns in it: tricky edge cases, unclear tech, open design questions. Solve them or cut them from the plan now. One unresolved hole can sink the whole project later.
Keep the deadline fixed and cut features to fit inside it. Teams always discover more than planned. Deciding what to leave out is the real work, and it keeps you shipping.
Don't keep a growing list of every idea anyone has had. Every few weeks, decision makers look at a few well-defined proposals and choose which ones to build next. Good ideas come back on their own, and nobody wastes time sorting an endless list.
Work in six-week cycles: long enough to build something meaningful, short enough to feel the deadline. Then take two weeks of cool-down to fix bugs, explore and plan the next bets. The rhythm prevents burnout and endless projects.
If a project isn't done when its time runs out, it stops by default. No automatic extensions. It forces honest scoping and keeps one stuck project from eating the next months.
Don't build all the backend first and all the UI later. Pick one small slice and make it fully work end to end. A real working piece teaches you more than a half-finished whole.
Every task has an uphill phase where you figure out how to do it and a downhill phase where you just execute. Track which side each part is on. Unknowns hide uphill, so tackle them first.