Agile Conversations
'Agile Conversations' book by Douglas Squirrel and Jeffrey Fredrick

Agile Conversations

Big 5: high trust, low fear, clear why, definite commitment and accountability 


Why Agile or DevOps transformations often do not bring the expected results? Many companies implement all the right practices of high-performing teams, but do not see results because they have not fixed the cultural glue, the very thing necessary to make those other practices work. The key to success is not only to adopt good practices, but also to have difficult conversations with people that build the right environment for these practices to work.

“Fundamental shift in how people had to think about how they interact, how they collaborate and work, and if you don’t spend time changing people’s behaviors, you don’t spend time changing culture and how people make decisions, all of this falls flat.”
Michael Gale, 'Why 84% Of Companies Fail At Digital Transformation'

It's not a big secret that in the IT industry most of the so called 'technology' problems are actually people's issues. Conducting difficult conversations with an attitude of transparency and curiosity helps organisations build lasting trust, reduce fear, clear purpose and finally achieve the results you want.


Difficult conversations

There are Five Conversations, crucial discussions of the five key culture characteristics that all high-performing teams share - not just software development teams but all human teams.

The Five Conversations are:

  1. The Trust Conversation
  2. The Fear Conversation
  3. The Why Conversation
  4. The Commitment Conversation
  5. The Accountability Conversation


#1 The Trust Conversation

No alt text provided for this image

Building trust is - for sure - the prerequisite to build a people-oriented organisation with high-performing culture.

Everyone should believe that those we work with, inside our team or outside, share organizational goals and values.




#2 The Fear Conversation

No alt text provided for this image

Fear is one of the biggest inhibitors of transformation. People can feel fear of failure, building the wrong product or feature, disappointing managers and many other disasters. Nevertheless, this fear paralyzes the team, inhibiting their creativity and collaboration.

That's why you should openly discuss problems in your team and its environment and deal with those obstacles.


#3 The Why Conversation

No alt text provided for this image

Building 'why' gives your company and team a strategic direction that guides big and small decisions and is a strong motivation for a success. It's worth remembering 'Start with why' by Simon Sinek.

So, the company and the team should share a common, clear purpose that inspires people.



#4 The Commitment Conversation

No alt text provided for this image

Execution of the transformation, or rather – beginning of the journey, is usually the first issue you will encounter when diagnosing a troubled team. You will probably hear that new processes are slowing down your people or that users have not seen improvements in months. The reason is that if you have not built up trust first, reduced fear, and agreed on why, execution will only get you to the wrong destination faster.

To build commitment you should regularly and reliably announce what you will do and when.


#5 The Accountability Conversation

No alt text provided for this image

By building trust, removing fear, defining why and honouring commitment, your team has become much more autonomous and unconstrained. We call this a self-organising team. But now the team needs an accountability. This is an obligation to explain work results. Each team member is empowered to make their own decisions about how to allocate time and energy. However, with this empowerment comes an expectation to share what those decisions are and why they were made.

This is why our intentions should be openly presented to the team and publicly explained how our results compare to commitments.


It's worth talking

The Five Conversations address attributes that give teams everything they need to use modern people-oriented practices. They allow you to smoothly adapt to changes in requirements and present your customers with working software that solves their real problems. And these are exactly the characteristics missing from the teams we often see around, where agile standups are places to hide progress rather than share it, where sprints are part of a rigid water-scrum-fall plan, where the customer’s purpose is lost in a sea of irrelevant scenarios, and where frustration is the only one shared emotion in the whole organisation.

The Five Conversations could be the way to develop the five key attributes of high-performing teams: high trust, low fear, clear why, definite commitment and accountability.

Agile conversations by Douglas Squirrel and Jeffrey Fredrick

'Agile Conversations: Transform Your Conversations, Transform Your Culture' book by Douglas Squirrel and Jeffrey Fredrick gives a practical guide to using the unique human power of conversation. If you want to be successful with Agile and DevOps, stop following meaningless rituals that don't deliver results. Instead, build effective high-performing team using the Five Conversations.

To view or add a comment, sign in

More articles by Michal Florys

  • Wrong Fit, Right Fit

    Jaki jest koszt braku zaangażowania pracowników? 7,8 biliona dolarów! Ile kosztuje posiadanie miejsca pracy, do którego…

    2 Comments
  • Konflikt wartości w cyfrowej organizacji

    Mark Schwartz w „Adaptive Ethics for Digital Transformation” wyjaśnia meandry cyfrowej transformacji stawiając akcent…

    1 Comment
  • ITIL Master, czyli podróż z zarządzaniem usługami IT

    ITIL to bezapelacyjnie najpopularniejsze i najszerzej akceptowane na świecie podejście do zarządzania usługami IT i de…

    1 Comment
  • (Delikatna) sztuka biurokracji

    Jak zachować kontrolę nad organizacją, nie pozbawiając jej szczupłości (lean), umiejętności uczenia się i chęci…

  • ITIL 4: Knowledge Management

    Zarządzanie wiedzą to dostarczanie właściwych informacji właściwym ludziom, by dokonywali mądrych wyborów. Tylko bądź…

  • ITIL 4: Problem Management

    Któż nie ma problemów? Usługi też je mają. Mają błędy, wady i inne niedoskonałości, które mogą powodować przerwy w…

    2 Comments
  • ITIL 4: Incident Management

    Usługa dla klienta ma być użyteczna, ma działać, być wydajna, bezpieczna i gwarantować ciągłość działania biznesu. A co…

    5 Comments
  • ITIL 4: Service Level Management

    Zarządzanie poziomem świadczenia usług to 1 z 34 praktyk zarządzania usługami IT zdefiniowanych w bibliotece ITIL 4…

    4 Comments
  • The future is built on ITIL

    ITIL is the most widely adopted guidance for IT service management for 30 years. And now, ITIL4 has been launched, with…

  • The Unicorn Project: The Five Ideals

    ‘The Unicorn Project’, a new novel by Gene Kim is all about developers, digital disruption and thriving in the age of…

    24 Comments

Insights from the community

Others also viewed

Explore topics