Skip to main content

Illustrative examples

See how a familiar problem can become a practical first step.

Review familiar software situations, the decisions they raise and practical ways to test a direction before discussing your own context.

These are composite, illustrative examples, not client cases or claims of delivered results. They do not describe a specific organisation, project or confidential system from previous employment.

01
Fragmented systems and handovers

Create one controlled flow across existing systems

What you may recognise

Information is copied between an ERP platform, spreadsheets, portals and partner systems. People reconcile differences manually, while failures become visible only after work or a customer is affected.

Decision to clarify

Establish which system owns each piece of information, which failing handover causes the most harm and whether integration can improve the flow without replacing useful systems.

Controlled information flowSystem integrationVisible failures
Review this example
02
Software no longer fits the operation

Support the rules and exceptions that matter

What you may recognise

The standard path works, but important exceptions live in spreadsheets, free-text fields and individual knowledge. Routine changes are slow because the operation and its software have drifted apart.

Decision to clarify

Determine which needs justify configuration, integration, extension or purpose-built software, and which exceptions should remain a deliberate human decision.

Complex decision logicDomain knowledgeOperational fit
Review this example
03
Customer journey disconnected from operations

Connect a customer application to the back office

What you may recognise

Customers submit a request but lose visibility once internal work begins. Staff copy information between channels, answer status questions manually and handle exceptions outside the customer-facing application.

Decision to clarify

Identify which customer promise can be supported by dependable operational information and which back-office actions, permissions and exceptions must be part of the same workflow.

Customer journeyBack-office workflowEnd-to-end workflow
Review this example
04
AI opportunity needs careful assessment

Test AI against a real workflow and measurable value

What you may recognise

A repetitive knowledge task appears suitable for automation, but the quality of available data, acceptable error, privacy, integration and human oversight are still unclear.

Decision to clarify

Decide whether AI, conventional automation or a process change fits the task, and where people must still review or intervene.

Applied AIHuman reviewMeasurable value
Review this example

A comparable situation

Start with the operation, not a predetermined solution.

Share the workflow, application, integration or custom business rule you recognise. A complete specification is not required.

Discuss your situation