Stop-doing · Focus · Productivity · Team Management · PTOS

Stop-Doing List: The Main Accelerator for a Product Team

Why the Stop-doing list is an integral part of the Iterate phase, how to form it, and how it helps the team maintain focus, avoiding task sprawl and hidden work.

Stop-Doing List: The Main Accelerator for Your Product Team

In product development, speed is not about "doing more," but about "learning faster." But teams often slow down not because of task complexity, but because of accumulated ballast: hidden work, "eternal" assignments, and dispersed focus.

To move quickly, you need not only to decide what to do next, but also to ruthlessly determine what to stop doing. For this, the PTOS methodology uses a powerful tool in the Iterate phase—the Stop-doing list.

Fundamental Principle

A Stop-doing list is not "an extra document for show." It's an integral part of the solution.

Every time you decide to make the next move (Next Bet), you are obliged to determine what you are giving up to free up resources and focus for it.

Why is it the Main Accelerator?

The Stop-doing list eliminates three main "devourers" of speed:

1. Hidden work: Supporting old, ineffective features, fixing bugs in code that no one needs.
2. Vague promises: "Eternal" tasks in the backlog that were once promised to stakeholders but have lost relevance.
3. Information noise: Discussing metrics that don't affect anything, and dashboards that only distract.

Consciously giving up these things frees up an enormous amount of energy that can be directed towards what truly matters.

What Can Be Included in a Stop-Doing List?

A Stop-doing list is not just a list of tasks to close. It's a list of conscious renunciations. Here are some typical categories:

1. Kill: We completely delete, disable, or stop supporting something.

   • Example: "We are removing the old import module because 0.1% of users use it, but it generates 20% of errors."

2. Rollback: We revert everything to how it was because our change caused more harm than good.

   • Example: "We are rolling back the new registration form design because it dropped conversion by 15%."

3. Freeze: We leave the feature as is and stop touching it until a new, strong signal appears.

   • Example: "We are freezing further development of the analytics module. It works, but its improvement is not a priority right now."

4. Stop promising: We stop making promises about certain features or directions to avoid accumulating unfulfillable obligations.

   • Example: "We are stopping promises to clients about HubSpot integration this quarter because we are focused on improving the core scenario."

5. Stop measuring and discussing: We remove noisy, uninformative metrics from dashboards and discussions that only distract.

   • Example: "We are no longer discussing DAU every week because our North Star Metric is the weekly frequency of value-event."

Stop-Doing is Focus Protection

If you don't have a Stop-doing list after an Iterate session, you've likely just added more work on top of existing work. Your focus hasn't sharpened; on the contrary, it has become even more diffused.

Implement the Stop-doing list as a mandatory part of your product rituals. It enforces discipline, forces difficult but necessary decisions, and ultimately makes your team truly fast.