What a forward-deployed engineer does in week one.
Less building than you might expect. Mostly sitting with the team and writing down how work really moves.
People expect the first week of an automation project to be about software. Ours is mostly about people: sitting next to the team that does the work, following real requests, and writing down where they wait.
Day one: a first read
You write one sentence about what takes too long. Before we meet, an engineer replies with what we heard, in plain words, so you can correct it early.
Days two and three: a call
Thirty minutes to understand the work and who it touches. We ask who raises it, who picks it up, and who is waiting at the end.
The rest of the week: walk the work
We sit with the people who do it and follow a handful of real requests from the moment they arrive to the moment they are done. The task itself is rarely the problem. The delay usually sits between two desks, and that is what we write down.
"The first deliverable is a page of notes, not a line of code."
What you have by Friday
- {{ q.n }}{{ q.t }}
Building starts in week two, on your systems, with your people deciding every exception. Thirty days after it goes live, we measure again the same way we measured the baseline.