Eighteen months ago we were stuck in a pattern I suspect most small engineering teams recognise: two-week sprints that felt like they were optimised for ceremony rather than output, a backlog that grew faster than we could groom it, and a persistent feeling that we were busy without being productive.
A friend recommended Shape Up — Basecamp's approach to product development — and we gave it a real shot. Not a "let's try this for one cycle" shot. A "we're committing to six months and we'll evaluate honestly at the end" shot.
The core idea
Shape Up replaces the continuous backlog with a six-week cycle. Before each cycle, senior people "shape" the work — defining the problem, setting boundaries, and producing a pitch. The team then has six weeks to build it, with no interruptions and no scope changes. After the cycle, there's a two-week cooldown for bug fixes, exploration, and recovery.
What worked
The appetite concept changed everything. Instead of asking "how long will this take?" we started asking "how much time is this worth?" That single reframe eliminated most of our scope creep overnight. When you've decided that a feature is worth three weeks of a senior pair's time, the team naturally cuts scope to fit — and the result is almost always better for it.
What we changed
We shortened the cycle to four weeks. Six felt too long for our team size. We also added a lightweight demo at the end of each cycle — not a formal review, just a "here's what we built" session that keeps the rest of the company in the loop.
What we threw out
The hill chart. I know it works for some teams, but ours found it more stressful than useful. We replaced it with a simple traffic-light check-in: green (on track), amber (need to cut scope), red (need help). Three colours, once a week, no ceremony.