How to Build with Shape Up

When working with Shape Up’s building phase, the emphasis shifts from planning to execution, and it’s crucial to do this effectively. Below are key elements to consider, especially when applying them in project management and software development.

Handing over responsibility

Once a project has been shaped and pitched, it’s time to hand it over to the team. In Shape Up, this handoff is essential because it trusts the team to execute without constant micromanagement. This responsibility gives them ownership and autonomy to solve problems on their own terms.

For founders and managers, this isn’t easy—relinquishing control can feel risky—but it’s necessary for success.

In software development, this means trusting the engineers, designers, and product managers to make informed decisions. The goal is to avoid bottlenecks caused by top-down management and empower teams to build solutions as they see fit.

Getting one piece done

The secret to moving fast is focusing on delivering one small, working piece of the project at a time. This approach ensures that each part is functional and contributes toward the larger goal. In software, it’s tempting to aim for big releases, but getting one piece done means shipping small features regularly—providing value incrementally.

Mapping the scopes

Scopes are critical in Shape Up’s building phase. Instead of trying to tackle an entire project at once, work is broken down into clear, manageable chunks. These scopes serve as the building blocks of the project, making it easier to focus on smaller, more tangible objectives. Mapping scopes is similar to sprint planning in agile, but it allows more flexibility by focusing on outcomes instead of fixed timelines.

In a software project, mapping scopes might mean defining individual features or technical components that can be tackled independently. Each scope should have clear boundaries, making it easier to know when it’s done.

Tracking progress

In project management, work is more like climbing a hill than following a straight line.

Picture your most recent project and think about the progress you made over time.

If you’re like most people and teams, it probably looked at least a bit like this sketch:

In the beginning, you face uncertainties and solve complex problems. But eventually, your team begins to figure things out, and the path to execution becomes clearer and faster.

Unlike a linear approach, where progress is often misunderstood as a percentage, tracking progress on a hill helps teams see real progress over time, focusing on overcoming challenges rather than just checking off tasks.

Knowing when to quit

In any software project, it’s important to know when to stop refining and move on. Shape Up emphasizes constraint—teams are given a fixed timeframe to work, and they deliver what they can within that boundary. If they hit snags, they don’t keep pushing indefinitely. Instead, they stop, reassess, and decide whether to move forward or rethink the approach.

For teams, this mindset of stopping when necessary prevents burnout and scope creep, and keeps projects aligned with the time and resources available.

Moving on

Once a project scope is finished, it’s time to move on to the next piece. Shape Up encourages teams to quickly shift focus from one completed scope to the next, maintaining momentum without being stuck in endless refinement. For software developers, this means having the discipline to ship features and move forward without constantly revisiting what’s already been built.