Shape Up is a product development method that fixes the time and varies the scope. Teams shape a bet, commit to a six-week build cycle, and cut or adapt requirements so they can ship useful work on schedule.

At Process Street, that shift helped our engineering, product, and design team reduce a development cycle from roughly six months to six weeks. Delivering features and modernizing our tech stack via Shape Up became parts of the same bounded strategy, rather than competing imperatives. The method created room for technical modernization without putting feature delivery on indefinite hold.

• How Shape Up helped us cut delivery time
• How Shape Up changes the design process
• A Process Street engineer’s view of iteration

How Shape Up helped us cut delivery time

This section was written by Mike Schutte, who was a Senior Front-end Engineer at Process Street.

Time is perhaps the most precious resource when building a product. And yet, it is often spent as if it were infinite. Teams adapt timelines to fit features and requirements instead of adapting the requirements to fit the timeline.

The essence of the Shape Up methodology is exactly that: adapt requirements to fit timelines. Instead of estimating an idealized feature and allowing its schedule to expand, a team chooses an appetite for the problem and shapes a solution that fits.

We do not talk about being feature complete. We build, communicate, revise, and repeat. The team could build, communicate, revise, and repeat on a daily basis instead of waiting for an idealized version to become feature complete. The goal is to identify the biggest levers at our disposal, add as much value as we can within the six-week cycle, and do so without compromising on quality.

Shapers identify a valuable area in which to invest. A betting table decides which shaped pitches receive time. Builders then have the autonomy to find the right implementation, cut lower-value scope when necessary, and test the bet using feedback from real users. The result is a stream of good-enough improvements at a predictable cadence instead of one theoretically perfect release on an amorphous timeline.

The six-week build cycle provides a hard boundary. A two-week cooldown follows it, giving teams space to fix issues, explore ideas, and prepare for the next bet. That rhythm changes the planning question from “How long will this take to build?” to “How much time are we willing to bet on this area of the product?”

That distinction also helps technical priorities compete in business terms. During the original transition described here, Process Street was moving parts of its application from AngularJS to React. AngularJS has since reached end of support, but at the time, rewriting an application while continuing to deliver features was a difficult and often demoralizing task.

Developers used the agency built into each cycle to deliver valuable features and, when it made sense, convert more of the application to React. The current approach at the time used react2angular as a historical bridge for replacing AngularJS nodes with React nodes. That worked in many cases, although complex areas sometimes made a clean React implementation more practical.

Shape Up gave engineers two additional avenues to pursue this kind of paradigmatic change. First, engineers could use cooldown time for preliminary work on a separate React application and incremental, page-by-page replacement. Second, they could shape the rewrite around business value: better hiring outcomes, fewer bugs, and faster feature delivery. Features modernizing the tech stack could therefore be shaped as bounded bets. Stakeholders could decide how much time to bet on those benefits instead of debating an open-ended rewrite.

We use Shape Up, but this is not an endorsement of Basecamp or Ryan Singer.

How Shape Up changes the design process

Product design does not disappear when a team adopts Shape Up. It moves upstream and becomes more deliberate. Shaping defines the problem, the appetite, the boundaries, and the risks before a team commits to build. Designers can explore the right level of fidelity without turning a pitch into a rigid specification.

Process Street product designer Ivy Kwan explained how Shape Up’s design process works in practice, including how it differs from Scrum and Kanban. One useful takeaway is that a shaped pitch should remove the largest unknowns while leaving builders enough room to discover the best solution during the cycle.

That balance matters whether a team follows Shape Up directly or combines its ideas with an Agile workflow process. The operating model should make scope decisions visible, protect the appetite, and keep feedback close to the people doing the work.

These workflow templates make the three core activities concrete:

• Shape Up Process: Shaping
• Shape Up Process: Betting
• Shape Up Process: Building

A Process Street engineer’s view of iteration

Herbie Porter, then a Full-Stack Engineer at Process Street, described his day-to-day work as part of the engineering, product, and design team in this profile. He also captured the practical value of a bounded cycle when Process Street first shifted from Scrum:

Shape Up encourages short, concise periods of time to solve the problem quickly and get something out. It might not be perfect, but you can iterate on it later on.

Herbie Porter

That is not an excuse to ship careless work. It is a way to separate what must be true now from what can be improved after users respond. A builder can review the outcome, learn from real behavior, and shape the next iteration without holding the current release hostage to every possible enhancement.

Process Street now brings this kind of operational discipline into one Compliance Operations Platform. Teams use Docs and Ops capability areas, plus built-in AI, to document how work should happen, run repeatable workflows, and keep evidence connected to execution. The same fixed-time, clear-boundary mindset that makes Shape Up effective also helps operational teams improve work without losing control of the process.

The post Delivering Features & Modernizing Our Tech Stack via Shape Up first appeared on Process Street | Compliance Operations Platform.