1
4 Comments

Seeking a partner to test decision-boundary rules in async

I’m mapping why async B2B workflows stall before a decision.

The pattern I keep seeing is simple: reversals feel risky when the reopen condition is undefined.

What I want to test with a collaborator:

  • Define “this decision reopens only if X changes” rules
  • Make ownership and expiry visible in the workflow
  • Compare what changes in momentum when these defaults are explicit

I’m not looking for a long chat or a vague brainstorm.

If this resonates, leave a comment with one decision type you’ve seen reopen repeatedly, and I’ll share a minimal boundary template that stops the churn.

on January 14, 2026
  1. 2

    That happens, based on my experience, when an enterprise gets bigger and when the decision is not concentrated on 1 person. When the decision is divided, the responsability of a failure is also divided. Lack of leadership, maybe.
    I used to notice that some decisions stay "in the air" and no decision gets taked, because no one wants to take responsability from it. Then, one day, sometimes months later, when no one talks about that anymore and it seems less risky, someone takes action, because the responsability seems lower.
    I face that pattern everyday.
    Actually, i guess the problem is that no one wants to take that for real. The consequence will allways seems more scary than the incentive.

    1. 1

      That matches what I keep seeing as well.

      Once ownership is diffused, the decision never really closes.
      It just waits until the perceived risk drops enough for someone to act.

      In many cases, nothing changes in reality.
      Only the fear decays over time.

      I’m trying to make that boundary explicit earlier,
      so decisions either move forward for a clear reason,
      or pause intentionally instead of lingering in the air.

      1. 2

        So, what's your plan?
        You want to create an "modus operandi", that force them to act?
        That would force to recreate the organizational chart of the company.
        Or...

        1. 1

          Not trying to force action or redesign org charts.

          What I’m testing is much narrower.

          I’m making the decision boundary explicit without changing who owns the decision.
          Who decides stays the same.
          What triggers movement or pause becomes visible.

          The goal is not to make people act.
          It’s to remove the ambiguity that lets decisions linger without intention.

          If action follows, it’s because the conditions were already met.
          If not, the decision pauses on purpose instead of drifting.