Heavy Burdens: Should, Always, Must, and Never

We all carry around a heavy burden of over-generalized rules: I must always do this, I must never do that. I first learned of these rules from the work of Virginia Satir, who called them "survival rules." Rules usually have relevance and value, but in their over-generalized forms, they limit our choices and lead us into trouble.

An example: "An effective leader must always communicate and provide leadership and motivation." While a laudable goal, it isn't always possible. For instance, you might be directed to withhold certain information, or you might have an employee or two who are so distracted by problems at home that they cannot be motivated — by anyone.

Anyone who believes that an effective leader must always communicate, lead, and motivate, risks feeling bad most of the time, because the standard is so often unachievable.

Our example has the form "I must always X," but rules can take other forms: "I must never X," "I should X," "I should always X," and so on. Their unforgiving language leads to trouble: if you violate X, you're not an effective leader. Life is not like that — there are always circumstances. Sometimes those circumstances provide good reason for not "meeting the standard," but the rules make no allowances for Life.

We all carry around
rules that limit our choices
and lead us into troubleTo see the impossibility of adhering to these rules, apply a simple test. Certainly if you must do something, you can do it, so if you change must to can, the statement should be true. If it isn't, you have an impossible rule. Our example becomes "An effective leader can always communicate and provide leadership and motivation." Laughably impossible.

Because of our rules, we can feel guilty when we're innocent. And because of our rules, we have "buttons" that other people can push. Fortunately, Virginia Satir has given us a way to shed the burden that rules impose. She called it Rule Transformation.

Rule transformations have two steps. You first change the rule to a guideline, and then you add conditions for its application. In our example, we change "must always" to "can sometimes" to make it a guideline, and then we add some conditions:

An effective leader can sometimes communicate and provide leadership and motivation, when communication is appropriate, when people are able to accept leadership, and when they can be motivated.

This form removes much of the unbearable burden from the leader, and acknowledges that other people have roles to play, too.

What are your rules? To find some examples, saddle up your favorite search engine and search for "an effective leader should," "an effective leader must," "leaders must never," "the best leaders always," and so on.

See how many of the rules you find are rules you carry around with you every day. When you find one, transform it. You will have set down a heavy burden.  Top    Next Issue

The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More

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:

The Mind Reading Trap

When we think, "Paul doesn't trust me," we could be fooling ourselves into believing that we can read his mind. Unless he has directly expressed his distrust, we're just guessing, and we can reach whatever conclusion we wish, unconstrained by reality. In project management, as anywhere else, that's a recipe for trouble.

Email Antics: II

Nearly everyone complains that email is a time waster. Yet much of the problem results from our own actions. Here's Part II of a little catalog of things we do that help waste our time.

Films Not About Project Teams: I

Here's part one of a list of films and videos about project teams that weren't necessarily meant to be about project teams. Most are available to borrow from the public library, and all are great fun.

TINOs: Teams in Name Only

Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.

Be Choosier About Job Offers: II

An unfortunate outcome of job searches occurs when a job seeker feels forced to accept an offer that isn't a good fit. Sometimes financial pressures are so severe that the seeker has little choice. But financial pressures are partly perceptual. Here's how to manage feeling that pressure.

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

Forthcoming issues of Point Lookout

Coming April 24: Antipatterns for Time-Constrained Communication: 1

Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.

And on May 1: Antipatterns for Time-Constrained Communication: 2

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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