For a little over two years, Engine-For-Change.com has been my labor of love.  I write this blog because I enjoy it and I know through reading it you urge yourself forward in your own changes, one post at a time.  Yet, lately I’ve been thinking there is more I could be doing to help you make your organization work the way you want. I want to branch out.

But which direction should I go?

As I looked at the sites and blog of others writing about change I noticed an almost uniform multitude of consultants, who happen to have a blog, peddling their services (e.g., coaching, speeches, strategic planning).  I couldn’t see myself putting in the effort to expand Engine-For-Change only to become one of the millions trying to sell a set of products to you.

So, instead, I created a new page here at Engine-For-Change.com, Troubleshooter-For-Hire.  The page contains my rough outline of what service I think I can offer to the market if I were to move Engine-For-Change past a hobby to a small business.   You’ll have to let me know if the concept makes any sense outside of my own mind.

I see myself not as the consultant ready with a catalog of parts (speech, coaching session, assessment).  Instead, I imagine myself getting involved upstream of the fix at the troubleshooting stage.

How’s that work?

It’s a very clear step in the engineering world  When I interned at Cummins Engine Company in 1997, my job wasn’t to design the engine blocks.  My job was to take the engine block that was cracking at low miles and figure out why it was failing.  I hooked up my instruments, applied my knowledge, and found the flaw in the design (or manufacturing process) that was creating the cracks.  I was neither designer, nor customer.  I was the troubleshooter.

Today, I play the same role.  I’m not the leader who selects what the organization should achieve.  I’m not the workman ordered to carry out the process.  I’m the in-between, helping both parties–who are often too close to the problem–see the big picture, notice the important details, and solve their own problem.  I’m good at it, and I love doing it.

So, if you think you need a good troubleshooter to help you find the flaw, the short circuit, or the leaking system in your organization, then send me an e-mail at engineforchange@gmail.com.

Maybe I’m wrong and there is no market for this specialized kind of help.  But, if you’ve been needing this service all along, but didn’ t know where to find it:  Here I am.

I tell it to you all the time, now I’m repeating it to myself: Why not try?

p.s. All of you reading Linchpin will recognize that Seth Godin would be proud of me because I’ve pushed past the resistance and I’ve shipped. It is as tough as it seems, but it is also freeing.  This is going to be fun. This is my way of being indispensable.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

If you don’t like something, change it. If you can’t change it, change your attitude. Don’t complain.” – Maya Angelou

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

I just love it when I’m on the same wavelength with Dr. Kotter, author of Leading Change and the famous 8 Step Process.  Once again, he and I posted about the same topic only days apart. [See his post and mine from Nov 2010.]

Yesterday, I posted about the need to refill the tank, in part by stopping some activities that are draining all your time.

Today, Dr. Kotter posted about Why Busy Work Doesn’t Work and included a video.  Anyone who’s sick of staying busy instead of accomplishing something truly important should check out his post.

Let’s not be busy (and drain all our time pretending to change).

Let’s be urgent and drive some amazing change.

Why not try?

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

One option is to struggle to be heard whenever you’re in the room…Another is to be the sort of person who is missed when you’re not. The first involves making noise. The second involves making a difference.” – Seth Godin

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

With a quick Google search you can find page long lists of blog posts dedicated to complaining about meetings.

I challenge you to find another blog post like this.

Why is this post unique?  Because I intend not to complain about meetings, but about the word meeting itself.

As of today, I’ve given up the word meeting.  I’m writing to ask all my friends to help me strike the word meeting from my vocabulary.

Why such a bold (and odd) move?  Because meeting is a word used beyond its usefulness.

How can I tell? Because one word, meeting, should not be commonly used to describe both of the scenarios below.

Scenario 1: A gathering of a group of excited “get to” team members eagerly working on a project they are passionate about.

Scenario 2: A forced encounter of disheartened workers confused as to the purpose of the current physical co-location, learning and doing nothing of importance.

After reading those scenarios, can you see the disservice we are doing to the powerful difference driving change brings?  Our gathering with other “get to” energized people gets the same word as a sad session of driving people.  No more!

Join me in boycotting the word meeting.

Here’s one way you can carry out this boycott.

When you send your electronic invitation, or make you in person request, describe your gathering in other words.

Examples:

  • We need to generate our next goals.  Would you like to come to the Improvement Improvisation Hour we’re holding at 2 on Tuesday?
  • I’m seeking volunteers to help me safe-fail test my idea to find the flaws. Would you be willing to attend my Devils Advocate Session at 8 on Wednesday?
  • We’ve accomplished a lot in the past two weeks.  Shall we hold a Wins Report from 10 to 11 on Friday in the small conference room?
  • It’s time for performance reviews.  My boss and I are taking Reflection and Projection Time on Thursday at 1.

I’m sure I could come up with plenty more.  The options are endless if we cease the mindlessness of calling everything a meeting and start describing why we are gathering people with the title we give the gathering.  These new titles are more enjoyable to read and they clearly tell me what sort of preparation or mindset I should be in when I finally get to join the other attendees.

Imagine the time saved if you knew exactly why you were there (on top of the wanting to be there energy that driving change brings!).  Can you tell this idea excites me?!

I’m so excited, I started to wonder what the non-meeting titles of current driving people sessions could be.  Here are a few examples, included just for fun:

  • I have to go to the Listen-to-Bill-Yell-At-Us event again on Wednesday.
  • I wish I didn’t have to attend John’s I-Insist-on-Reading-the-Status-Report-to-You-Instead-of-Just-E-Mailing-It gathering every Thursday.
  • Will your boss skip the No-One-Knows-Why-Any-of-Us-Are-Here session again on Friday?  I wish I could skip it.

Join me in boycotting the word meeting.

Don’t wait.

Be brave.

Start renaming your meetings today.

Why not try?

[Bonus: If you want to check out one of my earlier rants about language at work, read Why One Blue Crayon Isn't Enough.]

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

The rules of improv are simple:

1. Always agree with and add to the last person’s statement.  “Yes, and…”

2. Always make the other people look good.

If you’ve watched a comedy improv troupe in action, you know improv results are always unexpected and hilarious.

If you apply those same improv rules to your team discussion, you can create memorable, amazing discussions.

Peter Sims, in Little Bets, sings the praises of improv in unleashing creativity.

I’ve seen the improv power at work amongst my own group of friends, a troupe of our own that gets together one weekend day twice a year to discuss improvement methods and implementations.  We talk for 12+ hours and the conversation never idles.  We talk at a mad rush all day, building on the first kernel of conversation using the “Yes, and…” improv language to build, and build, and build. By the end of each day we’ve learned more than any of us thought possible and had a wonderful time doing it.

This week I tried a safe-fail experiment using the improv rules to unleash creativity during a two-person meeting.  Our goal was to create a new training product and we had few boundaries to limit ourselves.  Using the “Yes, and…” language we created more than a few major “ah-ha” ideas.  I’m excited to try the concept out again with another team next week.

So far, I’m hooked on this improv idea.  Try it out and tell me what you think.

If you’re interested in how the improvisation method works to shut off the judging center of the brain, the prefrontal cortex, check out the research of Dr. Charles Limb at this Ted Talk.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Change is good. You go first.” – Anonymous

In her blog post, “What? You want me to go first?” Connie Moore writes about her thoughts after seeing the sign above in a store.  Readers of this blog will likely relate to her ah-ha moment realizing how little about change discussions includes emphasis on going first.

Let’s all drive some change this week and show the world how powerful going first with a change can be.

[H/T to Rogue Polymath for sending me the link to Connie's post.]

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

The Center for Applied Research (CFAR) had prepared a fabulous three page briefing sheet “Small Wins–The Steady Application of a Small Advantage” differentiating two types of small wins in change management.

The first type, what they call the little victory, is what we typically think of when we discuss Step 6 (Create Short-Term Wins) of Kotter’s 8-step change method.  These wins produce a feeling of success, but rarely translate into sustained modification of the behavior of the people involved.  They are moments, not shifts; useful but not transformational.  They are a key to keeping motivation up, and in that sense necessary, but not sufficient.

The second type, what they call the small-but-steadily-applied-advantage, produces a modification in the way the people involved interact with each other.  These wins are both necessary and sufficient.

In the sense of Kotter’s 8-steps these wins aren’t part of a step at all, but are instead a mechanism through which you make the 8-steps work. Driving change isone small-but-steadily-applied-advantage that readers of this blog know well.

Show me an implementation team with at least one person who is aware of the benefits of driving change over driving people (and chooses to act on that knowledge) and I’ll show you a successful team.  That one person can pull the group to better performance, whether through their positional influence (more directly) or their language, behaviors, and questions (less directly).

I’d love to hear your thoughts on the CFAR briefing sheet.

H/T to Ralph Soule for showing me the briefing sheet.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

To start off 2012 right I created this one page pdf to illustrate the difference between driving people and driving change.  Those of you who’ve seen earlier versions will notice the old figures have been replaced with my not-so-awesome-but-still-lively stick figure people.  (I’m an engineer, not an artist, so go easy on me.)

If you’d like your own copy of the pdf, just leave a comment and I’ll send the file to your contact information.  In your file I’ll include your name in the permission line at the bottom so you can use the file as you drive change.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Next Page »