Agile at the Speed of Trust – An Overview

This content is syndicated from LeadingAgile by Peter Callies. To view the original post in full, click here.

Guest Post from Peter Callies:  As LeadingAgile grows, you are going to start seeing more posts from people other than me.  One of these days we’ll get Dennis to do a post… probably Rick as well.  One of the things I’ve considered for a few months is the idea of having one or two of my clients do a post.  Peter is super smart and really gets this stuff and we’ve become friends over the year I’ve worked with his company.  

This is the first in a series Peter plans to do on trust… specifically around Stephen M. R. Covey’s book ‘The Speed of Trust’.  I’m a huge fan of both Stephen Covey and his son Stephen M. R. Covey.  What could be a better way to kick things off, and introduce Peter Callies, than to go deep into one of my favorite authors while exploring a topic critically important to people and companies everywhere.  

In early 2011, a company made a major investment in Agile.  An intentional decision was made from the executive level down to the grassroots that an Agile approach would be used to develop products.  An investment in training, months of coaching, and lots of hard work led to measurable results.

At about the same time, the company recognized that it had an issue with trust within the company.  Instead of burying their heads in the sand, hoping the issue would resolve itself like I’ve seen done other places, the leadership team confronted it head on.  The company brought in training and coaching help from CoveyLink, formally reflected on trust behaviors at regular intervals, conducted “360″ assessments — even made trust part of their performance management processes.

Those two decisions and the actions undertaken to become agile and to build trust have had a profound impact on the company’s culture and ability to build products.  Because Agile and trust are behaviors, not destinations, the company continues to work at them and is continuously conscious of them.

I believe that Agile and trust are mutually reinforcing.  In this post, I’ll provide an overview of The Speed of Trust and how it relates to Agile.  In the future, I’ll delve into specifics.

In his book The Speed of Trust, Stephen M.R. Covey puts forth an argument that “trust is not some soft, illusive quality that you either have or you don’t; rather, trust is a pragmatic, tangible, actionable asset that you can create[i]”.  While many, including me until recently, think of trust as a squishy, nebulous concept that is difficult to measure, Covey looks at it a measurable formula where trust impacts speed and cost.  When trust goes down, speed goes down and cost goes up.  When trust goes up, speed goes up and cost goes down.

↑Trust = ↑Speed ↓Cost

↓Trust = ↓Speed ↑Cost

Covey goes on to describe trust taxes and trust dividends.  These are the sometimes hidden variables that quantifiably increase or decrease trust in measurable ways.  As an example, he puts a twist on the traditional business results formula that says results (R) equal strategy (S) multiplied by execution (E).  He says (where T is trust):

(S x E)T = R

In this case, high trust (i.e. trust above 1.0) can be an enhancer of strategy and execution or low trust (i.e. trust below 1.0) can be a deterrent no matter how good the strategy and execution are.

The Speed of Trust uses a model based on waves of trust.


Covey, Stephen M.R.; Merrill, Rebecca R. (2006-10-17). The SPEED of Trust (p. 33). Simon & Schuster, Inc.. Kindle Edition.


The outer waves evolve from the inner waves – it’s difficult to successfully start with organizational trust without relationship trust and it’s difficult to build relationship trust if you don’t trust have self trust.

Self trust relates to our own credibility.  The book focuses on four cores of credibility: integrity, intent, capabilities, and results.  This is the foundation of being able to effectively contribute to an Agile team.

Relationship trust is based on behaviors, demonstrating to others that you are capable of trust.  You need to walk the talk for others to trust you.  Many of these behaviors really resonate with me when I’m thinking about Agile and trust together.

Organizational trust deals with aligning an organization’s structures and systems to decrease trust taxes and increase trust dividends.  This is where leaders can impact the ability of Agile to impact product development from top to bottom.

Market trust reflects an organization’s reputation and trust level of external stakeholders.  If you’re defining “organization” as a company, this wave of trust could get into high-order Agile adoption.  However, looking at “organization” on a smaller scale (e.g. Product Development) with external stakeholders that are internal to the company (e.g. Marketing, Operations, or Account Management) might make market trust easier to grasp.

Societal trust is pretty self-descriptive.  It deals with contributing to the community at large. As with market trust, this wave can be applied with different definitions of “society”.  Society may truly be the city, country, or the world you live in.  It could also be the company you work in.  Or maybe it’s a loosely knit group with a common interest like the Agile community.

Although the relationship between Agile and trust has been percolating in my mind for months, this is the first time I’ll be writing about it.  I’m looking forward to the process of developing my thoughts and getting your feedback.


[i] Covey, Stephen M.R.; Merrill, Rebecca R. (2006-10-17). The SPEED of Trust (p. 2). Simon & Schuster, Inc.. Kindle Edition.


Leave a Reply

Your email address will not be published. Required fields are marked *

3 × three =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch