Systems at Scale · Consulting · anonymized synthesis

AI platforms for operators who didn't build them

A model is one step in someone's day. The rest of the workflow decides whether it gets used.

Role
AI Decision Science Analyst, Accenture Strategy & Consulting Owner-reported
Relationship
Team member
Period
2024 – present
Where
Southeast Asia — FMCG, telco, banking, energy and public sector

Anonymized aggregate · no client names or figures

The situation

Across consulting engagements in several sectors, the same pattern comes back: AI systems are built by engineers, but run every day by operators who did not build them and need to trust what they do.

If reviewing an answer, handling an exception or handing work to a colleague is awkward, the system fails no matter how good the model is.

People in the picture

  • Operators and analysts who run AI systems day to day

What I did

My work spans customer-service assistants, content and campaign workflows, data-migration automation, analytics for commercial decisions and AI roadmap prioritisation.

Client names, figures and original diagrams are withheld. What is shown here is the shape of the problem, redrawn generically.

  • Agentic systems
  • Applied machine learning
  • Analytics
  • Workflow design
  • Stakeholder translation

Decisions that shaped it

  1. Design the review step, not just the model

    Where a person checks, corrects or escalates an output is part of the product. It decides whether the system is trusted.

    Owner-reported

  2. Make the system legible to non-engineers

    Operators need to know what the system did and why, in their own terms — not a model score.

    Owner-reported

What was made

a generic operator-facing stackgenericsees what it did, in plain termsreviewexceptionshand-offsone step, not the productmany sources, uneven qualityoperatorworkflowmodelsdataadoption is won or lost in the workflow layergeneric redraw · no client system depicted
A generic operator-facing AI stackConceptual illustrationOwner-reportedData, models, workflow, operator. Redrawn generically — no client system is depicted.
model onlyinputmodeloutput?then what? who checks it?the whole workflowinputmodelreview · a person decidesapprovecorrectescalateto someone seniorhand-offcolleaguegeneric redraw · no client system depicted
Where judgment sitsConceptual illustrationOwner-reportedModel-only on the left; the whole workflow on the right, with review, exceptions and hand-offs designed in.

Results

Not claimed yet. Results appear here only once they are documented — until then, this page shows what was designed, built or proposed.

Limits and honest caveats

  • All engagements ran under confidentiality. No client names, identifying figures or original diagrams appear on this site.
  • Reported results from individual engagements are withheld until they are documented and cleared.

In the Living Mind

This world feeds these lessons: