Each figure only once: what rebuilding the shift book showed
A page with eight control bars looks complete. In a shift it costs orientation. Rebuilding the shift book removed many controls without losing a single function.
Read more →Notes
I write about postings, shift handover, product boundaries and what counts after go-live. Product news is on the homepage.
A page with eight control bars looks complete. In a shift it costs orientation. Rebuilding the shift book removed many controls without losing a single function.
Read more →Whoever changes a recipe version or a posting leaves a trace. It belongs in the system, not in a wiki nobody opens during a shift.
Read more →Knowing the batch log and shift handover changes the questions you ask. That produces different rules in the system, and not just more fields on the same screen.
Read more →Both use the same domain core, but they serve different working days. In one application, drafts end up in stock or stock ends up at the desk.
Read more →Batch sheet and daily log describe the same day. If they sit in separate systems, it shows at shift handover at the latest.
Read more →After weighing, a posting has already changed the silo and the batch log. Corrections are therefore made with a reversal, a cancellation or a reconciliation.
Read more →A shared shift start, migrations and backups are often added late. In production they belong in the application from the beginning.
Read more →First call · 30 minutes · free
A few sentences about the process are enough: what runs in lists or side calculations today, and who works with it. Within two working days you get a reply and a clear view of whether I am the right person for it.