Why We’re All So Angry All The Time

In his book “The Surprising Purpose of Anger” Marshall Rosenberg tells us that anger stems from situations where our needs are not being met. When a need is unmet, we’re likely to feel frustrated and react aggressively (see: Blair, “Considering Anger from a Cognitive Neuroscience Perspective” . And, being human, we’re also likely to look for other people to blame for our needs going unmet.

That may be so. Indeed, Rosenberg’s perspective is a key element informing the Antimatter Principle.

But I have another theory. Or at least, a complementary theory. What if we’re so angry all the time – at a whole host of different things – because we have a need to feel angry? What if we find some real joy, delight – or at least catharsis – in feeling angry?

The theory: We’re all so angry all the time because we like it that way. We delight in the rush of adrenaline and flow of blood to the amygdala – and related parts of the brain – that accompanies our feelings of anger.

This might help explain some of the behaviours I see time and again in work and life. And note in myself, too.

“There’s something delicious about finding fault with something, Especially when our egos are involved (which is nearly always the case), we may protect our anger. We justify it and even feed it.”

~ Perma Chodron

Moral Imperative

We see lots of self-help articles about moderating or dealing with our anger. I suspect an underlying moral imperative along the lines of “anger is bad”. I don’t subscribe. Anger, like any other emotion, strikes me as neither bad nor good – it just IS. Of course, emotion-led responses borne of anger can lead to unfortunate outcomes – such as deterioration in our relationships with others. Which we probably would find useful to avoid, not least in the context of the workplace.

Dealing

Some research suggests that when we attempt to tackle our emotional state head-on, it only makes things worse:

“…when experimental subjects are told of an unhappy event, but then instructed to try not to feel sad about it, they end up feeling worse than people who are informed of the event, but given no instructions about how to feel. In another study, when patients who were suffering from panic disorders listened to relaxation tapes, their hearts beat faster than patients who listened to audiobooks with no explicitly ‘relaxing’ content. Bereaved people who make the most effort to avoid feeling grief, research suggests, take the longest to recover from their loss.”

~ Oliver Burkman

Conclusion

In conclusion, may I suggest we recognise and acknowledge the feeling, embrace the delicious joy of anger, use it as fuel for our spirit, and don’t get caught up in moralistic judgments of ourself or the emotion. And remember, we don’t have to ACT on our anger.

– Bob

Further Reading

Considering Anger from a Cognitive Neuroscience Perspective ~ R. J. R. Blair
The Surprising Purpose of Anger: Beyond Anger Management: Finding the Gift ~ Marshall Rosenberg
Anger And Domination Systems ~ Marshall Rosenberg
How To Get Rid Of Anger: 3 New Secrets From Neuroscience ~ Eric Barker
Buddhism’s Solutions for Anger ~ Barbara O’Brien
The Power of Humane Relationships ~ Think Different blog post

The Relevance of Giants – 2. O Sensei (Morihei Ueshiba)

On most every occasion when I’m speaking in public – at conferences, workshops, and the like – I tend to mention one or more of my “Giants” of Rightshifting. Men and women who, through their lives and work have contributed significantly to my understanding of work, and in particular to my understanding of effective collaborative knowledge work.

Many folks express interest in these Giants, but I do wonder if they appreciate the relevance of the ideas and experiences of these Giants to their own daily lives at work.

I mean, what relevance does, say, O Sensei have to developers, testers, operations staff and the like? Which aspects of any of these Giants’ work could be useful or helpful or simply comforting to these folks?

In this occasional series of posts I’ll be exploring some of the Giants’ relevance to folks other than theorists, managers, consultants and the like. I’ll be sharing some insights into their work, and specifically, the likely relevance.

With these posts I hope to pique your curiosity just a little. Let’s continue, with this second post in the series, with O Sensei.

O Sensei

Morihei Ueshiba

(December 14, 1883 – April 26, 1969)  (See also: Wikipedia entry)

I’m not going to dwell on his early life and experiences in the Japanese Army, his adventures in Mongolia, nor his experiences in Manchuria and Japan during the time of World War 2.

Aikido

I suggest the primary relevance of O Sensei to most folks working in the field of software development (and production operations) is Aikido – the martial art he developed. Excepting it’s less a martial art, and more a philosophy for life, and for harmonising with others.

Unlike many other martial arts, Aikido is focussed on caring for others, as emphasised by the translation of the three kanji: ai-ki-do as the Way of Unifying Spirit or the Way of Spiritual Harmony. O Sensei envisioned Aikido as an expression of his personal philosophy of universal peace and reconciliation. O Sensei’s goal was to create an art that practitioners could use to defend themselves while also protecting their attacker from injury.

“Blending“, one of the core techniques of Aikido, invites us to look at conflicts from the perspectives of the other person – or people – involved. For me, this has a direct connection with empathy – as promoted by e.g. Marshall Rosenberg and others of the nonviolent community.

“Life is growth. If we stop growing, technically and spiritually, we are as good as dead.”

~ Morihei Ueshiba

Where’s the Relevance?

How do we make it more likely that we’re all spending our time on stuff that matters? How do we go about attending to folks’ real needs? I find blending a great asset in identifying with the needs of others. As I blend, I see their perspective, and their needs, more clearly. And in turn, they can feel more listened-to. And choose to reveal other things, crucial things, that means we get to understand more about what matters to us all. With this knowledge – and goodwill – we have a better chance of focusing on what matters, and of reducing the chance of wasting some or all of our time on the inconsequential, on detours, and on dead ends.

Practical Investigation

You might like to join an Aikido dojo, to practice the physical forms of the techniques. And to discuss the philosophy with like-minded people wha have already started the journey. Beware, though, of those dojos and sensei that emphasise the physical forms at the expense of Aikido philosophy.

– Bob

Further Reading

The Life We Are Given ~ Michael Murphy, George Leonard
The Way of Aikido ~ George Leonard
It’s A Lot Like Dancing ~ Terry Dobson

The Antimatter Opening Question

In Clean Language, a conversation with a client often opens with the question “What would you like to have happen…?”

This has bugged me for a long time, for two reasons:

1. Maybe the client doesn’t like for anything to happen (therefore it’s not truly a Clean question). 
2. In the Antimatter frame, it matters little what the client might like (or want) to have happen. It matters a whole lot more what they might need to have happen.

So, I generally open with “What might you need to have happen…” (the Antimatter frame). 

As I make no pretence to use Clean Language (excepting on the rare occasion), reason 1, above, is rendered moot. And reason 2 dissolves as we expressly ask what the client might need. I’ll just point out that this is a much harder question to answer, not least because folks may be able to quickly state what they’d like, but generally have much more difficulty identifying their needs. For me, this is another point in favour of the Antimatter frame – we can directly begin to explore the question of what they might need to have happen. And for this, I generally opt for the NVC (nonviolent communication) four step approach.

– Bob

Difficult Conversations

Before this turns into a mini-series, I’d just like to add one observation to my previous two posts.

Setting aside the outcomes sought by the people that matter, outcomes related to the business and its needs, there’s the not inconsequential matter of the unexpressed outcomes sought by these folks with respect to their own personal needs. Often, these needs are not discussed, shared or even registered at a conscious level by the individuals concerned. And often, then, explicit outcomes have yet to be identified – both by them and by us.

There’s not much point addressing the needs of the organisation (see my previous post) without also attempting, at least, to address the needs of the individual people that matter. This asks of us more effort, because we’re likely to be starting “further back”, before these folks have even expressed their personal sought outcomes. And because they may be reluctant to get into these kinds of conversations, being unusual in a workplace context. And then there’s the difficulty involved in “speaking to power” or at least empathising with people in positions of power.

Examples

Some examples may help clarify this observation.

Senior managers and executives, in articulating the sought outcomes listed previously, may also want to control the solutions chosen, hence their providing solutions in the form of wants. Often there’s an underlying need to feel “in control”, driven by some need, such as their need for order, or personal safety, or kudos.

Similarly, articulating their sought outcomes may, in part, derive from their need for tangible progress, or a need to be seen as the driver of that progress.

Summary

Entering into, and sharing the exploration of these often intensely personal topics is certainly difficult. But that difficulty can ease when we have the right conditions – such as trust, friendship, skill, and safety. And without such conversations, we’re that much more likely to spend much time and effort on delivering outcomes that no one really needs, or worse – that actively work against folks’ needs.

– Bob

Further Reading

Crucial Conversations ~ Patterson & Grenny
Difficult Conversations: How to Discuss What Matters Most ~ Patton, Stone, Heen & Fisher
Discussing the Undiscussable ~ Bill Noonan
Feelings Inventory ~ List at the Centre For Nonviolent Communication
Needs Inventory ~ List at the Centre For Nonviolent Communication

Testbash Dublin and Organisational Psychotherapy

As I mentioned in my previous post, I’m just back from presenting an interactive session on Organisational Psychotherapy at Testbash Dublin. Some folks seemed confused as to the relevance of Organisational Psychotherapy to testers and the world of testing, so I’m happy to explain the connection as I see it. (And please note that many of my previous posts on Organisational Psychotherapy may also help to illuminate this connection.)

I’ll start by riffing on something Rob Meaney said during his presentation:

“Significant quality improvements [aren’t] driven by testing. They [are] driven by building relationships and influencing the right people at the right time.” ~ @RobMeaney #TestBash

Quality (and other) improvements come from improved relationships. This has been a theme on this blog for some years now. For example see: The Power of Humane Relationships.

I asked a key (for me) question during my session (several times):

“If we accept that (as per the Marshall Model) it’s the collective mindset of the organisation that determines its relative effectiveness, how do we propose to support the organisation if and when it choses to do something about its mindset?”

Unsurprisingly perhaps, I heard no answers, excepting my own proposal for a means to that end: Organisational Psychotherapy.

I wonder how many folks involved with testing ask themselves and their peers the question “How can our organisation become more effective at testing?”. Or, using the #NoTesting frame, “How can our organisation become more effective at delivering quality products and services?”

Fellowship

Organisational Psychotherapy is not just about improving product quality, however. Through improved relationships, and a shift in how the organisation relates to its people (i.e. from Theory-X to Theory-Y), the quality of life at work also improves. Put another way, we all have more fun, more job satisfaction, and get to realise more of our potential at work. Further, for all the folks that matter, their several needs get better met. And, as a bonus for the organisation itself, it gets to see its people more productive and engaged. What’s not to like?

Incidentally

I’ve also written elsewhere about using the Antimatter Principle in practical ways during software development. For example, during development we eschew requirements gathering in favour of incrementally elaborating hypotheses about the needs of all the folks that matter, and then conducting experiments to explore those needs. I can envisage teams that still need testers adopting a needs-focused approach to driving testing. For example, putting into place various means by which to answer the question “how well does our product meet the needs of the people that matter to us?”.

Practical Applications

On a related note, some folks asked me about practical applications of Organisational Psychotherapy in their day-to-day work as testers. Here’s just a few applications which immediately come to mind:

• Improving communication with the people that matter (i.e. developers, fellow testers, management, stakeholders, customers, etc.). I find NVC (nonviolent communication) skills and practice particularly useful in this context.
• Clarifying what works and thus what to do more of (Cf Solutions Focus). This can improve team retrospectives.
• Helping the people that matter (including ourselves) feel better about what we’re doing (Cf. Positive Psychology).
• Understanding each other’s strengths, with a view to having the right people in the right seats on the bus (Cf. StrengthsFinder).
• Eliciting requirements (if you still do that) (Cf Clean Language).
• Building a community (such as a Testing CoP or a multi-skilled self-organising product team) (Cf Satir Family Therapy).
• Improved cooperation with higher-ups (empathy, Transactional Analysis, etc.).
• Dealing with blockers to changing/improving the way the work works.

Invitation

I’d love to hear if this post has helped put my recent Testbash session in context.

– Bob

Testbash Dublin

I’m just back from presenting an interactive session at Testbash Dublin. I enjoyed conversations on the topic of the session – Organisational Psychotherapy – as well as conversations around e.g. #NoTesting. Indeed, I noted a common theme running through many of the sessions from the more seasoned testers presenting: a grumbling low-key disaffection with the notion of testing as a path to quality.

No Testing

A number of folks engaged me in trying to better understand what I might mean by #NoTesting. Such conversations generally start out with “What do you mean by ‘testing’?”. My time in Dublin has allowed me to see through my discomfort in avoiding this question (yes, I generally choose to avoid it). I’m loath to get into semantic arguments from the get-go. I find they rarely lead to productive mutual exploration of such topics.

The bottom-line, is: It doesn’t matter one iota what I mean by “testing”. Whatever YOU mean by “testing”, that’s what I’m talking about when I mention #NoTesting. It’s an invitation for YOU to pause awhile to consider how life would be different if you stopped doing “testing” (whatever YOU choose to understand by that term) and did something else to address the same ends.

Ends Over Means

There’s an idea from therapy which might help you understand this perspective. In eg Nonviolent Communication (and some other therapies), human motivation is assumed to stem from attempts to get our needs met. That is, our behaviours and actions result from the strategies (means) we choose in order to meet our needs (ends). Any particular strategy affords us a limited palette of behaviours and actions. Aside: Often, we have little or no conscious awareness of either our ends or our chosen means.

“Testing” (whatever YOU choose to understand by that term) is a strategy you (or someone else) has chosen – almost always, implicitly –  for getting your or their needs met. And other folks’ needs, too, in the general case.

There are always other strategies (means, options) for meeting folks’ needs. Yet rarely do these other strategies receive any consideration. Maybe some of these other options offer a way to better meet folks’ needs. How would we ever discover that, without considering them, becoming aware of them, exploring them?

So that’s what I’m talking about with #NoTesting (amongst a raft of #No hashtags) – an invitation and reminder to actively consider whether your default means (strategy) are best serving your ends (needs), whether your first and automatic choice of strategy is the most effective way to attend to your – and other folks’ – needs.

– Bob

Do Nothing That Is Not Play

If we think about it calmly for but a moment, one logical outcome of nonviolence is folks not working for a living, but playing for a living.

Innovation

Many companies seem desperate for “innovation”. Is innovation more like to come about through folks doing what they’re told (“working”) or through playing with things, as they see fit? I posit the latter is far more likely.

And no, this is not some flight of fancy. Do we really embrace wholehearted the set of assumptions labelled by Douglas McGregor as Theory-Y?

Theory-Y assumptions are: (1) physical and mental effort are natural and most people (depending on the work environment) find work to be a source of satisfaction, (2) they generally, on their own motivation, exercise self-control, self-direction, creativity, and ingenuity in pursuit of individual and collective (company) goals, (3) they either seek responsibility or learn to accept it willingly, and that (4) their full potential is not tapped in most organisations.

Could it be that folks’ “full potential is not tapped in most organisations” because they are obliged to “work” rather than play?

Could it be that engagement (and productivity) would take an amazing leap forwards if we invited folks to “play” rather than “work”?

Could you have the courage to experiment to find out for yourself?

Or are we all so in thrall to what Walter Wink calls The Domination System that play as an alternative to work is undiscussable?

– Bob

Further Reading

Serious Play ~ Michael Schrage
The Importance of Play (A Valentine for Marshall Rosenberg, part 2) ~ John Kinyon
What If #7 – No Work ~ Think Different
The Human Side of Enterprise ~ Douglas McGregor
Theories of Motivation ~ Think Different

The Advice Process – Flaws and Fixes

“The advice process is a tool that helps decision-making via collective intelligence. Much depends on the spirit in which people approach it. When the advice process is introduced, it might be worthwhile to train colleagues not only in the mechanics but also on the mindset underlying effective use.”

We’ve been using the Advice Process for several months now. Whilst we’re still very much committed to its use, and wish to see the changes it promotes, all has not been going smoothly with its uptake.

Potential

We chose the Advice process as a means to devolving and distributing decision-making. We like its potential for quicker – and more impactful – decisions, raised levels of trust, improved communication, and higher levels of involvement and engagement. This list describes this potential, as described by its early promoter, Dennis Bakke of AES, in more detail:

• Community: it draws people, whose advice is sought into the question at hand. They learn about the issue. The sharing of information reinforces the feeling of community. The person whose advice is sought feels honored and needed
• Humility: asking for advice is an act of humility, which is one of the most important characteristics of a fun workplace. The act alone says, “I need you“. The decision maker and the adviser are pushed into a closer relationship. This makes it nearly impossible for the decision-maker to ignore the advice.
• Learning: making decisions is on-the-job education. Advice comes from people who have an understanding of the situation and care about the outcome. No other form of education or training can match this real-time experience.
• Better decisions: chances of reaching the best decision are greater than under conventional top-down approaches. The decision maker has the advantage of being closer to the issue and has to live with responsibility for the consequences of the decision. Advice provides diverse input, uncovering important issues and new perspectives.
• Fun: the process is just plain fun for the decision-maker, because it mirrors the joy found in playing team sports. The advice process stimulates initiative and creativity, which are enhanced by the wisdom from knowledgeable people elsewhere in the organization.

Practice

In practice, we have not yet seen full realisation of this potential. Overall, we attribute this to poor implementation of the Advice Process, which we’re now intent (sic) on fixing – whilst not undermining its original intent (see above).

Flaws

Some of the implementation flaws we have experienced include:

• Permission-seeking. Some folks have not yet overcome their established reflex of seeking permission. The Advice Process as conceived rejects permission-seeking, placing implicit responsibility for outcomes on the individual or team with the intent, not on the permission-giver. This shift (i.e. from authoritarianism to co-creation) requires a degree of courage from all parties.
• Trust. Some advisors have found it challenging to trust the intentions or competence of those seeking advice.
• Belief. Some with intentions have found it challenging to believe that they now have the power/authority to make key decisions.
• Misunderstanding/clashing frames of reference. Sometimes, advice sought and then given has been received/interpreted as denial of permission.
• Impatience. The delay between announcing intent and receiving advice has proved a source of friction, leading on occasions to proceeding without waiting to receive considered advice from advisors who may hold key pieces of the puzzle (often, these are the busiest of people).
• Criticality. Some people have voiced concerns that key business decisions with serious negative commercial or reputational risks could proceed to action, even when some key risks go unappreciated or unaddressed (due to advice being sought from the wrong quarters, ignored, or not understood).

Fixes

We’re intending to experiment with addressing the above concerns through a couple of refinements:

• Shared responsibility. The onus of communication will rest equally with those communicating intent and those from whom for advice is sought. Those announcing an intent are requested to actively pursue advisors to confirm their intent has been heard and understood by all the necessary parties; those from whom advice is sought are requested to respond promptly and with due consideration of the significance of their role and advice.
• Time-outs. In those cases where someone believes there is a problem – maybe they feel the Advice Process has not been followed correctly or not used when it should have been – that someone may call a Time-out. The intention or action in question – which may already be in train – will then be suspended, pending a go-around (i.e. another taking of soundings, general proposal of intent, seeking of advice, confirmation that the intent has been understood, and consideration of advice received). Note: This does not imply that the intention itself has been denied or overruled. Rather, some party to a particular instance of the Advice Process believes the Advice Process has not been followed or used appropriately, and that the risks implicit in the intention or action are likely not being duly considered or attended-to.
• Arbitration. We’ll see if we need to introduce some arbitration or conflict-resolution mechanism to handle repeated time-outs being called against a given intention or action, or to handle occasions where parties disagree on whether the Advice Process has indeed been followed correctly or not.

I’ll keep you posted on how our experiment is going.

– Bob

Further Reading

Decision Making ~ ReinventingOrganisations Wiki

The Advice Process – Definition and Usage Tips ~ Daniel Tenner

Advice Process for Effective Organizational Decision-Making ~ Agilitrix

How to Communicate Your Needs At Work

When people come to understand the disadvantages of ordering others about, some can over-compensate by avoiding all forms of telling. This can lead to frustration, inaction and disconnection. One of the things these awakening folks can struggle with is communicating their needs to others. Because they shy away from conflict, and don’t want to trouble or inconvenience or coerce others, they might favour avoiding expressing their own needs in case it might become a “burden”, or lead others to feel obligated or compelled to do something. So these folks find it difficult to share their personal goals and desires. Instead, they might opt for a reliance on “mind-reading,” believing their colleagues and peers should intuitively know what they need without them having to say anything.

Relying on mind-reading to get your needs fulfilled creates feelings of frustration, maybe even anger and contempt towards colleagues, feelings which will almost invariably lead to the atrophy, even deterioration, of your working relationships. To keep working relationships positive and flourishing, it’s up to you to make your needs clearly known. Nobody is in a better position to understand your needs than you are:

“You have a right to ask for the things you need in a relationship. In fact, you have a responsibility to yourself and your co-workers to be clear about your needs. You are the expert on yourself. No one else, not even your best friends, can read your mind and know what you need in the way of support, connection, time alone, order, independence, play, joy, financial security, and so on.”

So if articulating your needs isn’t something you’ve felt comfortable doing, how do you start going about it? And how do you do it in a way that doesn’t create obligations, defensiveness or anger, and offers the best chance of your colleagues being willing to listen and fulfill that need?

Script

Here’s a sample “needs script” to follow when initiating this kind of conversation. Obviously, it’s not a word-for-word script – what you say will vary greatly according to your relationships and personal situation. Instead, it offers a very simple template for communicating your needs in a healthy and productive way. However, if expressing your needs is something you really struggle with, you may actually find it helpful to write out your “script” beforehand. You don’t need to read it to your colleagues, but putting down your thoughts on paper can help you prepare. That way, in the heat of the moment, you don’t fall into old traps of passiveness or aggressiveness and can instead navigate the healthy middle path of assertiveness and clarity.

The Needs Script

Situation (specific, objective description of facts). Start off the conversation by offering a straightforward description of the situation you want to address. Leave out analysis, interpretation, and inflammatory or accusatory language – try to make it as specific, impersonal, and objective as possible.

• Our relationship has really sucked lately. We’ve been disagreeing a lot more than usual these last few weeks.
• Our office looks like a bomb went off. There’s a lot of stuff lying about.
• Your spending is out of control. We’re $3000 over our budget this month.
• I’m going crazy in at the lack of progress here. We haven’t accomplished much in two months.
• I’m always stuck in the office and never get to meet customers or partners. I’s loosing what little touch I had with our customers’ needs.

Feelings (non-blaming “I” statements). When you tell your colleagues what you’re feeling, you need to be careful to not vent or explode in a vague, accusatory way (“I’m angry/stressed/upset and you’re to blame!”) which may feel cathartic, but isn’t actually productive. In order to keep the conversation as a problem-solving discussion rather than a heated argument, you want to accurately convey the nature, intensity, and cause of your feelings. So before you begin the conversation, you’ll want to have honed in as much as possible to the specifics of what you’ve been feeling. Once you’ve identified the broad feeling that first comes to mind (angry, upset, hurt, etc.), You might like to use a Feelings Inventory to help narrowing down its nature and focus, or use these these modifiers:

1. Definition. First, make your broad feeling more specific by adding some synonyms. When you say angry, do you mean angry and stressed, or angry and irritated? Or are you really more confused or disappointed than mad? When you say you’re upset, are you upset and disappointed, or upset and depressed? The more specific descriptors you can use to describe how you’re feeling, the better.
2. Intensity. Add modifiers that accurately convey the intensity of your feelings. Have you been feeling a little resentful or a lot? Slightly discouraged or majorly depressed? Be honest here.
3. Duration. How long have you been feeling this way? Have you been stressed since your latest vacation, since your role changed, or ever since you started working here? Have you felt irritated for months, for weeks or for days?
4. Cause and Context. You want to avoid naming your colleagues as the cause of your feelings, no matter how tempting, and even if their actions really have been the catalyst. Blame begets defensiveness, not communication. What will result is a fight that doesn’t end up addressing the real problem whatsoever. Instead, try to communicate the cause of your feelings in the form of their impersonal context, and describe your own feelings rather than those of the other person. You can accomplish this by using “I” statements rather than “you” accusations.

Request (for behavior change). Ask for a change in behavior only. This is a very important rule. Don’t expect your colleagues to change their values, attitudes, desires, motivations, or feelings. These characteristics are very hard to change. It’s like asking someone to be taller or more intelligent. People feel personally threatened if you ask them to change intangibles that are seen as part of their very nature and beyond their conscious control. For example, what does it mean to ask someone to be ‘more loving’ or ‘less critical’ or ‘neater’? These kinds of requests are heard as attacks, and little real change is likely to result.

Instead of going after someone’s “core” attributes, and having them react defensively, stick with making a request that they modify a specific, observable behavior.

• I need a neater environment around me. Would you be willing to keep some of this stuff in the drawers and shelves?
• I want you to be less critical of me. I would appreciate it if you didn’t make jokes about me in front of the management.
• I need to see more action. It would mean a lot to me if we could work together on how to make things happen more quickly round here.

When you make your request, only tackle one situation and 1 or 2 observable behavior changes at a time. You don’t want to overwhelm your colleagues – they’ll likely just shut down. Pick small changes that might make them feel like, “Okay, that’s reasonable. I can do that.” See if your colleagues follow through on your requests. If they do, then bring up something else to work on down the line.

 

Other Things to Keep in Mind

Keep your tone as calm and level as possible. Don’t let anger or annoyance creep into your voice – using even a slightly heated, annoyed, accusatory, or patronizing tone can escalate things into an unproductive argument.

Pick a time when your colleagues can give you their full attention. Don’t start the conversation in the middle of a meeting or when they’re in the middle of something important. You don’t want their annoyance about the circumstances to color how they receive your request. Select a time when they’re in a good mood and ready to listen.

Start out by expressing a small need, rather than a large, contentious one, especially if your relationship has been struggling. Once you start meeting each other’s needs successfully, you’ll be in a better position to tackle more polarizing problems.

Sometimes, empathising with them and their situation may be necessary to “earn” their trust and the right to bring up your needs.

Don’t feel like having to ask for something makes it less valuable. It’s easy to fall into the trap of waiting for your colleagues to come to you and should know what you need without you having to say anything – that if they really cared about you and knew you, or weren’t so busy or engrossed, they would just naturally do it. You might then feel that a change in their behaviour is somehow less “real” or valuable because you had to ask for it. “You’re just doing it because I told you I needed it, not because you really want to.”

But people, even those in the closest of relationships, think and see the world differently. Something may seem obvious to you, but simply not occur to them – not because of some character defect or lack of interest — but because they are simply a different person with a different brain – and heart – than you. Instead of seeing their inability to anticipate your needs on their own as a flaw, accept your differences. And instead of seeing behaviour changes you directly asked for as less valuable, appreciate the way they’re willing to meet that need, even if it doesn’t come naturally. It’s just as worthy as a gesture of interest and commitment, if not more so.

Communicating needs is not a one-way street. Hopefully this is obvious, but asking someone to meet your needs is not a unilateral process. Encourage your colleagues to make their needs known as well, and do your best to listen to, understand, and try to meet those needs when you can. In a healthy relationships, all parties are eager to try to do what they can to make the other person flourish.

If you’re on the receiving end of a needs request, one of the most important things to do is to try to accept the other person’s “quirks.” You may not understand why they like things done in a certain way, or how something that can seem so trivial to you can be so important to them, but you have quirks, too, that they find equally hard to grasp. The more you can compromise and accommodate everyone’s unique, but not-so-onerous needs, even without necessarily understanding them, the happier you’ll be.

You have a right to ask, but that doesn’t mean your needs will always be met. Your colleagues have needs too, and their needs may conflict with yours. Making your needs known is not about issuing an ultimatum, but about open communication, compromise, and cooperation. Even if you don’t achieve the exact solution you had hoped for, being open about your needs will make you a happier, less angry colleague, co-worker or employee.

If your colleagues are unwilling to compromise or cooperate with you in any way, you have a choice in how to proceed. You can:

• Try to put this one refusal in perspective with all the good things they do offer and bring to the table. Is the issue such a big deal in the big picture? If not, you express your disappointment and work to understand why you can’t meet on this issue, but ultimately accept their position. Ask if you can re-open the discussion at another time.
• Utilise a self-care alternative. You might choose to have “self-care alternative” in mind (a Plan B) when possible in case your colleagues can’t or won’t meet your needs. While it doesn’t hurt to ask, in the end, it’s not other people who are ultimately responsible for meeting your needs.
• If an issue is too important to you to simply accept a “No,” and/or if this refusal to meet your needs is a consistent pattern, in which you’re always being walked over while giving a lot in return, you may need to remove yourself from the situation permanently, or even end the relationship.

– Bob

Nonjudgmental Feedback

People are not like dogs. How often have you seen someone recommending the giving of praise as a way of raising morale, increasing engagement, making folks happier, and so on? The thing is, giving praise has a significant downside.

Eschew Praise and Compliments

“Compliments are often judgements – however positive – of others.”

~ Marshall Rosenberg

Rosenberg regards compliment and expressions of appreciation and praise as life-alienating communication. I share that viewpoint. Instead, he suggests we include three components in the expression of appreciation:

• The actions that have contributed to our well-being
• The particular needs of ours that have been fulfilled
• The pleasureful feelings (joy, delight, togetherness, w.h.y) engendered by the fulfilment of those needs

In other words, providing nonjudgmental feedback (in the positive case) consists of sharing:

• This is what you did
• This is how I feel about it
• This is the need of mine that was met

And in the negative case, sharing:

• This is what you did
• This is how I feel about it
• This is the need of mine that was NOT met
• (Optional) a refusable request seeking to get the unmet need met.

Judgment

I’ve written previously about What’s Wrong With Judgment. This applies just as much to the judgments implicit in praise, and in other forms of judgmental feedback.

“the most salient feature of a positive judgment [e.g. praise] is not that it’s positive but that it’s a judgment; it’s more about controlling than encouraging. Moreover, praise communicates that our acceptance…comes with strings attached: Our approval is conditional.”

~ Alfie Kohn

Even warm and fulsome praise is likely to be received, albeit subliminally, as controlling and conditional. More useful then, might be non-evaluative (i.e. nonjudgmental) feedback. Researchers have found that just such a response – information about how someone has done, without any judgment attached – is preferable to any sort of praise.

– Bob

Further Reading

Punished By Rewards ~ Alfie Kohn
Feedback Without Criticism ~ Miki Kashtan (Online article)
NVC Feedback – The Executive Advisory
Non-violent Communication: A Language of Life ~ Marshall B. Rosenberg
The Core Protocols ~ Jim and Michele McCarthy

What If #7 – No Work

One of my “giants” is the amazing Richard Buckminster Fuller. As it happens, the “Synergistic” mindset, the third of the four mindsets in the Marshall Model, is named for him and his work in Synergetics.

“We should do away with the absolutely specious notion that everybody has to earn a living. It is a fact today that one in ten thousand of us can make a technological breakthrough capable of supporting all the rest. The youth of today are absolutely right in recognizing this nonsense of earning a living. We keep inventing jobs because of this false idea that everybody has to be employed at some kind of drudgery because, according to Malthusian Darwinian theory he must justify his right to exist…

The true business of people should be to go back to school and think about whatever it was they were thinking about before somebody came along and told them they had to earn a living.”

~ R. Buckminster Fuller

Others, including e.g. Bertrand Russell, and Henry David Thoreau, have also remarked on the essential folly of working for a living. Indeed, some progressive municipalities are beginning to discuss, consider, even experiment with providing their citizens a stipend, sufficient to allow them to live and pursue their individual callings.

What if the whole notion of work, and the civic duty to work so beloved of the conservative right, is just a fiction conceived and maintained to hold us in thrall?

“The conception of duty, speaking historically, has been a means used by the holders of power to induce others to live for the interests of their masters rather than for their own.”

~ Bertrand Russell

Play

Alternatives, might we but consider them, abound.

I myself am fond of the idea of play:

“Do nothing that is not play.”

~ Marshall Rosenberg

Marshall Rosenberg defines play as all those things we truly choose to do – actions we take for their own sake, and not because we are afraid of the consequences or hoping for some kind of reward.

What if we encouraged folks to “play”, rather than “work”? To do those things in which they find intrinsic joy and delight, rather than those things they “have” to do (to please the boss, to get paid, because they feel obligated, etc.).

What effect would that have on motivation? On joy? On engagement? On innovation? On delight, for everyone concerned?

Maybe you believe that folks, free from the violence of coercion, would just slack off? What might that say about your Theory-X vs Theory-Y orientation? About your assumptions regarding people and human nature?

How do you feel about the notion of replacing work with play? How far is it from e.g. Drucker’s widely-accepted perspective?:

“Accept the fact that we have to treat almost anybody as a volunteer.”

~ Peter Drucker

– Bob

Further Reading

Henry Hikes To Fitchburg ~ D.B. Johnson
The Importance of Play (A Valentine for Marshall Rosenberg, part 2) ~ John Kinyon

Other Posts In This Occasional Series

What If #1 – No Management
What If #2 – No Process
What If #3 – No Telling
What If #4 – No Answers
What If #5 – Continuous Improvement Is Useless
What If #6 ~ Agile Nirvana
What If #8 – Agile Never Happened

NVC In The Workplace

For five weeks now, Miki Kashtan of Bay Area NVC, one of the leading lights of the Nonviolent Communication movement, has been publishing (via email) an excellent mini-series about nonviolent communication and collaboration in the workplace.

I’ve been finding her words to be full of widom, compassion, and highly actionable advice. For some inexplicable reason, her posts have not been published on the web. I repeat them here, verbatim, in the hope you find them useful and in the hope that Bay Area NVC doesn’t take offence.

Postscript: I’ve added Week 6 to round out the series.

Week1: What’s stopping you from bringing NVC to work?

If NVC seems impossible to use in your workplace, I want to tell you that it isn’t – it just functions somewhat differently in the workplace than in personal relationships. Over the next five weeks, you’ll be getting a mini-course on making NVC work at work.

What’s stopping you from bringing NVC to work?

I’ve often heard from people that NVC just doesn’t work in the workplace, that it doesn’t have a chance in that world. Have you had doubts about this yourself? If so, what is it that comes to mind specifically – a painful experience? Something you tried that didn’t work? Or an image you have about what would happen if you did try?

When I ask people about this, it usually boils down to one of a few common concerns:

• There’s no time to do the kind of dialogue that NVC requires.
• NVC only works between equals.
• People in the workplace aren’t interested in feelings and needs.

As we are preparing to launch the Center for Efficient Collaboration, I want to share with you some of the key lessons I’ve learned in years of working with organizations. By focusing on a few core principles and practices, I’ve been able to live, apply, and teach NVC in more and more organizations – everything from large manufacturing firms to charitable foundations. And one common response I hear from clients is that what they learn in the process is so practical!

It’s not just that NVC can work at work; applying NVC principles can actually change the whole dynamic of a team or organization, making it both more collaborative and more efficient. My hope is that by shifting how you understand and use NVC, you, too, will find that it’s just as powerful at work as in your personal life.

The one thing to know about workplace NVC

Bringing NVC to work starts to make more sense when you understand how NVC functions within an organization.

NVC’s main function in the workplace is to make it easier to sustain collaboration towards a shared purpose.

This is a different function from supporting our relationships and emotional well-being, and definitely requires a different kind of focus and different choices in how to think, speak, and act.

In the coming five weeks, you’ll get weekly emails from me that explore different ways of supporting collaboration with NVC. For starters, here are my responses to the concerns raised above:

• There’s no time to do the kind of dialogue that NVC requires.

The workplace isn’t designed for prioritizing connection and relationship. To collaborate for a shared purpose, we don’t have to work out what our deepest needs are and how we can meet them together; all that’s required is to have enough dialogue to know what’s important to all players in relation to the purpose at hand, and to find a practical solution that works for all of them. This usually consumes far less energy than intimate, personal conversations with family and friends.

• NVC only works between equals.

There are certainly very different dynamics at play when there are power differences between people. For example, people with less power may be afraid to say “no” for fear of reprisals. In fact, empowering yourself and others to say “no” is so important that I am dedicating an entire installment of this course to it. As you’ll see, specific skills are required to transcend power differences and create willing rather than coerced collaboration.

• People in the workplace aren’t interested in feelings and needs.

My own experience tells me something subtly different. I take seriously the core assumption that NVC rests on: that all human beings have the same basic needs. We have those needs both in and out of the workplace. When our needs are met, we will have certain feelings, and when our needs are not met, we will have certain other feelings – in and out of the workplace.

What’s different is the willingness to talk about the feelings and needs, not whether or not they are there. The culture of most workplaces is not welcoming of intimacy, vulnerability, and expression of need. Why? Because they are seen as inconsistent with the focus on producing goods and services.

What, then, can you do? You can learn to discern feelings and needs – both your own and others’ – and choose how to engage verbally with others based on what will contribute to the shared purpose within the cultural context of your workplace. This, again, takes learning additional skills which I share in the next few weeks of this course.

Stay tuned for future instalments:

• Week 2: Stepping into leadership wherever you are in the organization
• Week 3: How communication changes when you focus on what’s needed for the purpose at hand
• Week 4: Why personal skills don’t automatically translate to functioning well within teams – and what to do about it
• Week 5: Collaborating across power differences, both upwards and downwards
• Week 6: How to change behavior throughout organizations by setting up systems that support collaboration

Do you have specific situations within your workplace that you would like support with? Please hit “reply” and send them to us, so they may fertilize both this course and future blog posts beyond. You can also bring your workplace dilemmas to the free group coaching call that I’m hosting at the Center for Efficient Collaboration launch.

Yours,
Miki

Week Two: Embracing Responsibility for the Whole

When my late sister Inbal was in her twenties and unsure about what she wanted to do with her life, she did a stint of several months of temping. Since she didn’t have any describable skill, she qualified only for short-term, low-level administrative positions. Still, in several places where she worked, they asked for her specifically, and a few places offered her permanent jobs. Although they didn’t specify why, we knew. Instead of doing the bare minimum necessary to complete the assigned task and keeping her distance, Inbal actively looked for things to do. She noticed what was needed, even in offices she had never been to before, and gave her whole self to the place, even if only for one day.

Inbal’s attitude in those early days exemplifies to me one of the key ways you can bring the principles of collaboration to your workplace. Temp positions, in general, have a high level of alienation built into them. Yet even in that kind of job, it’s possible to go beyond focusing on your narrow self-interest so you can attend to the largest pool of needs possible: your own, those of the people around you, and the shared purpose of the organization or team.

This, to me, is an act of leadership. Leadership, the way I define it, is not a position – it’s an intention. It is the act of embracing responsibility for the whole.

Leadership means embracing responsibility for the whole and attending to a shared purpose.

What does this look like in practice?

• It means noticing when you tell yourself that something is not your job, and choosing to do a task because you know what it’s contributing to within the team or organization.
• It means taking the the risk of asking for the support that you need in order to contribute your gifts in full, while ensuring that you work within your own physical and emotional limits.
• It means offering feedback to people with more power when you see ways that the team or organization could be even better at achieving its purpose.
• It means engaging with others’ perspectives and needs to aim for a co-creative path, rather than always relying on your own wisdom alone.

This is not about being good; it’s not something you can “should” yourself into doing. I have found, for myself and others, that it only really works when it involves a true shift in attitude and orientation. Unless you genuinely step outside the frame of only doing “your job” and embrace everything as “yours,” you are likely to be too scared or too resentful to take any such steps wholeheartedly.

For myself, I have found it intrinsically rewarding to focus on serving the whole – even when I end up taking actions that don’t get me exactly what I want. Why? Because it allows me to live as I want instead of being at the mercy of what comes from the outside. Even when a long-term contract I once had was terminated because I offered more coaching to the CEO than was truly wanted, I left that site with a sense of wholeness, because I valued the risks that I took on behalf of supporting that organization to align with its stated purpose and values. Having embraced this approach for years now, I find that relying on internal measures to guide my actions, such as meaning, integrity, and a sense of contribution to something larger than myself, makes life so much more engaging.

This is not a path without challenge. For one thing, we are very habituated, from infancy, to orient our sense of mattering toward approval from others. Whether it’s about satisfying expectations or being appreciated for innovation, we look outward to know that our contribution and needs matter. This habit, if you are in a position with little formal authority, can leave you not trusting your own contribution and reluctant to speak up for fear of retribution.

Even if you are in a position of authority, choosing to embrace the whole is not easy. In addition to negotiating the approval of those with more formal power than you have, other dynamics enter into play. Including the needs and perspectives of others with less formal power – another key aspect of stewarding the whole – is unfamiliar, and rarely engaged with in fullness. Because of mistrust in the ability or willingness of others to take responsibility, attempts at inclusion are often seen as futile, inefficient, or both.

As we proceed with this email course over the next few weeks, I hope you will learn a thing or two about the internal orientation to leadership and how to translate it into concrete practices that support the larger whole and its purpose. For now, I want to leave you with a few questions to reflect on as you go through the upcoming days in your workplace.

1. What is your position within the organization in which you work? How much formal authority do you have in your position?
2. Review in your mind a typical day of work. How do you decide what to do and how to do it? What would be different if your choices were informed by caring for the whole? (Note: your answer is likely to be different in its focus depending on your position within the organization.)
3. Do you feel empowered to carry out your work responsibilities in a way that is informed by caring for the whole?
   • If yes, what would it take for you to put this into action and let this orientation guide all your choices more often?
   • If not, what is preventing you from feeling empowered? Put differently, what needs of yours might you be attending to by choosing, even if without awareness, to act in the ways that you do?

I would love it if some of you took the risk of sharing your responses to these questions by replying to this message. I am so eager for that kind of fertilization of my thinking as I write the rest of this course and future posts. You can also bring your thoughts and questions to the free group coaching call I’m hosting at the launch of  the Center for Efficient Collaboration.

Yours,
Miki

Week Three: Just Enough Connection for the Purpose at Hand

About ten years ago I was at a sociocracy training with others from the local NVC community, and I watched our group trip over a common assumption in the NVC world. The workshop was very challenging for many in the group, and unrest had been building up; I no longer remember the reasons, but I do remember the moment when someone became incredibly agitated. This person – I don’t recall who it was, let’s call her Nancy – spoke up repeatedly whenever the trainer tried to move forward, making it impossible to continue with the training. Being a crowd of NVC practitioners, a couple of us offered Nancy empathy. Within a remarkably short time given the level of upset, she settled emotionally. The relief in the room was palpable to me, and we were turning our attention back to the trainer, ready to proceed.

Then suddenly someone else said: “Wait a minute, I don’t believe we gave Nancy enough empathy, and I don’t think she is done.”

I watched in dismay as she turned to Nancy and re-opened the issue that had just been closed. The moment of peace and focus was lost for the next fifteen minutes.

Why we put empathy first

I’ve come back to that moment many times since, because it’s a classic example of something that many people struggle with when applying NVC tools outside the context of NVC workshops. Simply put, while the principles of NVC apply across the board, the form they take varies based on context and purpose. In this moment with Nancy, there was an NVC principle that didn’t get adapted to the situation we were in.

The principle in this case is the core intention of prioritizing connection. Here’s the language that my sister Inbal and I chose in our rendition of the key assumptions and intentions of NVC:

Prioritizing connection: We aim to focus on connecting open-heartedly with everyone’s needs instead of seeking immediate and potentially compromised solutions, especially in challenging situations.

As you can probably see, this is written as an intention, without specific directions about how to do it in the specific context that you find yourself in. It is aimed as an antidote to deeply ingrained habits: most of us, by default, find ourselves arguing opinions and negotiating solutions without ever connecting at the level of what the opinions or solutions mean to each person; without creating commonality on that level; and without the shared goodwill that makes the engagement worthwhile in the first place.

Whether you’re talking across a conference table or a kitchen table, reinstating a commitment to connection does wonders – as long as it’s coupled with a clear focus on the purpose at hand.

Nancy’s crisis happened during a workshop where experiencing the healing that comes from deep empathy wasn’t the main goal. While hearing the fullness of her pain would make sense in an NVC practice group, in this context it stopped us from refocusing on the reason we were all there.

By prioritizing connection, we escape the tendency to argue and negotiate without awareness of what we share in common. By coupling this with a focus on the purpose of our work, we put connection in service of the whole group or organization.

Here’s what it looks like to apply this principle when collaborating toward a shared purpose:

• Taking a moment to reflect the essence of what you hear from another person before responding to them. The practice of recognizing and naming needs is key to your success here.
• Finding a way to speak the deepest relevant truth about you with the most care for the potential effect on the other person. The practice here is converting any blame, judgment, strong opinions, or preferred solutions into a clear expression of what is true for you one level deeper.
• Making sure you know what you want to hear from another person in addition to what you want to say, so you can ask a question to support the organic flow of a conversation. The practice of formulating clear, specific, doable requests, framed in positive language, will enhance your capacity for dialogue.
• Choosing to offer feedback to people on the effect of their actions – on you, on others, and on the team – in a way that is designed to support your collective ability to achieve your shared purpose. The practice of providing clear, concrete observations is absolutely key here because it allows you to deliver meaningful feedback that isn’t a veiled form of criticism.

If you are familiar with NVC, you will no doubt see that all of the above are core elements of what people learn in NVC workshops and practice groups that are designed for personal use. So what’s the difference between prioritizing connection in an NVC classroom and prioritizing connection at work?

It’s not just about connection

In the workplace there is a purpose other than just connecting. Wonderful and nourishing as connection is, it’s not the primary reason for taking part in collaboration designed to achieve results. At work, we come together to produce and deliver something – a product or a service – that serves the particular purpose of the organization we are part of.

One of the key differences, then, is that the purpose of connection in the workplace is not to feel good, to heal from the past, or to create a bond of love. Rather, the purpose of the connection is to shift away from habitual win/lose thinking, competition, and alienation, and towards creating enough common understanding and trust to collaborate – thereby increasing your overall capacity to achieve your shared purpose.

Another key difference is about use of language. The language that works well in the context of a communication workshop or your personal life often doesn’t translate well into a workplace environment. Sometimes even the words “feeling” or “need” are frowned upon. If your first efforts to introduce NVC to your workplace didn’t work, this may be why. See if you can find ways of expressing fully what you want without using language that can be difficult for others. Just replacing “need” with “want,” for example, can go a long way to make your speech more acceptable without compromising any truth or connection.

We are looking for the sweet spot where connection supports what we’re here to accomplish, rather than interfering with it.

As you puzzle over this – just the right amount of connection – the following questions might help you gain some insight about where that sweet spot is for you.

1. Describe a moment in your work life in which you argued with someone about how to do something. What would you do differently in that moment, having read this segment of our course?
2. Consider someone’s actions that you believe are getting in the way of your team accomplishing its purpose effectively. If you were going to give feedback to this person, how would you frame it? What would you describe as the action? What would you say about why this matters? What would you offer as a way to address it?
3. Think of a difficult conversation you may have been avoiding. How could you deliver the difficult message while taking full responsibility for your experience, without putting blame or judgment on the other person?
4. For any of the above situations, what might you ask of the other person to help move the conversation and your collaboration forward?

Once again, I would love it if you took the risk of hitting “reply” and sharing your responses to these questions. I am so eager for that kind of fertilization of my thinking as I write the rest of this course and future posts. You can also bring your thoughts and questions to the free group coaching call I’m hosting at the launch of the Center for Efficient Collaboration.

Yours,
Miki

Week Four: Committing to Solutions that Work for All

It looked like the setup for a grueling meeting. I was sitting with five executives who were working out how to support a CEO transition. I asked them to state what they each wanted to see as the outcome. All were speaking from within their own positions and expressing their preferences. What they said couldn’t have been more divergent.

They looked at each other, partly helpless, partly amused. I could see this was not a first.

Then I asked them to take some time in silence to reflect on all the responses they had heard, and to come up with a proposal that would attend to the entirety of what they heard, in service of the entire group and the organization. I waited until they all were ready with an answer before hearing from any of them, so that they could truly form their own opinion of this new angle.

When I asked them to share their new proposals, all of us were in awe. Instead of five wildly different suggestions, we now had five overlapping solutions. Within two minutes they settled the one remaining difference, and all agreed on the path forward.

If alignment can happen that quickly, then why do meetings usually take so long and achieve so little?

Sadly, my conclusion is that most people, in most meetings, either tune out and just wait for the meeting to be over, or they are there solely to advocate for their own positions, irrespective of the shared purpose or what others want. Add to this some basic lack of skill – few people know how to participate in meetings effectively, or how to run them in a way that closes loops, attends to all that matters, and maintains and increases trust – and you see why it doesn’t work

So what happened at the meeting that converged so swiftly? Essentially, the executives present were able, with my facilitation, to shift from advocating for their own positions to attending to the whole. Although they were all in positions of authority within their company, they weren’t doing it before I directed them to think in that way.

Transcending an individual perspective

What’s surprising to me about this story is not the speed at which they coalesced. I’ve seen it happen enough that I have come to expect it when the necessary ingredients are in place.

Rather, I remain astonished at how often people see situations only through the lens of their own individual perspective. Even for people in positions of executive leadership, how will this decision affect me? typically becomes a greater concern than how it might affect the mission of the organization or the functioning of a team.

I have found that the capacity to think beyond our own individual needs is almost invariably there, ready to be invoked with remarkable ease – and it is rarely accessed spontaneously. Put differently: I need to explicitly invite people to look for a solution that works for all. Then, like the five executives above, they usually do it right away, even though they hadn’t thought of it on their own. It’s a muscle that doesn’t often get exercised in our society, because for generations we have been focusing only on the individual benefit.

It gets a little trickier, too, because a group or an organization cannot speak for itself in the way that humans do. The only information we have about what supports the larger purpose is the combination of everyone’s sense of what it is.

Clearly, people can easily have disagreements about what serves the shared purpose, and they need to work those out. In my experience, focusing on shared purpose and what will work for everyone enables us to resolve differences much more efficiently. It’s remarkable how much time and trouble this saves, compared with discussions where each person in the group is looking after their own benefit.

If we focus on supporting the shared purpose and seeking solutions that work for everyone, we can resolve differences much more efficiently.

To apply this principle within a group, think about three key aspects:

• Identifying and articulating the shared purpose – both the overall purpose of the organization or the team, and the purpose of any particular decision.
• Focusing on what’s important to each of the individuals involved, and how that relates to the shared purpose.
• Committing to find solutions that attend to as much of what’s important to everyone as possible, moving beyond either/or.

For small decisions, like the five executives identifying who would participate in their transition process, the middle point often remains implicit. In contrast, for large groups dealing with complex and contentious questions – like the lawmakers and advocates I’ve been working with in the Minnesota state legislature, who were deeply polarized around child custody policy – stating what matters to each individual becomes essential to recovering connection and finding common ground. (There’s much more to say about this: you can go deeper into it via this newly published case study and this recent blog post.)

After a while, as a group works with these principles, there is less and less need for explicit naming of what’s important to people, because of the trust they develop. Still, whenever tension or conflict arises and the group needs a compass to guide them through the storm, they can fall back on the more methodical process.

What makes this process so efficient?

The focus on a shared purpose and on solutions that work for everyone brings attention to what the group has in common and what brings them together. When a group operates on a high degree of trust – which is what this way of working together generates and sustains over time – the urge to protect and defend a particular position diminishes. Instead of fighting turf wars, people focus more of their attention on solving the problem.

If you want to see efficient collaboration become the norm for your group or team, here are some of the important conditions to put in place:

• Make it a priority to articulate the shared purpose that binds you together.
• Nurture every member’s experience of mattering. The most effective way to do this is to engage with whatever someone brings forth in discussions, distilling from it what’s truly important to them, and including it in the whole picture that the group is attending to.
• Have systems in place to attend to conflict when it arises and to provide ongoing feedback, so that resentments and disappointments don’t fester underground. (I cover more about systems in the final week of this course.)
• Encourage people to distinguish between their preferred outcome and what they are wholeheartedly willing to accept even if it’s not their preference.

You may notice that none of the above are individual skills or values. Rather, they are mechanisms operating on the group level; agreements and procedures that support the entire group in functioning well. This difference is key. In the absence of understanding that a group operates on a different level, many people expect that just putting together people who are committed to the same vision and values, and who have some individual communication skills, will be enough to create a well-functioning group. It isn’t.

The following questions might help you develop a proposal to a team or group you are part of about how to work together more collaboratively and efficiently:

1. Describe a moment in your work life in which you were part of a group aiming to reach a collaborative decision, and you were stuck. What would you do differently in that moment, having read this segment of our course?
2. Does your group or team have a shared purpose? If so, is it known by everyone? Does everyone truly resonate with it? If not, it may be a purpose, and yet it’s not actually shared. If yes, does everyone know and remember the specifics of the purpose? Do individuals use the purpose to guide their own individual decisions? If not, what would you recommend the group do, in light of this segment of the course?
3. When there are disagreements within your group or team, do you have mechanisms in place for incorporating what’s important to each person and providing an experience of mattering? If not, what do you now see as options for doing this?
4. Does your group have mechanisms for handling conflict and providing ongoing feedback to each other? If not, stay tuned for the final week of this course, which focuses on systems.

Once again, I would love it if you took the risk of hitting “reply” and sharing your responses to these questions. I am so eager for that kind of fertilization of my thinking as I write the rest of this course and future posts. You can also bring your thoughts and questions to the free group coaching call I’m hosting at the launch of the Center for Efficient Collaboration.

Yours,
Miki

Week Five: Collaborating across Power Differences

My late colleague Julie Greene was my student for a few years before we co-founded BayNVC, and in that time I was witness to an extraordinary transformation in her relationship with her boss. Julie was getting quite a bit of satisfaction from her work as an intake counselor at a methadone clinic. Yet she suffered in relation to her supervisor, whom she experienced as micromanaging her.

One day, an internal shift catapulted her out of the powerlessness she had been feeling. It came when she tried adopting an empathic attitude towards her boss as a way of humanizing the relationship – and it dawned on her that underneath the behavior that annoyed her so much was her boss’s commitment to high-quality service. This was a commitment that Julie shared, and her attitude completely changed.

Once she understood what was important to her boss, two things happened. First, it was no longer so odious to give her boss information. Second, and more significantly, their conversations changed as Julie positioned herself as her boss’s supporter. The first changes she made were within herself, as she kept looking for what truly mattered to her boss, regardless of what the boss said or did. After a while, she felt confident enough to offer her boss empathy and understanding when they talked, and she added offers of support when she sensed that her boss was open to it.

Within a few months of consistent attention to the relationship, Julie was her supervisor’s primary confidante and a source of ease and relief: the one person whose work the boss didn’t have to check. The relationship became collaborative, and continued in this vein until Julie was ready to transition into doing her NVC work full time.

Easier said than done, you might be thinking. Indeed, true collaboration across power differences is rare, because habit, fear, and mistrust all get in the way. In my experience, the mistrust usually goes both ways and is fed by both habits and fears.

For millennia now, some (few) people have been far ahead of most others in terms of their access to resources – in other words, they have had far more power. Within the workplace context, those with more power have the option of directly limiting others’ access, as well as penalizing them when their actions don’t meet the needs of those in power. Every employee knows this, and it serves to create mistrust and fear.

When some people have more access to resources than others, collaboration is at risk. Those with power can choose to limit others’ access or punish actions they don’t like, and the resulting mistrust and fear interfere with the willingness to look for solutions that work for all.

Meanwhile, those in power are habituated to believe that they can only make things happen through control, meaning that everything is done in the way they believe is best. They often lack trust that others will get their work done without coercion and incentives. This is the kind of atmosphere that makes collaboration nearly impossible.

Collaborating with someone who has more power

What Julie did, in her persistence with supporting her boss, was nothing short of subverting this familiar set of dynamics. By approaching her boss as a full person who needs support, she opened the door to an entirely different relationship between them – and she stopped waiting for her boss to change first.

If you are in Julie’s position – struggling with someone above you in the hierarchy – you can follow her example in these ways:

• As in any collaboration, remember to aim for a solution that works for you, for the person in power, for the team, and for everyone else involved. To get there, you need to base solutions on complete understanding of what’s important to everyone and link it to the shared purpose of the organization. (You may want to review Week 4 of this course for more on this.)
• If you have a disagreement with the person in power, find a way to express it that ties it to your best understanding of what they are aiming for. Propose another solution that you believe will work for them.
• Attend to the quality of your relationship with them, especially if they are your boss. Don’t focus only on the specific problem you want to solve. If you create enough trust and alliance, they may want to listen.
• Position yourself as their ally. This starts with seeing and engaging with their full humanity, continues with naming and aiming for the shared purpose, and ends with focusing on offering support as ally rather than challenging the person in power.
• As much as possible, do any inner work necessary to make choices with integrity and care, even if you are afraid of negative consequences.

Collaborating from a position of power

What if you are the one with power? In that case, the biggest internal challenge to collaboration is usually an attachment to having work be done a certain way, coupled with a habit of making things happen by using power. It takes some stretching and learning to recognize, in practice and not only in theory, that it’s extremely costly to get someone to do what you want when their sole motivation is that you can make their life miserable if they don’t.

So that’s the internal challenge. The biggest external challenge for bosses is that the people with less power are likely to say “yes” without engaging their full wisdom, going along with what you want even if it doesn’t make sense to them. This has happened in my own organization, BayNVC, where we are all committed to empowerment, truth, and collaboration. Even so, I know of many times, many more than I would wish for, when people went along with a proposal of mine because I made it, not because they thought it through and decided it worked for them. (Sneak preview: next week you will find out how we were finally able to transform this pattern.)

As a result, creating a collaborative team when you are in a position of leadership takes ongoing vigilance and practice, both within you and in interaction with others. Here are some practices you might find helpful:

• Engage in any practice that helps you open yourself to others’ wisdom and to what matters to them.
• Look for ways to encourage people to bring their full contribution and participate in decisions, design, and project definition.
• If you know that certain people are habituated to say “yes,” invite them explicitly to poke holes in your thinking, and express gratitude when they do. Do this, and solicit input and feedback, even when you are confident of your solution.
• When people present input, acknowledge the risk they took in speaking up, listen with care to whatever they say, and take it seriously. This doesn’t in any way mean you must agree with it. Rather, even when you disagree or go a different route, close the loop as much as possible: tell the person how their input affected your thinking, and share your reasons for choosing a different path.

If it seems to you that gathering all these contributions would slow you down, consider how much energy you expend in motivating people to work on timetables and conditions they didn’t choose, doing things that don’t make sense to them, and having an overall sense of not mattering. Think about the mistakes and complex fallout that result from not consulting with implementers, and the grind of absorbing hostile energy, unkept agreements, and even active sabotage of the decisions you make. By investing slightly more time in the short run to nurture collaboration, you avoid these huge long-term resource drains while adding a host of benefits. Collaboration increases buy-in and trust, since people give more of themselves when they participate. And it incorporates more people’s wisdom, allowing solutions to emerge through synergy between stakeholders. Because these solutions attend to more variables, they tend to be much more robust.

This week, instead of offering specific questions for reflection, I invite you to take a situation in which you were challenged to collaborate across a power difference, and walk your way through it applying the specific points and practices I outlined above. You might choose a situation in which you had either more or less power than someone else, or you might look at both sides by thinking about two different scenarios.

As always, I would love it if you took the risk of sharing your responses to these questions by replying to this email. You can also bring your thoughts and questions to the free group coaching call I’m hosting at the launch of the Center for Efficient Collaboration.

Yours,
Miki

Week 6: Creating Systems that Support Collaboration

Last week I mentioned my struggles, as the co-founder of BayNVC, to establish a fully collaborative relationship within our team. If you’ve read the previous installments of this email course, you may remember that collaboration from a position of power entails supporting people to say “no” and to express divergent opinions. As a founder and the organization’s main income generator, this certainly applies to me. Over the years, more and more people on staff were learning to say “no” to me, which was a relief because then I could truly trust their “yes”.

Still, something kept happening that concerned me: people would seek my approval when making decisions. I didn’t find a way for staff to shift to just asking me for input instead of giving me the final word, which ultimately leaves the power in my hands rather than with all of us.

New system, new behavior

The pattern started shifting when we all acquainted ourselves with Frederic Laloux’s Reinventing Organizations. Laloux has researched several organizations that have instituted self-managing teams instead of a chain of command, and his book documents how they do it. In particular, he describes a radical decision-making process that he calls the “advice process.” In this approach, anyone can make any decision, provided they first ask the advice of those affected and those with relevant expertise. The advice is not binding; the person is free to make a decision against the advice – and receive feedback about their choice over time.

At BayNVC, we adopted a modified version in which anyone asked for advice can request a collaborative group decision instead. Writing this up in a Google doc was all it took to replace our ongoing individual conversations with a decision-making system.

The result? The long-awaited full empowerment and collaboration finally materialized.

When our operations coordinator Adriana wanted to buy new software, for example, instead of asking the bookkeeper and me if she was approved to purchase it, she told us the price and the ways this program would support her, and then asked a question that changes everything. Instead of the traditional “Are you OK for me to buy this?”, she asked “Do you have any concerns?”, which gives her information to make her own decision rather than leaving that power with the bookkeeper and with me. Soon after, Anna, who is working on the new website for the Center for Efficient Collaboration (stay tuned! It’s coming in a few weeks), emailed all of us with her proposal for who would lead which aspects of the project, and who would be asked for advice.

Change the default system settings

So why is it that we needed a system in place before things would shift?

It’s the same reason the Kibbutz movement in Israel never fulfilled its aspiration of equality between men and women, even though it succeeded at economic equality. When a group neglects to consciously articulate and explicitly establish one of its organizational systems, that system defaults to the prevailing ways of being. The kibbutzim translated their commitment to economic equality into institutions and policies, while gender equality remained only a conversation. Similarly, BayNVC staff talked about collaboration for a long time without creating a collaborative system. In its absence, the norms of power that we all imbibed from early on continued operating.

Whenever a group does not explicitly articulate a new system, they unconsciously inherit and implement the prevailing ways of being.

Organizations can’t function at their full potential until they clearly define their foundational systems. You can think of these systems as sets of agreements around key questions. Some of the most essential are:

• Shared purpose: Why are we doing what we’re doing? How is awareness of purpose affecting our actions? A clear purpose owned by all can support more engagement, focus, and effective use of resources.
• Decision-making: Who makes which decisions, with input from whom, and communicating about them to whom? What processes do they use to make the decisions? Delineating this can dramatically increase efficiency and engagement.
• Information flow: How does information flow throughout the organization – and particularly from those in leadership positions to others, and vice versa? Simply put, information is to an organization like blood is to a human body. Vision, purpose, and direction might flow outward from the center, while ideas, wishes, and feedback flow inward from everywhere.
• Feedback loops: Who gives feedback to whom, when, and for what specific purpose? How do they provide the feedback? Imagine an organization with a feedback system designed for learning, rather than as one more subtle mechanism for reward and punishment, and you can see why it’s vital to look at feedback.
• Conflict resolution: Who can someone go to when there is conflict? What methods are used to resolve it? When engaged with skillfully, every conflict becomes an opportunity to fine-tune systems and relationships. In the absence of this conscious choice, conflict resolution reverts to punitive methods.
• Resource allocation: How does the organization distribute its resources – financial, human, and otherwise? Because decisions about budgets and pay so powerfully affect organizational functioning, clarity and transparency in this area are particularly important.
• Values: What values guide choices within the organization? What can be done to better embody those values in practice, through systems, procedures, policies, and the entire organizational structure? The more alignment with values, the more enthusiasm and commitment within the workforce.

Attention to the above systems helps any organization, even the strictest command-and-control hierarchy. Creating a fully collaborative organization requires an extra step of embedding the commitment to collaboration. It means designing the systems so that people routinely engage with one another and share decision-making power as they attend to as many needs as possible while keeping their focus on the shared purpose. Just like aligning with values, this usually means examining every part of the operation to find and transform all vestiges of authority-based functioning. Given where we are in our societal evolution, this is likely to be an ongoing process, with rewards every step of the way.

For your reflection this week, I invite you to consider:

1. For your organization or your team, see how many of the questions above you can answer. Any time you don’t know the answer, this is a part of the organization that isn’t functioning optimally. When systems are solidly in place, everyone within the organization knows how they work.
2. How would these systems need to change in order to become fully collaborative?

This is the final week of this course, and there’s still far more to say. This is why we are launching the Center for Efficient Collaboration. Its brand new website is scheduled to launch on October 1, and there is still time to sign up for the FREE coaching call I’m hosting at the launch. If you’ve already signed up, look for an email with call-in details next week.

Yours,
Miki

– Bob