Part of it is already shipped

Where it got stuckManagers copied requests from email into the records system. By morning, stock no longer matched what had been promised to the client.

What we are buildingWe are building an order workspace: the client sees available stock, the request lands in the records, and the warehouse gets the pick without entering it again.

Where this is headingThe check of “what was promised and what was shipped” will leave its separate morning shift. The system is still being built.

Where it got stuckBookings lived in the administrator’s messenger. A substitute on the shift lost track of who had confirmed the visit.

What we builtWe made a schedule, a bot for confirmation, and a visit record that both reception and the doctor can see.

What changedA substitute opens the shift and sees the day, without the correspondence being forwarded.

Where it got stuckThe work order arrived as a file. Photos from the site settled in personal phones. The acceptance note was put together in the office in the evening.

What we are buildingWe are building an app: a work order, a checklist, a photo, and a signature on site. The office will receive a closed package, not a folder of photos.

Where this is headingThe acceptance note will be assembled on site. We work in cycles. The showing happens along the way.

Where it got stuckMaterials sat on a drive, progress was marked in a spreadsheet, and the mentor could not see who was stuck.

What we builtWe built a workspace: modules, a completion mark, and a short report to the mentor for the group.

What changedThe mentor sees who is falling behind before the probation period ends, not from memory.

Where it got stuckThe client report was assembled by hand once a week from the workspaces. By the meeting, the figures were already old.

What we builtWe pulled the workspaces onto one screen and left the manager’s comment next to the figure, not in a separate email.

What changedThe client meeting runs from today’s screen, not from a file dated last Thursday.

Where it got stuckOne person shipped the release in the evening. A rollback was possible only if they remembered what had changed.

What we builtWe described the environment, separated staging and production, tied deploy to the repository, and left a change log.

What changedAny person on support can deploy a version. Rollback is the previous build, not a search through memory.

Where it got stuckAccess was handed out “for the duration of the project” and never taken back. Before a client check, no one could show the list of live accounts.

What we builtWe went through the entry points, removed extra roles, turned on a log, and left a short rule for who grants access.

What changedThe question “who opened the record” has an answer in the log, not in the administrator’s chat.

Where it got stuckA request from the site landed in a shared inbox. Who had taken the lead was visible only by who replied first.

What we builtWe set up a queue: source, owner, next step, and a reminder if the record was left untouched.

What changedA lead has an owner within the first hour, not at the end of the day.

Where it got stuckEnergy was read from the bill at the end of the month. A peak in a particular workshop was noticed only after it had passed.

What we builtWe took readings from the nodes, showed consumption by workshop, and set a message to the on-call person when a threshold is crossed.

What changedThe on-call person sees a spike during the shift, not in the closing documents.