Factory habits applied to building software.
All notes

Digital transformation

Three factory habits I use in software

Standard work, inspection at the station, and readiness before launch.

I spent my first years on production lines, World Class Manufacturing at Unilever and product launches at BAT, before moving into digital systems and then building software. The longer I build software, the more of the factory I see in it. Three habits carry over almost unchanged.

1. Standard work

On a line, standard work is the best-known way to do a job, written down so it can be improved. Without it there's nothing to improve against, and every shift runs its own experiment.

In software, shared ways of working, templates and a definition of done give the team a reference for checking a change.

2. Catch defects at the station

One of the most useful things I did in manufacturing was moving inspection into the process: checkpoints during scale-up and fast feedback to operators, instead of finding defects at the end, when they're expensive and the context is gone.

In software, run tests and reviews close to the change. Cargo & Consequence checks engine behaviour, code quality and formatting on each push.

3. Readiness before launch

At BAT, launch time came down from about five months to two through better planning: readiness checks, named owners and regular decisions across sourcing, planning, manufacturing and quality. Problems showed up while there was still time to fix them.

Before releasing a software change, check the affected workflow, its tests and the people responsible for support. Resolve any missing prerequisite before committing the release date.

NextAlarm management: make each alert worth responding to

Discuss an operations problem

I work with operations and transformation teams on operational excellence, digital transformation programs, supply chains and industrial AI. Send me the problem you’re working on and the result you need.

Abolfazl ShirkavandImage preview unavailable