The Field Report

Short pieces on problems that repeat across industries, each traced to its mechanism. Written for the leader who recognizes the situation and wants to know why it keeps happening.

Latest

The record that exists in one system and not the other

How a record reaches one system and never the other, and the two-way check that finds it.

Amit Govil · October 22, 2026

Read the perspective

XONIK, When two systems tell the same customer different things. Line illustration of two systems holding different answers about the same customer, drawn as two columns, one line short.

The Field ReportWhen two systems tell the same customer different thingsWhy one customer hears two answers, what staff do about it, and how to name a source for each fact.October 22, 2026 · 10 min read

XONIK, The decision that comes back every quarter. Line illustration of a decision that returns to the agenda because no one can close it, drawn as a ring of steps, one broken.

The Field ReportThe decision that comes back every quarterWhy settled decisions return, and what it takes to close one.October 22, 2026 · 10 min read

XONIK, Agreed in the meeting, owned by no one. Line illustration of a decision leaving a meeting with three people and no owner, drawn as parallel lanes, one hand-off broken.

The Field ReportAgreed in the meeting, owned by no oneWhy agreement is not assignment, and what turns a nod into an owner.October 22, 2026 · 10 min read

XONIK, What a pilot gets for free that production has to pay for. Line illustration of what a pilot receives for free, stacked, and the layer production has to pay for, drawn as stacked lines, one layer failing.

The Field ReportWhat a pilot gets for free that production has to pay forThe free things a pilot runs on, and who pays for each in production.October 22, 2026 · 10 min read

XONIK, The handover nobody scheduled between pilot and production. Line illustration of the handover between pilot and production, as the span nobody scheduled, drawn as two banks, one span missing.

The Field ReportThe handover nobody scheduled between pilot and productionWhy the first thing to schedule is the day someone else takes over.October 22, 2026 · 10 min read

XONIK, What your team cannot do while one person is on leave. Line illustration of a team's capabilities as columns, with the ones that stop during an absence, drawn as columns crossed by a broken path.

The Field ReportWhat your team cannot do while one person is on leaveA capability map of what stops in an absence, found by asking.October 22, 2026 · 10 min read

XONIK, The process that waits for one person to come back. Line illustration of a process stopped on a line until one person returns, drawn as a ticked line that slips once.

The Field ReportThe process that waits for one person to come backThe unwritten step one person holds, and how to see it before they are away.October 22, 2026 · 10 min read

XONIK, Why an assistant names your competitor and not you. Line illustration of an assistant choosing between two firms, one that can be verified and one that cannot, drawn as one line splitting, one branch short.

The Field ReportWhy an assistant names your competitor and not youWhat an assistant can check about two firms, and where to look first.October 22, 2026 · 11 min read

XONIK, The buyer who asked an assistant and never found you. Line illustration of a buyer's question traveling outward, reaching everything except the business, drawn as arcs from a dot, one blocked.

The Field ReportThe buyer who asked an assistant and never found youA lost buyer leaves no trace; a question log is how you find them.October 22, 2026 · 10 min read

XONIK, Every change now needs a meeting it did not need before. Line illustration of changes passing through more and more approvals until few come out, drawn as a narrowing funnel with one leak.

The Field ReportEvery change now needs a meeting it did not need beforeHow a meeting grows around a fragile system, and how written contracts return decisions to teams.October 22, 2026 · 10 min read

XONIK, Why the third change costs more than the first. Line illustration of each change costing more than the one before it, as a staircase that steepens, drawn as amber steps, one of them broken.

The Field ReportWhy the third change costs more than the firstWhat each change leaves behind, and why the next change has to pay to find it.October 22, 2026 · 10 min read

About the Field Report

What is a perspective, and what does it leave out?

A perspective is a short observation from delivery work. It opens with the answer, describes a situation a leader will recognize, traces it to the mechanism underneath and says what changes it. A diagram appears only where it does the work a table of findings would. It is built to be recognized in, and read in one short sitting.

What it leaves out is the evidence base. A perspective makes no claim about how common a problem is and names no client, so it describes how a failure forms and leaves the weight of the argument to the research reports behind it.

The six problems the series keeps returning to

Pilots that prove a model and then stop. The handover nobody scheduled between pilot and production looks at the date no plan names. Its companion lists what a pilot gets for free.

Decisions agreed and not carried out. Agreed in the meeting, owned by no one describes the room that leaves with different beliefs about who acts. Its companion asks why a decision returns.

Systems that disagree. When two systems tell the same customer different things covers the copies of one fact. A second covers the record that exists in one system only.

Change that gets dearer. Why the third change costs more than the first follows what each change leaves behind. The next piece asks why every change now needs a meeting.

Buyers who ask an assistant. The buyer who asked an assistant describes a loss that leaves no trace in any record. Its companion asks why a competitor is named instead.

Work that waits for one person. The process that waits for one person traces a step the process never named. The last asks what a team cannot do while that person is away.

The example in a perspective is a prop. The mechanism is what carries over to your team.

Read the perspective, or go straight to the report?

A perspective is enough when

You want to know whether a problem on your own team is the one described.
You are preparing a conversation with a colleague and need the mechanism in plain words.
You have a short sitting and a particular team in mind.

Go to the report when

You must explain how the failure forms to people who will challenge it.
You need the method, the sources and the limits in front of you.
You want the self-check to run against your own organization.

A perspective costs a short sitting and helps you recognize a problem. It cannot show how the problem forms in your case, and it states no rate. The report can, at the cost of a longer read.

Where a problem is set out in full

Each problem has a longer treatment elsewhere on the site. Use the table to find it when a perspective has told you enough to want the whole argument.

If this is your problem	Go deeper with
A pilot that worked and never reached daily use	The report on why AI pilots stall, and the AI-to-Production Readiness Assessment
A decision nobody carries out, or nobody keeps closed	The report on ownership of live AI systems, and the AI Governance Assessment
Systems giving a customer different answers	The report on systems and data that stop agreeing
Each change costing more than the last	The Technology and Architecture Risk Assessment, which asks about change and dependencies
A buyer who asks an assistant and never finds you	The report on being found through AI assistants, and the AI Search Visibility Checklist
A process that waits for one person	The Technology Architecture Review Checklist, with its section on ownership and knowledge

How is one made, and where does it lead?

A situation earns a piece when it recurs across different businesses and has a mechanism that can be stated. The example is described so that no client could be recognized, and a law or standard is cited once the passage it supports has been read. Drafting tools may help; a person checks every fact and the piece goes out under that person's name. A published perspective is revisited when the report or source behind it changes.

When a piece describes a problem you have, the free tools give a first scored read in your browser. AI Consulting is the service for pilots and ownership, and Technology Consulting for the problems about systems and change.

What do readers ask about the Field Report?

Should I read a perspective or go straight to the report?

Read a perspective when you want to know whether a problem on your team is the pattern described, or need the mechanism in plain words for a colleague. Go to the report when you must explain the failure to people who will challenge it, or want its method and self-check.

Does a perspective say how common a problem is?

No. A perspective makes no claim about how common a problem is. It describes how a failure forms and what changes it, and leaves the weight of the evidence to the research reports behind it. Test the mechanism against your own team.

Are the examples real clients?

No client is named, and each example is described so that no client could be recognized. Treat the example as a prop. The mechanism is what carries over to your team, so ask whether the same steps are happening in your own work, whatever your industry.

How does a situation earn a place in the Field Report?

It has to recur across different businesses and have a mechanism that can be stated. A person checks every fact against its source, and the piece goes out under that person's name. It is revisited when the report or source behind it changes.

Does one of these sound like a team of yours?

Name the team and the step that waits, and we will tell you whether it is the pattern described or something else.

Describe the situation Read the research behind these pieces