Workflow

IMPORTANT Durable execution is a crash insurance for a long-running software. It is not a business process, and adopting it does not mean your organization “has a workflow.” What it actually solves A program holds its state in memory, and memory does not survive the program. When a process dies halfway through a job, everything it knew is gone: which step it reached, which steps already completed, whether the payment went out once or twice. Regardless of the job. ...

IMPORTANT When someone says “we have a workflow for that,” they mean one of (at least) three things. Ask which. The answer tells you whether you are looking at a business decision, a description of one, or a piece of plumbing. One word, three jobs Start with something older than software. A workflow was a paper routing slip. A form moves desk to desk: approve, stamp, forward to accounting. Each desk does one step. The slip records where it is and what has already happened to it. If a clerk quits mid-task, someone finds the slip in the in-tray and picks it up, because the state is written on it. ...

The Flight Plan and the Autopilot The elusive goal of the “Competitive Advantage” What will “give” the “competitive advantage” is the Operational model, in order to navigate the whole organization around that huge iceberg of legacy. https://method.dbj.org/shop/ OP model introduction is not simple. But its worth it. Especially if organization is small(ish) and not too calcified. Just decide on one OP model, implement it and follow it. AI or no AI. ...