Research in Motion’s public battle

5 07 2011

When executives feel they have to go outside of a chain of command in order to voice concerns, we see perfect examples of the need for Operational Performance Management (OPM).  The current Research in Motion public battle is a great place to start.  An anonymous executive sent an open letter to Jonathan Geller, of The Boy Genius (BGR.com), to call out the current RIM culture.  What is more entertaining about this is the fact that RIM responds publicly, which only makes this sound like a bigger problem.

Highlights of the RIM letter:

  • You have many smart employees, many that have great ideas for the future, but unfortunately the culture at RIM does not allow us to speak openly without having to worry about the career-limiting effects.
  • We often make product decisions based on strategic alignment, partner requests or even legal advice — the end user doesn’t care. We simply have to admit that Apple is nailing this and it is one of the reasons they have people lining up overnight at stores around the world, and products sold out for months. These people aren’t hypnotized zombies, they simply love beautifully designed products that are user centric and work how they are supposed to work.
  • Teams still aren’t talking together properly, no one is making or can make critical decisions, all the while everyone is working crazy hours and still far behind. We are demotivated.
  • Strategy is often in the things you decide not to do.
  • We simply must stop shipping incomplete products that aren’t ready for the end user. It is hurting our brand tremendously. It takes guts to not allow a product to launch that may be 90% ready with a quarter end in sight, but it will pay off in the long term.
  • The truth is, no one in RIM dares to tell management how bad our tools still are. Even our closest dev partners do their best to say it politely, but they will never bite the hand that feeds them.
  • 25 million iPad users don’t care that it doesn’t have Flash or true multitasking, so why make that a focus in our campaigns? I’ll answer that for you: it’s because that’s all that differentiates our products and its lazy marketing. I’ve never seen someone buy product B because it has something product A doesn’t have. People buy product B because they want and lust after product B.
  • RIM has a lot of people who underperform but still stay in their roles. No one is accountable. Where is the guy responsible for the 9530 software? Still with us, still running some important software initiative. We will never achieve excellence with this culture. Just because someone may have been a loyal RIM employee for 7 years, it doesn’t mean they are the best Manager / Director / VP for that role.
  • However, overconfidence clouds good decision-making. We missed not boldly reacting to the threat of iPhone when we saw it in January over four years ago. We laughed and said they are trying to put a computer on a phone, that it won’t work.
  • Reach out to all employees asking them on how we can make RIM better. Encourage input from ground-level teams—without repercussions—to seek out honest feedback and really absorb it.

All of these are examples of what happens in almost every business culture I have witnessed.  It is certainly not unique to RIM. If you think this is not happening within your business you are sorely mistaken.

What can you do….

  • Foster honest discussions.  Stop punishing those who do not follow the company line. Reward critical thought.  Ask people to do their homework prior to the meetings.
  • Listen.  Tap into the collective intelligence of the organization.  1,000 eyes see a lot.
  • Act out.  Stress your opinion if you have a dissenting idea.If you love your company and passionate about what you do, chances are your opinions probably do matter.
Advertisement




Meeting Expectations

18 01 2010

In a recent MyMidwest (Midwest Airlines) inflight magazine there is a story by Kimberly Douglas of FireFly Facilitation on Meeting Management.  If we look at a couple of the numbers from Douglas’ research we can begin to quantify the impact of meetings.

38,000 msft employees say that their 5.6 hours per week spent in meetings are unproductive.  That’s over 11 million hours of meetings.  Now if we say the average msft employee makes 100k per year (including benefits), that translates to ~ $50/hr.  If we do the math, that’s ~ $550 million a year in meeting costs.

Microsoft’s 2009 annual income was $58.4 billion which makes just their meeting costs roughly 1% of their annual income.  Let’s make a couple more assumptions: that half of that value is waste (more people than needed, run longer than necessary, etc) and we could reduce that by 10% which should be easy.  The result is ~ $22.5 million.  I am guessing here, but it should be worthwhile to at least try and improve upon meeting management and find some other way to leverage that $22 million.

  • What % of time do you spend in meetings?
  • Would your employees feel that meeting management and effectiveness could be improved upon?
  • What would you do with an additional 1% of your annual income?
  • In what ways could you improve meeting management?




Jargon

19 08 2009

This is from Paul Bayne, a guest blogger:

When you’re listening to a presentation, how often do you hear the current management buzz words or internal company acronyms? Do they add depth to the message, or do they serve to increase the status of the presenter by making them appear more versed or knowledgable? When looking back at the information in a historical context, will the language enhance the meaning, or will it detract from it? I worked with a consulting manager who was famous for his use of buzz words. The following paragraph was compiled from the 55 buzzwords used during one 90 minute conference call:

I’m trying to level set your assumptions, so we can then incorporate these concepts into the communication plan’s talk track for an apples to apples comparison of the current state/future state. That should give us the safety net and support mechanism we need to factor into as we create the coathooks to harden the numbers in the discussion document, strategically migrating to a closely aligned, re-engineered future state opportunity model. We’ll then drive away from the shadow tracking spreadsheets into a conference room pilot where we can more effectively and efficiently operate in sandbox mode to hardwire the black box into an actionable white box.

Does your use of language provide clarity to your thoughts and actions, or does it communicate very little while saying very much?





Practice

10 06 2009

On of my favorite hobbies is coaching little league baseball.  During a game last year it hit me that many meetings are run in a similar manner.  Pardon me for the comparision, but the similarities can provide a little humor at a process that all too often needs improvement.

As I watched, I noticed I had three outfielders playing in the dirt, my third baseman had one foot in foul territory, and my second baseman was standing on second base.  I also had a few players that were ready, on their toes, and prepared.

  • How often at your meetings do you have the back of their room paying sporadic attention while most of their focus is either on their laptop or blackberry?
  • How many people do you have playing by their own rules?
  • What percent of the room is prepared and actively participating in the meeting?

As a coach, we know we need a game plan.  Yet often we “wing it” because of experience and love for the game.   Sometimes this works, and sometimes not-so-much.

During practice, we can move people into groups of like needs and work at different speeds to excel learning (or at least repetition).  We can redo things as many times as necessary.  We can freely move people into different positions.

We have the luxury of a practice schedule – organizations and managers do not.  They have to learn while doing.  They do not get trophies for participation.  We need our people to be prepared and active in a meeting or else we are not maximizing our use of time.

If the meeting is to understand a performance issue, then we need to have someone write up the issue and send a brief summary to the team.  We need the rest of the team to have read the brief, done their relevant research, and prepared a list of potential recommendations to discuss.  The meeting should not be about discussing what research needs to be done – it should be about looking at the research and agreeing upon a course of action.





Manage vs. Monitor

21 05 2009

It has always struck me as a little odd that a great deal of marketing literature in the Business Intelligence and Performance Management space talks about “monitoring” performance.  Isn’t the entire goal of this space to help companies actively “manage” their business.  My concern is that “monitoring” assumes that all is well unless some alarm is triggered.  

While it is fine for the thermastat to monitor temperature, perhaps business is a tad more complex.  Instead of waiting for things to get to a threshhold, we need to understand a number of things that all work more or less together to explain a more complex concept.  

Instead of just showing up for a meeting, what if we focus on creating a culture of being prepared for a meeting.  We can then use Business Intelligence as a organized and focused set of tools to help with our prep work.





Clarity – Pick One Voice

17 05 2009

A few months ago during the Presidential inauguration, a concept I have kicked around a bit presented itself in a vivid example.  What stuck me was all the pomp and circumstance, all the background noise.  Did I really want to hear the opening prayer, the closing prayer, all the singing, and the poetry?  No, I wanted one thing – to hear the message this President was going to deliver on how he was going to set up his presidency.  Everything else was in a way, distraction.

As organizations, how often do we set a clear and concise goals for the organization and the individuals?  How many times do we repeat what someone else just said?

When we design KPIs for the organization, do we create a single measure for a goal and use other analytics for support?  Or do we create a number of ways to view the goal?  If we create many definitions, we allow for people to pick the one they want.  Use KPI design as a way to gain clarity of a goal.  Use Scorecard design to gain clarity of purpose.





Customer Lifecycle Value

1 05 2009

Depending upon on how well your know your business, a great discussion to have somewhat regularily is whether or not the customer lifecycle value is increasing or decreasing.  To achieve this we need to know a few things…

  • How much has the customer purchased from us?
  • How long are they likely to stay with us?
  • What does it cost us to serve them?

None of these are necessarily easy questions to answer, but that does not mean we should not talk about these items. Worst case, you should at least be looking at the average revenue and cost per client and see how those are changing. They are probably pretty good indicators of lifecycle value.  If we look at the trends of our revenues, costs (COGS & SGA), and profits per customer this should certainly indicate if we are doing better or worse.

While most of us do this to some degree, we probably also throw in a great deal many more variables and business rules and end up discussing various concepts. What about once a month or once a quarter getting all the department heads together and discuss progress on only these items.





Is a failed action the same as a failure to act?

27 04 2009

Over the weekend, Seth Godin blogged about making timely decisions.  It brought to mind a number of items worth additional discussion.  One of my favorite sayings is “we should do something” when managers are shown a potential issue.  It is usually followed up with a flurry of meetings, too much information, and less than a clear path forward.  While frustrating, it became clear over time that we often lack a process to consider, debate, and ultimately put ad-hoc course corrrections into action.  It was also appearant that we suffer from a culture that uses information overload to decline action based on the need for additional information.

To make a little more sense of it, here is a two by two grid that shows the risk and rewards of whether action was created and whether it was correct or not.  The goal of this was to highlight perhaps the personal motivations behind action or lack thereof.

the-risk-of-action2

Creating action is more likely to cause the extremes in risk versus reward, while delaying or taking no action is often the safer route.  While companies need to take risks to lead within the market, employees may not have the same motivations.  Is the potential for a promotion, worth the risk of falling out of favor?  Do we, as company policy, reward action financially?  Is a failed action the same as a failure to act?





Business Intelligence vs Business Analytics

14 04 2009

There is a growing debate over Business Intelligence vs. Business Analytics and what the future holds.  Clearly the Business Intelligence world has been shaken with Hyperion, Business Objects, and Cognos all now smaller parts of bigger companies.  This has created a number of marketing opportunities for the likes of Microstrategy and SAS.  The obvious marketing play was independence.  Now it is clear that SAS is taking a slightly different tact by claiming that Business Intelligence is dead and the future is Analytics.

Marketing messages aside, what we need to be focusing upon how we use information and the management process.  Call it data, information, intelligence, analytics, or whatever we come up with next, it is all irrelevant if we don’t understand how to use it.  A basement full of great tools doesn’t mean the house remains maintained.  
  • Do you have rules on when to use the specific tools in the BI suite?
  • Do your people have the analytical skills required?
  • Do you have a process where the information can be discussed and actions agreed upon?
We all agree that organizations need to make fact based decisions.  The other thing we should all be working upon is creating a common vernacular for each of the tools.  As analysts, consultants, pundits, bloggers, we do little good if we don’t teach the value of how to use each of the tools.  You don’t need predictive analytics for an exemption report.  You don’t need a sexy looking reports that do little to explain the goal.  Organizations don’t need real time scorecards.  

What organizations do need are ways to make people comfortable to take decisive action.  We also need these actions to align to company goals and strategy.  The tools we use need to be consistent enough for us to trust them, and the minds that analyze them need to be able to use the tools well enough to communicate only what matters in a digestible presentation.





Because you can…doesn’t mean you should

14 04 2009

We do a number of things in the name of business intelligence.  We say we have to have real time information.  We have to have hundreds of reports.  We have to be able to look at everything in every direction.

Business Intelligence software promises us this and make this seem like an achievable goal.  And yes it would be great to know everything about everything and get a perfect 360 degree view of the organization.

Yet it is not really achievable, actually not even close.  Instead ask what are the goals & objectives of the organization, and how does this support that end.  We are very quick to say “we can do that” but we need to temper that with “why should we do that?”  Think of the goal of a dashboard – to providereal-time information on a specific subject.  I have known many managers that constantly stare at the screen to see if anything moved.  

What we really need is to understand how to use the function of time and integrate that into a analytical management process.  What would you get more out of, a tactical dial that shows us one KPI, or a meeting at the end of the day to review a number of KPIs?





The Continuous Improvement Meeting – CIM

2 04 2009

Including on this blog, much has been written about meeting management: how to run a more effective meeting, improving meeting outcomes, etc. All concepts in which I am in complete support. I’ve found, however, that it is very difficult to implement wholesale change into an organization’s meeting culture. And there are several characteristic profiles of meeting culture within organizations.

Meetings typically occur for the purpose of communicating information, yet most meetings I’ve witnessed over my career consistently end with no action or accountability to do something. So, what I’m going to suggest here is not a change in your existing meeting culture. Continue to hold the meetings that your organization routinely conducts, for whatever the purpose. But, if your organization is serious about driving operational performance improvement, you need to add a meeting to your schedule. Yes, that’s right. I’m advocating yet another meeting. This meeting is specific in purpose. It never deviates its agenda. And it is a critical management tool for driving performance improvement.

The continuous improvement meeting or “CIM” has five objectives.

1. Review progress against KPIs
2. Identify barriers to performance
3. Share best practices
4. Develop action plans for next period
5. Recognize superior performance

The CIM is 45 minutes in length, maximum. It is conducted at every level of the organization. This is critical to insure all levels of the operation are aligning their efforts with the strategy. Typically, the meeting should occur weekly at the front line to monthly and/or quarterly at the executive level.

The keys to successful implementation of the CIM are:

  •  It is a separate, distinct meeting. Not part of another meeting agenda.
  •  45 minutes maximum
  •  It is held at the same time & day every period
  •  It must be group meeting

One of the biggest gaps in operational performance management is the area of management effectiveness. We tend to focus on effectiveness and efficience of front line contributors. But how exactly does management improve its effectiveness at managing? Try implementing the Continuous Improvement Meeting into your management process and see how much more focus you create around the metrics that are important to your organization’s strategy.





Meeting Management & Agendas

26 03 2009
  • How much money do you spend annually on meetings?
  • Do people show up on time, follow an agenda, and end the meetings on time?
  • Do meetings regularly create and review actions?

Meetings need structure and process, yet most meetings happen because of momentum. “We always meet on Fridays as a team.” We meet to discuss and communicate. Yet this discussion is typically around individual status updates, and less about what needs to happen, or hurdles that need to be cleared.

Shouldn’t every meeting have a well defined purpose to specifically create an action. Change “meet to review project status” to “meet to analyze project performance, understand risks, and make recommendations.” Now we go from asking people to attend the meeting TO preparing the team for the meeting. Roles and tasks should be assigned and materials need to be reviewed prior to the meeting.

Here is a link to Seth Godin’s blog on the same subject – Getting Serious about your Meeting Problem