Category Construction Project Management

No One Here Gets Out Alive

A highly functional team knows each others strengths and weaknesses. Over the years, I have watched many teams and bright individuals follow processes that were more akin to a Rube Goldberg without questioning each other, the creators of the process or even their management. It’s always the same reason. We are taught to avoid conflict to stay out of trouble. Drawing attention to ourselves is not good business acumen.  While in most situations that can be true, avoiding healthy conflict is a sure way to stifle positive change, creativity and innovation for the good of all. Not knowing what should be addressed (“know which battles are the right ones” as one great mentor I had once told me)  simply to avoid all conflict actually encourages unhealthy conflict. Let’s explore the single most important asset you have when  trying to solve a problem. People are your most important asset.

Therefore, the bottom line to fixing a big problem is to be tough on the problem, not the team or the people.

A good process, a great set of rules or guidelines, can aide in binding new teams together and advance team productivity. Bad ones can too if the team is already highly functional. However, it cannot accelerate productivity on its own.  It’s an “all in” (or, fall short of the goal) commitment. What makes bad processes, rules or, guidelines worse? When they are at their core a disincentive to follow let alone commit to.

How do you make a necessary process worth using with a new or,  highly functional team? Let’s presume that incentive (the “carrot”) is the approach we will take, not disincentive tactics (the “stick” i.e. “do it, or else”).  If a process already exists, you can apply the same “all in” approach with the people who will be using it by diving into and understanding the data collected from different feedback channels.  For example, monitoring metrics on how many times a process flow is followed. When a workflow begins is it; a) 100% complete/correct,b) partially complete/correct, or c) incorrectly applied. Additional metrics such as where in the flow was the process subverted and why?  When was it not used altogether? Talking to a random sample of users whom you have collected metrics on to understand the data also puts it into the context needed to fully grasp the problems within a process.

The best way to capture the essence of what’s going on is to commit to the whole process not just a part of it. Unsurprisingly, there are no shortcuts to gaining proper insight.  What’s surprising  is that once a new process is launched in the name of continuous improvement,  ownership is disbanded. The application of Deming’s principle A Constancy of Purpose used temporarily is like washing your hands only when you think it’s a good idea.

When you are working with a new or highly dysfunctional team,  it can  feel like you’re watching a relay race of runners without a baton. The people on the team forget that the ‘baton’ is the process not them. They act independently of the actual goal of a team moving a baton forward as quickly as possible for the best possible outcome. The total amount of time and  money it takes to complete the entire task or, provide meaningful information as to where the baton is, is not a concern by anyone on the team. Then, there are those who “know the rules” of the game who are often more interested in pedantic catechism than in rendering an actual service. The absence of team spirit and customer advocacy (two things that make the baton real) becomes palpable when people use a process to absolve themselves of accountability to the whole purpose of what is supposed to be accomplished. What they have forgotten is that they unwittingly malign a company’s name and reputation more than their own when they do this.

So, if you find yourself bogged down by  a process or on a team that’s less than desirable, remember that no one here gets out alive. Meaning, make the most of what you have, while you have it. Success that comes with knowing that you have tried your best is carpe minutam more so than carpe diem. You’ll know who your peers are by how well they function when nothing is going as planned. Theses are the ones you can count on. The other ones, the ones that turn on each other need to know that they count on you and others like you to show them how to rise to the challenge. These are the ones that know the right baton for each sprint, by following the process and carrying on.

Review, Approve,Verify

How important is it to get it right the first time?

In nature, species evolve over eons. It’s important to note that with changes gained there is always something lost. Nature often has a way of letting go of what is no longer necessary. That too, also takes a very long time. Everything around us is in the natural world is proof positive of a loosely coupled review, approve and verification process.

“The fossil record implies trial and error, the inability to anticipate the future, features inconsistent with a Great Designer (though not a Designer of a more remote and indirect temperament.)” ― Carl Sagan, Cosmos

Imagine, for a moment, what the dollar cost would be if one were to begin a program with the objective of creating homo sapiens starting with single-celled organisms? Carl Sagan had it right when he suggested a “… Designer of a more remote and indirect temperament.”

I have yet to meet a business partner, CFO, CEO, or a CIO with that kind of patience! In the software development world we strive to get it right the first time. Money is the usually the motivating factor that is used to start quality improvement programs. Expectations are then set to unachievable levels causing a failure to launch sustainable quality practices.

While it’s a certainty that the dollars saved from quality improvement initiatives should and will not be ignored, it is also important that money should not be the main focus. When it comes to problem solving, money is not the most compelling reason for changing the way things are. In fact, money often  stagnates clear thinking, logical thought and creative processes of innovation and change. It often gets you temporary results that do not stand the test of time. To be really good at review, approve and verification you have to be really good at staying focused on innovation and change.

Note to leaders who just read that and thought, “Good to know, let’s start a new quality improvement organization with zero budget and or, resources, leave the rest of the organization well-funded and disinterested and see what we get!” A bad, if not silly (by which I mean, really silly) idea.

In my next few blogs I am going to discuss the known and hidden benefits derived as a result of following lean six sigma review, approve and verify series of workflows that you can build into your current SDLC process.