A week on site
This page follows two of our forward-deployed engineers through one week of an Embedded Build, day by day, so you can see what they do on site and what they ask of your team.
The week at a glance
Section titled “The week at a glance”| Day | What happens | Who is involved on your side |
|---|---|---|
| Monday | Planning with the workflow owner | Workflow owner |
| Tuesday | Shadowing at the order desk, then building | The order desk |
| Wednesday | Building, then showing work in progress | Two people from the order desk, workflow owner |
| Thursday | The weekly release | Workflow owner, the order desk |
| Friday | Measuring and review | Workflow owner, sponsor |
Monday: plan with the workflow owner
Section titled “Monday: plan with the workflow owner”The engineers and the workflow owner start with last week’s measurements: how many purchase orders came in, how many drafts the order desk corrected and which fields they corrected. One correction leads the list. Customers order by their own part numbers, and the agent’s drafts often carry the wrong item.
They agree on this week’s change: a cross-reference from each customer’s part numbers to your item numbers, which the order desk maintains and the agent uses. They also agree on how they will know it worked: fewer part number corrections on the drafts. The workflow owner picks Thursday after lunch for the release, when the desk is quiet.
Tuesday: shadow, then build
Section titled “Tuesday: shadow, then build”One engineer spends the morning at the order desk, watching how each person translates a customer part number. One keeps a spreadsheet. One searches past orders in the ERP. One knows them by heart. The other engineer pulls together the pairings that already exist, from that spreadsheet and from past orders in the ERP data.
In the afternoon they build the screen where the order desk can look up, add and correct a pairing.
Wednesday: build and show
Section titled “Wednesday: build and show”The build continues. In mid-afternoon the engineers sit with two people from the order desk and run that morning’s real purchase orders through the work in progress. The order desk spots a problem within minutes: two customers use the same part number for different items. The engineers change the cross-reference so that each pairing belongs to one customer.
The workflow owner sees the result at the end of the day.
Thursday: release
Section titled “Thursday: release”In the morning the engineers test the change. The workflow owner signs off. After lunch it is released to the order desk.
Both engineers are at the desk. One walks each person through the change at their own screen. The other watches the queue as the first real purchase orders come through. Nothing changes in the ERP this week. At Level 1 the order desk still keys every order.
Friday: measure and review
Section titled “Friday: measure and review”The engineers compare the drafts made since the release with last week’s: how many needed a part number correction, and which ones the cross-reference missed. They review the result with the workflow owner, who decides whether the order desk keeps the old spreadsheet for now or retires it.
Then they write the weekly update for the sponsor. It says what was released, what the measurements show, what is planned for next week and which decision is waiting. This week’s open decision is whether a draft for a customer on credit hold should be held back or shown with a warning. It involves the controller, so it goes to the sponsor.
What the week did not do
Section titled “What the week did not do”The workflow did not move up the autonomy ladder. It stays at Level 1 until a promotion review moves it. Weeks like this one produce the evidence for that review: the software records every correction the order desk makes, and that record is how accuracy on real work is measured.
What the week asked of your team
Section titled “What the week asked of your team”- The workflow owner: the Monday planning session, a look at the result on Wednesday, sign-off on Thursday and the Friday review.
- The order desk: being shadowed while they work on Tuesday, a session on Wednesday afternoon and a walkthrough at their desks on Thursday.
- The sponsor: reading the weekly update and settling the credit hold question within a week.
- Your IT team: nothing this week. The change needed no new access and no change inside the ERP.