Walden

Make things deliberately

Shape · Bet · Build — project management for the Shape Up method

Walden is the project management tool built for Shape Up. An idea earns its place through shaping. A bet makes it real. A fixed window forces the finish.

Your first six weeks are free.

The product

Purpose-built.

The pitch editor, the betting table, cycles with circuit breakers, live hill charts — Shape Up’s mechanics working out of the box, not a template you maintain.

See the product →
Pitch editor interface in light mode

Why now

Your tools are optimizing the step that stopped being expensive.

Every project management tool you’ve used was designed around a constraint that no longer holds: that building was the slow part. Backlogs, estimates, sprints and burn-down charts are all answers to how do we get more built, faster.

Building got cheap. Owning it didn’t. Every shipped thing is permanent surface area — something to support, explain, keep working, and account for in every decision that comes after it. You didn’t decide to stop deciding, but the signs are everywhere:

  • An endless backlog of work mostly written by AI.
  • Features nobody uses, shipped because there was no reason not to.
  • More shipped than last year, and no clearer sense of whether it mattered.

This is what happens when the expense that used to force a decision goes away. The scarce resource is no longer building time. It’s judgment — knowing what’s worth owning out of everything you could ship.

That’s what Walden is: a decision-making framework, not a faster tracker. Shaping makes an idea prove itself before it’s considered. Betting forces a real yes or no, with a team and an appetite attached. A fixed window ends the work on purpose. It puts a deliberate decision where the expense used to be.

Two jobs

A decision framework for leaders. A workspace for builders.

For the people deciding

Shaping and betting are leadership work. Raw ideas get shaped on the canvas, argued into pitches, and brought to a table where you commit a team and an appetite — or say no. Every cycle starts with a real decision, made on purpose.

For the teams building

Once the bet is placed, the team runs itself. Scopes, tasks, documents, and channels live beside the work, and hill charts show where things stand without anyone asking. Six weeks of protected focus, then a real ending.

Shape · Bet · Build

The method, built in.

Pitches, bets, and circuit breakers aren’t practices you maintain on top of Walden. They’re how it works.

Shape

An idea has to earn it.

Shaping turns a rough notion into a pitch: Problem, Appetite, Solution, Rabbit Holes, No-Gos. What’s worth solving, how much it’s worth, and where the risk hides.

Bet

A bet, not a backlog.

Shaped pitches go to the betting table, and someone decides. A bet has stakes — a team, an appetite, a hard stop. What doesn’t win isn’t queued; there’s nowhere to queue it.

Build

Built to finish.

The team owns the cycle: one vertical slice early, live hill charts, no status theater. When the appetite runs out, the circuit breaker trips — it ships, or it stops.

The whole method fits in a short manual. Start with the preface: The two tracks →

Convictions

Built on convictions,
not compromises.

These aren’t settings you toggle on. They’re the shape of the software.

No backlogsFixed time, variable scopeCircuit breakers that actually tripAssign projects, not tasksAppetite over estimatesBuilders own their workflow

If one of those is a dealbreaker, this is the wrong tool, and it’s better to know now.

Built for teams small enough to decide.

A good fit if

If AI made your team faster but not more certain, if shipping is cheap and owning what ships isn’t, and if the missing piece is a way to decide — you’re who Walden was built for.

Probably not

If story points are how you report up, if velocity is how you measure progress, or if sprint planning and backlog grooming hold your week together — Walden doesn’t offer gentler versions of those. It removes them.

Fair questions

“We’ve never run Shape Up.”
You don’t need to have read the book. Walden’s manual is short, and the method is mostly one habit: decide what’s worth building before you build it. The software holds the rest.
“We already use Basecamp.”
Basecamp wrote the method and built a general-purpose tool. Walden builds the method itself — pitches, betting, circuit breakers as real objects, not documents you maintain by hand.
“Can’t we just run Shape Up in Jira or Notion?”
Jira and Linear were built for Scrum: sprints, backlogs, estimates — everything Shape Up exists to reject. You spend every cycle fighting the tool’s defaults. Notion is the opposite problem: it holds no process at all, so the team spends its attention running the system instead of building. We wrote the full breakdown: Process Drift.
“Six weeks is too long for us.”
Then bet less. A small batch is one or two weeks; six is only the ceiling — the largest bet you're allowed to make. Appetite is the point, and big things get built as a series of bets that each earn their place.
“What about bugs and small requests?”
Truly small work doesn’t need process — just do it. Cooldown between cycles is where bug fixes and loose ends live. And a bug big enough to deserve real time gets shaped into a pitch and competes at the table like anything else.

A note from the founder

Walden is a solo company. I shape it, build it, and support it myself — one person, deciding what’s worth building and finishing it.

The name comes from Thoreau. He didn’t go to the pond because he had too little. He went because more was available than was good for him — abundance without intention is its own kind of poverty, which is a strange thing to read in 2026 and not feel addressed by.

That’s the whole idea, for the software and the company behind it: fewer things, chosen on purpose, seen through to the end.

— Rob Martin

The full story: Why I built Walden →

Make things deliberately.

Shape what’s worth building. Bet on it. Finish it.

Your first six weeks are free.