“Since the inventory in a product development process is not physical object but information, it is virtually invisible.”
Donald R. Reinertsen, “The Principles of Product Development Flow. Second Generation Lean Product Development”
Imagine bike store. Full of new, shining vehicles. If you looked for a bike, nothing better could have happened to you that day when you came into this store. Of course, all of them are too much expensive, but well… that’s the cost you can agree to accept.
Imagine the same shop in a year time. The same bikes, some of them covered by dust already, some of them with fingers marks – probably someone touched them right before you came in (but actually nothing more happened). They look a bit ugly – in the store just few miles away you saw the newest design, but you decided to visit this place anyway – the seller promised so much a year ago and maybe you still feel a bit of a sentiment. You took a look at the label. Wait, what? You expected discount at least, but it seems the price went higher since the last time you’ve been here.
“You know… labor cost didn’t fall down from the last time and we really need to sell these bikes. Don’t you want one? It’s still a bike, you can use it. You say, you saw a newer version in another shop? That’s a shame, you told us last year you need a bike, so what’s the problem?”
Imagine the warehouse full of bananas… Bananas in the country where people actually don’t like bananas anymore and they fell in love with apples. Bananas, apples, grapes… what’s the difference – all of them are fruits, don’t they? So why do you complain?
Stop your imagination for a moment, cause you know, where it’s all leading to – to the inventory problem.
The idea of inventory origins from manufacturing systems and relates to the raw materials ready for re-use (in goods production) and re-sale or goods ready for sale.
The reasons for keeping the inventory are:
- seasonal demand – in the time of high demand, the raw materials available on the market may be limited, hence we protect ourselves from running out of them, which is related to…
- … hedging against uncertain level of demand or variation to production demand – when we don’t know, how much of ready products will be required by customers and we don’t want to loose opportunity to sell as much as possible;
- economies of scale & (possible) quantity discount – there is always a chance that purchasing in big bulks will earn a discount from vendor and will be cheaper in terms of transport and overheads costs;
- advantage of raw materials price increase – when the price of already bought materials goes up, our margin increases;
- value appreciation – some goods just have to be kept in the inventory as they gain value over time (e.g. wine)
The inventory in all kinds of knowledge work (software development, system maintanance, accountancy, HR, finance etc.) is invisible. This invisible yet actually very real inventory sits either in the folders or within people’s heads.
Each work, which is:
- started and “in progress”
- started and forgotten
- never started, but awaiting for ages in the backlog…
…is your inventory.
Work in progress or design in progress are your inventory.
And there are also certain risks related to maintaining high level of inventory*:
- poor inventory turnover – inventory turnover is one of the main ratios for inventory accounting, which says, how many times in a given reporting cycle company has sold and replaced inventory; if a company is not able to sell the goods produced out of raw materials, it cannot prevent inventory buildup and loose the proper cash flow.
If you produce the requirements only, if your development and testing last forever without hopes to finish – you are not able to turnover your inventory, meaning you are not able to deliver (=sell) your product and cash the profits.
- high cost – inventory cannot be kept for free, there is a bunch of costs associated to that: labor cost to manage inventory, transport cost to move it, warehouse cost, sometimes insurance cost.
The more work in progress you produce, the more additional costs it consumes. Intangible inventory does not require warehouse or trucks to transport materials, but it requires people’s time and attention and neverending management. Additionally, if you use developers licenses, count them too.
- loss or damage – some inventory can go obsolete after certain time; perishable food can become rotten or spoiled.
If requirements are not translated into the product, if developed piece of work is not tested, if you are blocked before moving to production, there is a very high risk that you will not meet the initial customer needs and the value delivered will have to be scrapped.
- time wasted for strategic planning meetings – more inventory require more time spent on inventory management, meetings to agree, what to do with it and how to communicate to suppliers, etc.
Related directly to the costs – the more inventory you have, the longer the meetings are, the more senior managers have to consider them, the more impediments and dependencies you create. Also constant status reports and communication to customers awaiting their products is not only time consuming, but simply… embarassing.
- lower liquidity – cash is not available immediately, as it stucks in inventory.
This seems to be purely manufacturing problem, but in knowledge work case you loose the employees time and this time can be easily translated into money. The longer development team stucked in the project, the less “liquid” it is in terms of picking up the new challanges (unless we continue building up the work inventory levels – and vicious circle closes).
- shifting customer demand – the product customer wants today may not be the product customer requires tomorrow.
Again related to the “loss or damage” point, when customer waited so long for the product that requirements changed few times or became obsolete.
* inspired by:
Just In Time (JIT) Production
Just in Time is one of the basic concepts of lean manufacturing, which aims to zero inventory and high quality, and utilizes the pull system.
Below short summary and comparison of what JIT means in manufacturing and how its elements fit the knowledge work.
|Component of JIT||JIT in Manufacturing||JIT in Intangible Work|
|JIT purchasing||Raw materials are purchased as close to production as possible; they are delivered in small batches.||Requirements come in small batches and are ready to be picked up by development.|
|Close relationship with suppliers||The responsibility for the quality of goods lies with suppliers; if an organization has confidence that materials are of great quality and on time, no rejects are expected.||The groups or individuals that stand before us in the process ensure high quality of work delivered that does not have to be returned or rejected;
the same applies to us, when we deliver our part of work.
|Uniform loading||The product should be delievered to customer, when he needs it – not earlier; it prevents creating overloaded inventory and output is matched to demand (does not age).||Similarly the software product should be delivered to customer when required to minimize the risk of delivery being aged and useless.|
|Machine cells||Machines or workers should be grouped by the product or component instead of stage of work.||Development teams are complementary, so they can go through the process end-to-end and don’t need to wait for passing the work to another stage.|
|Quality||Scrap and defective usnits are waste, the same as reworking.||Defects need to be identified in the test phase to avoid putting live product with not detected mulfunctions.|
|Pull system||Components or product are pulled into the system only when they are needed by the next step of the process.||No work is pushed to the next phase or to another people’s queues, but rather pulled by them, when the capacity is released – in accordance with WiP limits.|
|Employees involvement||Employees working on one machine cell should be trained to be able to operate on the other machines within the team/group.||Cross-functional teams ensure better flow of work and quicker impediments or blockers solving.|
|Continuous improvement||Organization should never stop or fail in improving the processes continuously.||The improvement culture and mindset within the team should not be limited to regular meetings, but should happen all the time at each and every step of the process.|
What about the numbers?
The theory, we’ve just covered, and gut feeling are really nice things, but when it comes to the discussion with your stakeholders nothing is more persuasive than pure numbers.
That’s why I would like to encourage you to join me in the second part of this story, where I will give you practical advice on how to translate your intangible inventory into very tangible data and hard dollars.
To be continued…