Archive

Dialogue

What An Effective Group Workshop Looks Like

I have this theory, based on long experience, that folks in most every organisation have little or no understanding of what “effective” looks like. From concept-to-cash product development, to simple workshops and meetings, and even one-to-one conversations, people lack a “standard” against which to compare their own efforts and experiences.

Absent such a standard, many folks seem to assume that they’re doing just fine. And absent an awareness of the scope for doing better, they seek little in the way of techniques or knowledge about how to be more effective. Nor do they often realise – beyond a certain low-key, nagging discomfort – just how much time, energy and opportunity they’re wasting through ineffective behaviours. Of course that’s not the whole story, what with systems that lead inexorably to disengaged people, and collective thinking patterns – a.k.a. mindsets – that underwrite systemic ineffectiveness.

My work with Rightshifting started from the premise that if folks acquired some simple understanding of their organisation’s relative ineffectiveness, they might choose to look, just a little, into the matter of effectiveness. I see few other practical ways to humanely advance the effectiveness of knowlede-work organisations everywhere. And to reduce the egregious waste of human potential we see in most every workplace today.

[Note: This is a draft. Some elements of the following story are not yet complete.]

A Story

This post is a story about what an effective workshop might look like, from the perspective of those folks participating in it. How much is it like the workshops you’ve participated in over the years?

The Newbie

Sandra was feeling apprehensive. The email had been brief. “From: Ellie Lomas at BaCo.com To: Sandra Hardy at BaCo.com Subject: Upcoming Product development workshop. Hi Sandra, We’d love for you to join in the upcoming Product Development Workshop on 17 October. This one-day event will be held in the Marcus Suite of the Brocade Hotel, near our offices. RSVP to reserve a place. You can always cancel later if the details make it appear unsuitable. Thanks, Ellie, Coordinator, BaCo.com”

She’d not been with BaCo long, and didn’t know quite what to expect. The date was still a month away, though, so she made a mental note to talk with some of her colleagues about things.

Over coffee later, she broached the subject with Dave and Rasheeda. “So, I’ve been invited to next month’s Product Development workshop. Have you been on these kinds of thing before?”

Rasheeda smiled. “Yes. I was in a Skilled Dialogue workshop last month. And I’ll be attending this Product Development thing next month, too.” Dave nodded his head as if to say “And me.”

“Did you have the orientation around workshops as part of your induction?” “Oh, um…yes.” said Sandra, recalling that part of her induction week, but not quite remembering what the workshopping section has covered. “I’ve got the notes. I’ll check and remind myself about what we covered.”

Dave laughed. “Yes. They pack a lot into Induction Week, don’t they? Not much of it sticks, I guess. Still, back when I joined we had to figure most of it out for ourselves as we went along. It’s only been for the past six months or so that newbies have had the advantage of a formal Induction Week.”

Sandra couldn’t help but reflect admiringly on the way BaCo had grown its staff support services as its business had grown. She’d not seen that kind of care and attention to fundamentals in the other companies she’d worked for. I gave her a warm and fuzzy feeling, and strengthened her belief that she had made the right choice in accepting the job.

Back at her desk with a second cup of coffee, she browsed through the material from her Induction Week. Ah. Here it was. Workshopping. And her notes on the topic.

“At BaCo, we thrive on folks collaborating. But we’ve found that few folks know how to collaborate effectively. Exploration of the experience of working together, and opportunities to develop skills through both classroom practice and application in real situations can all help. We have regular courses in Skilled Dialogue, which you’re welcome to attend. And you will note in most meetings, workshops and other group sessions within BaCo a certain style of interactions, born of people wanting to see that everyone gets the very best out of the meeting or session.”

She skip-read a few paragraphs until she found the heading “Workshops”. She began reading more intently.

“When you accept a place in a workshop, you’ll receive a list of references – books, articles, videos, and the like – which might help you start thinking about the workshop topic, and give you some entry points into the subject matter. Most often this will include a few general, standard references to workshop-related topics as well as references directly relevant to the topic of the particular workshop at hand.”

“Presently, for all workshops in BaCo, we invite you to have read ‘More Time To Think’ by Nancy Kline and ‘Crucial Conversations’ by Patterson et al.. And more generally, many folks in BaCo are familiar to some extent with the work on e.g. Skilled Dialogue of folks like Argyris, Bohm and Isaacs, too. (See specific references at the end of this section).”<

This was a lot of information in a few paragraphs. No wonder it hadn’t really stuck during Induction Week. Sandra wondered if there were any courses on Skilled Dialogue scheduled soon. It seemed like an idea to attend one, if possible, before the Product Development workshop.

She began typing: “From: Sandra Hardy at BaCo.com To: Ellie Loma at BaCo.com Subject: Any Skilled Dialogue courses soon? Hi Ellie, I was just wondering if there were any Skilled Dialogue courses scheduled before the upcoming Product Development Workshop you’ve invited me to? Thanks, Sandra Hardy, Product Owner, BaCo.com” and hit “send”.

A few minutes later, a new email mail popped up her Inbox: “From: Ellie Lomas at BaCo.com To: Sandra Hardy at BaCo.com Subject: Re: Any Skilled Dialogue courses soon?” She was about to go for lunch, but opened the email to read. “Hi Sandra, unfortunately our next Skilled Dialogue course is not until. 24 October. I was already in the process of inviting you to that as a new starter.  You’ll be receiving your invitation next week.  Here’s a list of upcoming course, including those for Skilled Dialogue. [Elided] Please note you can also find the live list on our intranet at <link>. Please also note that the syllabus for each course is included in the course details, to help you decide how relevant it might be to your needs. Thanks, Ellie, Coordinator, BaCo.com

Walking down to the company restaurant, Sandra considered her quandary. Would it be better to decline the Product Development workshop invitation until she’d had the chance to learn something about Skilled Dialogue? Or accept and just go along anyway? She didn’t want to look stupid in front of her new colleagues, nor waste their time stumbling to participate without the necessary skills.

“You’re looking a bit pensive” said Rasheeda, as they walked together into the restaurant. “Penny for them?” “I’m just wondering whether to accept the invite to the workshop next month, given how little I know about BaCo workshops in general, and Skilled Dialogue in particular. Oh. You said you’ve been on a Skilled Dialogue course recently. What do you think?”

Rasheeda thought for a moment then smiled reassuringly. “Remember one of BaCo’s mottos: ‘There’s value in implementation and taking action. There are many things one doesn’t understand – why not just go ahead and take action; try to do something?”

“Ah, I kinda remember that from Induction Week”, said Sandra, still wondering if she could risk imposing on her coworkers’ time. “I guess you’re worrying about wasting people’s time? Don’t be. People understand that newbies need to find their feet. Everyone’s going to make allowances, and help you out” said Rasheeda.

“And don’t forget, there’s a lot of self-study material, and pointers to resources about Skilled Dialogue, and many other topics, on the BaCo intranet.”

“I hadn’t thought of that. Guess I’ve not got into the BaCo ‘taking the initiative’ way just yet. It’s hard to throw off old habits”, said Sandra. She sighed, but felt excited too, about the prospect of taking an active part in learning something for herself about Skilled Dialogue.

After lunch, Sandra dug into the intranet and searched the web, looking for materials and resources on Skilled Dialogue. The intranet had some pointers to some intranet forums where BaCo folks discussed related ideas and topics, shared articles, and generally explored the subject together. She recognised some of the names of forum posters as nearby co-workers.

She also spent some time on Twitter, asking her communities about Skilled Dialogue – and received some helpful-looking references. One in particular caught her attention: “Teaching Smart People How to Learn” by someone called Chris Argyris. She downloaded the PDF to her tablet, making a mental note to read it on the train home.

At the end of the day, she was feeling tired but energised, having made a start in understanding the whole subject of Skilled Dialogue. She was already beginning to see how it could make meetings and workshops go smoother. She had one last thing to do before putting on her coat.

She found Ellie’s email from earlier in the day, and hit “reply”. “From: Sandra Hardy at BaCo.com To: Ellie Lomas at BaCo.com Subject: Re: Upcoming Product development workshop. Hi Ellie, thanks for the invite – and your help with Skilled Dialogue course schedules. I’m delighted to accept the invite to the upcoming Product Development Workshop on 17 October. Thanks, Sandra Hardy, Product Owner, BaCo.com”

The next morning, over breakfast, Sandra found a new email from Ellie waiting for her: “From: Ellie Lomas at BaCo.com To: Sandra Hardy at BaCo.com Subject: Upcoming Product development workshop – Acceptance and Informations. Hi Sandra, Happy to hear you’ll be joining the Product Development Workshop on 17 October. Here’s the advance information going out to all attendees:

For: Sandra Hardy

Specific to this workshop: The topic for the one-day workshop is “Product Development”. In this workshop, we’ll be covering the future direction of Product Development at BaCo – that’s to say, how we believe we can most effectively take new ideas – for whole new products, for little incremental additions to out existing products, and everything in between – and turn them into things which our customers will love – and love to pay for.  We know we’ve a ways to go, and that there’s much scope for making this kind of work work better. Here’s a list of references to some relevant books, articles, etc. you might like to take a look at in advance, in preparation for the day:

Note: All books are available via our BaCo company credit account at Amazon.co.uk

Relevant authors include: Bill Deming, Russell Ackoff, Peter Drucker, Peter Senge, Donella Meadows, Allen C Ward, Michael Kennedy, Tom Gilb, John Shook, Jeffrey Liker, Don Reinertsen, John Gall, Douglas McGregor, Taiichi Ohno, Eliyahu Goldratt, John Seddon, Eric Ries, Steve Blank.

Relevant disciplines include: Systems Thinking, Lean Product Development, TPDS, Lean Startup, Theory of Constraints, Product Development, basic Queuing Theory, Hoshin Kanri, Scenario Planning, Value Streams, Value Stream Mapping, the Kano Model.

Relevant links include: <links>

General: Attendees at previous workshops have found that a working knowledge of and practice in Skilled Dialogue makes BaCo workshops more effective, a better use of everyone’s time, and results in more insights, actions, mutual exploration and learning.

Here’s a list of references to some relevant books, articles, etc. you might like to take a look at in advance, in preparation for the day:

Relevant authors include: Chris Argyris, Bill Noonan, Patterson et al., William Isaacs, Nancy Kline, Patrick Lencioni, Sir John Whitmore, Nonaka & Konno, David Bohm, Peter Senge.

Relevant disciplines include: Skilled dialogue, thinking together, team-building, team coaching, ba.

Relevant links include: <links>

You are registered for this event. Also registered are: Steve Wilson (Facilitating), Dannie Jones, Uppad Misra, Claire Leeson, Rigali Mussolo, Dave Walbrook, Nick Carty and Ken Prather. You can find the live list of registered attendees here: <link>

Thanks, Ellie, Coordinator, BaCo.com”

“Jeez!” Sandra gasped to herself. She suddenly felt overwhelmed. So many books. So many authors. So many disciplines. Almost all of them she’d not even heard of before. And I’m an experienced Product Owner?

Comes The Day

By the day of the workshop, Sandra was feeling all read out. She’d studied Lecioni’s teambullding model and his ideas on better meetngs, Noonan’s book on discussing the undiscussable, and Nancy Kline’s work on Thinking Environments. Coaching For Performance has opened her eyes to the potential in people. William Isaac’s stories had inspired her with the power of productive dialogue. But she felt like a total novice, even so. So many more references to follow up. So much knowledge yet to explore. She didn’t know how she was going to cover it all in a lifetime, let alone in the months or years she might be working for BaCo.

And there was the whole other domain of Product Development to cover. She’d believed she knew lots about that. And now, she wondered if she knew anything about that, either. But she knew one thing. She knew she’d found something she loved. At school, study had seemed dry and pointless. But now, to her utter amazement, she had discovered she did have a love of learning. Was this some kind of BaCo conspiracy? Did they know this was one effect of their encouragement to learn? Was it a deliberate and cunning ploy to exploit the workforce? It sure didn’t feel like exploitation.

She bumped into Dannie on the walk to the hotel. “Morning.” “Morning, Dannie.” “Looking forward to it?” Sandra thought about that. “Excited. And daunted.”

They’d reached the revolving door at the entrance to the hotel’s lobby. The conversation paused as they separated to go through the spinning glass and steel. “Ah, I can remember that feeling” said Dannie, taking a deep breath and smiling. “Quite a challenge.”

They followed the BaCo signs to the conference room. Half a dozen other BaCo folks were there already, hanging their coats and stashing their bags. One of the guidelines for BaCo workshops was to avoid using laptops. Several folks already had their tablets or smartphone out and were connecting to the hotel Wifi. The large screen showed the BaCo logo, the title of the day’s workshop, and a clock ticking in the lower corner.

“Welcome”, said “Bruce” – Sandra guessed, a hotel employee, by his badge and his dress. “Tea or coffee?” “Thanks” said Sandra, moving to take a cup, tea bag, and hot water from the urn on one of the side table.

While she was adding the milk to her tea, Ellie walked in, carrying a box under her arm. “Stationery and stuff!” she exclaimed, putting the box down on a side table towards the front of the room. “Get it while it’s hot! Everybody help themselves, as you need to.”

Sandra guessed most of the attendees had arrived by now. Most were chatting in groups of twos and threes, some animatedly, some more relaxed. She walked over to where Dannie was chatting with a dark-skinned woman. “Sandra, you know Uppad? She’s working on the Logix product at the moment.” They exchanged greetings. Sandra was unsure as to how to continue the conversation, but Uppad helped her out. “So you’ve been here a month now? Getting into the swing of things?” Sandra thought about saying no, about sharing her awe at the amount of stuff she now knew she didn’t know, but was cut short by Steve, the facilitator, tapping the bell for the room’s attention. “It’s two minutes to Nine, so who’s for getting started?” Everybody took their seat and most opened their Twitter apps. Some tweeted what Sandra guessed as a few words about the start of the workshop.

“Ok, how do we want to start?” asked Steve. “Do we want an amanuensis stroke cybrarian?” asked Nick. “If so, who’d like to do that?” Sandra had read about this role, and spoke up. “I’d like to do it. Except I don’t know much about it. Would it be OK to have a newbie?”

“Ah” said Nick. “All you have to do” he said, tilting his head down and looking up at her with a wry smile “is to tweet things that might be interesting for the group here, and maybe for other folks across BaCo, too. Our hashtag today is up there next to the Wifi code. He pointed to an A2 Post-it stuck to the wall with “#bacopd17” written on it. Tweet things like references to any key ideas that get mentioned, or any insights that emerge. Saves us all each writing our own notes. Also, we’ve found it’s handy to have topical images, book covers, quotes, notes, etc. visible on the big screen. Oh, and you might find using that laptop – with its keyboard and screen – more convenient than your tablet. Being our amanuensarian might help you pick things up quicker than just sitting quietly and listening?”

“Anyone else burning to do it?” asked Steve.

No one seemed keen to deny Sandra the opportunity, so she moved over to the vacant seat at the laptop controlling the big screen. Once seated, she called up a browser in one window and projected it onto the screen for all to share, whilst opening twitter in another, shared window, showing the live #bacopd17 hashtag stream.

“Ok.” said Steve. Do we want an agenda? “How about just throwing some topics onto some post-its, and choosing as we go?”

“Everyone nodded.” The Lean Coffee – like format was well-know and well-liked amongst those present.

“First – standard – topic is ‘Why are we here?’”. How about we make a start on that whilst we have some time to note what we’d each personally like to cover today?

Steve wrote something on a Post-It and stood to place the note on the flip chart. “Why are we here?” Sandra knew enough about this format of meeting to start the timer counting down the eight minutes they’d spend on the topic. The countdown appeared, discreetly, in one corner on the big screen.

Each person in turn shared their reasons for attending the workshop, speaking about how they were feeling being there, what they thought they needed to get out of the day, and any requests they had in that regard. Each also spoke to their shared common purpose for the workshop. Sandra noted how everyone appeared to have spent some considerable time thinking about these things in advance.

As each person talked, the others listened intently, looking down occasionally to make a note or two.

Although Sandra has been at some dozen BaCo meeting since her first day, she was still very struck by the no-nonsense, matter-of-fact way in which everyone in BaCo meetings just got right down to it. Idle chat and pleasantries were conspicuous by their absence. Everyone listening carefully, processing what they heard, and only so very occasionally speaking in response to something said. She could clearly see the influence of Nancy Kline’s work in action.

[Choosing a topic - tbd]

Every time someone mentioned an idea or reference that was not universally known amongst the group, Sandra would google for it and display some likely helpful information or image on the big screen. All the while, the twitter stream was updating in near real time with tweets from within and without the room.

[Illustrate engagement and constructive conflict - tbd]

And the Day is Done

“It’s a wrap!” Steve exclaimed. Everyone smiled. And sighed. It had been a long day. And the workshop wasn’t over yet. Everyone stood, gathered their possessions, bags and coats. As they filed out of the room, a few lingered to discuss this or that.

On her train home, Sandra reflected on her first BaCo workshop. It had been a good choice, volunteering as the amanuensarian. She’d learned a lot, through having to look up references, thinking about what to display on the big screen, and keeping abreast of both the twitter stream and the conversation in the room. The amanuensarian role had helped in making more of it stick.

She took her smartphone and scrolled back through the day’s twitter stream. Plenty there to catch up on and delve deeper into over the next few days. And folks not present in the meeting had contributed some interesting stuff too. Even some folks outside of BaCo. She followed everyone who had contributed something.

She replied to or retweeted a few of the day’s tweets, before relaxing into her seat and listening to some tunes, as the train rocked along, homeward.

End.

A Model

The above story illustrates a range of features of an effective workshop:

  • Certain shared proficiencies in e.g. Skilled Dialogue, Lean Coffee, etc..
  • Pre-reading (shared), including “standard” texts – here including Nancy Kline and Chris Argyris.
  • Clarity of purpose “just why are we here?”.
  • Shared purpose “we’re all here for the same things”.
  • Folks tweeting and googling continuously during the workshop.
  • Amanuensis / cybrarian to facilitate shared learning in the workshops.
  • Democratic agenda-setting.
  • Mutual exploration of topics.
  • Active curiosity.
  • “Essentiality” – avoidance of rabbit-holes and extraneous discussion of details.
  • Focus on impacts (as compared to busyness, or outputs, or even outcomes).
  • Post-reading – following up new references.
  • Follow-up conversations, actions.
  • Feedback.

- Bob

Afterword

In writing this story, it seemed to me that a video of a workshop in action would be a great addition to the resources available to BaCo staff to help them appreciate the nature of an effective workshop. Maybe one day I’ll have the opportunity to write and/or direct such a video.

TDR – Test Driven Relationships

TDD (Test Driven Development) seems fairly well known as a software development technique these days – even though uptake and understanding remains “patchy”. TDD purports to improve the quality of code by focusing on the intended behaviour of a piece of code before writing that code.

I believe that relationships – interpersonal relationships, relationships between people – are what really matters in work – and particularly in collaborative knowledge-work. Far more than code quality – although that’s handy, too.

One question which folks ask me regularly is “how might we go about improving the quality of our relationships?” I propose TDR – Test Driven Relationships might offer a way forward.

What is a Quality Relationship?

Psychology and psychotherapy have quite a lot to say about what makes for a quality relationship.

Gregg Henriques offers the “5 Cs” model (Conflicted -> Civil -> Cordial -> Close -> Connected)

Patrick Lencioni has his “5 Dysfunctions” model (Trust -> Positive conflict -> Commitment -> Accountability -> Results)

The Fundamentals of TDR

In improving relationships, it’s often helpful to try things out. For example, if we’re wanting to be more empathetic, it can be useful to try to guess how someone is feeling, and then ask them how close to the mark our guess is.

“In relationship, business, classroom, and parent-child conflicts, we can learn to hear the human being behind the message, regardless of how the message is framed. We can learn to hear the other person’s unmet needs and requests. Ultimately, listening empathetically does not imply doing what the person wants; rather, it implies showing respectful acknowledgment of the individual’s inner world. As we do that, we move from the coercive language we have been taught to the language of the heart.”

~ Marshall Rosenberg

Taking this principle and extending it, TDR says “define the results you expect – or desire – from an upcoming interaction with someone, plan an approach, have the interaction, and then compare the results against those expected / desired”. If the results don’t match up, refactor you approach to the interaction and try again.

As a reference and comparison, here’s the vanilla TDD four-step red-green-refactor process:

  1. Add a test – the simplest possible
  2. See it fail (red)
  3. Make all tests (to date) pass, using the minimum amount of instructions (green)
  4. Refactor

Why It Works

TDR helps us clarify our intent, and experiment in small increments with the way we relate to others, adjusting as we find things that don’t work so well, aw well as things that work particularly well.

“Every time I mess up is a chance to practice.”

~ Marshall Rosenberg

TDR also allows us to better keep the idea of “relationship quality” in our minds, and provides us with a practical means to focus on improving that quality.

For those who object to TDR on the grounds that it’s somehow fake, I offer the following advice:

“Fake it ‘till you make it.”

~ Neil Gaiman

How important is relationship quality to you? And what are you already doing about that, by way of e.g. deliberate practices?

- Bob

Holding The Space

You may have noticed that the title of this blog is “Think Different”. Some kind folks over the years have remarked upon the insightfulness of one or more of my posts. Some have gone so far as to ask me whether and when I might be holding a workshop, conference, or other such event on the topics touched-on in this blog.

Well, the time has come and October 7 is the day. This first one day event is titled “The Think Different Experience”. Maybe it’s even the first in a series. We’ll see how it goes.

From my perspective, I feel happy to share in exploring what thinking different means, how to go about it – deliberately and intentionally – and the value it offers to individuals and organisations both.

Busy Busy

I work with many folks, and often I get the impression that everyone’s so busy, busy thinking inside their own little boxes that they rarely have any opportunity or, indeed, inclination to spend some time on reflection, introspection and thinking outside their regular tramlines.

I’ve created the Think Different Experience event to afford some time (a day) and some space (Nutfield Priory hotel) for some interested folks (max 10) to come together and explore what Thinking Differently might mean for us.

Ba

With this event, I see my role first and foremost being to “hold a space” which – in itself – has some value for the folks participating. This is not too far from the the idea which inspired Falling Blossoms some fifteen years ago:

*One day, in a mood of sublime emptiness, Subhuti was resting underneath a tree when flowers began to fall about him.

“We are praising you for your discourse on emptiness,” the gods whispered to Subhuti.
“But I have not spoken of emptiness,” replied Subhuti.
“You have not spoken of emptiness, we have not heard emptiness,” responded the gods.
“This is the true emptiness.”
The blossoms showered upon Subhuti as rain.

The Outcome Is In Your Hands

The event will stand or fall on the quality of your participation. Do you feel happy about that, and about the opportunity to contribute to the joy and well-being of not only yourself but your fellow participants?

Don’t Come Along If

There are some aspects to the event which may cause some folks a bit of grief. So, in the spirit of fair warning, don’t come if:

  • You want to be spoon-fed ideas
    I’d describe my hopes regarding facilitating this event as “pull-driven”. That is to say, folks will be invited to pull ideas, feelings, and – ultimately – value from myself and the other folks present. Don’t expect – or hope for – others to “push” ideas at you (although that may happen, inadvertently, now and again).
  • You want to sit back and let others create your meaning for you
    I have some hopes that the folks attending will want to participate actively in exploring and creating their own meaning, and in creating shared meaning too. We’ll see how that goes.
  • You have fixed ideas and assumptions which serve you well enough that you have no wish to examine them, or consider possible alternatives
    I suspect some awkward questions might get asked,. and some tricky subjects – undiscussable to some, at least in their regular workplaces – might come up.
  • All your needs – in work and in life – are presently being well-met
    According to the precepts of e.g. Nonviolent Communication, every human being has needs, needs which each person is trying to get met the best way they know how. Sadly, many folks have chosen means to getting their need met which, by their own terms of reference, carry some pernicious or negative side-effects. Or even, sometimes, have chosen means which actively work against getting those needs met – even though they feel like the best or only means available to the person employing them.

Do Come Along If

  • You want to experience a different kind of event.
  • You’re curious about the value of play, therapy, Bohm dialogue – and similar principles underpinning the event.
  • You’re keen to spend time in the company of like-minded people (I can’t guarantee just how like-minded folks are going to be, though <wry smile>).

What you might come away with

It’s my hope that we all come away from the event with some of our respective needs having been met. This might include:

  • Meaningful connections – with self and with each other a.k.a. “fellowship”.
  • Play – “Do nothing that isn’t play”.
  • Ideas and pointers for getting one’s needs better met (i.e. alternative strategies / means).
  • An appreciation of the bigger picture – whatever that is.
  • An opportunity to be more human – however you may define that.

For what it’s worth, I share Marshall Rosenberg’s definition of “being more human”:

“Connecting with what’s alive in others and ourselves.”

Would you like to be part of that?

Some places still available.

- Bob

 

A Faster Workstation

MacPro

Like many things, the Antimatter Principle appears easy to understand, and, to me, even easier to misunderstand.

What could be easier as a coherent and comprehensive set of guiding principles than “attend to folks’ needs”, right?

And as a starting point, seeing folks actively engaged in attending to folks’ needs, any needs, makes my happy.

Digging Deeper

One of my needs is to help folks realise more and more of their innate potential – to use the old cliche “to become all that they can be”. And so I’m happy when seeing folks getting progressively more and more out of the Antimatter Principle.

As an example, consider this scenario:

Scenario 1a

A developer says “I need a faster workstation”. Sounds very straightforward. In many cases this might trigger defensiveness and/or analysis on behalf of the person who has to write and/or sign the purchase order. Setting aside this can of worms for the moment, let’s suppose we can get past this and the developer gets their new, faster workstation. Joy! Of a sort.

Let’s run through this scenario again. But this time we’ll take just a little more time and effort in the hope of maybe uncovering some deeper needs.

Scenario 1b

A developer says “I need a faster workstation”. Someone hearing this – at least, someone who is tuned-in to attending to folks’ needs – might respond with a question like “I guess you’re feeling stressed about not getting stuff done?” (NB Empathising).

Let’s follow a possible evolution of this dialogue:

“Sure am”.

“How’s your workstation for speed at the moment?”

“Well, I’m working on a Clojure module and the REPL startup times are interrupting my train of thought.” (Observation)

“I could get much more done if my workstation was faster.”

“So, how do you feel about that?”

“Quite frustrated, actually. I know folks are waiting on this module, and I feel like I’m letting them down.” (Feelings)

“Sounds like you have a need that’s not getting met?

“Yes. I guess I have a need to be seen as reliable and diligent and competent, and sharing in the customer-focus values of my team.” (Needs)

“So, needs for appreciation and belonging?”

“Yes. Sounds plausible.”

“I’ll go and ask Leslie about getting a new workstation and see what’s possible.” (Refusable request)

Let’s assume the basic outcome remains the same – our developer gets their new, faster workstation.

In this case, they’re still likely to find joy in being able to work faster, or more productively, or whatever. But it’s also possible that they might find much more joy in the situation, realising via the earlier dialogue that their needs for appreciation and belonging are what’s really better in their life. Not to mention the joy accruing to the person who helped them through the dialogue.

How do you feel about this? Does the explanation meet any of your needs?

- Bob

Further Reading

Words That Work In Business ~ Ike K. Lasater

Principles WTF

rock
“Hey. Why don’t we write down some principles?”
“Why?”
“Why not. It might help.”
“Help who? With what?”
 
I regularly see folks, in what I assume is their eagerness to help and communicate, invest what can amount to considerable time and effort in discussing and, moreover, writing down sets of principles, manifestos, and the like.
 
This all without asking:
“Who needs us to write down some principles?”
“What do they need them for?”
“How will they actually get used?”
“How will we know if they’ve been of any use in e.g. meeting folks’ needs?”
“Could we spend the time and effort on doing something else more useful?”
 
- Bob

Tea Lady

Tea lady

 

 

 

“We give advice, but we cannot give the wisdom to profit by it.”

~ Francois de La Rochefoucauld

 

I generally “bump” into topics for this blog. Or they bump into me. Either way, I’m happy to follow the path that serendipity chooses for me.

Today I’ve bumped into some thoughts about experts and expertise.

For some reason, folks seem drawn to the expert, and compelled to seek their wisdom. I observe many folks regularly seeking advice in the earnest belief that they will act on and benefit from such advice. Which, of course, almost never happens.

“Hakuin used to tell his pupils about an old woman who had a teashop, and praising her understanding of Zen. The pupils refused to believe what he told them and would go to the teashop to find out for themselves.

Whenever the woman saw them coming she could tell at once whether they had come for tea or to look into her grasp of Zen. In the former case, she would server them graciously. In the latter, she would beckon to the pupils to come behind her screen. The instant they obeyed, she would strike them with a fire-poker.

Nine out of ten of them could not escape her beating.”

~ A Zen Koan

I often find myself being seen by clients as some kind of expert. This generally bothers me greatly. For one thing I’ve seen the harm that can come from folks delegating their thinking to so-called experts. Yes, it can be comforting to have someone else do your thinking for you – God knows, thinking is hard. And there’s the added comfort of having someone lined-up to take the blame if, later, that thinking turns out to be flawed.

And then there’s the additional energy I find myself putting into guarding against my natural inclination towards trying to help through giving advice – even when in my heart I believe that any giving of advice is not in my clients’ best interests. I find it particularly difficult when folks ask directly for advice. Then, it can seem so churlish to demur, so patronising to launch into some more or less convoluted semi-dialogue about the perils of advice-giving. And so dissonant to advise on the perils of advice-seeking.

“The ONLY learning which significantly influences behaviour is self-discovered, self-appropriated learning.”

~ Carl Rogers

Feeding the ego troll also bothers me. I find it flattering when folks look up to me in some way – for my knowledge or experience or insights or whatever. Flattering, and rewarding, in that it meets my need to feel that I’m helping, making a positive difference for them. Bothersome, then, to feel each time it happens, that this is an illusion. For even slight reflection leads me to sense that by being recognised as an expert, I’m helping less, and making less of a difference, than could otherwise be the case. Approbation tastes sooooo sweet, yet simultaneously feels so bitter.

I’m hoping some current and future clients might get to read this. If for no other reason than it might provide an insight into just one of the many struggles that their therapist is also going through. And thus, perhaps, offer some opportunity for fellow-feeling, even empathy.

We’re all human after all.

“This man beside us also has a hard fight with an unfavouring world, with strong temptations, with doubts and fears, with wounds of the past which have skinned over, but which smart when they are touched. It is a fact, however surprising. And when this occurs to us we are moved to deal kindly with him, to bid him be of good cheer, to let him understand that we are also fighting a battle; we are bound not to irritate him, nor press hardly upon him nor help his lower self.”

~ Ian MacLaren

I’d love to hear about your feelings on the subject.

- Bob

If At First…

A sunny path under a blue sky

Since first naming the Antimatter Principle back in October 2013, it has featured in quite a few posts of mine. Even whilst composing that first post I suspected that I would have trouble adequately explaining such an “out there” idea.

And so, it seems, it has proven.

I say “it seems” because I have had very few folks engage with me on the topic. Reactions, one way or the other, have been sparse.

I reflect that “change”, as John Seddon is wont to observe, “is a normative process”. Folks have to experience a thing, first hand, to really begin to grasp that thing.

And, God knows, there’s precious few folks in precious few organisations consciously practicing “attending to folks’ needs” – or, indeed, anything even remotely like that.

“You only understand something relative to something you already understand.”

~ Richard Saul Wurman

For the vast majority of folks involved in “technical” work, where decades of collective wisdom has focussed on “process”, or leadership/management, I can appreciate that breaking out of those frames and exploring a very different, and alien, new frame may feel…discomforting?

Dogfooding

So, by way of eating my own dogfood, I ask “To what – and to whose – needs am I attending with the Antimatter Principle?”

My own, certainly:
A need for joyful connection with others.
A need for dialogue and exchange of perspectives.
A need for fellowship in the mutual exploration of the mysteries of the Universe – and more specifically, the mysteries of software development.

And for others? I see folks everywhere trying to figure out “this software thing”. I.E. Looking for answers to questions about productivity, quality, mastery, job satisfaction, and other such matters. I offer the Antimatter Principle as one possibility for a path to pursue in seeking such answers.

Having signposted this particular path – what I call the people path – I feel it best to leave folks free to choose which path they may wish to follow, if any.

“The most essential prerequisite to understanding is to be able to admit when you don’t understand something”

~ Richard Saul Wurman

So why rake over these old coals? Am I flogging (sic) a dead horse? Is it time yet to dismount?

Would you be willing to suggest something, by way of explanation, that might help you grasp the concept – sufficiently at least to consider it’s implications and ramifications?

And would you be willing to share some of your needs in this regard?

- Bob

Further Reading

Interview: Richard Saul Wurman; In Search of the God of Understanding ~ Nadine Epstein

Follow

Get every new post delivered to your Inbox.

Join 10,970 other followers

%d bloggers like this: