The concept of Waste faces natural obstacles

A key pillar of Lean Management is to reduce wastes, i.e. activities which “the customer would not pay for”.  The aim here is not necessarily to eliminate them but to consciously identify them and address them head on.

Before introducing Lean, normal operations would happily chug away at carrying out processes with little thought as to whether each process is waste or otherwise.

However, it is not a simple matter to simply switch to Lean thinking.  Whenever anybody attempts a paradigm shift in thinking, it is natural to feel overwhelmed by the vast effort required in re-thinking almost everything that have been on “cruise control”.  It is thus make sense to carve out bite-sized chunks to deal with.

And the effort required should not be under-estimated.  While normal operations would take many things for granted, a re-evaluation of each process would require the BAU staff to think deep into the underlying rationale behind each action and process step.  Oftentimes, teammates would have different perspectives and interpretations behind why something is done a certain way.  And if the work has been ongoing for sometime, the actual basis may have been known only to staff who have since left the company.

It is also why I feel it is important that most/all processes are based on simple principles so that the rationale/thinking behind process designs can be re-created without too much undue difficulties.

 

Trust and Accountability

Some readings to kick off this topic:

Trust and Accountability: They Go Hand-in-Hand!

  • “Accountability among team members does not occur until trust is built.”
  • Sharing information (personal and professional) builds trust among teammates
  • Fulfilling shorter duration assignments helps us build up trust with our teammates

 

https://leadergrow.com/articles/30-accountability-and-trust

  • If an employee who makes no effort whatsoever, holding him accountable “is logical and necessary”; but holding an employee accountable for an impossible task is ludicrous
  • “The conundrum is that employees who witness their peers not performing up to expectations, yet not being held fully accountable, leads to a lowering of trust in the organization as well.”

 

Trust and Accountability

  • While many managers hold employees accountable for missed targets and deadlines, many miss opportunities to hold employees accountable for successes and jobs well done
  • “Think about being more proactive with your accountability feedback. You can do so in a more principle centered way. When we hold people accountable in a punitive way it works against a culture of trust every time.”

 

https://www.mindtools.com/pages/article/building-trust-team.htm

  • “When people work together, honest mistakes and disappointments happen, and it’s easy to blame someone who causes these. However, when everyone starts pointing fingers, an unpleasant atmosphere can quickly develop. This lowers morale, undermines trust, and is ultimately unproductive.”
  • “Trust is an essential element in team productivity. Without it, you’re unlikely to get anything meaningful done.”

 

Striving for zero-errors doesn’t make sense

When Optimising For Robustness Fails

Optimising for robustness will inevitably lead to an overinvestment in pre-production risk management, and an underinvestment in production risk management. Symptoms of underinvestment include:

  • Stagnant requirements – “non-functional” requirements are deprioritised for weeks or months at a time
  • Snowflake infrastructure – environments are manually created and maintained in an unreproducible state
  • Inadequate telemetry – logs and metrics are scarce, anomaly detection and alerting are manual, and user analytics lack insights
  • Fragile architecture – services are coupled, service instances are stateful, failures are uncontained, and load vulnerabilities exist
  • Insufficient training – operators are not given the necessary coaching, education, or guidance

Cost of precautionary buffers

It is a natural instinct among Ops staff to allocate adequate buffer when scheduling any event.  At every juncture when the question arises whether to allocate more time to perform any task, we tend to opt for more time.

The thing is that such little buffers add up.

And it wouldn’t have mattered if there is no cost to such buffers.  Many often dismiss such concerns with: “Better be safer than sorry.”

Probability

Nobody can deny that it is important to ensure there are buffers to deal with unforeseen events that may disrupt the schedule.  Just as we often carry a little bit more cash in our wallets than we normally need, we should similarly provide corresponding time buffers when scheduling.  While the likelihood of something unexpected happening is small (By definition, if it isn’t small, we would have expected them), we would be prudent to make the necessary allowance.

However, it is a good practice to take one step back at the end of each planning exercise to evaluate the sum of all buffers allocated.

When we look at a larger plan, we would undoubtedly find many pockets of buffers allocated.  While the probability of any such event happening is low, the chance of all of them happening for the same project/event is miniscule, especially if there are many such events.

I think the mathematical term for this is compounded probablity.  If the probability of an unlikely event happening is 1%, the probability that all 5 such events happening in the same project is 0.00000001%, or once every 10,000,000,000 (10 billion) projects.

So, when you have many such buffers, the chance that you will need to utlilise all the buffer times allocated is if every one of these events occur in the same project.  And the chance of that happening is infinitesimal.

Assuming you were to buffer an additional day for each event, that would mean 5 days for each project.  Imagine instead you buffer only 4 days each project instead of 5, i.e. save one day each project.  You would then save 100 million days before encountering a project that will use up all the 4 days you have buffered.

Costs

When we think of the fallout from something bad happening, it is undoubtedly huge especially when compared against the cost of each time buffer.  And that line of thinking results in us plumping (almost instinctively) for making more scheduling allowances whenever this question arises.

The thing is that while small, such costs are not insignificant, especially when we add them up.

Besides the Business cost of potentially losing new business when customers finds the longer time-to-market  not suitable for their needs, we need also to consider the fact that extended timelines mean we have to juggle more items on our respective plates at any one time.

When we stretch out any timeline longer than necessary, we inevitably spend more time and attention on it, at the expense of other projects that we may be involved in.  And with more projects on our minds, we become less able to focus our minds on doing each of them well.

This is akin to keeping excessive inventory.  Just as inventory takes up physical storage space resulting in higher rental and storage costs, project checklists also soak up attention span and time in our mental space resulting in less space allocated to each project.

Final thoughts

Being conservative and prudent is indeed a valuable trait, and as professionals we should zealously ensure that adequate resources (time, manpower, etc) are allocated to get the job done well.  At the same time, we also need to be just as disciplined to recognise the real costs involved so that we can strike an optimum balance based on rational and objective evaluations.

Process inventory and improvements

Yesterday evening, Eugene proposed a framework listing 3 areas to focus on when serving the SMC team for the coming months:

  • Process inventory: Review and expand on the existing process inventory which Hemanth started some time ago
  • Update inventory: In view of the ongoing projects and changes, ensure the Inventory reflects current situation
  • Identify and capitalise on opportunities: With a better view of the process inventory, review and seek out areas to improve on