Monthly Archive: September 2014

Getting to the Root of It

September 25, 2014Blog, , , , , , , , , , , ,

root causeNicole and I have stumbled into a bit of a theme these days, talking about the basic activities involved in Process Improvement and sharing with you some user-friendly and simple templates. First, we wrote about how to actually map a process, and next we covered how to look at that process map and assess which steps are a waste of effort – i.e., they add no value. Both those blog posts include handy templates which you can edit and manipulate to suit your needs.

So now what?

In Nicole’s example, we learned that External Failures were taking 56% of the total time involved in completing a process. Since External Failures are clearly non-value-add steps, that is where we will focus. It may seem obvious, but often it’s over-looked so I’ll say it again: start your process improvement work on the steps that offer the most efficiency opportunities.

The next step then, is to look closely at the External Failures and think about what might be some root causes for them. By reducing or eliminating them, not only will we reduce the chance of upsetting a customer, but we will reduce the amount of time it takes to complete the overall time to do the process.

Root What Now?

Root cause. The main thing that is causing a process to fail. Here’s an example: a customer’s dessert arrives and it is burnt. What might the root cause be for that? There may be a few of them, so let’s brainstorm. The customer received the burnt cake because:

  • the server wasn’t paying attention
  • the oven was too hot
  • the recipe was wrong
  • the chef wasn’t watching the oven
  • the oven timer was broken

There are a few examples of why the cake might be burnt. Are they root causes? Nope. They are sub-causes. Let’s dig deeper:

  • the server wasn’t paying attention because:
    • he/she was rushing
  • the oven was too hot because:
    • the thermostat was broken
  • the recipe was wrong because:
    • the chef made it from memory
  • the chef wasn’t watching the oven because:
    • he/she was receiving an order of fresh vegetables during dinner service
  • the oven timer was broken because:
    • it hasn’t had any maintenance in 5 years

So are those root causes? Maybe. Let’s take a look:

  • the server wasn’t paying attention because:
    • he/she was rushing because:
      • three servers called in sick and there was no backup plan
  • the oven was too hot because:
    • the thermostat was broken
  • the recipe was wrong because:
    • the chef made it from memory because:
      • he/she learned it from someone else who didn’t write it down
  • the chef wasn’t watching the oven because:
    • he/she was receiving an order of fresh vegetables during dinner service because
      • the delivery truck was late
  • the oven timer was broken because:
    • it hasn’t had any maintenance in 5 years

Brainstorming with Fish

We’re getting closer. We have a few root causes in there now, and a couple of others might even be able to go further. A great way to do brainstorming like this is to think in terms of categories of what could possibly go wrong. You can use whatever categories will work for you or your business, but some common ones include:

  1. Equipment
  2. Process
  3. People
  4. Materials
  5. Environment
  6. Management

fishbone
A tool we love to use originated in Japan in the ’60s. Known by several names (Ishikawa diagram, Cause-and-Effect diagram, and Herringbone diagram, to name a few), we use the most common title – the Fishbone Diagram. This diagram is nothing more than a brainstorming tool that helps groups think about potential root causes of a problem or issue. Lucky for you, click on this Fishbone Template for you to use in your next brainstorming session. It will download automatically.

Here are the steps in using it:

  1. At the “head” of the fish, write the problem you want to address.
  2. At the end of each of the “bones” of the fish, write the categories you’d like to use. (Whichever ones will stimulate the best discussion.)
  3. You can start brainstorming sessions several ways. One we like to use is to give everyone a stack of sticky notes and a pen. Ask them to look at the categories and write down as many potential causes as they can – one per sticky note. Now have everyone put their sticky notes on the wall, clustered in the six categories. Discuss and add more (because people always think of more). Remove duplicates.
  4. Draw a line towards each “bone” and write the potential cause on it.
  5. Ask if there are any further “bones” that might go off of the one you just wrote. If there are, then draw a line connected to that line.
  6. Keep going until you’ve written down all the ideas, and then ask if there are any more.
  7. Done!

Now you have a big list of ideas, and the trick is to figure out which one of those is the most impactful. How do you know which one(s) to fix first? Well, Nicole will tell you that next week… so stay tuned!

Until next week,

Ruth

PS – details on our new course, Leading Process Change, are coming within the next few days. Stay tuned to our Twitter (@whiteboardcons) and Facebook feeds, not to mention our website.

How To Solve The Biggest Problems With Process Mapping

September 19, 2014Blog, , , , , , , , , , , , ,

Post-Process Mapping

A few weeks back Ruth blogged about how to do a basic process map (click here to check it out) and it included a free process template for you to use as well. You’re welcome.  Process mapping is a huge part of our business. We know process mapping creates engagement and buy-in for process change  (when done in a workshop setting) , is a great visual tool, and can improve effectiveness and efficiency.

whiteboardconsulting.ca/staging: Peacocks and ProcessesRuth talked about the key steps in documenting a process; the steps include:

  1. Determine the swimlanes
  2. Determine the trigger point
  3. Consider the end point
  4. Put a circle shape in the swimlane for the person/group that starts things off. Write the word “START” in it.
  5. Put a square shape next to the circle and label it #1, and write the step.
  6. Proceed with each consecutive step.
  7. Add the arrows last (you almost always have to change them as you go).
  8. When you reach the end point, put a circle with the word “END” in it.

AND, I can’t believe Ruth forgot this.  I am going to gloat since she is a stickler for this one.

9. NUMBER your steps (post-production comment from Ruth – I am mortified! I can NOT BELIEVE I forgot that… and is such a public way! I will never live it down. Sigh.)

We received a lot of really good feedback on this blog, and people loved the template.  The big question was:

What do I do next, after the Process Map?what-next

Great question.  The next 2 steps are to validate your process map and look at value added steps.

Validation

So if you’ve done your process map in a workshop style setting, you likely had many of the stakeholders (the swimlanes) of the process in the room.  So validation in this case is finalizing that process map and sending it back out to those participants to see if what you’ve documented is accurate.

If you’ve worked on a process map by yourself,  validation becomes even more important. You are verifying that all the steps are accurate and represented properly. In fact, this is an opportune time to re-group and re-engage to validate the map, or engage for the first time.  A few things to keep in mind:

  • Talk to the people in the process and follow the product or service through the service to make sure steps and swimlanes have been captured accurately.
  • Make sure to capture easily seen or invisible steps (i.e. where the product or service is waiting, or being moved to another area)
  • Ensure that you haven’t mapped the best case scenario, or worst case scenario.  The map should be representative of how the process normally works.

Now for the meaty stuff….

Next we are going to analyze the process! First let’s determine whether a step adds value or not? Ask these 3 questions:

  1. Does the customer consider this step important?
  2. Has the product or service had a physical change?
  3. Was it done right the first time?

Here you can identify the type of non-value added activities. Non-value added activities include:value-added-non-value-added

  • Moves: Steps in the process where the product or service is in transit from one place to another. How many times and to how many people in your organization does this touch?
  • Delays: Steps in the process where the product of service is waiting for the next step in the process (a great example of this is approvals or sign-offs). This is your classic bottleneck.  
  • Set-up: Steps in the process that prepare the product or services for a future step
  • Internal Failures: Steps that have to be re-done (i.e. iterations of something before it reaches final approval) that are detected internally
  • External Failures: Steps that have to be re-done that are detected by the customer (i.e. damaged product at shipping….)
  • Control/inspection: Steps where the product or services is reviewed to ensure customer satisfaction (i.e. Quality Control)
  • Value Enabling: Steps that don’t add value but are necessary for the functioning of the organization

How do you do this? Well by filling out the super easy Process Summary Analysis Template of course!

Process Summary Analysis Template Instructions

Step 1: Put in the number of process Steps

Step 2: Enter the amount of time it takes to complete this step in minutes (don’t know exactly? Time it a few times or guesstimate for now), sum that row in minutes, and its % is 100% because we are summing the whole process.

Step 3: Identify which process steps are value added and not value added. Sum the number of minutes for all the boxes that you’ve identified (in this case we have an x in step 1 and step 6 at 1 minute and 5 minutes respectively, so we have 6 minutes of value added work and 75 minutes of non-value added work).

Step 4: For those steps that are not-value added, identify what the type of non-value added activity it is.

Step 5: Assess the percentages, and start working on the biggest first.  In this case 56% of the non-value added steps are due to External Failures.

Screen Shot 2014-09-19 at 9.48.28 AM

That should keep you all busy for a little while!

Ruthie…I guess this means you have to give our readers some Cause-Effect Diagram templates next week. You’re welcome. 🙂

Also stay tuned for more info about our new “Leading Process Change” Course!  Over the next few weeks you’ll see guest blogs from our speakers, more info on the course, and more templates I think!

What do you think of this template? Did you use it? Was it helpful?  Let us know at info@whiteboardconsulting.ca/staging or Tweet us at @whiteboardcons! More questions for us?  Use #DearRuthandNicole!

Until Next Time,

Nicole

 

Two Things I Learned This Week From Students

September 12, 2014Blog, , , , , , , , ,

teacherThis week I taught a two-day course on behalf of the Centre for Leadership and Learning in the Ontario Public Service (OPS). It’s called “Management Essentials,” and is for non-managers who want to either learn more about how management is expected to perform within the values and objectives of the OPS, or to understand what it takes to become a manager – thus being able to assess their own skills gaps and build them up accordingly.

This is a great course, and I enjoy teaching it so much not only because the materials are current and relevant, but because the people who attend generally WANT to be there (vs. being “told” to take a course in presentation skills, or “how to write a briefing note”). Teachers reading this will agree that when people attend because they want to, they are generally much more engaged and the class has more energy.

This was true this week – a great class filled with 35 interesting people from many different areas of the OPS, with differing levels of experience and terrific stories to bring life to the material.

As I drove home I reflected on a couple of standout things that I learned from the class, and thought I’d share them with you in this week’s blog:

One: We need to remind people, over and over again, that THEY are responsible for their careers and their professional development.

Situational Leadership Model

One of the conversations we had (a couple of times) relates to the last blog post I wrote (Does Your Manager Like People). We had just finished discussion on the Situational Leadership model of applying directive vs. supportive leadership techniques. This tool is a BIG hit with people – while complex at first, it is extremely helpful for new managers when they need to accept and learn that their natural, or comfortable, style of learning may not be appropriate in all situations. It helps them assess, adapt, and communicate in a more effective way.

A student approached me at the break and said, “this is AMAZING. I think my manager missed this subject when she was promoted and attended manager training.”

“Ah, bless your heart,” I thought.

I made sure to share with the class that in most organizations, there is no training to become a manager. (As an aside, I may enjoy a little too much dropping those bombs and watching the reactions.) The conversation that followed was an important one, as people realized that it is up to them to learn how to be a good leader.

A great manager should be encouraging their teams to learn and grow, develop career goals and job shadow, take courses, or broaden their perspectives. In the absence of a great manager, many people flounder and future talent may be lost.

Two: There are employees out there who want to innovate, change, and improve, and we need to find and harness that energy more effectively.

After the “manager training is up to you” conversation, there was a slight shift in energy, with more questions aimed at the application of the course material in a practical way to help people apply for and win new jobs.

One question came from a young man who likes his job very much, has been with the OPS for about five or six years with no complaints, and who is starting to feel frustrated. “I’m naturally inquisitive and process-oriented. I see people do the same things over and over with the same results, but no one takes the time to stop and fix the process so that things improve. Where are all the process jobs???”

Not an easy question to answer. Of course there are process jobs out there, and within the Ontario Government there are specific areas that are more process-focused than others. The trick is in finding those job descriptions and being able to read between the lines and know that certain phrases indicate a culture of process improvement more than others.

The real key is meeting the right people. This student was taking control and doing the right things – taking courses, asking questions, discussing his goals and dream job criteria with people, and being open to new opportunities. By doing so, he was exposing himself to more people who might be able to point him in the right direction.

I’d love to see the process-focused culture shift happen more quickly – not only in the OPS but in other private-sector organizations as well. Imagine if more job descriptions included a requirement for some type of Innovation Thinking, or the ability to demonstrate a process-improvement focus as part of regular job functions.

I may be biased, but I think that a process focus culture is the next big thing required in business today. If we could find these naturally process-oriented people and maximize their energy, we could shift our thinking from “process improvement or day job” to “day job through process improvement.” (Click to Tweet)

I teach again in a couple of weeks… can’t wait to see what my students teach me then!!

Until next time,

Ruth.

3 Leadership skills I learned from Joan Rivers

September 5, 2014Blog, , , , , ,

Love her or hate her, Joan Rivers represents more than cringe-worthy celebrity fashion bashing and plastic surgery.  She was part of my childhood growing up. I would nervously glance over at my Macedonian Nana, watching Joan’s latest antics, her mouth and eyes wide with shock, waiting for her to become wildly upset. Suddenly she would burst into infectious laughter and I’d be relieved we wouldn’t have the change the channel.

In recent years, Joan fed my insatiable hunger for celebrity gossip, either providing it herself, or providing me great scathing material to copy so I could provide hilarious fashion commentary for my friends when out for drinks.

joan 2

Despite an image that often resonated more with plastic surgery or her latest offensive comment, she somehow managed to forge a role in women’s leadership. Let’s look beyond her shameless obsession with looks and see that she did in fact serve as a role model and inspiration for women, overcoming blatant sexism to rise up as one of America’s first female standup comics.

3 Leadership Skills I learned from Joan Rivers…

1. Say it like it is.

Joan sure did not have the “nice filter” that we in business have seemed to grasp on to.    A good leader has the ability to not only provide the right recognition and rewards when necessary, but can also provide great critical feedback.  DISCLAIMER: I am NOT suggesting that we use sarcasm, teasing, and ridicule to provide feedback to our teams.  In fact, it was that razor sharp tongue that created a 3 decade long dispute with the Tonight Show – we don’t want that at work. No thank you. What we can do is channel a bit of that blunt, “say it like it is” attitude to just SAY what we need to say. Even if it is hard, or we don’t want to hurt someone’s feelings.

2. Be humble.

Joan’s humour was often self deprecating.  The greatest leader’s and bosses have the ability to recognize their strengths and weaknesses, and rather than fear their weaknesses and hide them, be okay with who their are.  Let’s be honest here. I’ve been using self deprecating humour since birth. But as a leader, sometimes I had this fear that if I showed my team that I wasn’t perfect they wouldn’t respect me. Not necessarily true. Demonstrate a humble attitude that tells the team: “I can’t do it all I need your help.” It is this kind of attitude that brings a group of individuals to works together with you as their boss to become and interdependent team -one that achieves more than every individual could do on their own.

3. Be Funny.

Work is serious. Your job is serious.  Issues at work are serious.  But, it’s okay to laugh.  It’s okay to make things light and fun, and to be serious when appropriate.  Again, I cannot profess that Joan taught me how to be funny (I was already incredibly hilareous). But her passing reminds us to share some laughs with our teams in her memory.

To conclude. I am hilarious, but also very humble, and when I channel my inner Joan, I can also tell people what I need to tell them without fear of hurting their feelings.

I’ve learned from my dealings with Johnny Carson that no matter what kind of friendship you think you have with people you’re working with, when the chips are down, it’s all about business. – Joan Rivers

Tell us about your inner Joan @whiteboardcons, #JoanRivers.

Until Next Time,

Nicole