Getting Permission to Coach

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

Ever walk into a room and feel like no one is listening? It absolutely drives me nuts. Sometimes it happens in a lecture hall, sometimes a classroom, the worst is when it happens in a small conference room full of people you are being paid to coach. One of the things I’ve come to realize over the years is that no matter how credentialed your are, no matter what you know or how much you are getting paid, no one ever has to listen to you… you have to earn the right to be heard. Because I have a severe aversion to wasting people’s time, I’ve developed a strategy of sorts that I’ve found to be pretty effective and generally repeatable in most situations where you’ve got to have permission before someone will hear you. The formula goes something like this… Ask Questions Questions are interesting because they work on lots of levels. The most obvious is that you gain a ton of information and insight about how your audience understands their problem. Less obvious maybe is that good questions will demonstrate that you deeply understand your subject matter.

Good questions communicate a desire to understand and create a real opportunity to build trust and deeper connection. They help people feel heard and understood. People that feel heard and understood are generally more open to hearing what you have to say. But here is the deal… you are not just asking any questions. You are using your expertise and understanding of common problems to dig into places where you are likely to find trouble. The goal will be to use what you’ve learned to setup the next phase of the conversation.

Introduce Ideas At some point you need to start transitioning into problem solving, but we still don’t have permission to tell anyone how to do anything. No one has asked for our help. There is a transition line I’ll often use here that seems to work. I’ll ask the room for permission to ‘explore some ideas’ with them. We aren’t trying to solve their problem, but we may have earned the right to teach a little. It is much less threatening to discuss an idea than to go into the real issues. We can talk generically about how and why process works or how and why process fails, without having to tell them anything about themselves. The trick though is that we must dynamically teach around the problem areas the group shared with you during the question phase. If they have a problem with product ownership, you should teach about Product Owners. If the group is having problems forming teams, explore how and why teams work.

Get The Ask Hopefully, if all has gone well to this point, we’ve created a little cognitive dissonance. Cognitive dissonance is when people simultaneously hold two competing thoughts or ideas. The room should have a clear understanding of their current reality and a clear understanding of a possible vision for a future state. The idea is to get people to the point where they want to have that cognitive dissonance resolved. It should be uncomfortable and prompt ‘The Ask’. ‘The Ask’ is when the room requests your advice on how to resolve the conflict. This is when you finally have permission to coach. At this point, and only at this point, can you begin to start laying out specifics. Now we can start talking about how to solve their particular problems and help them work through their concerns. You can directly link their problems to the specific solutions and lay out a strategy for helping them get there. Conclusion Like any technique, you can use this kind of approach for good or for evil. To help or to manipulate. The goal in any coaching situation is to build trust, strengthen relationships, and genuinely find ways to help. To make it work, you have to really care, really listen, and create a real opportunity to connect. I’ve used this approach with small delivery teams and rooms full of executives. It really works. People want to be heard, they want to learn, and if you can really listen to them and help them learn meaningful stuff, you just might be asked to help. Only when you’ve been asked to help do people tend to actually listen.

Leave a Reply

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

16 + four =

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

What People Say

“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 was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“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 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 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’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.”


“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!”


“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 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.”


“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...”



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