Employment is an exchange of work for money. As with most negotiations, both sides would like to keep their cards hidden, so employers and employees use different tricks in an attempt to hide the true facts from the other.
This post looks at the tricks of employees, whereas the next post will look at those of employers. As employees have more control over the work than they do over the salary, this post shows how to keep management in the dark about the true workload.
In my last posts I explained the PDCA (Plan, Do, Check, Act), common mistakes, and its history. However, there is a whole fruit stand of additional versions with some modifications that have popped up: PDSA, SDCA, OODA, ODCA, DMAIC, LAMDA, FACTUAL, Kata, and 8D – and probably more that I do not know of. Let me explain a bit on the different offshoots and alternatives of the PDCA.
In my previous post I explained how the PDCA (Plan, Do, Check, Act) should work. However, while most people know the PDCA in theory, I find that the practical implementation is often lacking. And, quite frankly, I am also sometimes sloppy with the PDCA way more often than I would like to admit. Time for some reflection and observation on what works, and why so often it does not.
Hence, in this post I will show common pitfalls and problems when doing a PDCA. Also, simply because it is one of my pet interests, I will also show a bit of the history of the PDCA and its origins in quality control.
In the last two posts I showed you the basics of the A3 report and the (possible) content of the A3 report. In this last post of this series, I would like to talk about common mistakes and the limitations of the A3 report. Overall, for me the A3 report is a minor tool to help organize the real work of problem solving, despite all the fuzz some make about the A3 report.
In my last post I wrote about four basic factors for an A3 report (one sheet / A3 size / with pencil / on the shop floor). This week I would like to show you what goes in an A3 report. The important framework here is PDCA (Plan, Do, Check, Act). However, in my view there is no single perfect A3 template that will fit all of your problems. Rather, an A3 is created on the go. Make the tool fit the problem, not the other way round!
If you know your way around lean, you surely have hear about the A3 report, famously named after the DIN-A3 paper size. It is also known as the A3 problem-solving sheet. The goal is to get all the necessary data on one sheet of A3 paper using pencil while you are on the shop floor. The A3 report is commonly used for problem solving, but also for project management or status reports.
In many lean books and other writing, it is often recommended to use a pencil for certain tasks as, for example, the A3 report. Yet, I have seen very few uses of pencil in lean manufacturing in the Western world. Most of the documents are computer printouts based on Excel, PowerPoint, or Word. The few handwritten documents are usually done in pen (see also my post on The Advantage of Handwritten Data on the Shop Floor).
In this post I will look into why almost nobody uses pencils and why it would be good to use more pencils. I myself am also guilty of that, but I plan indeed to use more pencil in the future.
To manage your shop floor (or any other part of your enterprise), you need to have reliable data about the situation on the shop floor. Even with reliable data, the remaining uncertainty makes good management a challenge. Many managers, to save precious time, rely on data and information provided to them by their people. This is a grave mistake! Always verify at least part of the data with you own eyes! You would be surprised how different – and usually worse – it is in reality.