Executed or failed: why every priority needs a verdict

At the end of every month, each priority in Unbreakable OS closes as executed or failed. There’s no "mostly done" and no "carry over". Here’s why we built it that way.

Calvin Seamons, head developer · 2 min read · Updated October 2026
In short
  • Every priority ends the month executed or failed, with the results written down.
  • There’s no in-between status, on purpose.
  • A failed priority is information for the next decision meeting.
  • Unfinished work can be pitched again as a new decision.
On this pageHow a priority endsWhy there’s no "mostly done"Failing isn’t a punishmentWhat the verdicts add up to

Most companies have a project that’s been "almost done" for six months. Nobody decided to keep it going. It just never ended, so it keeps taking time and attention from everything else.

We built Unbreakable OS so that can’t happen quietly. Every priority has a month, and at the end of that month it gets a verdict.

How a priority ends

A priority starts as a pitch leaders approved in the decision meeting. It gets one owner and a month. During the month the owner posts weekly updates, marking it on course or deviating. At the end of the month the owner closes it one of two ways.

  • Executed: it delivered what the pitch promised.
  • Failed: it didn’t.

To close it, the owner has to write down what actually happened. A verdict without the story behind it doesn’t teach anyone anything.

Why there’s no "mostly done"

We could have added "partially complete" or "carried over". Both are easier to click. Both cause problems. Partial credit turns every month-end into a debate about percentages. Carrying work over skips the most important question: knowing what we know now, is this still worth next month?

That question belongs in the decision meeting, not in a status field. So if something didn’t get finished, it’s marked failed. If it still matters, it gets pitched again, and leaders decide with fresh eyes. Either way, someone made a decision.

Failing isn’t a punishment

People sometimes worry "failed" will be held against them. It shouldn’t be, and a healthy team will have some failures every month. Pitches are bets. If every single one gets executed, the bets are probably too safe.

What matters is the pattern. If something failed because the scope was too big, pitch smaller next time. If it failed because another piece of work slipped, change the order. The written results are what make those patterns easy to spot.

Give every priority a clear endingStart with 45 days free. Card required, $0 charged during the trial.
Start free trial

What the verdicts add up to

Because every priority ends one of two ways, you get a clean record: what you decided each month, who owned it, and what actually got done. That record becomes your execution rate, the share of finished priorities that were executed.

It also keeps the next month clean. You start with new decisions instead of last month’s leftovers.

Calvin SeamonsHead developer of Unbreakable OS. He builds intelligent systems for a living and leads engineering across the product’s AI, web and mobile apps.

Run your next month on it.

Start a 45-day trial today. A team member runs your onboarding call after you sign up.

Start free trialCard required, nothing charged during the trial.