Process mismatch
In tools built for Scrum, a task is an input: something you file, size, and work on. In Shape Up, a task is an output — something discovered while building work that was already shaped and bet on. That's the core mismatch, and it plays out differently depending on the tool.
Jira
Jira does exactly what it was built to do. Its shape is Scrum's shape: a backlog, estimates, sprints.
Teams bring Shape Up in anyway and try to make it fit the tool's shape. A scope becomes an epic. A task becomes a ticket. The pitch — Shape Up's document for a problem, its appetite, and a proposed solution — has no equivalent object in Jira, so it ends up living in a Confluence doc, disconnected from the work it's supposed to govern.
The substitutions are each small and reasonable on their own:
An estimate field is there, so it gets filled in — and the velocity report looks broken without it.
Losing bets need somewhere to go, so they land in the backlog. They aren't dead, they're waiting — and now someone has to groom them.
Appetite ("how much is this worth") quietly reverts to estimate ("how long will this take").
Before long, the team is running Scrum, with a backlog-refinement meeting back on the calendar. The tool's requirements pull the ceremonies back in.
Linear
Linear is fast and well made. It even has cycles. The mismatch here isn't a quality problem — it's an inheritance problem. Linear carries the same assumptions as Scrum, just executed better.
When a cycle ends with work unfinished, Linear rolls it forward automatically into the next one. It's meant as a convenience feature. It's also the inverse of Shape Up's circuit breaker.
Shape Up's bet is that the deadline is real. The whole mechanism depends on a hard stop forcing a decision — cut the scope and ship what's done, while there's still time to make that call. A tool that quietly carries unfinished work forward removes the one moment the method needs. Every six weeks, it says: the deadline was just a suggestion.
The rest of Linear reinforces the same shape without needing to. The triage inbox is a backlog with better manners. Velocity insights put throughput on the wall for everyone to watch. None of this is a flaw in the product — it's Scrum, built well, and Shape Up doesn't fit inside it any better than it fits inside Jira.
The tool celebrates finishing tickets. Shape Up celebrates finishing projects. Those sound alike, but they aren't.
Notion
Whether you start from a blank canvas or build from a template, you'll run into the same problems trying to run Shape Up in Notion.
Not because Notion can't do it — it can. I've run a pitch inside a Notion doc: problem, appetite, solution, rabbit holes, no-gos — and the template held the shape beautifully. Notion isn't missing a feature here — it's missing insistence.
Appetite in Notion is just a property on a page. Nothing compares it to anything, and nothing happens when it's exceeded. The cycle end date is a date field. It passes the same way any other date passes: quietly, without consequence.
So the mechanics still have to exist somewhere. In Jira and Linear, a process runs itself — the wrong one, but it runs, and nobody has to think about it. In Notion, the software enforces nothing, so the team becomes the mechanism. Every constraint the software won't hold gets held by attention instead — the same attention the team needs for the actual work.
The turn to Walden
What makes Shape Up different is its constraints: no backlog, a fixed time and variable scope, appetite instead of estimate, and a hard stop at the end that means what it says.
Jira and Linear aren't general-purpose. They're purpose-built, just for a different method — which is exactly why they hold their own constraints so well: a backlog, a sprint, a point, each enforced because the software was built around it. Notion is the general-purpose case, and general-purpose means every constraint is optional. Nothing gets enforced because nothing is supposed to be; a tool built to hold anything is a tool built to hold nothing in particular.
So the whole space comes down to two options: a tool that runs a different method's mechanics, or a tool that runs none. Both hand Shape Up's constraints back to the team's attention — the resource the method exists to conserve in the first place.
This was never an argument about features. Jira has more features than anyone. What was missing was a tool built to run Shape Up's mechanics specifically. Since it didn't exist, I built one.
That tool is Walden. It gives Shape Up's mechanics — the pitch, the appetite, the bet, the circuit breaker — first-class support, not as fields on a page, but as the shape of the software itself.
Originally published on the Walden journal. Walden is a project management tool built for Shape Up — walden.so.
Top comments (0)