Designing the workflow

The states and transitions ARE your process — write down the one you actually follow.

In this lesson

The states are the process

Every task on the Korba café flows through the same set of stages — To Do, In Progress, Review, Done. Read left to right, that is the journey of a single piece of work from being asked for to being signed off.

Each stage is called a state, and the list of states is simply your process written down. Not a secret kept in somebody’s head — here, where everyone reads the same thing.

Shaping it yourself

Below the diagram, the states and the moves between them are an ordinary, editable list. Nothing here needs a developer or a support ticket — Youssef changes the process himself.

He adds a Client Approval stage, right there in the list, because on this job Salma’s drawings must pass the client before a task can be called done.

Wiring it in

A state on its own is just a name, though. The thing that makes it reachable is a transition — the allowed path from one stage to the next. Without one, Client Approval would be a stage no work could ever enter.

So he wires a transition: work in Review can now move to Client Approval before it reaches Done. That single link is what enforces the rule that nothing skips the client’s sign-off.

Guarding a move

Any transition can also be gated with a rule — who is allowed to move it, or what must be true first. A snag, for instance, can be refused close-out until its photo evidence is attached.

The habit that matters

The habit: write down the process the team actually follows, not the one a textbook prescribes. A workflow that matches the site gets used; one that does not is quietly bypassed.

What just happened

  1. The states are the process

    Every task on the Korba café flows through the same set of stages — To Do, In Progress, Review, Done. Read left to right, that is the journey of a single piece of work from being asked for to being signed off.

  2. Shaping it yourself

    Below the diagram, the states and the moves between them are an ordinary, editable list. Nothing here needs a developer or a support ticket — Youssef changes the process himself.

  3. Wiring it in

    A state on its own is just a name, though. The thing that makes it reachable is a transition — the allowed path from one stage to the next. Without one, Client Approval would be a stage no work could ever enter.

  4. Guarding a move

    Any transition can also be gated with a rule — who is allowed to move it, or what must be true first. A snag, for instance, can be refused close-out until its photo evidence is attached.

  5. The habit that matters

    The habit: write down the process the team actually follows, not the one a textbook prescribes. A workflow that matches the site gets used; one that does not is quietly bypassed.

Open settings Opens Taskity in your own project.

Next: Letting the system chase people →

Put it into practice.

Boards, approvals, snags and client sign-offs — one platform your team will actually use.

fitdatum.com