Skip to main content

My Experience Building Deep Trust

How would a company function if its top leadership trusted each other deeply and truly shared a common vision for the future? This question burns in my mind as I ponder the impact of the retreat I attended last weekend.

I met Siraj while making contact with the Washington DC Agile/Scrum scene. I had offered to help him make high quality photographs of his collection of "influence maps." Having just moved to the DC area, and having time on my hands, I thought that some small acts of service would be a good way to get to know and integrate into the Agile community here.

An influence map is both a discovery tool and an information radiator for reflecting on and telling the story of your life. It was fascinating what I could learn about people I had never met just by looking at their maps.

There was always something mysterious about Siraj. As his name suggests, he is of Indian origin, but he grew up in Middle East and studied in a Jesuit school. His life has always been driven by the questions, 'Why am I here?' and 'Whats next for us?' So when he invited me to attend a weekend retreat on change leadership based on these influence maps, I was intrigued and just had to come.

His model for influencing change is called The Influencers Mantra, and the monthly retreat to learn this model is called Temenos, which is the Greek word for "container." Just as you can't control your heartbeat, you can't control the container. But you can influence your heartbeat (and many other reactions) by controlling your breathing. Temenos is about how to influence containers of people like a marriage, a partnership, or a company.

A Temenos has a simple format:
  • Warm-up on Friday evening - a fancy word for dinner (and maybe some wine) and otherwise getting to know each other. 
  • Saturday and Sunday were the formally defined parts of the workshop, 
  • Cool-down Sunday night - another fancy word for dinner (and maybe some wine) and enjoying the afterglow of an intense weekend together
  • Monday morning departure 
Siraj's model of influencing change is based on simple premises:
  1. Any group of people, like a company, a partnership, a team or a marriage is a container.
  2. A container is not a soldier to be commanded, it is a woman to be wooed. It is also a raging fire which will will burn you if you take the wrong approach. Having been burned several times and having wooed an organization once or twice, I recognize the truth of this statement!
  3. Listening and Observing are the keys to influencing the container.
So most of the time in the workshop is spent listening and observing: 1) Understand yourself and each other by creating and sharing influence maps. 2) Create a clean slate to start afresh. 3) Understand your and each others' Personal Vision. 4) Working as a group, create a compelling shared vision for moving forward. 5) Supplication.

Influence maps and Mandalas are both visual representations (or information radiators, as Agilists would call them). The Influence map represents your life to date, and the Mandala represents either your personal vision or the shared vision of your container.

The workshop follows this approach:
  • Check-in
  • Introduction to The Influencers Mantra + Temenos
  • Influence Maps - draw and share the story of your life 
  • Clean Slate - recognize and forgive the failures of the system and your own failures to the system
  • Personal Vision - draw a Mandala and share your vision for moving forward at a personal level. 
  • Compelling Shared Vision - create a Mandala for the container / organization / group
  • Supplication 
  • Theory - Personalities of Influencers or Archetypes and Forces of the container or patterns in the change process
  • Check-out
By the end of the Personal Vision exercise, we understood ourselves and each other so well, that we could talk to each other about anything, without fear or insult! I call this state Deep Trust. It's amazing. It is the perfect state for creating a compelling shared vision for the future.

Supplication was perhaps the hardest to grasp. "Supplication" is the process of bowing down in prayer. It represents a humble attitude towards the organization. I use the analogy of wooing a woman. I remember the night I met my future mother-in-law. There were only two chairs in the room, one for her and one for my future wife, so I literally sat at their feet! It seemed a bit a odd at the time, but it helped create a lasting, positive impression. In the successful change initiatives that I have coached, I have taken a similar approach, offering information, while encouraging those doing the change to figure out the best direction without telling them what the answer should be.

I came home exhausted, but full of energy and enthusiasm for this approach (and for my own future vision). I started making changes right away in my life and in how I deal with people; these were also noticed immediately. The approach seems to resonate. Everybody I talk to about it seems to get really excited: Connecting with your friends, colleagues, co-workers and even family members seems to be a deep need for many people. And I still ponder the question, what would your company be like if your top leadership deeply trusted each other and truly shared a common vision for the future?


alx said…
Sounds like an interesting journey could you give more detailes about each step the workshop to be able to do it with my new team?
Peter said…
Hi Alx,

Good question! Couple of suggestions:

InfoQ has talk by Siraj on the Inflencers Mantra

I will be assisting him at a workshop at Glasscon on June 8.

If that doesn't work for you, why don't you contact me offline, e.g. via email or twitter.

Best, Peter

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…