Ford-style flow and waste review
OfficialOfficial · updated Nov 4, 2026 · v1.0.1
Follows one item through a process and checks it against Henry Ford's flow principles: bring the work to the person, arrange steps in sequence, fixed handoffs, paced by trial, minimal stock.
Sign up free to add this skill to your pod
You come back here after you sign in, and add it with one click.
When to use it
- Work waits between people and people spend their time fetching, searching or carrying
- A workspace, tool layout or handoff needs redesigning
- Stock or a backlog keeps piling up between steps
What you give it
- One process as really done, arrival to exit
- Work and wait time per step, and how the item moves
- Trips, searches and carries with times
- Stock between steps and daily use
What you get
The item's path with work and wait time, the trips, searches and carries sized, layout and handoff changes that bring the work to the person, and one small trial.
Changelog
- v1.0.1 · Nov 4, 2026 · Example output now opens with the attribution and not-affiliated lines, as the skill's own checks require.
- v1.0.0 · Nov 4, 2026 · First release.
Sources
- My Life and Work, Henry Ford with Samuel Crowther (1922) - Project Gutenberg eBook #7213 (2026-11-04)
- Henry Ford: Assembly Line - The Henry Ford (2026-11-04)
- K-12 Research Guide: Assembly Line - The Henry Ford (2026-11-04)
Related skills
- Ohno-style seven wastes review Walks one process step by step, sorts it into value-creating work, incidental work and Taiichi Ohno's seven wastes, ranks the wastes and proposes what to remove first.
- Ohno-style 5 whys root-cause analysis Finds the root cause of a problem with the 5 whys Taiichi Ohno illustrated: a measured gap, a chain of whys with evidence at each step, and a fix for the cause, not the symptom.
- SOP from an explanation or recording Turns an explanation or screen-recording transcript into an SOP with a trigger, roles, exact-label steps, decision points, checks, and an owner.
- AI automation opportunity scan Scores a team's recurring tasks on frequency, time, rule clarity, and risk to find AI candidates, then picks the top 3 with a first experiment each.
- Team retrospective Runs a team retro from notes or a survey: themes, root causes with 5 whys, and 1 to 3 experiments with an owner and review date.