Matthew Lang

A lightweight adaptation of Shape Up for a solo developer working in short, intermittent sessions. The full Shape Up methodology is a coordination protocol for small teams. This version strips out the team machinery and keeps only the four concepts that survive working alone.

1. Appetite over estimates

The idea: Before starting any piece of work, decide how much time it is worth — not how long it will take. That number becomes your scope ceiling.

Shape Up calls this the appetite. It flips the usual project management question. Instead of asking “how long will this take?” and then scrambling when the answer is wrong, you ask “how much time is this worth to me?” and then shape the work to fit.

In practice:

Set your appetite at the start of each piece of work. There are three useful sizes:

Once the appetite is set, scope is the variable — not time. If you reach your limit and the work isn’t done, the right response is to cut scope, not extend the budget. Shipping something smaller on time beats shipping something complete late.

Why it works solo: Estimates create a false sense of certainty and invite scope creep. An appetite is honest — it’s a deliberate decision about value, not a guess about effort.

2. Shaping before building

The idea: Before writing any code, spend a short time sketching the boundaries of the solution. This is not a spec. It’s a rough map that defines what’s in and what’s out.

Shape Up calls this shaping. For a team, shaping happens in a separate phase before the build cycle begins. Solo, you do it informally — but the discipline of doing it at all is what matters.

What shaping looks like:

A shape doesn’t need to be polished. It can be a few bullet points in a notebook, a rough wireframe, or a short paragraph. The goal is to answer:

• What is the core use case? What problem does this actually solve?
• What are the rough components — what are you building?
• What are the boundaries — what are you not building this time?
• Where are the risks? What could make this harder than expected?

If you can’t answer these in 15–30 minutes of thinking, the appetite is probably too vague. Either sharpen the idea or split it.

The key property: A good shape is concrete enough to give you a clear starting point, but abstract enough that you still have room to make sensible decisions during the build. It’s not a blueprint — it’s a sketch.

Why it works solo: The main enemy of intermittent work is starting a session with no sense of direction. A shape gives you something concrete to return to. It also surfaces rabbit holes before you’re inside them.

3. Hill chart as mental model

The idea: Every piece of work has two distinct phases — figuring out the solution, and executing it. These feel completely different and should be tracked separately.

Shape Up visualises this as a hill. The uphill phase is about resolving unknowns: discovering the right approach, uncovering hidden complexity, making decisions. The downhill phase is about execution: the solution is clear, and you’re working through it. Crossing the top of the hill is the moment when uncertainty gives way to confidence.

          ◆ (peak — solution is clear)
         / \
        /   \
       /     \
      /       \
 Figuring     Executing
  out          it

Using it solo:

You don’t need a visual tool. The hill chart is useful as a question you ask yourself at the end of each session:

• Is this task still uphill (unknowns remain)?
• Or is it downhill (I know exactly what to do, just need to do it)?

This matters for two reasons:

1. When to stop. Try to get a task over the hill before ending a session. A downhill task is easy to re-enter — the path is clear. An uphill task requires you to reconstruct your thinking from scratch each time you return.

2. Spotting stuck tasks. If a task stays uphill for a long time, it’s a signal. Either the shaping was too vague, or the task is bigger than the appetite allows. Either way, something needs to change — not more time, a different approach.

Why it works solo: Context recovery is the main cost of intermittent work. Knowing where you are on the hill before you close your laptop makes the next session dramatically faster to start.

4. Re-entry notes

The idea: At the end of every session, write two or three sentences capturing your current state. This is not a task list — it’s a handoff note to your future self.

This is not a Shape Up concept directly, but it’s the adaptation that makes the others work for intermittent sessions. Shape Up assumes you work every day inside a cycle. When you return to a project every few days, the gap between sessions is where momentum dies.

What a re-entry note contains:

## Re-entry note — [date]

**What I was doing:** [one sentence on the specific task]
**Where I am on the hill:** uphill / downhill
**Next action:** [the single most concrete next step]
**Open questions:** [anything unresolved that will need thinking]

Keep it short. The goal is a 30-second read that drops you back into the right mental context, not a comprehensive log.

Where to put it: Wherever you will actually see it. Top of the file you were working in, a pinned note, a comment in the code. Friction to access it defeats the purpose.

Why it works solo: Without a team to provide continuity, the handoff is always to yourself. Re-entry notes make that handoff reliable. They also double as a lightweight record of how the build actually progressed — which is useful when you’re deciding whether to revisit something later.

Putting it together

A typical piece of work flows through all four concepts:

1. Set your appetite — decide how much time this is worth before you open an editor.
2. Shape it — spend 15–30 minutes sketching the problem and bounding the scope.
3. Build, tracking the hill — notice whether you’re uphill or downhill, and try to cross the peak before stopping.
4. Write a re-entry note — end every session with a 2–3 sentence handoff to yourself.

None of these steps are heavy. The value is in doing them consistently, not in doing them elaborately.