Features
Where the productivity systems examples agree, and where they do not
Toyota, Goldratt, Deming and three other named systems disagree about where productivity comes from, and the disagreement is the useful part.
Section
Features
Features
Business development ops framework: the pipeline is a queue, not a funnel
Explains why a business development pipeline works as a queue with limited attention, how to find a deal cap, define stages as buyer events and spot stalled deals.
Features
Operations case studies mistakes: the traps and the way around them
Operations write-ups mislead the next team in eight repeatable ways: what each omission does to a reader, and how to write an internal account that stays honest.
Features
Change management tools: four documents beat any tracker
Change management needs four documents more than it needs a product: what each contains, why a tracker turns into a graveyard, and when a plain file wins.
Features
Detroit lean operations compared with Chicago distribution process control
Operations process control in Detroit leans on takt and cycle time, while Chicago distribution runs on dock-to-stock and throughput metrics.
Features
Quality management guide: Write procedures people follow
A quality management guide to usable procedures: apply ISO 9001 document controls, map exceptions, and test drafts with the people who do the work.
Features
3 staffing patterns for Phoenix, Atlanta, and Dallas call centers
Capacity planning formula meets real labor markets: three call center staffing patterns for Phoenix, Atlanta, and Dallas, built on BLS wage data and local supply.
Features
How US supply chain disruptions test process control at ports and freight corridors
Process control at US ports and freight corridors turns Census Bureau trade data into control limits and escalation rules that absorb surges.
Features
Performance management redesigns: five recurring moves, what each trades away, and the test to apply
Five recurring moves in performance management redesign, what each fixes and gives up, and four questions to ask before agreeing to a change.
Features
Team management metrics start with a test, not a spreadsheet of numbers
Team management measured without pretending: the test before collecting anything, four numbers about you, what no team measure reaches, and non-numeric signals.
Features
Change management after go-live: a skeptical guide
A practical, skeptical guide to change management after go-live, covering parallel running, rollback triggers, training, adoption, and ownership.
Features
Management foundations examples, from the permanent exception to the bad delegation
Management foundations worked through seven constructed situations, from the permanent exception to the delegation that came back wrong, with the reasoning shown.
Features
Strategic planning: subtraction, the binding constraint and falsifiers written down early
Strategic planning built on subtraction, the binding constraint, real capacity counts, named assumptions and falsifiers agreed before the work starts.