Tuesday, April 22, 2014
Book Review, Professional
I've spent a great deal of my professional career working on helping users collaborate in one form or another. I setup Local Area Networks (LANs) when they were still called that and not networks. I connected folks via email before the Internet was a gleam in Al Gore's eye. I have spent the last 14 years helping organizations collaborate with Microsoft SharePoint. So when some colleagues said that I had to read Collaboration, I didn't hesitate to pick up the book. What I didn't realize when they recommended it was that the author, Morten Hansen, had a specific definition of collaboration in mind, and it didn't necessarily match my point of view.
To Conspire with the Enemy
If you've heard me talk about collaboration – or creating engagement – you know that I love to poke fun at the word collaboration because it means so many different things to so many different people. As a result it's a word that I've come to associate as the starting point for a conversation instead of the end. In most contexts, I define collaboration as working with others towards a common goal. It's a simple definition and it covers a lot of ground.
When I've got an audience that's being contrary, the dictionary definition I throw out to jar my audience is "to conspire with the enemy." This definition isn't the kind of definition that you would normally expect someone talking about collaboration to have and therefore can sometimes be the spark to start a discussion.
Regardless of how you define collaboration, Morten Hansen has a specific large organization definition for collaboration. His definition is focused on different parts of a large organization working together. As such, it's really not applicable to most of the organizations on the planet. It works great for the Fortune 1000, but as the organizations get smaller and more focused, the guidance from Collaboration gets less directly useful. Despite this, the book does echo some of the concepts discussed elsewhere which are broadly applicable – and important for organizations of all sizes. I found that most of the concepts in the book were rooted in strong research and can be easily adapted to organizations of any size.
Too Much of a Good Thing
Perhaps the most heretical discussion in the book is that there can be too much collaboration. Conventional wisdom is that collaboration is good and more collaboration is better. That is, that you should be able to have more and more collaboration with greater and greater positive impact on the bottom line but Hansen effectively argues that there are times when collaboration for collaboration's sake isn't adding value to the bottom line. His argument is that it's possible to have collaboration that makes everyone feel good but isn't helping to move the organization forward.
It is possible that the cost of collaboration exceeds the business benefit of the collaboration. The recommendation is to take the return on the collaboration and subtract out both the direct costs of the collaboration as well as the opportunity costs for the time spent on the collaboration process. If the number is positive then collaboration is warranted – if it's negative then the collaboration isn't worth it.
Of course, this puts the decision to a mathematical precision that may or may not be warranted – and as mentioned in How to Measure Anything, sometimes our ability to estimate isn't the best.
Lies, Damn Lies, and Statistics
The Heretic's Guide to Best Practices quoted How to Measure Anything to talk about biases. Thinking, Fast and Slow also spoke about biases – including an anchoring bias that causes us to make differential adjustments to an estimate – even if the baseline estimate is fundamentally flawed. Collaboration points out that many mergers speak about the synergies that the organizations will be able to capitalize on together – many of which never materialize. There are many reasons for this including bad estimates but also an underestimation of the work it is to merge two cultures.
Cultures are funny things. They're made up of the people, processes, and interactions but they also resist being changed by people or changing processes. This makes it difficult for employees at the various organizations to work together. Sometimes organizations have been competitors and the situation is worse because there's a distrust that has built up between the organizations.
Means and Ends
Sometimes we get so wrapped up in the idea of collaboration and how fun it is to be able to share with our peers that we forget to make sure that it's delivering business value. As I mentioned in my review of Who Am I?, Aristotle divided human motives into means and ends. Since then we've continued to struggle with forgetting why we're doing something. We get so wrapped up into doing it – like collaboration – that we forget why we're doing it.
In most businesses, collaboration is a means to the end goal of accomplishing the corporate mission. If we get lost in the idea of collaboration and forget that there's a mission to be completed we've slipped into the means and ends confusion.
In today's world there's a conflict between what managers are being asked to do to drive their own individual team performance and what they're being asked to do to support others – as they're trying to maximize their business unit's contribution to the bottom line. Managers are being asked to deliver performance from their units and simultaneously being asked to support their peers through collaboration. This sets up an interesting conflict since you only have so much time and you can only spend it working on improving your own performance or on helping others.
Collaboration makes a point that the best managers are those managers who can find a way to do both – to accomplish their own performance goals while helping others. Perhaps the need for both selfish individual team productivity and cross-team collaboration makes the question that was asked in Destructive Emotions about whether we're Rational egoists (we're compassionate because it's self-serving), selfish and compassionate, or compassionate and selfish – somewhat moot. Drive told us that some of our intrinsic motivators are overwhelmed and corrupted by explicit external motivators like compensation.
In Collaboration we learn that 70% of the time we'll collaborate with one another – unless we change the name of the game to Wall Street – in which case we'll defect (work in a non-collaborative manor) 70% of the time. Kurt Lewin's famous quote that "behavior is a function of both person and environment" includes the words that we use and the expectations as the environment.
Jerry Seinfeld is famous for his hit sitcom Seinfeld show – a self-described show about nothing. The assumption is often made that Jerry Seinfeld has always been a funny man. Perhaps that's true, but as we learned about many great leaders in Outliers and Extraordinary Minds, most great leaders had to practice. In Jerry Seinfeld's case, he honed his skills for comedy by working on brevity. He learned from the old saw "I would have written a shorter letter if I only had more time." Learning to be brief – but not too brief is an art form that isn't practiced that often any longer.
If you've been a part of marketing campaign development you know how much time can be invested trying to determine the right message – and even the right words. Discussions rage and testing ensues to ensure that the most impact can be extracted from a marketing exercise.
More close to home, most of us have been in a relationship where we've said the wrong thing and have inadvertently caused damage to a relationship. Wives have said things that hurt their husbands and vice-versa. (If this is a real problem, reading The Science of Trust might be useful.)
Leaders' words are important. They can fan the fires of collaboration or deeply hurt the collaboration path that the organization is on. A leader's words should both build the logical argument for collaboration but more importantly develop an emotional connection to the goal. In The Happiness Hypothesis and Switch there was the Elephant-Rider-Path model which encouraged us to ensure that we were making both the logical argument and the emotional one. If leaders choose their words they can effectively motivate employees to collaborate when appropriate.
Hansen believes that the key to effectiveness with collaboration is disciplined collaboration which he defines in one phrase "the leadership practice of properly assessing when to collaborate (and when not to) and instilling in people both the willingness and the ability to collaborate when required."
This practice – he believes prevents both over and underinvestment in collaboration. Disciplined collaboration takes strong leaders.
In Good to Great Jim Collins talks about the Stockdale Paradox "You must maintain unwavering faith that you can and will prevail in the end, regardless of the difficulties, AND at the same time have the discipline to confront the most brutal facts of your current reality, whatever they might be." It's this same type of strength that is needed to encourage the right kind of collaboration – at the right time – in an organization.
However, even with strong leaders who are practicing disciplined collaboration there are problems. Collaborative environments sometimes make it hard to maintain individual accountability.
Hiding in Plain Sight
Camouflage is used by animals and warriors to hide in plain sight. Because there is nothing specific about their marks and appearance they're able to blend in with the background. Some collaboration is like that when people are part of a large group and when performance isn't measured specific to the person they tend to develop a characteristic called social loafing.
That is they assume that someone else will do the work and they can sit back and relax. This is a hidden danger for organizations as they seek to improve collaboration – maintaining individual accountability in the context of supporting collaboration with others.
Make It Easy
If you want to make collaboration work, you'll need to ensure that the process is well understood as explained in Don't Make Me Think. Demand spoke about the idea of a hassle map and how you need to reduce the number of hassles to create a product that people want. Information Architecture: Blueprints for the Web mentioned that when Amazon introduced tagging on its site no one knew how to use it and so no one did. When driving collaboration you'll want to eliminate the ambiguity and help everyone know what to expect. Collaboration quotes a study that says that intention has little to do with execution – when students were shown how to get to the health center to get a tetanus shot they got the shot 28% of the time as compared to just 3% of the time if they were just shown the reasons to get the shot.
When you're trying to get to collaboration you want to make it easy rather than motivating them that it's something important to do. If your organization prevents information sharing or limits how business units can work with one another you may find that it's difficult – if not impossible – to get collaboration to take off. But this isn't the only barrier.
There are four key types of barriers that you may encounter when trying to implement collaboration. Each barrier has several factors that lead to it.
1: Not Invented Here
I posted a complete post on the Wisdom of Not Invented Here, however in the context of Collaboration, they believe that there are four factors that lead to it. They are:
- Insular Culture – The more tightly nit a group becomes the less open they are to input from the outside.
- Status Gap – People tend to accept input more readily from those of similar status to themselves rather than those who have a much higher or lower status.
- Self-Reliance – The more self-reliant folks are the less likely they are to acknowledge that good ideas can come from others.
- Fear – No one likes revealing their shortcomings. By accepting something from someplace else you're admitting one of your limitations.
Some kids will openly share their toys – and others won't. That may be because of the "licking and grooming" they received as children. (See How Children Succeed for more.) However, that does you little good when you're trying to drive collaboration in your organization. Here are four non-childhood factors that lead to hoarding behaviors:
- Competition – When people or groups inside the organization are invited to compete with one another there's a natural tendency to hoard. So keep competition outside the walls of the organization and collaboration inside.
- Narrow incentives – The more narrowly you incent people for their own performance, the lower the motivation for sharing activities. Make sure that the incentives are balanced between internal performance and sharing and collaborating.
- Being Too Busy – Organizations have lost thousands of workers so it seems like everyone is trying to do more with less. Collaboration takes time – and you don't have time you won't be able to collaborate.
- Fear of Losing Power – A common question is "If knowledge is power what happens to my power when I share it?" Despite the fact that generally you become more powerful – from a knowledge perspective – when sharing it feels uncomfortable and generates a fear.
In the world of today we're used to Google and the ability to find what we're interested in – however, that's only in our public lives. We still realize that inside an organization finding information is tricky and difficult. In most organizations there is no enterprise search and in many cases what you're looking for isn't written down. What you really need is locked up inside someone's head somewhere. Here are four factors that lead to the search barrier:
- Company size – The larger the company the harder it is to create an enterprise search solution that delivers contents and people to you when you need it.
- Physical Distance - The larger the difference between people the lower the chances that you'll discover the information you need by chance. Marcia Bates believes that we find 80% of what we know accidentally – so proximity matters. (See Pervasive Information Architecture, The New Edge in Knowledge, and Thinking, Fast and Slow.)
- Information Overload – We've created so many sources of information and we've made it so much easier for anyone to communicate, that we've created an overload of information. (See The Information Diet and The Paradox of Choice for more)
- Poverty of Networks – We believe that it's a small world – and in some ways it is. However, we fail to realize that what we see is not all there is. Just because we can't find it doesn't mean that it doesn't exist.
I've written a few times about tacit knowledge and the problems of knowledge management including in: Lost Knowledge; The New Edge in Knowledge; The Wisdom of Crowds; Thinking, Fast and Slow; Pervasive Information Architecture; and Apprentice, Journeyman, Master. The transfer barrier – the fact that transferring information is hard is a fundamental barrier to collaboration and life. Here are three key factors:
- Tacit Knowledge – Tacit knowledge is either "unarticulated knowledge waiting transfer" or "cannot be transferred: we know more than we can tell" depending upon who you want to believe. In either case, conveying it to someone else is hard and most frequently requires person-to-person communication which can be difficult.
- No Common frame – Because there's little similarity between two people it's hard to establish the common framework necessary for communication. Literally the mental models that two people have are so different they can't communicate (See The Fifth Discipline, Sources of Power, Efficiency in Learning, and The Art of Explanation.)
- Weak Ties – It's difficult to share your knowledge with someone that you don't have a strong relationship with. You want to have a deep connection to trust that the person you're sharing with won't use the knowledge against you.
Criteria for Effective Collaboration Goals
As Lewis Carol said "If you don't know where you're going then any road will get you there." Having an effective goal – or goals – is critical if you know you want to foster collaboration in your environment. Here are four criteria for setting goals that lead to collaboration.
1: Must Create a Common Fate
There's the parable of the farmer's birthday where all of the animals get together and agree to make him breakfast. The chicken will give up some eggs and there will be ham and toast. When the animals turn to the pig and ask him what he thinks of the plan he says "I think that you are all interested in this plan but I'm invested." Investment is what you want from all of the parties and that you'll only get if everyone is subject to the same consequences – good or bad. You won't get everyone motivated to make collaboration successful if some folks aren't a part of the rewards or consequences of the success or failure.
2: Must Be Simple and Concrete
Platitudes, those dull, flat, trite remarks uttered if profound, have no place in setting effective goals. Everyone should be able to understand the goal without any further explanation. It's not about being "preeminent in the exploration of space" – it's about "landing a man on the moon and bringing him safely back to Earth within the decade." There's no explanation needed because we know what needs to be done. Goals that leave no room for ambiguity and are simple are fuel for the collaboration engine.
3: Must Stir Passion
Most goals are positively boring. They talk to the rider (See the Elephant-Rider-Path model in The Happiness Hypothesis and Switch.) We need to talk to the elephant and get people emotionally involved. That means appealing to a higher purpose or at least connecting with the kind of person that someone wants to be. We want people to be engaged.
4: Must Put Competition on the Outside
As mentioned above, when employees are competing with each other it makes it hard to collaborate. It leads to hording behaviors where they won't help others for fear that it will give their coworkers an advantage over them in their competition.
Sins of Collaboration Hopefuls
Sometimes there are mistakes that can be made that will make collaboration harder than it needs to be or should be. Here are three sins that can kill collaboration.
1: Small Teamwork Kills Collaboration
The more that you get a small group to work together as a team and collaborate internally the less likely they are to collaborate across groups. Diffusion of Innovations speaks about how the cosmopolitan-ness of an individual determines how fast they'll adopt an innovation. Said differently, the more that someone interacts with other groups the more likely they are to accept external ideas.
2: Everybody Do Teamwork Now (Except Those of Us at the Top)
Collaboration is – sometimes – treated like a great idea as long as you're not the first one to have to try it. Leadership can kill collaboration by saying one thing and doing another – or the opposite. If you're a leader and you're invested in creating collaboration, you'll need to deliver the goods by doing some collaboration yourself.
3: Teamwork Becomes the Point of It All
As mentioned above you can't take your eye off the ball and forget that collaboration is a means to an end – it's not an end in and of itself. When collaboration becomes the goal instead of the tool to get to the goal, you've got a problem.
Rules for Effective Networks
Collaboration relies on the network of people that you build. It's the people that you can reach in and ask a question of. It's the people that you trust and that trust you enough to share information. Here are six rules for building your networks.
1: Build Outward, Not Inward
Diversity in your network is important as we've discussed above. The more that you can associate with people in different networks the more effective your network can be because you can reach out to people with dissimilar skills and knowledge. The more heterogeneous your network the more likely it is that you'll find an answer when you need it.
2: Build Diversity, Not Size
Each connection in a networks requires some level of effort to create and to maintain – though admittedly some require remarkably low levels of energy to maintain such as a childhood friend. The goal in building an effective network is to build diversity in the group – not to increase the size of the network for the sake of the network size. Consider the Dunbar number – the awareness that the number of social connections that an animal can maintain is directly related to the size of the animal's brain and that humans can maintain roughly 150 social connections. (See The Information Diet and The Happiness Hypothesis.)
Most professionals today are working well above this number with hundreds or thousands of Facebook fans, Twitter followers, and Linked In connections. Being aware that we're working beyond the number of connections that humans can reasonably support should keep us focused on building connections that can get us to different resources – rather than having six or more connections to the same information.
3: Build Weak Ties, Not Strong Ones
The Dunbar number actually refers to close social connections. That is the number that is fixed. Our connections through social media and our casual acquaintances don't directly count. The Dunbar number is derived from the amount of capacity the brain has for retaining and recalling facts about other people. So it's quite literally impossible for someone to maintain close social connections with a large number of people – so build the connections you can but realize that they won't be the closest.
4: Use Bridges, Not Familiar Faces
Despite the fact that we have automated operators that can answer and route calls through an organization, most organizations haven't fired their live operators. The reason is clear, live operators are better at connecting people when they don't know exactly where they need to go. They're great at translating the caller's language into the language of the organization. A similar thing happens with bridges. They are able to translate the question which due to lack of knowledge, is ill formed and push it along the way to someone else who can get the person closer to what they need.
Bridges have large numbers of connections which are typically very diverse. This large number of connections doesn't often provide the answer directly but rather moves things forward. For instance, I have a handyman who is a friend. If I need to find a plumber, someone to do flooring, or a roofer I call my friend. He's a bridge into a whole class of workers for home repair and improvement.
5: Swarm the Target; Do Not Go It Alone
Building credibility and trust with someone – so that they'll collaborate with you – can be challenging particularly for those folks who don't trust easily like those folks who are in power. When you're seeking to expand your network to influential people, leverage a variety of connections to help them realize that you should be trustworthy. (See my post Trust=>Vulnerability=>Intimacy for more on trust.)
6: Switch to Strong Ties; Do Not Rely on Weak Ones
Weak ties are enough to get you to someone to be able to start the collaboration process – however, if you're in a sustained collaboration you'll need to make some direct investments to strengthen your connection to someone for a time. The more distance between you and the other person geographically or experientially, the more effort you'll need to put into building a strong connection.
Collaboration may have defined the word collaboration differently than it's defined in many contexts but that definition didn't stop the content of the book from being relevant to those who define collaboration more traditionally. Whether you're trying to get a team to work together or collaboration across groups in an organization, there's a lot to learn from others – and from Collaboration.
Monday, April 14, 2014
Whether you're in Venice or Las Vegas – or both – 10,000+ people is a lot. The number is staggering, particularly when you walk into the keynote hall and can't see anything but a sea of chairs from wall to wall and wall to wall. The keynote stage seemed like it was in a different zip code than the back of the room. That might have been a good thing for one of the ad-hoc communities that sprung up around the conference who were trying to get their steps in to report their progress via FitBit.
The SharePoint community seems like one large community but at 10,000 people it's more like a collection of communities than a single group. With folks running, walking, doing fitness, and doing drinks, there weren't many places in the Venetian that you couldn't find a few people connected to SharePoint – and talking about the new things that Microsoft announced at the conference.
Saturday, April 12, 2014
Book Review, Professional
Running your own company is sometimes challenging – in truth most entrepreneurs would say that it's almost always challenging. In some ways I feel like the challenges of a small business are very different than the challenges of large organizations. Sometimes when I'm reading management books it's hard to translate the "big company" view into one that's more appropriate for a small organization. That struggle surfaced in my reading of The Four Disciplines of Execution – but in a slightly different way than one might expect.
Strategy or Execution
Most large organizations have some sort of a strategy planning cadence. They go for off-site meetings and come up with the plan for the organization over the next few years. Sometimes the focus is on the next year with only limited focus beyond that point. The idea is that the grand direction for the organization will be set by the best minds in the organization over the course of a few days.
Some of those strategy planning retreats – as they're often called – are very effective. They identify the clear rallying cry that the organization should follow to reach its mission. However, more often than not, the meetings end and there are still unanswered questions, unfinished conversations, and at least a little bit of fog over the goal. However, there's a need to wrap up the strategy setting process, and so a bow is put on the package – much like lipstick on a pig – and the strategy is proclaimed done.
But is the process of creating the strategy the hard part – or is that the easy part? Is it harder to put the strategy together or to execute it? In most cases it's much harder to execute a strategy than it is to set it. There are several reasons for this. Not the least of which is that there are different kinds of strategies. There are the 'stroke of the pen' strategies that are implemented by a signature on a contract. These are easy strategies. The other type of strategy requires behavioral change. The behavioral change strategies require people to understand what is expected of them and why they're making the change, and difficulty communicating the what and why becomes difficult to surmount.
4DX quotes a Bain and Company report that says "About 65 percent of initiatives required significant behavioral change on the part of front-line employees—something that managers often fail to consider or plan for in advance." They go on to quote other research that says that only 51 percent of employees could say they were passionate about the team's goal. That's pretty damning evidence that employees don't understand what the strategy means for them.
Inside of these two statistics are at least two problems that I've seen in countless organizations. First, most strategies are locked up behind closed doors and never spoken of. Second, most strategies aren't translated into tactics.
Behind Closed Doors
In my work as a consultant I get the opportunity to work with a wide variety of organizations and I'm always meeting new organizations. It never ceases to amaze me how some of the simplest and most direct questions are met with such surprise. I routinely ask clients what their strategic goals are and how their project with me (typically SharePoint) aligns to one of their strategic goals.
The surprising part is that most of the clients that I'm working with cannot even tell me what the organization's strategic goals are. I can't imagine how anyone can operate in an environment where they don't know what the end goal is. Imagine getting in your car and driving without knowing where you wanted to end up. You could just as easily be moving away from your goal as moving toward it.
Sometimes I'm told that they can't tell me what the strategic goals are because that's confidential or proprietary information. (Notwithstanding the fact that I have a non-disclosure clause in my standard contracts.) It seems that the strategy is so super-secret that it has to be guarded even from the people who are supposed to be executing it. It may seem crazy when stated like that, but many organizations aren't in the habit of shouting their strategies from the rooftops for all the employees to hear.
In some organizations the problem isn't that the strategy is unknown. The strategy is known – but how the strategy will be executed is missing. The "What" is clear, but the "How" isn't. If your organization has a strategy of delivering the best quality widgets to the health care industry that tells the person who is the receptionist in the front office almost nothing about how she can contribute to the strategic goal.
What's needed is a way to translate the big strategy into a set of actions that can be taken by every employee in the organization. That means translating the corporate strategy into strategies for each of the divisions and then tactics for each of the divisions to achieve those strategies. Those tactics get translated into goals and ultimately the goals get translated into actions and the actions get translated into tasks for individual employees.
In most organizations that I've worked with the process breaks down somewhere. There's not a clear link between what the individual contributors do and the strategy, because they don't feel like their role can impact the corporate strategy, and the tactics, goals, and activities, between their tasks and the strategy aren't aligned. Or somewhere along the way, there's not a transition from the broad-brush visionary language into specific language about what has to be accomplished and when.
By the time that we're talking about goals we should be talking about what specifically needs to be done and when. 4DX uses a simple "from X to Y by When" formula in the way that it talks about goals. This is a great simplification of SMART goals which I first wrote about in 2005 in an article for TechRepublic, "Use SMART goals to launch management by objectives plan." SMART is an acronym for:
- Specific – The goal must be more than just superlatives like "good", "better", or "best" – the goal should have a specific value associated with it.
- Measurable – The goal should be measurable given the tools you have. Saying that you want to improve customer satisfaction scores by 10% is specific but unless you have an instrument to measure satisfaction - like a survey – it wouldn't be measurable.
- Achievable – Setting a goal that can't be achieved is pointless. If you're currently penetrating 10% of the market with your service, how likely is it that you can penetrate 90% in the next six months?
- Realistic – Being realistic means that you don't assume everything will go right. If you need to close all four big deals to achieve the goal but your sales closure rate is about 50% it's not a realistic goal.
- Time-based – Everything has to be done sometime. Time-based means that there's a specific time for the goal to be met. In the context of strategic planning, it's often the interval that the planning is done on – like a year.
While I like the SMART acronym better than "from X to Y by when" that works too – coupled with the guidance that the goals must be set so that employees feel like it's possible to "win the game." Setting unrealistic or unachievable goals won't make employees feel like the game is winnable.
Once you have the specific goals, it's time to hold employees accountable for delivering on those goals – and unfortunately this is another area where organizations struggle.
The Power of Accountability
In the surveys that 4DX referenced, 81% of employees said that they weren't held accountable for regular progress on the organization's goals. 87% had no clear idea what they should be doing to achieve the goal. That's as frightening as the problems with communication. Even if your organization was great at communicating what needs to be done, there's no one minding the till. No one is being held accountable for driving the strategy forward. This isn't surprising given how conflict avoidant – or dare I say passive-aggressive - most organizations have become. In the name of being friendly, we've stopped holding people accountable.
Holding people accountable is uncomfortable. It's uncomfortable for the person who's being held accountable because inevitably they're going to miss a commitment and have to admit that they failed. It's uncomfortable for the manager because it leaves that negative emotion of the employee in the air and can create some level of guilt or embarrassment that feels awkward in a professional meeting. However, failing to hold people accountable leads to a continuous decline in performance.
When I've spoken of personal mastery (The Fifth Discipline), I've mentioned that personal mastery is doing something you don't want to do because it's the right thing to do – in spite of the momentary pain associated with doing it. The pain of holding someone accountable may be met with one of these excuses:
- It will fix itself – We all have a limited amount of energy that we can spend on things. Our time, attention, and emotional presence is expensive and sometimes you believe – or probably more accurately hope – that problems, like a lack of follow through on a commitment, will just fix itself. It's rarely the case that this is correct, but we keep hoping that it will be one day.
- It doesn't matter anyway – Sometimes we believe that even if we try to hold someone accountable it won't change anything. It won't change their behavior and it won't change the outcome.
- I don't want the fight – Sometimes the fight is something that we don't have the emotional energy for, other times we don't feel like we've got the relationship necessary to support a healthy resolution. In either case, we just don't want the fight that we perceive will be necessary to hold someone accountable.
- I wasn't clear enough – Some leaders question whether the commitment that was made was clear enough. Either because the person who was being asked to make the commitment didn't understand – or because the leader didn't understand what the team member was saying. So next time the leader will attempt to be clearer.
- They know how I feel – In another attempt to hope the problem away, we don't hold others accountable because we believe that they know how we feel and that they understand the problem of not meeting their commitments.
Clearly, there are other possible issues and excuses but the fact of the matter is that in many cases we don't hold people accountable to the most important commitments because it's hard. Sometimes, however, the problem is more difficult. That is, the problem is based on the fact that the commitment wasn't something that they could control – or even influence.
Pushing or Pulling (Lead and Lag Indicators)
When we make a commitment we're often asked to make a commitment for a result. We're asked to improve sales by a certain amount, or reduce costs by some other amount. These requests are partially in our control – but also they're a measure of the results. Measuring results is great – and ultimately what we have to do. However, results measurement happens after all of the work to drive the results are done. You can measure whether someone has met a sales quota, but not until the end of the period. As a result, it's too late to do anything about it. That's why results measurement is a lag measurement. The changes always lag from the behaviors that lead to the results. Most of the results we seek are lag measurements and that's OK – until you try to influence the results.
For instance, if you have a goal of losing weight you can step on the scale and see whether you have achieved your goal. Even if you measure your weight daily you're still measuring the result of the day's activity. Measuring your weight is a lag measurement. However, if you were to measure the number of calories you took in – through eating and drinking – and those you expended through exercise, you'd have a set of leading indicators. These indicators would allow you to predict whether you were going to lose weight or gain it. That's the power of a lead indicator. It's something that you can control that predicts the outcome that you want.
While lag indicators are generally pretty easy to figure out, leading indicators are generally harder to pick – and harder to track. However, in any program, when you're trying to execute a change, you need lead indicators to help you know how you're doing. However, sometimes finding leading indicators for the leading indicators you pick can be both necessary and problematic.
If We Knew What We Should Be Doing
For more than five years I've been selling the SharePoint Shepherd's Guide for End Users. The guidance there on how to do the most common tasks in SharePoint has been highly regarded by many people over the years. I've collected many great quotes about the Guide. And I've spent a great deal of time and money over the last five years trying to improve sales. I've been primarily focused on generating a larger number of leads – the number of people who are inquiring about the product. However, in the end analysis, all my work on the Shepherd's Guide marketing in the last five years as not appreciably changed the number of leads that I get in a year. Let me say that differently – none of the actions that I've taken have mattered.
This may seem like a fatalist view – that I'm not having an appreciable impact – however, that's not the intent. The intent is to say that I don't know how to change the number of leads that I get for the Shepherd's Guide. It doesn't appear to matter how often I speak at conferences or users groups. Nor does it appear that it matters whether I support users groups across the US. Not that I'm planning on changing these behaviors, but the point is that they don't appear to be making a difference in the number of inbound leads that I'm seeing.
The idea of a good lead measure is that it predicts desired outcomes – like sales – and that it can be influenced. Certainly I can accept that the number of leads I get will lead to sales – there's a reason they're called leads in the first place. However, based on the evidence I have, it's hard to believe that I can influence the number of leads that I get.
The principles – disciplines – in The Four Disciplines of Execution are relatively straight forward and, in fact, they're not that different from the article I wrote titled Create a Path to Reach Your Strategy nine years ago. However, as I've found over the years, sometimes you have to repeat the same message to have it heard. In The Checklist Manifesto, Atul Gawande said, "Discipline is hard—harder than trustworthiness and skill and perhaps even selflessness." This is the essence of the 4DX method – instilling the discipline to get things done. However, we should go through the disciplines in order – to put first things first, as Stephen Covey (in The Seven Habits of Highly Effective People) would say.
Discipline 1: Focus on the Wildly Important
If you could do just one thing, what would it be? That's at the heart of finding your wildly important goal. If you could only do one thing to improve your organization, what would it be? The truth is that we believe, culturally, that we can multitask. However, the evidence is strikingly in contrast to this notion. 4DX quotes professor Clifford Nass of Stanford University who says "Habitual multitaskers may be sacrificing performance on the primary task. They are suckers for irrelevancy." A more damning quote comes from Jordan Grafman of the National Institute of Neurological Disorders and Stroke in the USA. "Improving our ability to multitask actually hampers our ability to think deeply and creatively… the more you multitask… the less deliberative you become; the less you're able to think and reason out a problem."
If you're looking for a bright side, Clifford Nass admits, "The neural circuits devoted to scanning, skimming, and multitasking are expanding and strengthening," but he cautions, "while those used for reading and thinking deeply, with sustained concentration, are weakening or eroding." So even if we, as a human race, could become better at multitasking, it would have severe consequences in our ability to focus. Mihaly Csikszentmihalyi would be concerned since he demonstrates in his research and documents in Finding Flow, that the most productive time people have is when they're in "flow" and that requires uninterrupted focus on a task. So what happens when we're constantly interrupted – and we have no chance to get into flow? (This fundamental idea isn't new. You can also find coverage in Peopleware.)
The more that we can focus our energies on a single task – including finding a single (or a few) wildly important goals, the more aligned we are with how people think. With too many things going on, the interruptions become inevitable. So the first discipline is the discipline of focus.
4DX encourages you to focus on one Wildly Important Goal (WIG) and try to make just that happen.
Discipline 2: Act on Lead Measures
Knowing what you want to accomplish and knowing how you're going to accomplish it are two vastly different things. You may know that your goal is to increase the number of leads for a product, but influencing that number may be difficult – if not impossible – to do. That's where the power of finding the right lead measure comes in. Leads coming in are, in and of themselves, a lead measure for sales (assuming a stable conversion rate). A lead measure for generating inbound leads may be the number of quick reference cards I give out. However, it can equally be that the number of cards that I hand out has nothing to do with the number of leads I get.
Picking the right lead measure is arguably the hardest part of the 4DX system. Making progress on the right lead measures means that you'll make progress on your wildly important goal. But how do you ensure that you'll make progress on the lead measure? It starts with visibility.
Discipline 3: Keep a Compelling Scoreboard
4DX speaks frequently that people play differently when they're keeping score. There's a different level of intensity to the play. They're more serious and less jovial. Malcom Gladwell describes the impact of practice in Outliers, but is careful to point out that it's an intentional practice. It's possible to have intentional practice without keeping score – as might have happened with the Beatles (their take-home pay each night didn't materially change based on their performance) or Bill Gates (who was solving non-monetary problems with computers in high school before he started Microsoft.) However, for most people – who aren't outliers – keeping score makes a serious difference.
In order to keep score, you need a scoreboard – and not the kind of statistical spreadsheet that a baseball statistician keeps. You need the kind of simplistic view of the measure that is glanceable. Peter Morville, in Ambient Findability, speaks about how to create environments where the results are more likely. That is, everyone should know at a glance what the key measures are. Scorecards have become the rage in some business circles. In my world, I've realized that there are only two issues with business intelligence initiatives including the development of balanced scorecards. First, the data is missing or bad. Every organization struggles with bad data at some level. Second, businesses have no idea what to put on the scorecard. (See the problem above about choosing a lead measure.)
4DX discusses the need to automate scorecards and to distribute them so that they're visible. In some cases, that means capturing data that you're not used to capturing – such as the percentage of normal at which a machine is operating – and sometimes is means automating the display of the scorecards. In one of my manufacturing clients, they've installed large TVs with low powered PCs that constantly display a web page that changes with a set of statistics about how the machine is doing, how the operator is doing, how the shift is doing, and how the plant is doing. The rotation of these statistics means that there's some motion to attract the eye and the relatively low number of indicators means that the screens are glanceable. This is a perfect execution of creating and automating a scorecard.
If you're trying to build your score card, start with your lead measure and then make that measure instantly understandable – perhaps using some of the techniques from Infographics. However, just making a measure visible won't be enough. You'll also have to hold team members accountable as well.
Discipline 4: Create a Cadence of Accountability
Agile techniques, most notably Scrum, have a daily standup meeting. (See Agile Software Development) Why a standup meeting? The answer is simple. People don't tend to be long-winded when they have to stand up for the full meeting, so it keeps it short. What does a standup meeting do? It reports on progress, it makes a commitment for tomorrow, and it identifies issues. This is strikingly similar to the 4DX WIG meeting. Though WIG meetings are typically held once a week and daily standup meetings are – well, daily – they are structurally similar. In 4DX language, the words are Account (report on progress), Review the scoreboard (make a new commitment), and Plan (remove obstacles.)
The beauty of the model is that this meeting is focused not on doing the work but planning the work. No issues (of any significance) are resolved here. Any issues are deferred to outside of the meeting. This is intentional, as it helps to keep the focus on the accountability of the meeting – and keeps it short. Having worked on numerous software development teams that use agile development, the impact of an accountability meeting can be stunning. The peer pressure to do what you commit to reduces problems and the frequent reviews mean that, when there are problems, they're discovered early on. The teamwork of the group – the understanding that we're all going to succeed or fail together makes the collaboration and support of those struggling very quick and generally sufficient. People won't languish for days on a problem that someone else on the team knows how to solve.
It Didn't Work
Sometimes even with the right execution plan you won't see results. Sometimes the results won't come because of external factors – like a market change – sometimes those factors are internal – like you aren't really executing as well as you think – and sometimes you just bet on the wrong horse. We talked about lead indicators needing to be predictive and able to be influenced. If I pick the number of quick reference guides I give out as my lead measure – because I can influence it – but that doesn't generate more leads, then it's a bad measure, and a goal (of selling more licenses) that won't be met. It's not a matter of strategy or execution – it's a matter of both strategy and execution. If you get either of them wrong – and all of us will at times – you won't see the results that you want.
Getting To It
The Four Disciplines of Execution may not lay out some fancy 25 step process for execution or some complicated techniques for getting the results you want. It's just four understandable steps – on purpose. The authors knew that you have to make things make sense and they have to be simple if they're going to get executed. So pick up The Four Disciplines of Execution and get started on executing your strategy.
Monday, April 07, 2014
Management books from as long as I can remember have been talking about a phenomenon called "Not Invented Here" which is used to describe the resistance that people have to accept ideas that other people have come up with. Certainly this is an issue when trying to implement a new solution and get buy-in from a new group of people, however, it may just be that this resistance is less about general opposition and more about an unconscious awareness that has developed about how ideas are implemented – and that unconscious awareness might need to be made conscious in order to move forward.
Best for Whom?
The implication of trying to use an idea from someplace else is that it's a best practice – that when applied to our circumstances that it will yield the similarly impressive results as when it was done elsewhere. However, every set of circumstances are different. Apply a low calorie high-vitamin diet to someone who's already underweight and you're asking for trouble. Inviting people to comment on an idea for which there are already too many opinions will only serve to confuse the situation further.
On the other hand, it's entirely possible that although the practice isn't best for one person, it is best for the majority of folks. In the general case, a low calorie high-vitamin diet is a good thing. Similarly, getting comments from multiple people is generally good.
Assessing who the practice is best for is an essential part of deciding whether it's wise to accept an idea that wasn't invented here – or whether it's better to resist it because it won't work in this environment or with these people. Said differently, the trick is determining whether it applies to your situation – and whether you're controlling the essential attributes.
Essential and Accidental
When someone does a formal study, a great deal of care is taken to ensure that only one variable is changing at a time. The one controlled variable is supposed to be isolated so that it's possible to identify the impact of changing that one variable. However, getting to a single variable is very difficult when humans are involved, as is evidenced by the Hawthorne Effect. That is a study where they attempted to see if productivity was increased by improving lighting at the Hawthorne Works plant. Good news, when they increased lighting the productivity went up. Bad news, it also went up when they reduced the lighting. The uncontrolled variable was how workers would respond to being monitored.
When any new best practice comes out, it comes with the package of ideas and behaviors that are supposed to drive the results. However, sometimes behaviors and thinking that had no impact on results are copied – and all too often the important behavior and thinking aren't included with the best practice package because they weren't deemed to be essential.
Researchers often attempt to replicate other researchers' work as a way of validating it. They do this to ensure that the initial results were correct – but also to ensure that the experiment wasn't tainted by other factors which weren't a part of the study. However, best practices rarely get the kind of scientific rigor as an experiment. Often someone says that something worked for them and it suddenly becomes a best practice – even when the practice isn't correlated with the results at all.
If the practice is tested, the next step is to determine whether the entire package of behaviors and thinking are required for the result or if there are a few essential components of the practice that are responsible for the results – or most of the results. The challenge is that sometimes it's hard to identify the essential attributes of a best practice. A single practitioner may be able to implement the practice with great results – but no one else can get the same results. In cases where the essential attributes of the change can't be identified, it may be because the practitioner has tacit knowledge that cannot be captured in the best practice.
Experience has value and not all experiences can be neatly coded into boxes, a report, or even in a presentation. Gary Klein noted in Sources of Power that fire captains knew more about fires than they were aware of. Solutions didn't just come to them. Problems triggered pattern recognition which caused them to build mental models and ultimately propose solutions that matched their recognition-driven awareness of the problem – what Gary Klein would call a Recognition Primed Decision.
Lost Knowledge and The New Edge in Knowledge Management discuss at length how difficult it can be to codify tacit knowledge. There are so many ways to capture and code knowledge – but ultimately much of the contextual richness of the knowledge is lost and simply cannot be captured.
Sometimes the illusion is that the practice contains all of the knowledge necessary to be successful when in truth, there is tacit knowledge that has formed in the practitioner which can't be easily captured and conveyed. If you can't capture and convey the tacit knowledge that the practitioner has developed, there's little hope that the best practice contains enough useful information to be effective. In fact, even if there is a way to capture the tacit knowledge, the problem may be Wicked enough that it doesn't matter.
Everett Rogers exposed the issue of how difficult it is to predict the impact of an innovation in his book Diffusion of Innovations. The problem is that there are many systems that aren't visible to the casual observer. Well-meaning missionaries introduced the steel axe head to aborigine tribes with the disastrous results of seriously disrupting their societal norms. We built dams to control flooding and to produce energy only to realize that we had disrupted fish reproduction – particularly salmon.
What appears to be a simple change – like giving better hand tools to aborigine tribes can result in an enormous change. Without the knowledge of the fact that the elders owned all the stone axe heads and loaned them out to the younger men of the tribe, you would never expect such dramatic negative effects with providing steel axe heads. Even with this knowledge, you're unlikely to recognize the breadth of the problems that would be created – including an increase in prostitution.
Preventing flooding is a good thing. Humans lose their life and certainly their wealth through floods so flood control must surely be a good thing. Certainly when all of the factors are considered it can be a good adjustment. However, not realizing that some fish need to swim upstream to reproduce, the reduction of river volumes that results from building damns can create problems for the fish populations – and ultimately for the fishermen who rely on them for their living.
The problem with undiscovered systems – which lead to best practices not being best practices – is that they have an element of wickedness to them. Wicked in the way that Horst Rittel meant it when he used it to describe the problems of urban planning.
There's an old saying attributed to Heraclitus that a man never steps into the same river twice – he's not the same man and it's not the same river. Sometimes even if you've captured the tacit knowledge, have identified the essential attributes, and have a similar situation as the practice was originally proven in, you still can't get the same results – but that's because the environment that you're in is different. This is the heart of a wicked problem. Every time you attempt remediation, the problem changes, and as a result, there are a different set of actions needed to correct.
In my review of Dialogue Mapping, I discussed briefly what a Wicked problem is. I pickup the thread again in my review of The Heretic's Guide to Best Practices. One criteria for a Wicked problem is that there is no stopping rule. That is to say there is only "more good" and "less good" – there's never Complete or Done. However, as Horst Rittel defined it, it's broader than that. There's also no definitive formulation of a Wicked problem – you can't precisely define it. Wicked problems also don't have an enumerable set of solutions. Sometimes they're even the solution to another problem – so in this way, Wicked problems are an interlocking set of constraints – a system of systems that all interact. Systems thinking – and how you can cause unintended consequences was a key part of The Fifth Discipline.
Often best practices are entwined with people. From the manager to the worker and to every affected customer and vendor. People and the complex systems which operate inside the best practices frequently mean that the problems that best practices are designed to solve are Wicked – and therefore resistant to having a best practice at all. That's due in part to the fact that people have egos.
Everyone has an ego – and often ego gets a bad reputation. John Dixon says in Humilitas that "One of the failings of contemporary Western Culture is to confuse conviction with arrogance." In other words, we confuse people who are self-confident and convicted in what they believe as arrogant. The Advantage, Good to Great, Who, and other books all caution about the out of control ego. Books like Heroic Leadership, Personality Types: Using the Enneagram for Self Discovery, and How to Be an Adult in Relationships speak about the need to control and channel ego in a more productive way.
Books like Daring Greatly, Mindset, and The Happiness Hypothesis speak about self-confidence and self-image instead of using the negative word ego, but they're speaking of the same thing. They're speaking about our belief systems, and for most of us, we believe that we're better than average. That we're able to come up with our own solutions to our own problems – so we don't need it if we didn't come up with it. Our fragile ego doesn't like to have it pointed out to us that we're not really the ones that are the best at something.
Humilitas spends a great deal of time with studies, including those by Thomas Gilovich, where various groups of people believe collectively that they are better than they can possibly be. For instance, 70% of high school seniors who believed their leadership capabilities were above average. We've all got an ego and we, in general, tend to see ourselves slightly better than we actually are.
So, when we are confronted with an idea or best practice that we didn't come up with, we want to believe we can come up with something better. Perhaps we have been bitten by a previous best practice that didn't work out. A practice that wasn't tested or a practice that didn't address the wickedness of our situation. However, more likely, we're just indulging our ego by rejecting that someone else could have a better solution than we did. For most folks the mental model we have that we're smarter than other people isn't right.
Above, I mentioned Gary Klein's research with fire commanders, which was documented in Sources of Power, from the context of tacit knowledge – but that's just half the picture. The other half of the picture is that people make decisions based on what they recognize in the situation. It turns out that fire commanders – and folks in many other walks of life - learn slowly and silently about how situations unfold and build mental models on that learning. The models allow the fire commanders to simulate what the fire will do – hypothesize about its origin – and test different ways of solving them.
These mental models are powerful. Their utility was discussed in Thinking, Fast and Slow, Efficiency in Learning, Dialogue Mapping, and The Fifth Discipline. One of the points made in The Fifth Discipline is that often our espoused beliefs and our actual mental models are different. As it pertains to our ego – we will often say that we can learn from everyone. Intellectually, it makes sense that we can learn something from other people and that we should. However, how many of us – including myself – have stopped listening to someone because we disagreed with their views, heard them say something that we knew wasn't quite right, or we just didn't like.
The reason for covering the impact of our ego on "Not Invented Here" is so that we can make it conscious.
Unconscious Made Conscious
Mental models are powerful in their control of us – up to the point that they're made explicit. The more conscious that you make your mental models the more you can shape and change them into alignment with the way that you want to be. In the case of "Not Invented Here," a healthy skepticism to make sure that the idea is really the best thing for your situation. It's important to verify that the results are repeatable across scenarios – and across practitioners. We must be sure that it's the right answer and not just blindly accept something from somewhere else.
However it's equally important to ensure that the reason for resistance to an idea isn't related to our egos expecting that only we can come up with good ideas. Good luck sorting out which thing is stopping you – and your colleagues - from accepting ideas that were "Not Invented Here."
Saturday, March 29, 2014
Book Review, Professional
John Kotter's work on organizational change has been substantial and in reading Leading Change and The Heart of Change I became a fan of his work. Compared to those other works, the book Buy-In is a radical departure in approach. The first half of the book is a story (like Patrick Lencioni's The Five Dysfunctions of a Team). The second half of the book are 24 objections that can be raised against your idea – and what to do about it.
Meet the Cast of Characters
In the story portion of the book, Kotter introduces us to a cast of characters that we've all seen in our travels (my translation provided parenthetically):
- Pompus Meani (Pompous Meanie – Just plain mean)
- Avoidus Riski (Avoids Risk – Doesn't want to do anything risky)
- Allis Welli (All is Well – We don't need change, everything is good)
- Divertus Attenti (Diverts attention – Pay attention to something else)
- Heidi Agenda (Hidden Agenda – Wants something but won't share what)
- Spaci Cadetus (Space Cadet – Just doesn't get it)
- Lookus Smarti (Look Smart – Wants to appear smarter than everyone else in the room)
- Bendi Windi (Bends with the wind – Will move to whatever position seems to be gaining the most strength)
The cast of characters makes it easy to identify what's going on in the story where in real life it's often hard to predict what role a person will chose to play for a given situation. Learning to read the situation and know the people so you can predict what's going to happen is a part of being effective at keeping your ideas from being shot down.
Lessons Learned from Comedy and Presenting
As I was reading the story component of the book I was making notes about how the responses matched what I have learned from either comedy or presenting. As I've mentioned in my blog post "I am comedian", I took a set of courses on standup and improvisation comedy to learn to become a better presenter. The upshot is that some of what I've learned about crowd work from that – and from just being a presenter – stood out as I was reading the story. Here are some of the ideas that were indirectly exposed through the story.
Getting the Audience on Your Side
Dealing with objections in a public setting isn't that much different from being heckled on stage as a comedian or from having someone try to disrupt your presentation. In both cases, the audience has a choice to make. They're going to need to either side with the disrupter – or they need to side with you. The good news in this is that there's a power imbalance that works in your favor. As long as you're respectful, the audience will usually side with the comedian or presenter. That's what they want to do, because it assures them of their sense of power that the person in the front of the room should be the one that's right.
The quickest and most sure-fire way to solidify the audience on your side is to defend them. If you're a comedian, you can say that they're disrupting the experience for the rest of the audience. In a presentation, you can simply say that you want to respect the other people's time and that you're happy to deal with the objections later.
Get the Audience Agreeing
Sometimes the decision on whether the audience will side with you or the disrupter is too close to call, so it's time to pull out an old sales trick. That is to get the audience saying yes – either in their heads or audibly. When an audience is saying yes, they're agreeing with you. After they're agreeing with you for a while, their detailed processing (what Thinking, Fast and Slow would call System 2) stops evaluating things and settles back into the default processing – which is that you're the expert because you're in the front of the room.
However, sometimes even this isn't enough. Sometimes you have to substantively change the frame of the discussion.
Appeal to Values
Each of us has things that we value. (Who Am I? discusses 16 values that we all have in varying degrees.) Sometimes it's necessary to remind people what their values are. If you're arguing for a new process or tool that will make more work for the nurses, it would be understandable that the nurses would resist the additional burden. However, when you reframe the problem to what is best for the patient and appeal to the nurses' value that helping the patient get well is the most important thing, you can sometimes melt away resistance.
While we're all concerned about our own lives and our own selfish interests – we also like to believe that we're selfless, compassionate people as well. Appealing to the higher values or purpose can often help folks step outside of themselves.
Put them in Your Shoes
While they're stepping outside of themselves, they might as well step into your shoes for a moment. Sometimes arguments may not intentionally become personal attacks but they can feel that way. In some cases it's our own personal thinking that is to blame, and a normal person wouldn't perceive the argument as an attack – but not always. If the argument could be reasonably perceived as an attack, it's sometimes effective to reflect the argument back. "How would you feel if I said that about you?" When combined with the idea of values, you can even suggest that an honorable person supports or has reviewed the proposal and surely they're not imputing that honorable person's character.
Find the Principle Behind the Practice
Sometimes the actual topic of discussion isn't the real principle in play. Often there's an argument that by changing, we'll be betraying the core values that the organization believes in. However, if the core value that is stated is providing books for community use, the value may be too narrowly defined. At one level, it's true that libraries were designed to provide access to books to the public. However, at another level, the purpose of the library is to allow those who want to enrich their lives through reading to be able to do so. The shift is that the definition no longer includes books.
This shift broadened the value and more closely reaches the core principle. The principle is that knowledge is power and we want to allow everyone who is interested to reach their potential through knowledge. The delivery of books is just one way that this is done. With this larger framing of the core principle, it makes sense to offer computer access inside of the context of a library. After all, there's more reading available on the Internet than a traditional library.
However, sometimes when broadening the conversation, reframing, and reaching down to find the principle, people can get the wrong perception.
Owning the Misperception
Communications is fraught with problems. We don't understand what words mean – or even when we do our definitions don't match the definitions of others. Misperceptions are a natural and expected part of communications. One good way to disarm someone is to own the misperception. Apologize for the misperception and clarify what you did – and didn't – mean. This frequently disarms the person who is being disruptive and helps them to realize that there was no intent to malign them or the group that they're interested in protecting.
It is Not Personal
No matter how much the idea has been shot at. No matter how much the argument seems to be wearing on. You have to remember that a disagreement about a topic isn't a personal attack on you – or the people raising the issues. It's simply a disagreement. The more that you can remind folks that it's not about personalities, it's about the topic – or the values underlying the topic – the better off things will go.
Five Guidelines for Responding
Kotter offers up five guidelines for responding when your idea is being challenged.
- Don't be afraid of distracters. Handled correctly, they can actually help you!
- Always respond in ways that are simple, straightforward, and honest.
- Show respect for everyone.
- Watch the audience (not just the people shooting at you).
- Anticipate and prepare for attacks in advance.
With the background of knowing how to respond, here are the 24 archetypes for objections that you'll get to an idea.
- "We've been successful, so why change?!"
- "Money (or some other problem a proposal does not address) is the only real issue."
- "You exaggerate the problem."
- "You're implying that we've been failing!"
- "What's the hidden agenda here?"
- "What about this, and that, and this, and that . . . ?"
- "Your proposal goes too far/doesn't go far enough."
- "You have a chicken-and-egg problem."
- "Sounds like [something most people dislike] to me!"
- "You're abandoning our core values."
- "It's too simplistic to work."
- "No one else does this!"
- "You can't have it both ways!"
- "Aha! You can't deny this!" ("This" being a worrisome thing that the proposers know nothing about and the attackers keep secret until just the right moment.)
- "To generate this many questions and concerns, the idea has to be flawed."
- "We tried it before—didn't work."
- "It's too difficult to understand."
- "Good idea, but this is not the right time."
- "It's just too much work to do this."
- "It won't work here; we're different!"
- "It puts us on a slippery slope."
- "We can't afford this."
- "You'll never convince enough people."
- "We're simply not equipped to do this."
Rather than reproduce the responses to each of these objections, I'll point you to the web site for the book at www.kotterinternational.com/buyin which has the summaries.
Wrapping the Argument Up
Buy-In is a different approach than Kotter's other books – however, it's an effective one. It's great focus on one of the topics that few of us get a chance to focus on. Learning how to respectfully deal with disagreements and folks who are trying to prevent your idea from moving forward is helpful to all of us, whether you're a student, an academic, a manager, or a consultant.
Saturday, March 22, 2014
Book Review, Professional
As I mentioned in my review of Dialogue Mapping, my friend Paul Culmsee and I met many years ago and continue to speak despite the 12 hour time difference between us. Last year Paul and Kailash Awati (whom I've never had the pleasure of meeting) coauthored The Heretics Guide to Best Practices. I've had it on my list of books to read since before it was published. (I received a few drafts from Paul along the way.)
In our conversations, I have learned that Paul's a brilliant and irreverent consultant. He – like I – will knock over the chairs in the room if that's what's required to move things forward. He's had more experience with best practice models – ITIL, PRINCE2, etc. – than I have but through our conversations I know he's mapped the edges of where they're valuable. So I knew the book about where frameworks, methodologies and standards are good – and bad – would be a good one.
Why be a Heretic?
First, we have to agree that it is heresy to say that doing best practices is not a best practice. The operating assumption in most environments is that a best practice is the thing to do. When we duplicate the conditions where the practice was used successfully, we can get the desired results. However, in my experience with healthcare and IT, what's written in the best practices is rarely enough, and sometimes misses the point entirely.
Scientific studies are tested at different places by different teams to see if they can replicate the results of a study. This is a part of the process and it ensures that the process is reproducible and that the characteristics of the environment described by the discovery team are sufficient to replicate the result. However, best practices rarely get the kind of rigor that a scientific study gets. Often times once something seems successful at one or two organizations it's assumed to be a best practice. This is particularly true of management consultants and leaders who want to instill practices they've used successfully in the past but is also true of larger methodologies.
One of the discussions in the book is about the Project Management Institute (PMI) and the Project Management Body of Knowledge (PMBOK). Kailash is a certified Project Management Professional (PMP). The book stops short of saying that the PMBOK doesn't ensure project success – and neither does having a PMP. However, there is an absolute awareness shared that sometimes the stated goals of project management to deliver projects on time, in budget, with an acceptable level of risk isn't all that's at stake.
With IT project success rates hovering below 50% based on a wide variety of sources, it's clear that the creation of the PMI, the PMBOK, and the PMP certification hasn't eliminated the problems with delivering IT projects successfully. Of course the argument will be that the PMP certified practitioners aren't running those projects. With just shy of 600,000 professionals who have a PMP, I personally find it hard to believe that they're not involved with at least some of the projects that are failing.
However, the real issue may be in how we define success. Some of the failures in IT projects were about how the end solution didn't match – or appear to match – the problem. As a result the project was technically successful in that it was implemented but practically a failure because it didn't solve the problem the project was created to solve.
The Sydney Opera House, one of the worlds' most noticeable landmarks, was ten years late, over budget by more than fourteen times, and reportedly the primary architect has never been inside it. By the PMI definition of project management, it's a failure. However, opera attendees and the world at large seem to disagree.
The Heretic's Guide is about looking beyond the success or failure of an individual best practice to see whether the practice is really "best" but also to understand the criteria beyond the traditional thinking.
Network of Commitments
Years ago – well before I met Paul – I was introduced to the work of Fernando Flores, specifically Understanding Computers and Cognition. One of the points made there was that an organization is a network of commitments. The ability for an organization to keep its commitments to itself and others is essential to its survival.
I've seen numerous echoes of the problem with commitments showing up over time. I mentioned what I call commitment cancer in my post called "Running Users Groups." Having individuals be accountable to one another through their network of commitments is essential to collaboration. It's a part of trust as I described in several places including in my post "Trust=>Vulnerability=>Intimacy." Trust is earned through a decision to make your interactions Win/Win instead of Win/Lose.
Win/Lose or Win/Win
In The Seven Habits of Highly Effective People, Steven Covey introduced the idea of a shift in attitude from "I win, you lose" to "I win, and we all win." This has surfaced a few times including in The Science of Trust where it discusses the Nash Equilibrium (Win/Win) vs. von Neumann-Morgenstern (Win/Lose) from a game theory perspective. In Heroic Leadership there are glimpses of the idea of an ecosystem where all of the organisms are interdependent. (There are several other ties to the concepts in Heroic Leadership that we'll explore shortly.)
One point of view is that you should shrewdly negotiate deals to your maximum advantage. This is the von Neumann-Morgenstern (Win/Lose) point of view. The other point of view is that you need to ensure that your partner(s) in the deal are able to have some win, so you negotiate the best place for all of you – the Nash Equilibrium (Win/Win).
Win/Win leads to better overall outcomes – even if not to one individual organization (or person)'s sole benefit. It's the heart of collaboration. A collaborative environment which is more productive than one where each individual team member, organization, or person looks out only for their own best interests. However, many organizations attempt to layer a Win/Win facade on top of a structure that is fundamentally Win/Lose. Competitive environments are not necessarily bad. They can, in fact, be highly motivating – however, the do make it hard to collaborate.
The key with creating effective competitive environments is to make sure that the competition is externally focused. In the context of an organization, the competition should be against competitors in the market. You shouldn't be pitting one person against another or one group against another. In the context of collaboration outside of the organization, you shouldn't be competing with the folks that you're trying to collaborate with.
One of the keys to collaborating with one another – with alliancing – is that the fates of the various parties are intertwined. That is "All for one and one for all." Or as Aesop first said it, "United we stand, divided we fall." The nature of having our success intertwined is important because it gives us the shared sense of success. It's not just that win/win is an option – it's required. This fundamental shift in thinking, that we have to succeed as a team, creates a different atmosphere and a different kind of working together. While in some sense organisms in an ecosystem still compete – there's a sense of coopetition. That is, there are places where we are forced to complete, but fundamentally, we're looking to cooperate to make everyone healthier.
Some might say that this is an impossible ideal or idealistic. However, I've spent years working with others to cultivate this point of view in Indianapolis, as the consulting companies all come together to support the community, and yet we sometimes find ourselves bidding on the same work. It absolutely does work, but it takes a personal strength – and alignment to the goal that everyone should end up better off – just like the kind of organizational-personal alignment that needs to happen in organizations.
Many years ago I was working special projects for the CEO of a manufacturing company. During that time I remember him telling me that he was like a big gear at the center of the organization. If he turned even a little all the little gears in the periphery of the organization would end up spinning very, very fast. The Heretic's Guide uses the metaphor of individual marble maze boards on a much larger framework of a tilting frame which is the organization. The idea is that when the organization makes a shift all of the individual boards are effected and they have to adjust as well.
This reminded me of two things. First, some organizational work from years ago about organizational contribution. Second, about how lining up personal and organizational goals could be valuable.
In the organizational contribution model I'm considering, how folks contribute to an organization aligns along two dimensions. First, there's the dimension of their interest. We all have interests that drive us and some of our work aligns with those interests. The second dimension is the dimension of ability. I may be very interested in electronic circuit design but that doesn't mean that I'll be good at it.
Looking at the four quadrants, if I'm low on interest and ability I'm going to be disinterested and dysfunctional – a model of an employee that should be terminated. If my interest is there but my ability isn't, I'll be interested but dysfunctional. The good news is that folks here tend to improve their ability. Because you're interested, you'll learn and generate better abilities. (See Outliers) That leads us to the category of an interested achiever. Inevitably though, your interests will shift and lead you into the quadrant of the disinterested achiever. In this quadrant you're still effective at delivering solutions but because it's not aligned with your interests you'll get burned out and will disengage from the organization.
I was thinking about how this cycle plays out if the organization's interests are shifting as well as the personal interests. The organizational interests changing will tend to pull down the ability as employees are shifted out of their comfort zones. It can be that these changes will transition people into an area of disinterest and dysfunction – making a change necessary. Realizing that with change comes growth so the organizations changes means that individuals will need to grow as well.
Personal Goals Alignment
In another life, I had a friend who wanted to be the best public speaker possible. He wanted to get the top speaker scores at every conference. Some would say that he was obsessed with getting the top scores. He painstakingly rehearsed, he added comedy and "crowd work." A short time later he was clearly the best speaker in the market. The good news was that he was the co-owner of an organization that needed an evangelist, someone who would be good at engaging people to buy their product. His personal goal to become the best speaker was completely aligned with the organizational goals to become better known in the market place.
After he reached the top of his game his interests shifted – creating a misalignment with the organization. In effect, he had moved from an interested achiever to a disinterested achiever – and while that works for a while it isn't sustainable.
When an organization and an individual's goals are aligned it's amazing how much can be accomplished. Sometimes the alignment can be simply in principles and not necessarily in skills.
Behind much of the Heretic's Guide is a visibility to the principles that are behind the processes and programs. The same sentiment is expressed in Heroic Leadership where it describes what made the Jesuits successful over the long term wasn't a set of prescriptive methods of doing business. It was a set of principles that led to the right point of view. The four principles from Heroic Leadership are:
While these are more personal and lofty concepts than those shared in the Heretic's Guide – they represent the same fundamental view of problems that are espoused in the Heretic's Guide. It's the difference between the ways an apprentice sees the problem compared to a master. I wrote about the learning curve we experience from apprentice through journeyman to master. I revisit the concept again in my review of The Art of Explanation. The methodologies are great when the principles line up, but they don't work so well when the problem exposes its wickedness.
What It Means to Be Wicked
Given my recent review of Dialogue Mapping, I won't spend a great deal of time reviewing the meaning of wicked problems or why so many of the problems we encounter have wickedness in them. The Heretic's Guide covers both wicked problems and the dialogue mapping technique using IBIS that Conklin discusses in Dialogue Mapping. Having known Paul for so long and having discussed it with him so many times, I find it hard to say which discussion of dialogue mapping is a better place to start – so I'll just recommend that if you're serious about dialogue mapping and wicked problems that you read both – they have obviously similar points of view, but there's a different type of richness in each explanation.
Where Heretic's Guide goes beyond Dialogue Mapping is in discussing other Problem Structuring Methods (PSMs).
Structuring the Problem
It seems like everyone is looking for a way to structure problems so that they're easier for everyone to understand. Shared understanding of a problem is one of the key issues with wicked problems, so it's natural that it's an area where folks are struggling to find an answer. One of the quotes from Heretic's Guide is "The good thing about standards is that there are so many to choose from." That is certainly the case when it comes to problem structuring methods. Paul and Kailash reviewed numerous problems structuring methods:
- Soft Systems Methodology
- Breakthrough Thinking
- Polarity Management
- Dialogue Mapping
- Back of a Napkin
- Journey Making
- Strategic Choice Approach
- Robustness Analysis
- Drama Theory
Of these, there are details on the strengths and weaknesses of each approach for Soft Systems Methodology (SSM), Breakthrough Thinking, Polarity Management, and obviously Dialogue Mapping.
Because there are some good insights for how to think about wicked problems and facilitating understanding, I'll summarize the Heretic's Guide's coverage of SSM, Breakthrough Thinking, and Polarity Management.
Soft Systems Methodology (SSM)
Soft Systems Methodology is the oldest PSM but has been criticized for its relative lack of specificity. It's described as a loose framework. However, there are some specific views for conceptual modeling including CATWOE:
Customers. Who is on the receiving end of this transformation? How will they react to what you are proposing? Who are the winners and losers?
Actors. Who will be carrying out this activity?
Transformation. What are the inputs? What are the outputs? What is the process for transforming inputs into outputs?
World View. What view of the world makes this definition meaningful? What is the bigger picture into which the situation fits?
Owner. Who is the real owner of the process or situation?
Environmental constraints. What are the broader constraints that act on the situation and this definition?
Certainly there's a great name in the PSM Breakthrough Thinking. It's got marketing zing. It's described as a way to avoid "analysis-first" and "technology traps". Breakthrough Thinking doesn't believe that more data necessarily means more insight. Additionally, Breakthrough Thinking doesn't believe that people resist change – the methodology believes that people resist change they don't understand or that they believe is threatening to their wellbeing.
Breakthrough Thinking also believes in institutionalizing continual feedback because that is essential to understanding problems – which is consistent with the way that wicked problems are defined.
Polarity Management believes that wicked problems should be considered as poles to manage rather than problems to be solved. I tend to think of this as continuum and things are on that continuum. The idea in polarity management is that problems tend to oscillate between the poles.
Here are the key steps for problem solving in polarity management:
Battling the Flavor of the Week
If you're tired of battling the "flavor of the week" management philosophy or framework. If you're ready to look past the checklist and standardized process to figure out how to make your organization or situation better, read The Heretic's Guide to Best Practices to see how you can survive.
Monday, March 17, 2014
Book Review, Professional
In my work on knowledge management it's become all too clear that labor costs are the costs that dominate most organizations' budgets. Unless you're in a particularly material cost intensive industry – such as manufacturing – most of your cost in an organization is labor cost. That drives the need to improve efficiency through knowledge management and training techniques – however, there's a part of the equation which starts much earlier than how you retain the knowledge that you have – it starts with hiring the right people in the first place. That's what Who: The A Method for Hiring is all about. It's about selecting the right people to be a part of the team. The heart of this is a method created by Geoff Smart's father, Brad Smart and is described in more detail in the book Topgrading: The Proven Hiring and Promoting Method that Turbocharges Company Performance.
The "A" method for hiring is all about hiring "A" players. That is those employees that are going to help drive your business. It is in the context of a grading system, like a typical school. The "A" players are best followed by "B" players, etc. The assertion is that if you hire only "A" players then you'll drive the organization forward – Who teaches you how to find and employ "A" players and separate them from the "B" and "C" players that most organizations will admit that they have on their team in at least some places.
I picked up the book because it was referenced in The Checklist Manifesto In connection with how people made their decisions. I knew Who was about hiring – and I have some hiring to do. In reading it, I learned more about how I'd been doing hiring wrong – and where I had seen it done right.
The Technical Interview
When I was working for Crowe Horwath (it was Crowe Chizek at the time), I was part of the team that was hiring new consultants. We had the hiring process down to a well-oiled machine. I would, along with a few others, review resumes, do phone screen interviews, and participate in a face-to-face interview set. Human resources would send a relatively steady flow of resumes and they would be sorted into a not interested and phone screen "piles." The phone screen candidates would get a time scheduled for a 30 minute conversation. They were generally pretty quick and ultimately we screened out about 95% of the people we spoke to simply based on a lack of technical skills. I can remember going through some interviews wishing that I could make the half hour go by faster. But our screening rate was pretty good.
If they passed the technical screen they would be brought in and we'd ask them a set of standard questions. We'd coach them to be specific if they were speaking in generalities. Ultimately after a few of us would interview the candidate we'd huddle back together and put folks into a yes, no, and maybe pile. The maybe pile was really only a temporary holding spot, we moved them either to yes or no very quickly.
The process was very structured and very good. However, it felt pretty time consuming. It also felt like it was built on the need for highly technical positions. I didn't think about using the process – or a similar one – when I started hiring for myself. Over the last several years I've hired and fired more than a few people. Sometimes my bleeding heart wanted to help someone in trouble. Other times, I didn't understand what I was asking from folks. All the time I felt like I'm lousy at hiring people – but it was something I had to do in order to grow the business. What I learned from Who is that the same discipline we applied to technical candidates should be applied to every candidate from the CEO of a Fortune 100, multi-national corporation to the receptionist being hired to welcome guests in the corporate office. I also learned that there are ten different types of interviewers.
Ten Different Interviewing Styles
Who calls out ten different styles of interviewing that the authors have seen in their practice. They are:
- The Art Critic – Gut instincts and the belief that he or she can read people guide the Art Critic to deciding whether they think that a candidate is good.
- The Sponge – Believing in the wisdom of crowds – on really small sample sizes – the Sponge tries to get everyone to interview the candidate instead of them doing the job themselves.
- The Prosecutor – Acting like a first year drama student the interviewer attempts the kind of interrogation seen on TV cop shows.
- The Suitor – So preoccupied with whether the candidate will like them or not, they spend all their time speaking about how wonderful the company is that they forget to ask the candidate about themselves.
- The Trickster – Using logic tests and quirky questions the trickster believes that anyone who can make it through their gauntlet of questions relatively unscathed must be OK.
- The Animal Lover – Steadfastly refusing to let go of favorite questions, these interviewers like to ask questions that they themselves believe are illustrative of the candidate.
- The Chatterbox – This interviewer loves to hear himself (or herself) talk so much they forget to ask the candidate the right questions and dig for the right responses.
- The Psychological/Personality Tester – With the weapon of testing by his side, the Psychological/Personality tester seeks to be able to hire based on their DISC profile, Meyers-Briggs Personality Type Indicator, or some other test. The problem is that these tests weren't designed for this and this still tells you relatively little about the person's capabilities.
- The Aptitude Tester – This interviewer seeks to determine a person's aptitude for a specific position. The trick is in measuring the right aptitudes for the right roles.
- The Fortune-Teller – Like the preverbal ground hog on ground hog's day, the fortune teller likes to ask the candidate about how they see the future with them in it.
None of the interviewing styles are perceived to be particularly effective. Instead a structured approach with layers of interviews is recommended.
The process laid out for successful hiring has four key steps. They are:
- Scorecard – The record of what you want in a candidate.
- Source – How you're going to get a steady stream of candidates into the system.
- Select – The heart of the system is the set of interviews that the candidate must go through and the process the interviewers should follow.
- Sell – Once the candidate has been located, selling the candidate on the company so that they'll take the offer that is provided to them. After all, you've got a substantial investment in interviewing the candidate, you want to make sure that they accept what you're offering.
Let's look at each one of the steps in turn.
While most folks are familiar with creating a job description, few people have created a scorecard for a job that they've not hired someone for yet. If scorecards are used (and according to Who, that's not frequently), they're usually developed after someone has been hired. As a result, the idea of creating a scorecard can be a radical departure from how things have been done in the past. The scorecard is, however, not complicated. It contains just three major sections:
- The Mission – The summary statement of the job's core purpose.
- The Outcomes – The specific, measurable, outcomes that the role must achieve.
- The Competencies – What a successful person in this position must be able to do.
One of the interesting biases that the scorecard is supposed to address is the tendency to hire someone with a wider range of – necessarily shallower – skills. By focusing on the specific competencies required for the position you can eliminate the desire to find someone who can do everything – but not do it extremely well. I'll say that this is an area where I see the focus of Who clearly. Who was written for larger organizations. There's even an admission in the book about having not hired a nanny with the process (with poor results.) While most of what is written is solid on both ends of the scale – sometimes it's hard to realize that small businesses require a greater degree of flexibility in employees. So the idea that you should hire for specialties is somewhat counter intuitive.
I'd refine the statement for smaller businesses to say that you have to get sufficient depth in the specialty that you're hiring for – while having a broader set of skills to make it easier to adapt to changing market and organizational needs.
Who also speaks of a set of critical competencies for "A" players: (The descriptions are direct quotes)
- Efficiency. Able to produce significant output with minimal wasted effort.
- Honesty/integrity. Does not cut corners ethically. Earns trust and maintains confidences. Does what is right, not just what is politically expedient. Speaks plainly and truthfully.
- Organization and planning. Plans, organizes, schedules, and budgets in an efficient, productive manner. Focuses on key priorities.
- Aggressiveness. Moves quickly and takes a forceful stand without being overly abrasive.
- Follow-through on commitments. Lives up to verbal and written agreements, regardless of personal cost.
- Intelligence. Learns quickly. Demonstrates ability to quickly and proficiently understand and absorb new information.
- Analytical skills. Able to structure and process qualitative or quantitative data and draw insightful conclusions from it. Exhibits a probing mind and achieves penetrating insights.
- Attention to detail. Does not let important details slip through the cracks or derail a project.
- Persistence. Demonstrates tenacity and willingness to go the distance to get something done.
- Proactivity. Acts without being told what to do. Brings new ideas to the company.
There are several different CEOs quoted, each with a slightly differing views on what makes a top performer. For instance, Bill Johnson – The CEO of Heinz, had five characteristics:
- Chemistry – Does the person fit with the rest of the team?
- Commitment – Are you committed to making it work for them and are they committed to making it work with you?
- Coachable – Are they able to be coached into more effective behaviors?
- Ego Control – Do they have their ego under control?
- Intelligence – Do they have the requisite intelligence? (This might be stated as aptitude as well.)
This reminded me of Bill Hybel's thinking in Courageous Leadership. (Which I've still not fully read.) Bill believed that a candidate needed to have:
- Competency – The ability to get the job done.
- Character – A strong sense of who they are and who they want to become.
- Chemistry – A strong fit with the team.
No matter how you define the scorecard for the position and how you frame the right answer for your organization, the next step is building a sourcing system that works.
It used to be that you would place an ad in the newspaper for a position and a few days later you would watch for the avalanche of resumes from job seekers. My friends in HR used to hate this process because they knew that they would have hundreds of resumes to sift through. They might get two hundred applicants, of which, maybe twenty were even worth forwarding to the hiring manager. Of that, the hiring manager might interview two or three. Today the process isn't all that different. We post jobs on automated job boards which then force people to provide their information into a database for us and we use tools to keyword search to sift and sort through resumes. If they don't have the requisite degree they're out. If they have the requested certifications they're in the pile to be reviewed by the hiring manager.
In the end, the process of advertising to the general public to find someone is an approach of last resort. With so much overhead in the filtering process and such a low success rate, it's no wonder that HR managers want to use this option last. Who says that 77 percent of industry leaders cited referrals as their top recruiting technique. They're not interested in delivering an avalanche of resumes – they're interested in delivering candidates that match the organization and the organization's needs.
Referrals can come from professional networks, from employees and their networks, or even from friends of the firm – those who like the organization. Of course, you can also hire recruiters to do some of the screening for you or researchers which can identify potential candidates – without interviewing or substantially filtering them.
The final way to source represents a fundamental shift in the way of thinking. That is that large organizations are always looking for good people. One way of thinking about it is a semi-active approach where there's continuous recruiting of top talent whether there's an open position or not. This creates a great network of people who can be tapped when an opening happens.
The Selection Process
Imagine for a moment that you go out on a blind date. Your friends have looked at you and another one of their friends and believe that you are a good match so they "set you up." (The fact that it's a setup should be a clue.) You meet the person for an hour and they seem OK so you set a wedding date and send out the invitations. As ludicrous as this sounds we do essentially this when we hire someone after a one-hour interview. Perhaps the stakes aren't as high, however, we don't know any more about a candidate after a one-hour interview than we know about someone after the first date. Steve Karr, the Chief Learning Officer at Goldman Sachs, said the common interview processes are "almost a random predictor" of job performance. Of course they are, how could you possibly know in an hour if someone is a good fit or not? That's why the "A" method is different. In the Select Phase, it layers four steps together to try to ensure a better understanding of the candidate.
The four interviews are:
- Top grading
The first three are with the candidate, the fourth is a set of interviews with the references provided by the candidate.
The purpose of the screening interview is to quickly get to the point of determining whether the candidate is worth going through the rest of the process with. Interviewing in this process is a fairly intensive process, with the Top grading and Focused interviews taking a full day's worth of time for the employer.For that reason, it's important to filter folks before they get to the next step.
It's recommended that screening be done via telephone – but it could also be done at a job fair or some other situation where the cultural norms and expectations set that the screening will last 30 minutes or less. The recommendation is that you ask four questions in the screening interview:
- What are you career goals? – Ideally the candidate will discuss goals that are aligned with the organizational direction – or opportunities that the organization can provide. Good candidates know where they're going and what they want.
- What are you really good at professionally? – This is generally easy as people love talking about their strengths. Talented people know what they're good at.
- What are you not good at or not interested in doing professionally? – This is more difficult as people don't like discussing their weaknesses or have been coached to couch their strengths as weaknesses. You have to pull these out of folks to understand their strengths and weaknesses to have a complete picture.
- Who were your last five bosses, and how will they each rate your performance on a 1-10 scale when we talk to them? - The key here is to ask how others would rate them and encourage them to be honest since you will be calling their bosses to ask.
My experience with a technical screening interview – which was similar in purpose to the screen interview in the Who method - was that less than 10% of the candidates would pass through this step.
Presuming that you believe the candidate is a reasonable match to the organization, you can schedule time to do the Top grading and Focused interviews. These are often scheduled together and can take most of the day. The Top grading interview on its own can take three hours. The Focused interviews will take a few hours – depending upon how many areas you need to get focused on.
The Top grading interview is a review of the candidate's career from the oldest relevant job up to the most current position. The process walks through a set of questions for each job that the candidate had:
The recommendation is that you do the Top grading interview with a colleague if you can, so that one of you can take notes while the other asks questions. It's easy for an interviewer to get overwhelmed by trying to take notes and keep the conversation moving. The more support the interviewer has the better the results will be.
As was stated above and should be obvious by now, the process can take a long time. Who says that CEO candidates can take five hours and even entry level positions can take 90 minutes. It's time to settle in and get comfortable before you start the process. The next step is shorter increments but can be just as lengthy. So Who offers a few tactics for keeping the interview flowing:
These techniques help you clearly understand a person's history and job circumstances – and the techniques keep them moving through the interview –but you still don't know how the candidate's competencies line up with the competencies of the job. That's the role of the Focused interview.
The scorecard for a position lists a set of core competencies that every candidate should have for the job. The Focused interviews – yes there can be one for each competency – are designed to provide a clear picture of how the candidate does – or doesn't have – a competency. The specifics of how to determine whether or not a candidate has a competency will vary, however, it's recommended that the interview include three components:
- Explanation by the interviewer about the scope of the interview
- The question, "What are your biggest accomplishments in this area during your career?"
- The question, "What are your insights into your biggest mistakes and lessons learned in this area?"
When I was interviewing developers, I'd ask a series of questions about how they would solve logic problems – related to the kinds of software development they were going to do. We assumed that we would be filling in some skills because that's the nature of learning, not everyone learns the same things. We wanted to know, however, if the person was comfortable with most of the concepts and if they were good at decomposing problems.
The limited structure of the Focused interviews is designed to ensure that every competency gets its own time for evaluation so that none of the core competencies for the position are overlooked.
By this point, you should have a good sense for how the candidate did in their various environments over their career as well as the competencies (skills). The next step is to calibrate the candidate's responses with what other people say about them.
For the most part, I assume that references are a formality. Having been on people's reference list very frequently, I realize that for every ten times that someone asks for permission to list me as a reference, I get called maybe once or twice. Clearly, most organizations ask for references, but very few actually follow up on them. However, the Who approach has you not only asking for references, but even asking candidates for specific references and for actions on those references.
The recommendation is for three past bosses, two peers or customers, and two subordinates – a total of seven references. Typically I've seen candidates provide three – upon request. Those references typically all cluster into one type. They're frequently all peers. In addition to the variety and number of references, the method also asks that candidates prepare the references that they'll be receiving a call. While it is common practice for people to ask permission to list you as a reference, it's not always done. By the candidate talking to the reference they often make the reference more open to discussing the candidate. For instance, in the US most employers are limited as to what they can say about an employee – even though, as the book notes, there are sometimes messages encoded in the limited set of responses. By the candidate requesting that the reference talk to you, the doors are opened up for the reference to say more.
The outline for the reference interview is:
Obviously, the goal is to understand how others' perceptions of the person match with that the person said in the interviews. The structure of some of the questions are chosen carefully to elicit the right response. For instance, when asking for areas of improvement "back then" you're encouraging the person to be honest about how they were without feeling bad about saying something negative about them today. (Even if the assumption is that people really don't change that much.)
Presuming that you like the reference checks, it's time to sell the candidate on the organization.
Selling the Candidate
It's impossible to get to this point in the process without offering some information about the organization to the candidate. However, that information may – or may not—be a complete picture of the organization. The goal of the final phase isn't just to get them an "offer letter" or even an "offer package." The goal is to make sure that they're as sold on you and your organization as you are on them.
There are five things that candidates look for in an organization. They are:
- Fit – Do they fit into the company's vision, needs, culture and direction?
- Family – Is the family onboard with the change? Will they find that the new organization is an extended family?
- Freedom – Will the candidate get the freedom they want? (See Drive and Who Am I? for how people are motivated)
- Fortune – Is the company financially stable and how will they be compensated for their efforts?
- Fun – We spend half or more of our waking lives working, it should be something that the candidate will enjoy.
The goal of the entire – intensive – process is to separate "A" player candidates from the rest of the pack. It would be an absolute shame if you got to this point and realized that you weren't able to get the candidate because they weren't sold on the organization.
Using the System
The results of using the system seem clear. There are fewer employees hired that aren't a good fit and then leave the organization. Those that do stay seem to perform better than a normative group. However, we'll often shortcut or bypass steps because we believe that our particular method of doing the process is better. As The E-Myth demonstrates, there are some things where systemization is important. The consistency and rigor in hiring people is key to organizational success. Who shows you how to do that. Try it and reap the rewards.
Sunday, March 09, 2014
This is another one of the posts that got pushed aside from a book review because the topic was thorny enough that it needed its own post. This post was largely sparked by The Fifth Discipline, but has its roots in other books as well. More importantly, team learning is at the heart of how every organization becomes better and more effective.
I've spent much of my life working on learning and teaching. I've always wanted to help folks understand the skills they need (See the Shepherd's Guide, for instance). I've tried to help folks think about problems differently (See the Psychology of SharePoint Adoption and Engagement). I've researched instructional design (See Efficiency in Learning). I've learned about how adults learn (See The Adult Learner). Learning how individual adults learn and how to teach them has been a passion of mine for a long time.
However, helping teams learn is something very different. It's more about team dynamics and trust than the skills of teaching (See Trust=>Vulnerability=>Intimacy). I've done my share of research and thinking in this area, too. There's a long list of books that talk about leadership of teams, innovation, and efficiency, for instance – Leading Change, The Heart of Change, The Seven Habits of Highly Effective People, Heroic Leadership, Good to Great, The Advantage, etc.
Individual learning is about pedagogy, andragogy, instructional design, and principles of learning and teaching which have long been studied. Certainly individual teaching can vary by topic and by the learner, however, the long history of training individuals in skills and knowledge has created a relative wealth of information about how to do the individual instruction well. The profession of instructional design has arisen because there are people who have focused on learning about learning. As with other professions there are good and bad instructional designers, however, the fact that there's a more-or-less established professional discipline is an indicator of the level of maturity in designing solutions for individual learners.
Learning individually is a different set of skills than team learning. There's a sense of emergence that comes with team learning that's like the way that fish school and birds form flocks. There's no single characteristic that identifies when a group of fish become a school or birds become a flock. Nor is there a central coordinating intelligence that defines that fish should school or when birds should flock. It just happens. This is very similar to the way that teams learn. In many cases, there's no one thing that triggers teams to learn.
There are certain conditions that are optimal for team learning. There are themes for how teams are able to become effective at learning as a unit. Some of those themes are:
- Trust – Trust is the great lubricator in teams and is also a prerequisite for vulnerability (as I explained in Trust=>Vulnerability=>Intimacy). Trust may seem like a strange theme until you realize that it's important to be vulnerable in order to learn.
- Emotional Intelligence – Certainly teams learn about what it is to do the technical tasks of their work, but more importantly they learn how to work together. It is not working together in the sense of the mechanics but rather from the point of view of the sensitivities of one another that must be considered for everyone to effectively contribute. (See Emotional Intelligence.)
- Identity – Good teams learn to connect their personal identity with the identity of the team. The more that people are able to form a shared identity with the group the less internal fighting and positioning will happen – and therefore the team will be more effective and will learn more.
In the discussion of learning themes above, there was the inevitable slip into a discussion about how teams learning is measured. The desired outcome of team learning is that the team will be more effective. As a result team performance is a rather obvious measure of how a team is learning. That is, the team that is performing better is probably learning better, or so the thinking goes. However, how do you determine which one is doing better?
One can compare the results of two teams and decide which one is doing better. Although that isn't as simple as it would seem – except for two very important challenges.
First, no two teams are solving the same issue with the same resources so getting a calibrated comparison is difficult. The teams have different people, with different experience and skills, thus different resources. Without a control group, it is hard to tell what the normal performance would be – so it's hard to measure how well the team performed compared to normal.
The second challenge is that success on a single project is a short term metric and teams are most frequently together for several projects. That means that we need to sample their performance on enough projects that we're sure we're getting a representative sample of their work, not a one-time blip.
If we look at measuring a team's effectiveness for solving a particular problem, it can absolutely be that the team wasn't well aligned to solve that type of problem, or there was a mental block, or some other unforeseen barrier. Most organizations, while they desire teams to have excellent success every time, don't expect it. The expectation is that every person and every team will have projects that are challenging for them. The trick is, that measured across the long term, the team should be able to deliver reliable results on a wide variety of projects most of the time.
If your organization believes that every team should succeed every time, then perhaps the organization isn't challenging its teams to solve new and novel problems. No professional baseball player bats perfectly. No organization succeeds on every initiative. Failure is always an option – and is necessary for success.
If we look at long term measures, it's hard to take corrective action in the short term if your measures are long term measures. In fact, team learning is itself a long-term measure. You can't measure learning directly. You're measuring effectiveness through measuring specific results. That's three derivations away from where you started. You can't measure the rate of change of effectiveness – which is the rate at which the team is learning. In fact, you can't really measure effectiveness – although, you can measure the results that were achieved. Learning is the rate at which the effectiveness of the team is changing. Effectiveness is the rate at which there are successes in projects.
A Good Example
Years ago I read and reviewed The Wisdom of Crowds. It was a book about how crowds can be either very smart – or very stupid. One of the things I wrote about when I reviewed it (which wasn't in the book) was about the Skunk Works at Lockheed Martin. Kelly Johnson's team cranked out some of the most sophisticated and radical aircraft designs of his era. The important part of the Skunk Works was the way the team worked together. If the assembly team had trouble getting a part to work, the engineer and the machinist would meet on the floor, the engineer would "fabricate" a piece of cardboard and tell the machinist to make the part in the shape of the cardboard – and then return the cardboard shape to the engineer so he could draw it up later. That's a team that's working well.
There was no accusatory finger-pointing going on. Instead, everyone was lending their experience to the project and working towards the common goal, rather than remaining focused on who didn't do their job or who was to blame.
Kelley Johnson is arguably responsible for a very results-focused environment that didn't allow "the blame game" to be a valid option. Everyone knew what they were doing was intensely difficult, so there was no point in focusing on failures. Much of their work was considered impossible. Consider the SR71 Blackbird, the aircraft that could fly higher and faster than a missile fired at it. It's incredible to think that that aircraft could be created with the technology of that era.
Creating the right environment for team learning to flourish requires utilization of the themes that were discussed here, possessing the character to create the right environment, and implementing the techniques to keep the team together despite difficult circumstances. While it may be difficult to measure the ability for a team to learn, it's not impossible to do if you have leaders with the right passion and emotional intelligence of their own to be able to discern how to lead the team.
Sunday, March 09, 2014
Originally published on 8/21/2005
Most users of SharePoint Portal Server rapidly become enamored with the ability to add new fields (containing meta data) to documents in the document library. All of the sudden it becomes possible to associate information to a file beyond the file name that we've been limited to since the beginning of the computing era. However, few users have the opportunity to understand how this meta data is used by SharePoint for searching. This leads to problems when users decide that it's necessary to use SharePoint Portal Server Search to search on information contained in a field that they have added. In this article you'll learn how SharePoint uses document library fields to create properties which are searchable and how to enable searching on those properties.
The Power of Properties
SharePoint Portal Server's search facility really works in two different ways. First, there's the full text search. This searches across all of the text in every document that is in the index. This search is what most people think of when they think of SharePoint's search capability.
Second, there is the property search. During the indexing process, the IFILTERs which extract the text out of the documents put property information into special property buckets which are kept separate in the index so they can be searched separately. This allows you to set properties in your Office documents such as department, project number, author, keywords, etc., and then you'll have the ability to search on those fields individually. You can use the search engine in SharePoint to search for documents where the department is engineering and the project is 123. Where a full text document search for engineering and 123 may find hundreds of entries because the words engineering and the number sequence 123 appears in many documents, a search via properties may yield the 10 or so documents that are truly relevant to your search.
Properties are what most people believe that they are creating when they create a new field in a document library. That's not actually true. The meta data fields in a document library don't have anything to do with properties directly.
Office Does a Slight of Hand
However, during the edit process Office perform a little slight of hand. It takes the information you enter in the meta data fields for the document library and makes corresponding custom properties in the document. The net effect is that although you've only created fields in a document library, you're documents now have custom properties.
These custom properties are picked up by the indexing process (more specifically the IFILTER for Office documents) and they are placed into the search index. You can then use those properties by making them available via the advanced search page in SharePoint.
However, this also means that non-Office documents don't share the same relationship between fields in the document library and the properties of the document itself. So if you're trying to develop a searching mechanism for documents like TIF documents or PDFs you'll find that setting up a meta data field for those document libraries won't allow you to search for those documents directly via their properties. You'll still be able to organize the information
Setting up a test
Now that we understand the basic mechanisms of how SharePoint uses meta data and properties let's demonstrate how it works. Here's what you need to do to set up the demonstration.
- Create a site. For instance, I used /Sites/Test.
- Open the Shared Documents library by clicking on the Quick Nav Bar link to Shared Documents.
- Click on the Modify Settings and Columns link in the left bar.
- Click on the Add a new column link
- Enter a name in the Column name box. You can select any name you would like, I used Rob, Try, and IntranetJournal as my field names.
- Click the OK button.
- Repeat steps 4-7 for any additional columns you want to create. I repeated the process two additional times to get my two additional fields in.
- Click the Go Back to "Shared Documents" link to return to the Shared Documents Library.
Putting it to work
Now that you have a document library with custom fields, you can create a few new documents. Here's what to do:
- Click the New Document button on the task bar.
- Enter some basic text in the document. (This text can be anything you would like.)
- Click File-Save.
- Give the document a name and click the Save button.
- Enter the meta data into the fields which are displayed. You should consider entering different text than the text you used in the document.
- Click the OK button.
- Close Word.
- Verify that the text that you entered is visible in the new fields on the document library.
- Click the document you just created in the document library list and click OK to the warning dialog if necessary.
- Click File-Properties. Notice that the meta data properties from the document library appears.
- Click the File Properties button. The standard Word document properties dialog is displayed.
- Click the Custom tab.
- Note that the meta data that you entered for the document library also exists as a custom property of the document.
- Click OK to close the properties dialog.
- Close Word.
Now you have a document in SharePoint with properties so you can go setup the search for them.
Ensure that the Document is Indexed
Before you can search on your new property you have to first ensure that SharePoint has indexed the document. This is done from the Portal by following this procedure:
- Open the SharePoint Portal
- Click on Site Settings in the navigation bar on the top of the window.
- In the Search Settings and Indexed Content section, click the Configure search and indexing link.
- In the Content Indexes section, click on the Manage content indexes link.
- Hover over the Non_Portal_Content link, drop down the menu via the arrow on the right, and click Start Full Update.
- Wait for the Last Update Status for the Non_Portal_Content index to display the word Idle. The page will automatically refresh itself.
Set up the Properties for Search
We had to ensure that the document was indexed so that the new properties would appear. During the indexing process the IFILTER which processes Word files automatically created new entries in the SharePoint Search Property list for the properties which were discovered in the document we just uploaded. The final set of steps are to enable the properties on the advanced properties page. To do this follow these steps:
- Open the SharePoint Portal.
- Click on Site Settings in the navigation bar on the top of the window.
- In the Search Settings and Indexed Content section, click the Manage properties from crawled documents.
- Click the plus sign to the left of urn:schemas-microsoft-com:office:office.
- Scroll down to one of the names of the fields you added to the list above (and verified became a property). Click the property from the list.
- Check the Include this property in Advanced Search options checkbox.
- Click the OK button.
- Click the Return to Portal link at the top of the page.
- From the Start Menu select Run and then type in IISRESET and press return.
- Click the magnifying glass to the left of the drop down list containing the text All Sources.
- Expand the drop down underneath the Search by properties: label to see that your new property is available to be searched.
You can now search SharePoint Portal Server for just the field you added in the list . Of course, as you have seen, you're actually searching the property that was added to the Word document, but the effect is the same since Office is managing the transition to the document properties.
Sunday, March 09, 2014
[I'm reposting a handful of articles which are no longer available on the Internet as blog posts so that they're not lost forever.]
Originally published on 6/10/2008
One of the challenges with most portals, including Intranets is maintaining relevancy of the information that the user sees and interacts with. You'll hear a ton about search relevancy but relatively little is said about what is displayed on the home page. Some organizations approach the home pages as simple landing pages, a place for links to other places. Others try to serve up relevant content but all too often there are substantial portions of a corporate intranet home page that just aren't relevant. If you're in Indianapolis, how important is the company picnic taking place in New York?
In our information overload culture we've gotten adept at blocking out advertising and other non-content items on a page and still ad blocking software is in widespread use. We can filter information ourselves but the more we can filter information for users the better they like it. The more focused we can make our content the better the user experience. Luckily SharePoint has several ways that we can deliver customized content to users and groups.
One Size Fits All
Perhaps in some things one size does fit all. Golf balls are regulation size so in that sense one size does fit all. However, in most things we want to be unique, expressive, and interesting. If you don't believe me walk into mall and notice the wide array of mobile phone covers that are available. There's enough face plates that you can have any color that you want. That's not all. Your mobile phone should be unique like you so there's holographic screen protectors, and other kinds of "bling bling" to make it unique.
While I can't advocate putting "bling bling" on the home page of your portal, one cannot ignore that individuals are just that – individual. They need different information at different times and for different reasons. Part of developing a portal is focusing on development of a solution that adapts to the major groups of users and tries to meet their specific needs.
In SharePoint there are three basic ways of accomplishing this as discussed in the following sections.
Perhaps the easiest way to manage personalization is to have the web parts that you include on your page manage the personalization themselves. Whether it's a web part for the weather that asks for your ZIP code and remembers it from visit-to-visit or a web part that remembers your search preferences, web parts in SharePoint can have personalized information that allows users to personalize their unique preferences – if the web parts support it.
Although the easiest to manage In-part Personalization does have the disadvantage that the web part itself must be coded to support the personalization – it's not something that you can add in later. The out of box personalization support in SharePoint means that support for personalization in the web parts that you develop is transparent. Literally, there's only one attribute that changes to make a property of a web part work for user level personalization.
In part personalization is great for web parts that you create – however, it simply doesn't work for some third party solutions and some of the out of box web parts. It also can negatively impact performance if there are a large number of users customizing a larger number of web parts on a page. As a final note, this is truly personal personalization, meaning that it must be done on a user-by-user basis and it must be done by the user. That means most users won't take advantage of the functionality unless the web part makes this process very easy.
Peacock of Parts
A somewhat more challenging approach, but one that offers the ability to layer on personalization no matter who wrote the web part or when they wrote it, is the targeting engine in SharePoint. Targeting in SharePoint is best known through the MOSS audiences implementation. Audiences are compiled groups of users to which web parts and information can be targeted to. The implementation of audiences is on top of a public interface called IRuntimeFilter2. Without going into too much detail, it allows you to add additional editing controls in the editor zone and supports the events necessary to make sure that these extra editing controls receive their data back when the properties are saved. They can then be validated.
Once targeting is enabled (through having a value in the correct property) the IRuntimeFilter interface (which is a part of the IRuntimeFilter2 interface) is called to determine whether the web part should be displayed on the page.
The net effect of the personalization framework is that SharePoint can show or hide web parts to individual users or groups of users. This means that you can have a web part that is only displayed to operations team members (even if the rest of the organization has access to the data). Similarly you can surface or hide information based on the time of day, or any other criteria that can be tested.
This is a great strategy when you have a way that you want to be able to filter all of the web parts in the system. So showing different things based on location, time of day, or other criteria will work great. If you need to change what information is displayed in the web part – such as the weather for Carmel, IN vs. Daytona Beach, FL – this isn't the strategy for you. Although you can show or hide a ton of web parts – one for each city. It's really not practical.
Pages for People
Another, lower tech solution, which requires neither web part support for personalization nor the SharePoint targeting infrastructure is to have each user have their own page. With MOSS My Sites are available which do essentially this. Each user can have their own personal portal starting page. However, the challenge with this is that changes are hard to implement across the system. If each user has their own page just adding a new web part to the portal means adding one web part for each of your users – if you have 10,000 users you've just turned a simple change into 10,000 operations.
Still, the greatest flexibility is offered by having each user have their own page so that they have the flexibility to configure the page exactly as they would like – without concern for impacting other users.
Drawing the Target
In reality there may not be one answer to how you want to personalize your web part pages. In order to produce consistently relevant content to users you may need a variety of strategies. You might create different portal sites for each of the different departments so that users have the option to see content relevant to their department, implement My Sites for a personal view, and customize the home page so that the current weather conditions and predictions for the user's current location are shown. There isn't a single right answer to getting the right content to users at the right time.
Having a set of tools that allow you to filter and direct the information that users see is essential to driving relevance and therefore driving engagement in your portal. Go target your users.