All posts by Nicole North

The Ultimate Cheat Sheet on Effective Teleconferences

conference call

Working from home has many advantages. The fact that I just had a powernap with the dogs curled up at my feet is one of them.  The other also happened today: one too many glasses of wine at girls night, and I was not so pretty this morning. On went the sweatpants and off I went to conduct business in the comfort of my living room. What convenience! No commute. No fussy office attire. Hair and makeup? No thanks. #sorrynotsorry

Companies are on a mission to cut costs and tele-commuters and flexible work arrangements are on the rise.  Teleconferences are (when executed well), an efficient and cost effective way to get things done.

A colleague of mine sent me this the other day after a particularly painful teleconference.

As comical as that was, the real truth is teleconferences can often be frustrating and ineffective. Whiteboard has a few simple tips to make your teleconferences better, faster, and cheaper. Behold! Whiteboard’s Ultimate Cheat Sheet on Effective Teleconferences (Click to Tweet):

Whiteboard’s Ultimate Cheat Sheet on Effective Teleconferences

1. The right medium.

First before deciding to hold a teleconference, ensure that it will be the right medium.  Teleconferences are great for information sharing and questions.  In-person meetings are better for decision making, complex problem solving, brainstorming, or decision-making.

2. An Agenda.

Create an agenda and use it.  Clearly state the objective of the meeting and expected outputs and timing. People will be better prepared when they understand why they are there.  Also feel free to place some of the tips for participants in the agenda (particularly #3).

3. Mute & Speakerphone.

I’m going to say this only once. Use this cute (and not nearly as crude as my last) helpful mnemonic:

AMPLUS =>

Always

Mute

Please &

Limit

Using

Speakerphone.

No one wants to hear you masticate, your yappy dog greet the mailman, or your heavy breathing.  Nor do you need to sound like Darth Vader. Speakerphone quality is horrible compared to a mouthpiece, and all these extra sounds make it worse. AMPLUS. Catchy, eh?

4. Make it personal.

Have everyone on the line introduce themselves and their role/title. Make sure people’s ideas are heard.  If you know Sally had questions about the budget yesterday, but all you hear is radio silence when you’ve finished presenting, call it out with a conversation starting open-ended question: “Sally, what are your thoughts on the budget?” or “Doug, this indicates some significant cuts to your division’s budget. How will this impact you?”

Note: this also keeps people alert and focused (i.e. not checking email, playing CandyCrush, or making breakfast).  Ruth did this to me on a teleconference the other day and I was MORTIFIED because I had just looked away to read an email and had no idea where they were in the document.  #teleconferencefail

5. The 10-second rule.

Without seeing facial expressions, it’s often hard to gauge how people are reacting to the content you are delivering.  Often, people’s natural reactions are to fill that glorious muted silence with more of their own cherubic voice.  They never take a breath for anyone to jump in. Or worse, they say “Any questions?” (Olympic 0.000037s pause). “Great Thanks. Talk Next week. “.  Allowing a whole 10 seconds (1 Mississippi, 2 Mississippi……) allows for that awkward silence to penetrate and 9 times out of 10 someone (or more than one) will pipe up with a great question or comment that will spur discussion and make your call an effective use of time.

Like these tips? Have some funny teleconference stories to share?  Give us a shout at @whiteboardcons!

Until next time,

Nicole

The “ASS²” Method of Resolving Conflict.


ASS2 Method
Yep, you read that right – ASS “squared”.  I’m tired from a busy two weeks after vacation and I’m feeling cheeky.  I also met a Canadian guy while on vacation that owned a donkey in Albania named Richard (it’s a long story).  It’s my blog and I’ll swear if I want to.  I also hate mnemonic sayings that you forget.  You will never forget the ASS2

As consultants, Ruth and I recommend a lot of different things to a lot of different people. We see some recurring themes.  One of them is:

How do I deal with difficult situations at work?

I’m an avid conflict avoider.  My natural instincts are to apologize profusely, take all necessary actions to avoid said conflict again, and cry privately while staring at myself in the bathroom mirror. Not really a great coping mechanism.

The better option is to calm your emotions and deal with the issue as soon as you can.  Organizations large and small, public and private are all subject to workplace conflict.  Differing personalities, competition, cultures, work styles, thinking styles, communication styles, and lack of clarity in roles and responsibilities are all potential sources for conflict in the workplace.  When you confront your conflict, or have someone confront you – use the ASS2 method.

6 Tips to Resolving Conflict

  1. Actively Listen: Use silence, nod, maintain eye contact, show open body language, and use kindness and curiosity to probe for more info.

“Tell me more?”

“Help me understand!”

  1. Say it back: Repeat what you heard in your own words.

“It sounds like the tone of my email really upset you.”

“Let me try to paraphrase. You are unclear where your role ends and mine begins?”

  1. Sympathize: Show your genuine concern for their emotions.

“I can see how that would make you feel.”

“I understand your frustration with this situation.”

  1. Appreciate: Thank them for confronting you or for taking the time to hear your concerns.

“I appreciate you bringing this up to me.”

“Thanks for being so open to hear my concerns.”

  1. Sum up your Options: Allow some discussion to analyze the situation.

“Let’s talk about how we move forward from here.”

“Let’s consider the options.”

  1. Solve: Create a solution that results in benefits for both parties.

“Can we both try to….?”

“Perhaps to mitigate the risk of this occurring again, we can….”

Conflict Resolution

Confronting conflict is not easy.  Hearing constructive feedback from a team member, peer, or leader is equally difficult. Respect one another’s feelings and emotions. Not treating one another with respect makes you the square root of ASS2 (a bit of an ASS).

Having trouble with a team member, peer, or leader in your organization?  Contact us to learn more about resolving conflicts in the workplace in the best way possible. Tell us what you think of the ASS2 method and what your results were if you tried it out.

In the meantime I’m going to spend some time thinking of more shocking yet amusing mnemonics for you readers in hopes of you having a laugh while learning.

Until Next Time,

Nicole

Processes and the Flu Bug: 10 Surprising things they have in common.

“Pam! Call my mom!”

For two weeks I have been miserable. Sneezy. Cough-ey. Stuffy head.  It is worse than the man cold.  I’ve even gone so far as to post Facebook photos of my medicine arsenal trying to elicit some extra sympathy from my old elementary school friends and random people I met at bars. I even finally went to the walk in clinic – which I never do- and the doctor told me to “get over it sweetheart” and to stop coughing into my hand and into my elbow. No sympathy from that gem.

Whether by the delirium of the flu I’m battling, or the near-fatal cocktail of NyQuil & NeoCitran, I bring to you some amazing parallels between the flu and bad processes in your organization:

1. At first, it just seems like no big deal, or nothing at all.

Was I mouth breathing last night?  Is that why my throat hurts? No, I can’t be sick.  I just can’t be. It’s so dry in here. I must need a humidifier.  I must have sleep apnea.  I’m allergic to the dogs! Every single time I get a cold I refuse to believe that it is actually happening to me.

Similarly, organizations often start by telling us that it isn’t their processes that are broken. Staff don’t have the right skill-set. Staff aren’t paid well enough to do their work.  Clients don’t understand what they’re doing.  The marketplace is changing. This is how we’ve always done it. And nothing has gone wrong…yet.

2. Something suddenly goes very, very bad.

That sore throat is still there.  The natural remedies I tried don’t seem to be working. Stuffy nose and stuffy head have arrived on the scene.  Things are really bad now and I am scared.

Red alert.  A process has gone fully AWOL.  You missed a deliverable.  The product arrived to the client late.   You missed your money back guarantee. You lost the client.  The client fired you.

3. Sometimes you cover up the problem so you can pretend its not there.11664847_BG1

Once alert mode hits, I start medicating hard and fast, almost as if to ensure I don’t have to experience the cold at all.  I run to the drug store and swipe my hand along the cold aisle getting everything I can. Daytime. Night time. Natural. Narc….just kidding.  I want to pretend I don’t have a cold. I want to go to the gym, take out the dogs, and carry on business as usual.

In the business world, this happens too.  Little bandaid fixes are lurking everywhere.  The manager now approves all TPS reports.  TPS reports are now approved by the team lead, manager, director, and Senior Director to prevent any and all errors.  TPS reports are now exclusively completed by Tom (Tom is apparently very good at these TPS reports and everything he touches. He never makes an error).

4.It always rears its ugly head.flu-prevention

3 days after I’ve self medicated my problem away I forget my Tylenol Cold for Daytime at home while running off to one of my very important meetings with a very important client.  By 3pm I am wheezing, coughing, stuffy head, and I can’t think anymore.  I tried to make it go away, but the problem was still there lingering behind all the meds.

Despite all those approvals, and Tom’s full time job of spitting out millions of perfect TPS reports, a problem still occurs. Don’t worry, Tom, it wasn’t your fault.  The process was still broken, and all the bandaids in the world couldn’t fix it. As Ruth always says, you put a good person in a bad process and the process wins every time! Click to Tweet!

Note: In the real world Tom wins every time – it is quite annoying.

5. It can set you back by days or weeks!

Once the ugliness of the cold comes back. I admit defeat. I let it take its course. I hole up in bed, give everyone around me sad eyes, post sad Facebook statuses, and am generally a pathetic excuse of my former self. I carry on like I’m on my deathbed.

Once the process breaks again, usually folks step back and start to think of other bandaid fixes to ameliorate the problem.  Or they stop working on EVERYTHING and start having some high level strategic meetings to find out what is really going on.

6. Sometimes you need a professional, even when you really don’t want one.

Usually after publicizing my illness with those self deprecating Facebook statuses, someone demands that I see a doctor.  And I’m so sad at this point that I usually comply.  Sometimes they help and sometimes they say “suck it up buttercup”.

Sometimes those strategic meetings end up with a those dreaded fancy consultants in your office working on fixing your processes.  And depending on how good they are, sometimes they help and sometimes they don’t.

7. It takes patience to really get to the root cause and get it to go away for good.

Sometimes, you need to go and see your family doctor when things still aren’t getting better.  And this takes more time.  And patience.  But hopefully the right diagnosis.

Your consultants (or maybe your in-house process specialists) have done interviews, current state mapping sessions, root cause analysis, future state mapping sessions, final reports – the whole toolkit comes out.  It’s taken time (and money) – but they’ve figured out how to make it work better, faster, and cheaper! And they made it fun too! Oh…they didn’t? I’m sorry.  Call us next time.

8. Hindsight is 20/20.

I really should have gotten the flu shot.

We really should have hired those consultants sooner

9. Sometimes you think you are better, but you still need a bit more time.

Really? Four weeks for a cough is normal? Fine I will be patient and rest.

Another small tweak to this process and we’re good to go!

10. When you are better you can go back to saving the world!

A lovely friend of mine responded to my Facebook statuses with: “Quit trying to be a hero, get better, and then go back to saving the world.”

And once you’ve fixed your dreaded process, and Tom’s ego has recovered from the process beating him (just this one time), you and your business can go back to saving the world.  Or like Ruth and I, making it better, faster, and cheaper.  Tell us about your cold.  I can sympathize way better than most. Or tell us about your processes, we actually have a cure for those. Tweet us @whiteboardcons #betterfastercheaper.

I’m going to bed now. I’m still sick. Pout.

Until next time….

Nicole

Warning: Explicit….7 Steps to Simple Process Mapping Facilitation

Ruth and I have been focusing on being more explicit. And if you know me, that doesn’t mean expanding my potty mouth.  I’m quite….colourful in my diction. What I mean is, Ruth and I are working on being more clear. Perhaps saying a little more than we’re used to.   Maybe writing a little more than we’re used to.  Making sure we, and our clients, and our colleagues are all on the same page.

When you spend as much time together as Ruth and I do and also think almost exactly the same way, we know exactly what the other is thinking.  We barely need to say a word to one another.  Usually we finish each others sentences, or chime in to a conversation in stereo with the both of us saying the exact same thing. That’s what makes it so hard sometimes to explain to others exactly what we mean. Since we seem to have a brilliant insight into each others minds –  we barely need to say much to know exactly what we need to do. So what does being explicit actually mean? See below!


Screen Shot 2013-12-12 at 7.29.49 PM

All this talk about being explicit in our training classes, our written mediums (reports to clients), and even our emails had a great connection with process improvement.  We’ll often ask questions of our clients like “What is your customer on-boarding process?”.  Here are a few typical responses…

explicit

“Well, we do this….and then maybe this….and sometimes this….and Barry always does this (but I don’t do it that way)….”

or

“Well, it depends, sometimes its like this, but if this happens I might do it this way….or that way….I’m not really sure”.

When your processes aren’t explicit it means you don’t really have a process, and you are going with the flow and changing things ad-hoc – which is great if you are a new organization that is still getting into its groove. But as soon as you start to mature, things may start to fall through the cracks.

Be Explicit…B-E Explicit. B-E-E-X-P-L-I-C-I-T (clap clap).

By documenting a process and clearly defining the roles, responsibilities, and tasks in a step, you and the team you are functioning with are able to very clearly understand what they need to do, in what order, with what inputs, and producing what outputs – consistently – every time. You start to understand what works and what doesn’t, and be able to improve your process.

So how can you get your organization on board to be more explicit with their processes? Other than calling us in for a consult you mean?  What about facilitating your very own process mapping session to understand what everyone is doing?

7 Easy Steps to Simple Process Mapping Facilitation

  1. Schedule it: Find a date and time where you can get all the people that touch the process to be in a room together to spend 2-3 hours on specifically mapping a process.
  2. Get your Materials: Get some brown craft paper, or flip board paper, post it notes, and markers.
  3. Set the Ground Rules: Let everyone know that this is an open session that will involve lots of voices.  Make sure the room is respectful, allows for open conversation, but also sticks to task – you’re probably on a timeline.
  4. Ask questions: Use open ended and probing questions to help you get the starting point, and subsequent steps.  Remember you are documenting what ACTUALLY happens – not what SHOULD happen ideally.  Think questions like: Where does this process start? What happens next?  Is that what ACTUALLY happens? What does happen? Who takes care of this? Who is ultimately accountable? Where does this go? What do they do with that document?
  5. Just Draw it: Check out our process mapping techniques from our past blog  here.  Identify your swim lanes, use your shapes, number your steps…you get the idea.
  6. Make it neat:  It may look like a sloppy mess with lines everywhere.  Go right to your desk and redraw it neatly, or document it in a software package that either you or your team have access to (Visio is easy, but you can also use others).
  7. Validate it: Send out your new neat copy to everyone at the session, maybe people who were absent, a trusted client or external partner.  Get them to see what might have been missed or captured on paper incorrectly. Have then send you their changes/edits/questions.

Depending on the number of changes and whether they make sense, you may be able to finalize a new document – or you might need an in person session to validate your work.  Either way, you will end up with a current state process map! Hooray.

And now you can be explicit.  *#&*$(&# that was a lot of work!

Now what? Well,  you can look to our past blogs like:

Step Three: Imagine It! In which you brainstorm potential solutions to process issues and draw how they might look.

Step Four: Prove It! In which you build the case for the improved process you want to implement.

But at a minimum, you’ve gained some clarity on  a process, and have a good idea of what’s going on and how to fix some things that have been the pebble in your shoe.

Let us know if you’ve had experience (good or bad!) with process mapping sessions and whether any of the tools above resonate with you. Please use the comment space below or tweet us @whiteboardcons! And don’t forget to send us any general process improvement questions or suggestions for future blogs.

Until next time,

Nicole

Process Improvement via The Whiteboard Way© – Step Four

Using Return on Investment and Cost Benefit Analysis in Process Improvement

Step Four: Prove It!

prove itAs we continue along our process improvement journey we focus today on PROVE IT!

But first, a little recap.  So far we’ve taken you through the first three steps of The Whiteboard Way© (if you haven’t checked them out yet, here they are):

  1. Define it!
  2. Draw it!
  3. Imagine it!  

We’ve regaled you with:

  • how to remove assumptions and pre-conceived ideas about the solution,
  • to be unbiased and creative in the possible solution,
  • then how to map a process to visually identify opportunities for improvement, and
  • lastly how to imagine a potential solution.

And now the rubber hits the road – we need to do some math to determine if your solution will work! Our first  task to to collect some data!

Collect the Data

We love to plan here at Whiteboard, and while often we want to jump the gun and just start collecting everything we can find, a great start is a data collection plan.  It helps organize data collection activities and makes sure everyone involved with it understands the goals and objectives to provide the best data possible.

Consider asking the following (to yourself ,your project team, and your stakeholders):

prove it 2

  • What data is needed?
  • Who is responsible for getting it? Why is it needed ?
  • How will it be collected?
  • When will it be collected?
  • Where will it be collected?

Cost Benefit Analysis

One of the biggest complaints we hear from teams and their management when we go to implement cost improvement activities are things like:

“We always try to tell management about these ideas, but they just ignore us!”

“Our teams have all these ideas, but they can never tell me why we should spend that much money on them!”

One of the reasons that great ideas often don’t fly is that they are missing rationale.   Everyone can tout the benefits of process improvement initiatives, but its a skill to be able to  articulate why the costs and efforts to implement  are worth it.  A cost/benefit analysis is a structured process for determining the trade-off between implementation costs and anticipated benefits of potential improvements. The analysis is done to ensure that a particular improvement is the most efficient one in a set of potential alternatives.

What is ROI?

roi

 

Return on Investment (ROI) is the difference between the gain from investment and cost of investment divided by the cost of investment. ROI considers hard costs and savings (actual reductions in costs to the organization). The business case to prove your solution should also talk about soft costs and soft savings (other organizational benefits like employee engagement that don’t have dollar values associated with them).

 

 

ROI= (Gain from investment – Cost of investment)/cost of investment

  So remember to consider the following when completing your cost/benefit analysis:

  1. All the costs associated with implementing the improvement
  2. Capital investment
  3. People costs (consultants, staff time)
  4. Training
  5. Lost production
  6. Determine the benefits of a fully-implemented improvement
  7. Calculate Return on Investment
  8. Keep it simple!

You might have come up with the best idea since sliced bread, but unless you talk about it, share it and explain it to others, it won’t happen! Stay tuned for our next blog on Talk About it! – how to communicate your process improvement idea!

Until then, please leave a comment – anything! Process questions, ideas for an upcoming blog, your thoughts on Toronto’s classy mayor…

Nicole

Process Improvement via The Whiteboard Way© – Step Two

Last week Ruth started a series on The Whiteboard Way©, our very own process improvement methodology (this proved to be advantageous for me, as I was at a creative standstill with blog ideas. Thanks Ruth!)

First, a Little Background

A little recap – last week Ruth talked about the most critical step in The Whiteboard Way© – Define it! By removing assumptions and pre-conceived ideas about the solution, it allows you to be unbiased and creative in the possible solution.Today I’m going to delve into my love-hate relationship with process mapping.

Why do we process map?

Approximately 65 percent of the population are visual learners and people process visual information much faster.  Visually representing a process allows you to see things that may not necessarily jump out at you when you read a procedures document or when you just “imagine” the process in your head. Here are some things that jump out at you when  you process map:

  1. Touch points. How many people, teams, departments must a product or service pass through to reach the customer? The higher the number of touch points in the process the longer the process will take, and the higher likelihood that a defect (or error) will occur.
  2. Duplication. Process maps are great at visually highlighting work that is duplicated across the company by different teams. With our clients, we usually see a map highlight, for example, people that enter the same data into different databases, or forms in different areas of the organization.
  3. Bottlenecks. Bottlenecks occur when there is a blockage in the flow of information or work. For example, when a busy executive is holding an approval at their desk for days upon end.

So Ruth helped you develop your problem here. Some examples of  “Good” Problem Definitions are below:

  •  In the last 3 months we have had to fix this issue 6 times for four customers, causing dissatisfaction for our customers and wasted processing time for our staff.
  •  Each month we are 5-7 days late completing this process, impacting other departments and generating late fees for the company.
  •  This piece of work costs the organization $5,000 per month. Best practices in similar companies is half that amount.

report

Step Two: Draw It!

So now, take your “good” problem definition from last week , and think about the process(es) that contribute to it. There are many types of process maps out there, each serving a different purpose. We like to use the swim lane process map because it allows you to identify the ‘hand offs’ or touch points in the process. At this point you are mapping the As-is current state process, not the Should-be (in an ideal world), or Thought-to-be (what we think it looks like).  Get everyone in the room who touches that process and talk about what “ACTUALLY” happens.

There are four steps you need to remember when mapping a process.

 

  1. Determine level of detail. A high level view of your process will require 3- 5 process steps, while a more detailed view can have up to 20 process steps.
  2. Lay out your swim lanes. Identify how many people, positions, teams or departments are involved in the process (keep in mind the level of detail you have chosen to map it) . Create a swim lane for each. Your process should flow from the top to the bottom, left to right. So if your administrative assistant or your client starts off the process, their lane should be placed at the top. The same, if your shipping department is the last to finish the process, their lane should be placed at the bottom.
    whiteboardconsulting.ca/staging: Peacocks and Processes
  3. Use your Shapes. The are 4 key shapes to use when mapping. The oval represents the start and the end of your process. The rectangle represents your process step. The diamond represents your decision point. The arrows represent direction and connection. The diamond is the fork in the process and therefore will always two arrows, a Yes and No.
  4.  Number your Steps. Although the arrows help with direction, sometimes with complicated processes, you lose track of the flow, especially if there are a lot of decision point. For this reason it is important to number your process steps.

 

So get out your whiteboards, sticky notes, and markers, and start to Draw It! Let us know what you find out!

Leave us a comment below!

 

Until next week,

Nicole

 

 

Making Efficient Business Decisions

frankenstein-monster-the-green-terror Frankenstein Decisions

It used to drive me crazy.  Busting my buns on another PowerPoint Presentation on a new strategy/project/or idea.    I’d done my diligence . I’d told a story using some data (check out our previous blog post here). I went to dazzle them with my presentation skills and present my options and recommendation, and here’s what I started to hear:

“I like recommendation 1, with a bit of recommendation 2.”

“Can you do recommendation 2, but with recommendation 1’s budget and timelines?”

“Did you consider a hybrid option?”

As a real “doer”, this frustrated me as an employee, and I interpreted it as an inability to take a risk, or low risk tolerance on behalf of my executive leaders.  And worst of all, it wasn’t efficient use of my time, or theirs.

It’s ALIVE!

Success (including employee engagement) in organizations today is hinging more and more on the ability of leaders to optimize operations by making quality decisions quickly from a data rich environment.

As a process improvement specialist, I also aimed to ensure that my options were efficient, and these hybrid or Frankenstein options were’t the most efficient solution -much like Frankenstein himself – big, burly, and slow moving.

While the individual solutions may have been better, faster, or cheaper (or hopefully all three) – the hybrids were unattractive, difficult to put together, and didn’t yield the best results – even if they were technically feasible, or “alive”.

3 Tips to eliminating Frankenstein and Promoting Efficient Decision Making

  1. State  your case upfront. The solutions and alternatives your are recommending are standalone.  Use data to support this, but demonstrate right at the outset that it has been evaluated as an option. Or create a hybrid option to present that IS efficient.
  2. Make sure your data is accurate and timely.  Encourage to drive a data driven culture forward buy using data to build your case.
  3. Be collaborative.   Bring as many people into your story during to development, so that people aren’t tempted to make a monster mash of your hard work.

Do you have a Frankenstein experience? Give us a shout via Twitter @whiteboardcons using#betterfastercheaper or email us at info@whiteboardconsulting.ca/staging.

Until next week,

Nicole