Technology provides us with some fantastic tools to help us work better, smarter, faster and more efficiently. BUT, it doesn’t help us think any better. We can actually get too dependent on it and our thinking is weakened. If you don’t believe that, just watch what happens when you try to buy something and the computerized cash register goes down. Can they actually take payment? And if you use cash, can the clerk make proper change without looking at the cash register to tell them how much to give you. [Read more…]

Even if you have excellent planning and scheduling, you may still experience excessive downtime. Some consultants will promise that you’ll save a great deal of money with good P&S simply because planned and scheduled work is less expensive to execute. They are partially right too! But that’s only part of the picture. [Read more…]

Surprises happen anywhere and to anyone. In your operation, you can expect that regardless of your best efforts, some work will arise that must be done right away. Most would call these emergencies.

To me, an emergency is something that is or is about to have a MAJOR impact on: Safety (i.e.: injury or death), Environment (i.e.: a major incident that is likely to get you fined or shut down), or Production/service delivery (i.e.: irreparable impact on the bottom line in the financial reporting period). [Read more…]

A lot of people think about this one, but their actions reveal that this myth underlies what they are thinking.

Shutdowns are major undertakings performed when production is at a standstill (zero revenues) and because of the scale of the work being undertaken, costs are at a high point. There is a natural and well-justified desire to minimize the duration and frequency of shutdowns. [Read more…]

This myth, is about who should plan your work and there is plenty of confusion around this one. For the most part, I’d agree that planners should do this, but not all – see below.

First understand that all jobs should be planned and those plans should be saved as “standard jobs” (or whatever you want to call them) in a job plan library. Plans should be written once and then used many times. Each use, subjects the plan to what is happening in the field and therefore each plan is subject to upgrading with each use. Feedback from the trades in the field triggers that continuous improvement loop that keeps plans current and ready for next use. [Read more…]