DOMINIC J. ARROW Let's talk

Software / Systems / AI

Find thesignal.

Many fine lines forming one coherent shape A POINT OF VIEW

01 / Perspective

A clear mind.
For complicated things.

02 / Approach

Clarity is a choice.

Less.
But deliberate.

See the whole.
Question the unnecessary.
Make the essential work.

From complexity to clarity An abstract field of tangled paths sharing a beginning and an end, with one path picked out in orange.

Human judgement.
Machine possibility.

03 / The real organisation

Follow one changed order.

The work ignores
the org chart.

Sales has the promise. Operations has the constraints. Finance has the exposure. The customer has one question: what happens now?

Before adding AI, trace where context disappears, where approval waits, and who owns the exception.

The organisation on paper. The work in practice. An illustrative order change crosses Sales, Operations, Finance and Service. Orange paths connect the actual handoffs across grey reporting lines. REPORTING LINES Sales 01 Operations 02 Finance 03 Service 04 Customer request 1.1 Revised quote 1.2 Promise made 1.3 Stock & capacity 2.1 Delivery plan 2.2 Exception found 2.3 Margin check 3.1 Credit terms 3.2 Approval needed 3.3 Customer history 4.1 Status update 4.2 Promise kept 4.3 The organisation on paper. The work in practice. An illustrative order change crosses Sales, Operations, Finance and Service. Orange paths connect the actual handoffs across grey reporting lines. REPORTING LINES Sales 01 Operations 02 Finance 03 Service 04 Customer request Revised quote Promise made Stock & capacity Delivery plan Exception found Margin check Credit terms Approval needed Customer history Status update Promise kept
One changed order. Four teams. Context has to travel with the work.

Illustrative workflow / trace the handoffs

Worked example: a delivery date changesAI drafts. A person decides.

Illustrative example / one changed order

The customer needs it sooner. The order, stock record and delivery plan no longer tell the same story.

01 / Gather the evidence
Order, stock, margin and customer history. Keep each fact linked to its source.
02 / Give AI a bounded role
Draft the next action, flag conflicting facts and cite the records used. Missing evidence becomes a question.
03 / Keep authority human
A named person approves the price, delivery promise and customer message.
04 / Test against today
Compare missing information and rework with the current handoff before expanding.

If the records cannot support a recommendation, stop and escalate. A fluent answer is not evidence.

Find the handoff.
Keep the context.

Close the loop

04 / The learning system

Decisions need a way back.

A decision is
half a loop.

A model recommends. A person decides. The outcome becomes new evidence.

Connect the recommendation to its sources, name the person who can act, then test the result against what actually happened.

A continuous Möbius ribbon A broad half-twisted ribbon forms one continuous surface and one continuous orange edge.
One half twist joins every perspective into the same continuous system. Orange signals travel its single edge and return changed by new evidence.

Möbius surface / evidence · action · outcome

01 / Ground itUse the actual records.
Show the sources.

02 / Give it an ownerAccept, change or reject.
Someone owns the decision.

03 / Close itRecord the decision and result.
Review what needs to change.

Feedback is part of the design.

Choose a first test

Find the first useful move.

Bring one real workflow: the decision, the handoff, or the exception that keeps coming back.

Start with one handoff. Agree who owns it, track missing information and rework, then decide whether to expand.

A bounded first experiment A decision blueprint where workflow, friction and ownership converge on a first test. Success and stop conditions both lead to review. TEST BOUNDARY / 01 ONE WORKFLOW WORKFLOW repeated handoffCONTEXT LOSS FRICTION decision delayWAIT / REWORK OWNER who decides?CLEAR HANDOFF 01 FIRST TESTsmall + reversible ASUCCESS SIGNALfewer missing fields BSTOP CONDITIONrework does not fall REVIEW learn + adjust Workflow, friction and owner define a first test, with success and stop conditions leading to review. WORKFLOWthe handoff FRICTIONthe delay OWNERwho decides? FIRST TESTsmall + reversible SUCCESS SIGNALfewer missing fields STOP CONDITIONrework does not fall REVIEW + ADJUST
A small experiment, with a clear boundary.

05 / A first move

AI & systems consulting

A working conversation with Dominic. Trace the bottleneck, question where AI belongs, and identify a useful next step.

25 minutes Video call

One workflow. One constraint. A useful place to start.

© 2026 Dominic J. Arrow Amsterdam LinkedIn