Monthly Archive: June 2016

Sorry. Be Canadian and apologize at work.

Canada Day.

Tomorrow, July 1st, we celebrate Canada Day.  Sorry to say, it’s not with the same gusto as our neighbours to the South celebrate Independence Day, but we celebrate with a certain “Je ne sais quoi,” that only we Canadians have.  Mostly we celebrate with beer, swimming in the lake, and mildly dangerous home fireworks.

In honour of the birth of our country….wait, let me google that’s what we are actually celebrating to be sure.

Canada Day (French: Fête du Canada) is the national day of Canada, a federal statutory holiday celebrating the anniversary of the July 1, 1867, enactment of the Constitution Act, 1867 (then called the British North America Act, 1867), which united three colonies into a single country called Canada within the British Empire

(source: Wikipedia)

canada dayHmm.  Interesting.  Not sure I knew that explicitly. Thank heavens for the interweb.  Either way, the day off in the middle of summer where I always go to a cottage got me thinking about being Canadian and office culture.

Canadian Workplace Traits

What Canadian traits do we have in the office workplace (if any)? While I know you all want me to describe the intricacies of using “Eh,” I will not. Sorry.  Oh ha, there it is! What I am going to discuss is our use of sorry and how it impacts our business culture.

Compared to our English speaking neighbours, apparently we have a penchant for overusing the apologetic term.  Our friends to the South apparently don’t say it at all, and according to the National Post, our accented colleagues in the UK don’t mean it.

#sorrynotsorry

So presumably the theory is, when we say sorry too much we are meek, over-polite, and perhaps even admitting guilt that isn’t there (I won’t begin to tell you the number of times someone bumps into me and I say sorry!).

So in the work environment, we want to create a culture that is polite, respectful, accountable (meaning we are willing to say out loud that we bungled something up), but saying sorry for everything might undermine our career aspirations. Saying sorry might:

a) be perceived as excessive and unnecessary (particularly for the analytical types who may favour data to feelings),

b) create a perception that we’ve done something wrong, when we actually haven’t, and finally,

c) it might render the use of the word somewhat meaningless.

How to Say Sorry Just Enough!

  1. When you have hurt someone’s feelings. So, in yesterday’s TPS report meeting, you tell Cynthia that the new TPS reports are “THE DUMBEST IDEA EVER”.  Cynthia has been a little aloof lately, and you find out later she designed the new TPS reports.  This is a good time to admit that your statement was offensive.  “Cynthia, yesterday I said the new TPS reports were dumb. I realize that might have been offensive. I’m sorry. Can you help me understand them better so I can have a better appreciation of the work you did?”
  2. When you have made an error and are owning up to it. Once very early on in my career in the Ontario Public Service, I made a $150,000 procurement error.  I forgot to type over the system default date of April 1 with Mar 31.  We lost that money from our budget that year.  After creating a small wading pool of sweat in my cubicle and panicking to the point of fainting, lumberghI went into Lumbergh’s (not his real name…but there is a movie reference here) office and said: “I made an error in the system. This money is coming out of this years budget, not last years. This is how I’m going to fix it so this never happens again. I’m SO sorry.”  Lumbergh turned beet red with rage, and then immediately resumed his natural “public service pale,” and said – “thanks for owning up to it, not making excuses about the system, and for your apology.  Let’s move on”.  Now, I wasn’t normally a fan of Lumbergh, but in that moment I could’ve hugged him.
  3. When you have not acted politely. You interrupted Sally’s story during a meeting. You failed to notice Henry two-stepping it to catch the open door because he had two coffees in his hand and let the door crash into his face and his lattes. “Wow.  I’m sorry. I just interrupted you/slammed expensive coffee into your face. Please go on/let me hold the door.”

The Goldilocks of Sorry – Just Right.

My point here is that sorrys don’t have to become ubiquitous.  Use sorry sincerely and genuinely.  Don’t say “Sorry, but…..it was x,y,z’s fault” – that negates your sorry and says you aren’t sorry at all. Don’t say sorry unless you know what you are sorry for.  Don’t say sorry when someone bumps in to you (say excuse me instead – and honestly as Canadians we don’t want to be doormats!). canada sorryDon’t say sorry when you are late for the 100th meeting in a row. You clearly aren’t sorry because you aren’t fixing your complete lack of respect for others’ time.

Say sorry when you screw up, and you know it. Say it in isolation. I’m sorry {period}.  Let it sink in. Say it with passion, and if you must, add an “eh” on the end to seal the deal.  And as a major belieber, it is never too late to say sorry. 

Happy Canada Day!

Until Next Time,

Nicole

 

 

 

Process Mapping? I’d rather be Napping.

So I’ve heard a lot of people say they are so fascinated by what I do in the process improvement world, and how great they think it is , but how “it’s not for them”.  Using my coaching skills, I usually say something like, “Oh yeah?  Tell me about why it isn’t for you”.

Here are some of the responses I get:images

“Snore.  Processes are super boring. My company is really intuitive, and we just know exactly what to do and we fix it.” – my super annoying friend

“Processes, who needs it? I already know my team is garbage and as soon as I can replace them, things will turn around”. – a client who later realized her team was great because process mapping revealed a culture issue

“Ugh.  Sounds bureaucratic. I’m an entrepreneur.  There is nothing corporate about he way I run my business, and to be honest we don’t need it.” – my sister-in-law

PROCESS MAPPING3 Signs You Need Process Mapping STAT!

  1. Something is wrong and you “think” know exactly how to fix it.  How do you know what’s wrong?  What leads you to believe that?  What is the expected outcome if you make the change? You might be right. Intuition is super important.  Why not validate those gut feelings with some evidence in a process map? It’s a great way to get buy in from your stakeholders and employees!
  2. You “think” your employees are the problem. They suck.  While this is the first place many people look for solutions, it’s usually something else.  Why do you think they suck?  What tells you that? What could be inhibiting them? Have you asked them? Research shows that if you take great people and put them in a bad process, the process will win every time. Process mapping sometimes uncovers secrets that are hiding within a bad process.
  3. You “think” process is too rigorous.  Well, it can be, but it doesn’t have to be.  The right people, the right style, and the right moment can take you from being a fly-by-the-seat-of-your-pants entrepreneur to a being a strategic one.  Why not set the stage so you can pass the tasks that aren’t worth your time (or you aren’t great at) to someone who can actually add value (so you can go and be amazing). Process mapping identifies those tasks and lets you properly divide them up.

If you’re not a “process person,” or even if you are but don’t have a lot of time, we can help you. We are expert at coming in, talking with you and your team, and uncovering the hidden opportunities to improve your business.

Even better – why not build process improvement and process mapping capacity on your team? We offer public workshops that are fun, interactive, and relevant. Check them out by clicking here, and contact us if you want to know more.

#whiteboardworskhops #theyredifferent

Until Next Time,

Nicole

Screen Shot 2016-06-16 at 4.09.44 PM

Whiteboard Workshop: Introduction to Process Mapping

pmProcess Mapping is awesome and fun and helpful and easy and so amazing, right?

No? If you disagree, you’re not alone. We did a quick Twitter poll and asked people what their thoughts are about Process Mapping. Here are some of the replies:

  • Process mapping? More like process napping! (Click to Tweet!)
  • Process mapping is critical, in that if you don’t do it, you can save the rain forest, your time, and your sanity.
  • Who needs sleeping pills when you could participate in a process mapping session?
  • Process mapping is the paleo of the workplace. (Click to Tweet!)
  • AT FIRST GLANCE THEY ARE SO INTIMIDATING AND COMPLICATED (this one was complete with caps)

So yeah. We get it. There are a LOT of people who don’t like process maps.

At least they think they don’t – they just haven’t met us yet.

But I “Need” to Do Process Mapping

Despite how people may feel about process mapping, they still need to use them. Either they have to design them on their own, or read some that have been designed by someone else. Some people know the “why” behind process mapping but still haven’t quite mastered it, and others have no idea what they are doing or why, only that “they have to do this for audit purposes.”

The truth is that process maps are necessary and critical in so many situations:

  • Training new people,
  • Documenting processes for audits,
  • Understanding the flow of information in an organization,
  • Having a picture of how customers are impacted by business processes,
  • Identifying areas to improve,
  • Identifying areas that are excelling (and should be modelled), and
  • Imagining a future state organizational structure.

So if you, or someone you know needs to do any of these things (or is responsible for others who are), then our latest workshop is for you. Read on.

1Whiteboard Workshop: Introduction to Process Mapping

If you have been reading our blogs for a while, then you know we love to make processes better, and we loathe things that are over-complicated. It follows then, that we don’t do process mapping (or training, for that matter), like most organizations do.

Our latest workshop, Introduction to Process Mapping, was first delivered on May 26th, and was a great success. Some testimonials:

  • I have done process mapping in the past, but it has been a long time since I’ve been able to utilize those skills. I was so happy to attend and receive a great refresher. Thank you!
  • There was a wide variety of different folks with different backgrounds, and you did great to keep all levels engaged and interested.
  • This course came at the perfect time! Something I really liked was the actual process mapping we did as individuals – it helped me demonstrate what I learned from the course.
  • I loved your banter – so funny and yet still professional. (This was our favourite, because we think we are very funny.)

We have two more dates set this fall. Both are Thursdays, and both will be in downtown Toronto (location TBD based on the group).

People who attend this course will be able to

  1. Understand the basics of process mapping theory and activities,
  2. Articulate the value of process consistency and when it can be “too much” (too rigorous),
  3. Demonstrate the ability to facilitate and develop a process map, and use appropriate levels, tools, and concepts (incl basics of Visio), and
  4. Analyze process maps to identify improvement opportunities.

You should come. You really should. CLICK HERE TO REGISTER. And if you have any questions, shoot us a note or Tweet us @whiteboardcons #ILOVEPM.

See you soon,

Ruth.

 

 

Should you follow the pack or go rogue?

I’ve been thinking lately about our human tendency to follow the pack and my newfound tendency of “going rogue.” I’m a trusting person and easily influenceable. If you tell me this is the BEST HAND CREAM EVER, I will buy it.  If you tell me you tried a new workout and it was THE HARDEST WORKOUT EVER, I will go and try it tomorrow.  Ask me to smell this milk because it is the MOST EXPIRED MILK EVER, I will get my nose right in there.

So it’s a newfound habit for me to say, “That’s awesome that it is working for you.  Right now I’m doing this, and it is really working for me too. Yay us!”

But Everyone Says So!

People (and probably some science reports too) say that we MUST eat breakfast; doing so helps us consume fewer calories later in the day and maintain a healthy weight and may even improve our concentration and productivity. They also say we shouldn’t weigh ourselves every day because it could case us to become over fixated on what may be natural fluctuations rather than indications of weight gain or loss.

“They” say we shouldn’t look at our phones first thing in the morning – it can distract us from our morning routine and can decrease our productivity by focusing on external priorities rather than our own.

And we mustn’t work out every day, because our bodies won’t have adequate time to recover and we won’t get results.  

Screen Shot 2016-06-02 at 4.57.45 PM

Don’t get me wrong, I realize there are studies and science  that may back these statements up with statistical significance.  But here’s the thing: all of the “pack ideas” I talked about above don’t work for me.

When I eat breakfast, I’m starving all day and (after testing this theory out by tracking and monitoring the data) I consume more calories than are necessary for me to maintain my weight. So do I keep doing it because everyone else is telling me that is the right thing?

Similarly, weighing myself every day keeps me on top of fluctuations that could otherwise be more dramatic after a week.

And I LOVE working out.  Provided I balance my workouts, it is my stress relief and my time that makes me happy. So why should I be unhappy, provided I am being safe and taking care of my body, when my way works for me?

And finally, if I don’t check my phone before bed AND first thing – guaranteed I will miss a meeting, or miss a cancellation of a meeting and make an unnecessary trip.

Now statistically speaking these “rules” might be great for the majority of people, and the majority of people will see better results following these rules.  But, as we know, there is a great deal of human variation.  I am a sparkly unicorn and I am different.  These rules do not work for me.

The thing is, it’s easy to follow the pack.  It’s part of our human nature.

…social conformity is based on mechanisms that comply with reinforcement learning and is reinforced by the neural error-monitoring activity which signals what is probably the most fundamental social mistake – that of being too different from others

Read more: http://news.softpedia.com/news/039-Follow-the-Crowd-039-Tendency-Finally-Explained-102066.shtml#ixzz4ASKrOwCW

Follow The Pack? Or, Go Rogue!

Maybe your competition uses a certain process improvement methodology (like Lean or Six Sigma), or a particular sales tool, or social media strategy and you want to implement it to keep up with the trends. But what if it just doesn’t work for YOU (and your team, and customers, and stakeholders)?
keep-calm-and-go-rogue

  1.  Does it feel natural to do what the pack is doing?  Sure, good habits take time and consistency, but if the process is so difficult that you can’t get the habit to stick, maybe it isn’t the right strategy for you.
  2.  Have you experienced errors, defects, or problems using the pack’s idea? If you notice missed deadlines, faulty products, decreased employee engagement, or increased customer complaints – maybe you need to re-examine your plan.
  3.  Have you tried and tested any other options? If you haven’t tested and tried out alternatives, how do you know that this is the best for you?  How can you make a decision with out data – numbers or experience? Reflect on the past – was there a time that you were doing really well?  What were you doing?  Should you align with the pack, or “go rogue”.

Let us know how you follow the pack or go rogue @whiteboardcons #gorogue or #followthepack!

Until Next Time,

Nicole