What happens between a request and a result.

One piece of work, followed from start to finish, including the part where it stops.

Worked example

Worked example with sample data.

  1. Request

    A client cancels the 2:00 PM appointment. The booking tool records it.

  2. Context

    Three people on the waitlist asked for an earlier time. Two have agreed to receive texts. One opted out yesterday. It is within business hours.

  3. ExceptionStopped

    The person who opted out is taken off the list. She is left off before anyone is asked.

  4. DecisionHeld

    Offering a slot by text is on the list of things the owner approves. The owner gets one message: "2:00 PM just opened. Offer it to Maya and Luis? Reply Y to send, N to skip."

  5. PermissionDone

    The owner replies Y at 1:48 PM. The approval covers these two people and this slot, and it expires.

  6. ActionDone

    The offers go out. Whoever accepts first gets the slot. The others are told it is taken.

  7. OutcomeDone

    Slot filled at 1:52 PM. The request, the person left off, the approval, the two messages sent and the result are on record.

How we design it.

What stops the work.

What stops the work, and what happens
SituationWhat happens
The action involves money, a refund or a price HeldIt waits for a named person
The message is a first contact with someone new HeldIt waits for a named person
The approval has expired, or the details changed after approval HeldIt asks again
The person opted out StoppedThe message is not sent.
The system is not sure HeldIt asks, or it hands the matter to a person. It does not guess
Something fails StoppedThe work stops, a person is told, and the failure is recorded with its cause

We run our own company this way.

These are accounts of Kijestic's internal work. They are not client results.