shameless idea thief

Entries categorized as ‘Management’

Bob Sutton’s 15 Beliefs:

November 9, 2009 · Leave a Comment

  1. Sometimes the best management is no management at all — first do no harm!
  2. Indifference is as important as passion.
  3. In organizational life, you can have influence over others or you can have freedom from others, but you can’t have both at the same time.
  4. Saying smart things and giving smart answers are important. Learning to listen to others and to ask smart questions is more important.
  5. Learn how to fight as if you are right and listen as if you are wrong: It helps you develop strong opinions that are weakly held.
  6. You get what you expect from people. This is especially true when it comes to selfish behavior; unvarnished self-interest is a learned social norm, not an unwavering feature of human behavior.
  7. Getting a little power can turn you into an insensitive self-centered jerk.
  8. Avoid pompous jerks whenever possible. They not only can make you feel bad about yourself, chances are that you will eventually start acting like them.
  9. The best test of a person’s character is how he or she treats those with less power.
  10. The best single question for testing an organization’s character is: What happens when people make mistakes?
  11. The best people and organizations have the attitude of wisdom: The courage to act on what they know right now and the humility to change course when they find better evidence.
  12. The quest for management magic and breakthrough ideas is overrated; being a master of the obvious is underrate
  13. Err on the side of optimism and positive energy in all things.
  14. It is good to ask yourself, do I have enough? Do you really need more money, power, prestige, or stuf
  15. Jim Maloney is right: Work is an overrated activity

Categories: Balance · Change · Engagement · Management · development · learning · linkedin · understanding

Helping Teams Advance One Gemba at a Time

November 8, 2009 · Leave a Comment

Most frontline teams in my organization are not used to being asked to improve their own process.  Like most organization in transition most improvement that has taken place in the organization in the past was management driven and usually owned and executed by outside experts like consultants and project managers.  As we transition into a system where teams are asked to be responsible for improving their processes every single day one of the most powerful tools management has is the gemba walk.   There are many reasons why the gemba walk is not only an important tool, but an essential tool in a Lean transformation.  Here are just a few:

  • Gemba walks are one of the most important methods for teaching management Lean.  It takes Lean out of the conceptual world and forces management to learn by doing. 
  • Gemba walks demonstrate a behavior change from management.  It shows that management is curious about the work and interested in seeing the real problems.   Early on they also demonstrate to the teams that everyone is in the change together.  Management is learning alongside the teams they are coaching.
  •  Gemba walks allow management to begin to understand the problems that they create and forces them to begin to take responsibility for solving the gaps in their management system.  They see firsthand the challenges created by unclear or too many priorities, silo thinking, narrow job classifications, etc.    
  • Gemba walks teach leaders how to set clear expectations and have the discipline to follow-up to see progress.  In order to do this effectively the manager must understand the content of the work; know how to see problems, and to know how far a team can improve over a set increment of time. 

In several post in the past I have talked about some of the advice I give leaders as the learn how to effectively lead gemba walks.  As my own experience has grown some of my thinking has advanced.  Here are a couple of tips that I hope help:

  • Gemba walks can only be effective if leaders are disciplined, consistent and organized.  This is why having management standard work is so important.  In our organization we create visual systems (Kamishibai boards) that track adherence to management system work to help reinforce this discipline.   These boards track the frequency, sequence and content of what should be checked during each gemba walk and clearly make visible that the walks are happening as scheduled.  As managers build these boards they need to determine how often they will visit each team (less frequently the higher you are in the organization), and then the board makes it transparent to the teams how often they can expect a visit thus reinforcing the management responsibility.
  • Early on it is important to have some coaching help during gemba walks.  It is nice to have a Sensei to go with you, but it is also effective to walk with a leader that has more experience then you do if a Sensei in not available.
  • During each walk a leader should ask the team a series of open ended questions to assess the current situation, challenge the current thinking and prepare the team for taking the next step.  If you are just getting starting it is very helpful to have a set of standard questions you always ask the team as well as a system to track notes from past gemba walks.  The leader should take the time to review their notes and prepare their questions so that they respect the time of the team.
  • Gemba walks and visual management go hand and hand.  Without visual systems gemba walks often end up being disorganized, not focused on data and worst of all they turn into PR visits or complaining sessions.  Gemba walks are probably the most important tool in helping set and maintain the expectation that teams make their processes visible.
  • Finally, at the end of each gemba walk the leader should summarize what they and the team has learned and then clearly define the follow-up items that the team and the leader need to resolve.  Often the due date will be during the next gemba.  This is the most powerful part of the gemba, because when done effectively it helps move the team to the next level of improvement and at the same time gives leadership credibility as the leaders solve some of the systems problems that get in the teams way.   In order to do this well a leader needs to have a system to track on follow up items.  If they ask a team to try x by y date the leader better show up to check or they will lose credibility quickly.  When they do show up to check on the follow up just like they said they would teams start to see that management is serious and they will invest the appropriate time in the improvement activities moving forward.  Something very important as teams begin to learn how to improve their own processes.

Categories: Change · Engagement · Lean · Management · Strategy · linkedin

10 Reasons Why You’re Probably Going to Fail

November 8, 2009 · 1 Comment

Post on failure by Tony Morgan, “10 Reasons Why You’re Probably Going to Fail” is really worth sharing, so here is Tony’s list…

10 Reasons Why You’re Probably Going to Fail

  1. It’s not your passion. If it doesn’t make your heart beat fast or cause your mind to race when you’re trying to sleep, you’re probably doing the wrong thing.
  2. You don’t have a plan. You need a vision, and you need to identify specific steps to make that vision become reality. That includes a financial plan. (I happen to believe you need direction from God on this.)
  3. You’re waiting for it to be perfect. Test-drive it. Beta-test that new idea. You’ll fall into the trap of inaction if you think it has to be absolutely right from day one.
  4. You’re not willing to work hard. Everything worth pursuing in my life has involved discipline and perseverance.
  5. It’ll outgrow you. Keep learning. Keep growing. But more importantly, build a team of people including leaders that can be who you’re not.
  6. You’ve had success in the past. I’ve watched organizations hang on to a good idea for too long. Time passes. Momentum fades. It’s risky to let go of the past and jump on the next wave.
  7. You’re unwilling to stop doing something else. Complexity is easy. Simplicity takes discipline. You can’t build a healthy marriage if you’re unwilling to give up dating other women. Who/what do you need to stop dating?
  8. You won’t build a team of friends. Anyone can hire from a resume. You need to find people you want to share life with. In the long run, great relationships will get you out of bed in the morning.
  9. You won’t have the tough conversations. When breakdown happens (and it always does), someone needs to put on their big-boy pants and initiate the difficult conversation that leads to relational healing.
  10. You’re afraid of failure. When fear consumes you, it will cause you to do stupid things. You’ll let negativity distract you. You’ll embrace the known, and grow comfortable with mediocrity. The more often you fail, though, the more often you’ll find success.

Categories: Management · Strategy · duh · failure · linkedin · understanding

Great Innovators Spend Less Than Good Ones

November 8, 2009 · Leave a Comment

A story last week about the Obama administration committing more than $3 billion to smart grid initiatives caught my eye. It wasn’t really an unusual story. It seems like every day features a slew of stories where leaders commit billions to new geographies, technologies, or acquisitions to demonstrate how serious they are about innovation and growth.

Here’s the thing — these kinds of commitments paradoxically can make it harder for organizations to achieve their aim. In other words, the very act of making a serious financial commitment to solve a problem can make it harder to solve the problem.

Why can large commitments hamstring innovation?

First, they lead people to chase the known rather than the unknown. After all, if you are going to spend a large chunk of change, you better be sure it is going to be going after a large market. Otherwise it is next to impossible to justify the investment. But most growth comes from creating what doesn’t exist, not getting a piece of what already does. It’s no better to rely on projections for tomorrow’s growth markets, because they are notoriously flawed.

Big commitments also lead people to frame problems in technological terms. Innovators spend resources on path-breaking technologies that hold the tantalizing promise of transformation. But as my colleagues Mark Johnson and Josh Suskewicz have shown, the true path to transformation almost always comes from developing a distinct business model.

Finally, large investments lead innovators to shut off “emergent signals.” When you spend a lot, you lock in fixed assets that make it hard to dramatically shift strategy. What, for example, could Motorola do after it invested billions to launch dozens of satellites to support its Iridium service only to learn there just wasn’t a market for it? Painfully little. Early commitments predetermined the venture’s path, and when it turned out the first strategy was wrong — as it almost always is — the big commitment acted as an anchor that inhibited iteration.

These ingredients are a recipe for sustaining thinking — trying to leap-frog over existing incumbents with cutting-edge technologies. Research shows that market leaders tend to beat back these kinds of attacks, resulting in a lot of squandered resources.

So what should leaders do?

Be frugal with financial resources but generous with human resources. What holds disruptive innovation back in most organizations isn’t a lack of money. It is a lack of committed people, a surplus of inappropriate mindsets, and a whole series of standard operating procedures that run counter to the fast-cycle decision making, in-market learning, and iterative approach to strategy required for disruption.

Freeing people to fully engage in this problem, and having leadership focus their energy on helping to ward off what I call the “sucking sound of the core” can be critical to success.

In an interview with Innosight, Intuit Chairman Scott Cook said that in his experience, the most successful disruptive teams have “an executive that is rooting for them, cheering them, mentoring them, actively spending time with them every week and protecting them from the antibodies of the rest of the companies that are trying to love them to death, or, exterminate them.”

Signing checks is easier than spending time. If you are truly committed to innovation, though, spend less money and more time. You’ll end up making substantially more progress.

Categories: Management · Strategy · design · development · linkedin

Helping Teams Advance One Gemba at a Time

October 19, 2009 · Leave a Comment

Most frontline teams in my organization are not used to being asked to improve their own process.  Like most organization in transition most improvement that has taken place in the organization in the past was management driven and usually owned and executed by outside experts like consultants and project managers.  As we transition into a system where teams are asked to be responsible for improving their processes every single day one of the most powerful tools management has is the gemba walk.   There are many reasons why the gemba walk is not only an important tool, but an essential tool in a Lean transformation.  Here are just a few:

  • Gemba walks are one of the most important methods for teaching management Lean.  It takes Lean out of the conceptual world and forces management to learn by doing. 
  • Gemba walks demonstrate a behavior change from management.  It shows that management is curious about the work and interested in seeing the real problems.   Early on they also demonstrate to the teams that everyone is in the change together.  Management is learning alongside the teams they are coaching.
  •  Gemba walks allow management to begin to understand the problems that they create and forces them to begin to take responsibility for solving the gaps in their management system.  They see firsthand the challenges created by unclear or too many priorities, silo thinking, narrow job classifications, etc.    
  • Gemba walks teach leaders how to set clear expectations and have the discipline to follow-up to see progress.  In order to do this effectively the manager must understand the content of the work; know how to see problems, and to know how far a team can improve over a set increment of time. 

In several post in the past I have talked about some of the advice I give leaders as the learn how to effectively lead gemba walks.  As my own experience has grown some of my thinking has advanced.  Here are a couple of tips that I hope help:

  • Gemba walks can only be effective if leaders are disciplined, consistent and organized.  This is why having management standard work is so important.  In our organization we create visual systems (Kamishibai boards) that track adherence to management system work to help reinforce this discipline.   These boards track the frequency, sequence and content of what should be checked during each gemba walk and clearly make visible that the walks are happening as scheduled.  As managers build these boards they need to determine how often they will visit each team (less frequently the higher you are in the organization), and then the board makes it transparent to the teams how often they can expect a visit thus reinforcing the management responsibility.
  • Early on it is important to have some coaching help during gemba walks.  It is nice to have a Sensei to go with you, but it is also effective to walk with a leader that has more experience then you do if a Sensei in not available.
  • During each walk a leader should ask the team a series of open ended questions to assess the current situation, challenge the current thinking and prepare the team for taking the next step.  If you are just getting starting it is very helpful to have a set of standard questions you always ask the team as well as a system to track notes from past gemba walks.  The leader should take the time to review their notes and prepare their questions so that they respect the time of the team.
  • Gemba walks and visual management go hand and hand.  Without visual systems gemba walks often end up being disorganized, not focused on data and worst of all they turn into PR visits or complaining sessions.  Gemba walks are probably the most important tool in helping set and maintain the expectation that teams make their processes visible.
  • Finally, at the end of each gemba walk the leader should summarize what they and the team has learned and then clearly define the follow-up items that the team and the leader need to resolve.  Often the due date will be during the next gemba.  This is the most powerful part of the gemba, because when done effectively it helps move the team to the next level of improvement and at the same time gives leadership credibility as the leaders solve some of the systems problems that get in the teams way.   In order to do this well a leader needs to have a system to track on follow up items.  If they ask a team to try x by y date the leader better show up to check or they will lose credibility quickly.  When they do show up to check on the follow up just like they said they would teams start to see that management is serious and they will invest the appropriate time in the improvement activities moving forward.  Something very important as teams begin to learn how to improve their own processes.

Categories: Change · Engagement · Lean · Management · Productivity · Strategy · design · understanding

Make a decision

October 17, 2009 · Leave a Comment

It doesn’t have to be a wise decision or a perfect one. Just make one.

In fact, make several. Make more decisions could be your three word mantra.

No decision is a decision as well, the decision not to decide. Not deciding is usually the wrong decision. If you are the go-to person, the one who can decide, you’ll make more of a difference. It doesn’t matter so much that you’re right, it matters that you decided.

Of course it’s risky and painful. That’s why it’s a rare and valuable skill.

Categories: Management · godin

Brilliant Management – “you put in the details”

October 17, 2009 · Leave a Comment

Categories: Engagement · Management · design · development · graphic

Change Initiatives and Employee Engagement

October 8, 2009 · Leave a Comment

According to a recent global study by Right Management, 94% of employees who report that change was not handled well in their organizations – are disengaged.

Drawing from research of 28,000 employees in 15 countries, Right Management’s key findings from the global study include:

  • Employee engagement is a key driver of organizational effectiveness and directly impacts productivity and profitability.
  • Best-performing organizations manage change nearly four times more effectively. In top-performing companies (defined as those achieving higher revenue and above-average customer loyalty profit results), 60% of employees responded that “change is handled effectively in my organization,” compared to 16% of employees in below-average performing organizations.
  • Less than half (43%) of employees are confident in their organization’s change process. One in three employees believes their organization does not handle change effectively.
  • The biggest downfall for senior leaders is the perception that they do not follow through on what they say they will do. Less than half (47%) agreed that senior leaders communicated change effectively; 54% of employees doubted senior leaders’ ability to respond appropriately to changing external conditions.
  • Organizations that do not manage change well are four times more likely to lose talent. Twenty percent of employees who perceived change was not handled effectively indicated they planned to leave within one year versus only 5% of employees who held a favorable view. The latter planned to stay for at least five years.
  • Ineffective change management can lead to lower levels of job confidence. Of the employees who reported that change management was not handled well, 45% expressed favorable feelings about not losing their job within 12 months, while 32% did not. This is in stark contrast to organizations with effective change management, where 80% of respondents had positive feelings about keeping their job versus only 7% who did not.
  • Ineffective change management negatively impacts an organization’s ability to attract talent. When employees reported that change was managed poorly in their organizations, 75% of respondents had concerns with their company’s ability to attract talent.

Categories: Change · Engagement · Lean · Management · duh · learning

Eblin’s 5 questions for struggling leaders

October 7, 2009 · Leave a Comment

Question 1: 
What am I trying to do that extends beyond the actual time available to me to personally do it?

Question 2: 
What am I trying to accomplish by doing that?

Question 3
Given the role that I’m in, what should I be trying to accomplish instead?

Question 4: 
What resources (people, systems, processes) do I need to acquire or develop to cover whatever still seems worthwhile in my answer to Question 2?

Question 5: 
What opportunities do I have to shift from retail leadership (being personally present or involved in everything) to wholesale leadership (leveraging and involving others to act on the overall plan)?

What are you noticing about limits lately? What are you doing to adjust?  I’d love to hear your thoughts and stories about changes you’re making to deal with the limits leaders face.

Categories: Balance · Change · Management · Productivity · understanding

10 reasons you are hated

October 7, 2009 · Leave a Comment

Your team hates you. Really. They do. They hate their boss (you) but they just won’t say so because they like getting paid. But when they go home at night, they spill their bile about their taskmaster of a boss who does nothing but drive them crazy (isn’t that what you do too?).

It’s been a while since I’ve been controversial (okay, maybe the post on trust not being the most important aspect business partnerships was provocative but I’m talking controversial at the level of the I don’t care about your degree post). For this post, I’ve been sure to drink a glass of vinegar before typing.

If you don’t start fixing some of these behaviors, you might end up with a mutiny on your hands. In today’s world though, that doesn’t involve them tossing you in a dinghy – instead they’ll all just quit their jobs.

Before you go all “Mike has lost it again. This post doesn’t apply to me so I won’t read any more of it.” I’d ask you to spend the 2-3 minutes it will take to spin through the below list and see if any of the points resonate. If you make it through all ten and can honestly say none apply to you, bravo (related: are you hiring?).

If some of the points do resonate, I’m asking you to commit to rectifying some of these behaviors. We’ll all be happier that way. To assist with that, I’ve offered some suggested behavior modifications for each of the ten.

Full disclosure – I’ve been plenty guilty of some of the below behaviors. Fortunately I’ve had talented folks around me help me work on many of them. I’m not perfect by a long shot yet. I guess what I’m saying is all of these things apply to all of us even in some small measure.

So here goes… 10 Reasons Your Team Hates You:

10. You don’t prioritize. Everything is important. When you do this, you remove your team’s ability to say no to less important work and focus their efforts on critical tasks. The fix: write down all the tasks you have folks working on and FORCE yourself to assign a H, M, or L to each task (and treat it as such). Thou shalt only have 33% of all tasks in each of those three categories – you can’t assign everything a “High” importance.

9. You treat them like employees. You don’t know a darn thing about them as a person (which makes them feel like nothing more than a number). The fix: read this post about 7Up.

8. You don’t fight for them. When is the last time you went to bat for a team member? And I mean went to bat where you had something to lose if it didn’t work out? When you don’t stand up for them, you lose their trust. The fix: identify something you should have gone to the mat for recently and get out there and fight. Get someone that raise they deserve. Go fight for them to get that cool new project.

7. You tell them to “have a balanced life” then set a bad example. You tell them weekends are precious and they should spend them with their family then you go and send them emails or voicemails on Sunday afternoon. The fix: either curb your bad habit of not being in balance or learn how to do delayed send in Outlook so your messages won’t go out until Monday morning.

6. You never relax. You walk around like you have a potato chip wedged between your butt cheeks and you’re trying not to break it. When you’re uptight all the time, it makes them uptight. Negative or stressful energy transfers to others. The fix: laugh, get a remote controlled car or tricycle to drive around the office, or put on a Burger King crown. When you relax, your team knows it’s okay for them to relax too.

5. You micromanage. You know every detail of what they’re working on and you’ve become a control freak. They have no room to make decisions on their own (which means yes, they’ll make a mistake or two). The fix: back off. Pick a few low risk projects and commit to not doing ANYTHING on them unless your team member asks you for assistance. It’ll be uncomfortable for you. Give it a try you micromanaging control freak.

4. You’re a suck-up. If your boss stopped short while walking down the hall, you’d break your neck. Your team hates seeing you do this because it demonstrates lack of spine and willingness to fight for them. It can also signal to them that you expect them to be a sycophant just like you. The fix: try kicking up and kissing down instead.

3. You treat them like mushrooms. Translation: they’re kept in the dark and fed a bunch of crap. Do you ration information? Do you withhold “important” things from them because it’s “need to know” only? All you’re doing is creating gossip and fear. The fix: stop acting like 007 and spill some beans.

2. You’re above getting your hands dirty. You’re great at assigning work. Doing work? Not so much. They hate watching you preside (and they hate it even more when you take credit for what they slaved over). The fix: get dirty. Climb under the proverbial tank and turn a wrench. Roll up your sleeves and pick a smaller project you can handle in addition to your other responsibilities and DO THE PROJECT YOURSELF.

1. You’re indecisive. Maybe. Or not. But possibly. Yeah. No. I don’t know. OH MY GOSH MAKE A DECISION ALREADY! That’s what you get paid to do as the leader. You drive them crazy with your incessant flip-flopping or waffling (mmmm waffles… oh. Sorry… still writing). The fix: DO SOMETHING! Acknowledge you might make a mistake but do something. A team is much more likely to follow a leader who makes decisions (even some bad ones) than a leader who makes no decisions at all.

There they are: 10 reasons your team hates you. Do any of them fit? I’ll tell you what: I DARE you to email this post to your team members and ask them to anonymously circle any of the above behaviors that apply to you. I then further challenge you to fix the one or two that have the most votes. Trust me – all of you will be happier if you do. How’s THAT for provocative?

Categories: Engagement · Management · Strategy · failure · simplicity