The Alactic library

Automation design guides

From a better WhatsApp conversation to a clearer team handoff. Find a specific decision, a useful checklist or a workflow your business can put into practice.

19 articles in Automation design

Clear filters
Automation design

Design a safe default path for cases no workflow branch covers

An unmatched case should not disappear or trigger a convenient catch-all action. Use an explicit fallback contract to preserve context, stop unauthorised actions, and route unresolved work to a named owner.

10 min read
Automation design

Write a workflow diagram in prose that two teams can interpret the same way

Turn a clear-looking flowchart into a shared operating specification with explicit authority, deadline rules, version control and terminal outcomes.

9 min read
Automation design

Decide what happens to active workflows when rules change

A revised workflow does not settle what happens to work already in progress. Use a continuation record to resolve wording, eligibility, sequence and deadlines without repeating completed actions.

9 min read
Automation design

Keep manual overrides from being immediately undone by automation

A manual change needs more than a new field value. Define what automation must leave alone, for how long, and under which release conditions—with a filled worksheet for three common override types.

10 min read
Automation design

Choose when to split a large workflow into smaller workflows

Split workflows around distinct decisions and independently verifiable outcomes. Use this filled worksheet and withdrawal trace to keep context, authority, and unfinished work clear.

9 min read
Automation design

Design the next step when only part of a workflow completes

Use a partial-completion decision table to preserve valid work, hold dependent steps, assign review, and authorise specific compensating actions without restarting everything.

9 min read
Automation design

Prevent competing workflows from making conflicting changes

When separate workflows can change the same business state, reasonable actions can collide. Use an authority map and a filled conflict matrix to decide which workflow waits, yields, stops, or requests review.

10 min read
Automation design

Decide when a completed record may enter the same workflow again

Separate genuine new work from incidental edits. Use a filled re-entry decision table to decide which completed, cancelled, expired, and manually stopped workflow instances may start a new cycle.

11 min read
Automation design

Resume a workflow after human review without using stale approval

Bind approval to a specific proposal, distinguish proposal revisions from internal edits, and route changed or expired cases back to the right check or decision.

9 min read
Automation design

Choose which workflow decisions require human review

Put human review before decisions that create meaningful commitments, resolve material uncertainty, or exceed delegated authority—not in front of every exception.

10 min read
Automation design

Define stop paths that cancel future work cleanly

A workflow is not stopped just because its main branch ends. Define what happens to queued actions, timers, reviews, and completed work, then record the outcome with a filled stop-path checklist.

10 min read
Automation design

Choose when a workflow timer starts and what can reset it

Stop routine edits from restarting workflow timers. Define the start event, meaningful resets, pause rules, and expiry checks with a filled fictional timeline your team can adapt.

10 min read
Automation design

Set timeouts that produce a clear next decision

Give every workflow wait a completion event, deadline, timeout destination, and accountable owner—and resolve competing events before releasing work.

9 min read
Automation design

Order workflow actions by dependency rather than convenience

A workflow should advance when a prerequisite is confirmed, not merely when the previous action was attempted. Use a filled dependency worksheet to separate safe parallel work from steps that must wait.

10 min read
Automation design

Separate workflow entry conditions from action-time checks

A record that qualifies when a workflow starts may not qualify after a delay. Use a filled eligibility matrix to decide what to check at entry, what to recheck before action, and how to handle changed or unknown states.

10 min read
Automation design

Resolve overlapping conditions before choosing workflow branches

When several workflow conditions are true, decide whether one path wins or several may run. Use a filled decision table to define precedence, permitted combinations, exclusions, and recovery.

10 min read
Automation design

Handle unknown values without treating them as false

Missing evidence is not a negative answer. Use explicit true, false, and unknown states to route requests, resolve uncertainty, and prevent unsupported actions.

9 min read
Automation design

Decide whether a workflow runs once per person, request, or transaction

A completed workflow should not block a new request from the same person. Use a filled scope worksheet to define the unit of work, its identifier, and the actions that belong to each instance.

10 min read
Automation design

Choose the event that should start a workflow

Stop unrelated record edits from starting work. Compare creation events, meaningful state transitions, and scheduled checks, then define the evidence each start requires.

10 min read

Turn a guide into a working customer journey.

Explore the tools and services behind the operating process.

Explore Communications