Waste is a constraint. Reducing waste in your organization is one the easiest ways of reducing constraints.
And here’s a surprise—waste in offices is usually greater than in factories, especially because it’s easy to hide waste in cumbersome or non-existent processes. Creating unnecessary information inventory is another common waste in offices. Doing too many tasks “in anticipation” of a possible client, for example…
One way to think about waste is in terms of push and pull systems. A push system, like much of traditional manufacturing, produces as much product as the company can and/or wants to produce and then gets it out to the customer. The result is usually large inventories.
A pull system only produces what a customer needs and has asked for. You want to have as much “pull” in your systems as you can. Toyota has very little excess inventory. That’s why when the Prius was so unexpectedly popular, people found themselves on waiting lists for the car. Seems like a problem, but Toyota is much more profitable as a result of being so lean. You might also hear this concept referred to as “just-in-time production” or JIT (remember? — it came from the supermarkets).
I think of it this way — there’s a place for everything and everything in its place. No more. No less.
Here’s a story on how to reduce waste (figuratively and literally), by integrating people and process in a pull system.
Many places all over South East Asia (And many other places for that matter), you don’t have a conventional toilet. However, some places in Japan you don't only have a hole in the ground, instead there is an incinerator toilet as many Japanese are shy to have their bodily disposables exposed to even sewer rats. You first press a button to start the heating system and then put a special purpose coated paper bowl liner (like a coffee filter, but don’t try using one for this purpose it won’t work) down between two sloping pieces of steel (sort of like a toilet bowl liner). You do “your business” into the paper filter, step onto a lever, and wave goodbye to your waste and any toilet paper. The toilet incinerates the filter and extra donations from you at a very high temperature, somewhere around 6,000 degrees Celcius or the surface temperature of the sun, whichever is hotter. It’s a great way to eliminate waste. However, you can’t use the toilet without these special purpose coated paper bowl liners—they’re needed to keep the steel clean while also aiding in the incineration process. Many have tried and got a good scolding for it.
A friend of mine and his wife have implemented a very simple “pull system” so that we always have just the right number of liners. Not too many, which ties up money and takes up extra space with excess inventory. Not too little which can shut down the incinerator if it’s overburdened by non-regulation uses.
Over time my friend and his wife have determined just how many boxes of this paper to keep on hand, based on the frequency of use. It happens to be four boxes. These boxes are then stacked on a specific shelf (the one closest to the toilet, not down the hall, which would create a different kind of production problem, but right where you need them—and can reach them).
On the bottom box is written—when you open this box tell Daniel or Yuko. You do tell them because it’s built into the culture of the dojo and you are part of the smooth functioning of the system. They then order 4 more boxes—and have determined, through learning by doing, just how long it takes to receive a shipment of 4 new boxes. It’s a very simple pull system that, in this case, only produces the right kind of waste.
As you can tell, there are a number of keys to success in this process.
Everything about this process is clearly visible and apparent to everybody involved in the process. If the box marked when you open this box tell Daniel or Yuko was inside a dark, hard to reach, cabinet, or it was written on the bottom of the box instead of on the flap that you have to open to get at the liners, it might not get noticed. The process relies on this visual indicator. Visual indicators or management charts, or checklists, etc. allow for communication and sharing. You can create standardized work sheets, but if you don’t have a way of seeing them, and the process, as if it were in a glass box, it’s likely that the standard practice won’t be followed and breakdown and waste will occur.
Problems have a way of bubbling up to the surface. The longer you let them simmer the bigger the problem will be when it surfaces. Our goal is to create standardized work processes that bring issues and problems to the surface, using visual indicators so no problems are hidden, at the earliest possible moment. People are stimulated by the visual, tactile and audible. People are part of the process.
Remember, we’re integrating. So it stands to reason that being able to see everything you manage is a balanced and harmonious way of creating flow in your work.
Idealism is what precedes experience; cynicism is what follows...
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2008
(123)
-
▼
July
(31)
- Adobe Flash Player : MultiThreading
- Adobe Flash Player : Codenames
- Google Gears : WorkerPool
- Google Gears
- Adobe Flex : Change between Debug and Production B...
- Adobe Flex : Code Quality of Flex 4
- Archived Adobe Flash Player Installers
- Debugging WebORB from Visual Studio
- AXIS IP Cameras SWF Streams are not loadable with ...
- WebORB : Installing on Vista
- Adobe MAX 2008 in Milan is now open for registration
- Adobe Flex : MXML 2009 Specification
- Adobe Flex : Documentation for Gumbo (Flex 4)
- Adobe Flex : 3 methods for Deeplinking
- Workaholics United : Push, Pull & Standardization
- Workaholics United : Consider All Factors (CAF)
- Estimation : Off-The-Cuff Estimates
- Flash Player is the most ubiquitous Platform avail...
- Writing Final Classes and Methods
- Workaholics United : Playing the Percentages
- 21 laws of Programming
- Workaholics United : Upgrade an Unproductive Day b...
- Flex : URI Class implementation
- Flex : Pageable ArrayCollection with support for a...
- PV3D : Training in Cologne
- Flex SDK : Skinning in Flex 4 (Codename: Gumbo)
- ILog Elixir 2.0 Beta Program Started
- Google Trends of XAML and MXML
- A Flex SEO contest (by Ryan Stewart)
- Adobe Flex : The Undocumented StaticEventDispatcher
- SWF now supports SEO !
-
▼
July
(31)
My Network
-
-
Stop dragging me into board meetings - Dear Reader : This might be a bit more NEGATIVE than you’re used to. Apologies about that. I love to chair startups and companies, but I hate 95% board m...9 years ago
-
Design practice makes perfect - Evidence gained from research is powerful. It can persuade the most stubborn board members if presented in a way where decisions can be made based on facts...10 years ago
-
-
dutch vs danish politics - First reaction: glad I don’t live there. And then I made this comparison. It doesn’t differ that much actually. CDA 14% – Konservative 10% VVD 21% – Venstr...14 years ago
-
The Next Web – Timothy Ferriss - First speaker on the last day of The Next Web was Timothy Ferriss, author of the ”4-Hour workweek”. I don’t know what I was really expecting from a guy who ...14 years ago
-
Links for Motorcycle enthusiasts - MC travel-blogs: Must see: http://www.kccd.no/ http://4qconditioning.blogspot.com/ Danish blogs: http://www.ossianbuilds.blogspot.com http://wrenchmonkees....14 years ago
-
New Arduino project - I found myself a new Arduino project – an automated car! Well how to go about this. My best approach was to get a cheap RC toy car from the local toy store...15 years ago
-
Unrecognized selector sent to instance - As you may or may not know, I do iPhone/Cocoa touch now... While playing around with something this evening I stumbled across something I thought I'd share...15 years ago
-
-
-
-
-
-
-
About Me
- Peter Andreas Molgaard
- Copenhagen, Denmark
Labels
- Adobe Flex (62)
- Events (28)
- Best Practices (27)
- ActionScript 3.0 (16)
- Adobe AIR (15)
- Tools (15)
- Workaholics United (14)
- PV3D (10)
- Arbitrary Thoughts (9)
- PureMVC (7)
- Adobe Flex SDK (6)
- Adobe Max (6)
- Methodology (6)
- RIA (6)
- State Machines (6)
- .NET (5)
- Adobe Flex Builder (5)
- DFUG (5)
- Google (5)
- WebORB (5)
- Data Visualization (4)
- Flash Platform (4)
- Independent Thinking (4)
- Process (4)
- SEO (4)
- Silverlight (4)
- Adobe Flash Player (3)
- Code Design (3)
- Flash Player (3)
- HCI (3)
- MAC vs. PC (3)
- Microsoft (3)
- Performance Optimization (3)
- Stockholm (3)
- Undocumentation (3)
- Visual Studio (3)
- Windows Workflow Foundation (3)
- ACE (2)
- AUG (2)
- Adobe Thermo (2)
- Ajax (2)
- Bug Report (2)
- Cairngorm (2)
- Commerciel (2)
- Documentation (2)
- Estimation (2)
- Firefox (2)
- Google Gears (2)
- London (2)
- Morphable Interfaces (2)
- SVN (2)
- SoftwareEngineering (2)
- Test (2)
- Admin (1)
- Adobe Flex Adobe Flex Builder (1)
- Facebook (1)
- Graphics (1)
- Hardware (1)
- HelloGroup (1)
- IEEE (1)
- Outsourcing (1)
- Training (1)
- XAML (1)
No comments:
Post a Comment