Indicators of Lock-In: I

Lock-in is a phenomenon in decision making in which we observe escalating commitment to a decision of inferior quality, or to a course of action demonstrably less effective than one or more alternatives. In organizations, vendor lock-in is a common form of this dysfunction. In IT organizations, vendor lock-in happens, for example, when the organization builds custom software solutions based on a particular proprietary software or hardware technology.

Lock-in has other forms. They can be more insidious than vendor lock-in because they are self-generated and more difficult to detect. One example from problem solving is solution lock-in, in which the problem solvers escalate their commitment to a particular solution even when superior solutions exist or might exist.

Here are some indicators of solution lock-in.

Escalating commitment

Escalating commitment is the psychological state in which we continue to support a decision with increasing levels of resources despite its repeated failure to achieve projected results. It's characterized by an irrational desire not to abandon the decision.

Escalating commitment can be difficult for the committed to recognize, because we cloak the irrationality of the compulsion to continue in a series of rational-sounding explanations: "We almost have it;" "We're 90% of the way there;" "Our recent breakthrough removes the last obstacle in our path;" "We've been under-resourced but we'll get it with just a bit more effort."

Sunk resources

When things aren't going well, and a growing minority begins to wonder whether we ought to scrap what we have and start over, some inevitably say, "We can't quit now — we have too much invested."

This is the "sunk resources" Escalating commitment can be difficult
for the committed to recognize, because
we cloak the irrationality of the
compulsion to continue in a series of
rational-sounding explanationsargument, and it often dominates. The appropriate reply — "let's not throw good money after bad" — often doesn't prevail until there is no more good money left to throw.

The prototype becomes the answer

Problem solvers sometimes create prototypes of possible solutions, originally intended simply to explore the solution space. Under pressure from Marketing, Sales or even senior management, these prototypes are often offered to customers, and eventually become the solution.

When this happens, little consideration is given to the question of whether they are good enough to become the solution. The organization just locks in, failing to provide resources to study other possible solutions.

Undervaluing open options

Groups that have too little regard for keeping their options open are more likely to lock in. This can be a result of the personal preferences of group members. Some prefer early closure, while others like to maintain alternatives.

A group dominated by the former is more at risk of lock-in. Lock-in behavior can also result from perceived pressure from outside or above. When the group resolves these perceptions by locking in, it is at risk of bypassing superior solutions.

Next time we'll explore indicators of lock-in that relate to the history of the decision-making group.   Next issue in this series   Top    Next Issue

Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!

See "Confirmation Bias: Workplace Consequences: II," Point Lookout for November 30, 2011, for a discussion of the connections between lock-in and confirmation bias.

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

Virtual Communications: II

Participating in or managing a virtual team presents special communications challenges. Here's Part II of some guidelines for communicating with members of virtual teams.

The Good, the Bad, and the Complicated

In fiction and movies, the world is often simple. There's a protagonist, a goal, and a series of obstacles. The protagonists and goals are good, and the obstacles are bad. Real life is more complicated.

Paradoxical Policies: II

Because projects are inherently unique, constructing general organizational policies affecting projects is difficult. The urge to treat projects as if they were operations compounds the difficulty. Here's a collection of policies for projects that would be funny if they weren't real.

The Self-Explanation Effect

In the learning context, self-explanation is the act of explaining to oneself what one is learning. Self-explanation has been shown to increase the rate of acquiring mastery. The mystery is why we don't structure knowledge work to exploit this phenomenon.

Six Traps in Email or Text: II

Collaboration requires communication. For many, communicating often takes place in email and text message systems. But much of the effort expended in communication is dedicated to resolving confusions that we created for ourselves. Here are four examples.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info