I have spent the last couple of weeks on the road – travelling to spend two days each with two of the five organisations that are participating in my remote coaching experiment. The time I have spent face to face with these wonderful people has been really humbling and continue to help me validate the reasons that I launched the experiment in the first place. I am learning some really important lessons that will help me shape a possible service and I’d like to share them with you.
#1. It doesn’t really matter where you start the conversation
I once was asked “should we focus on problems or improvement?”. This experiment is teaching me that – if you are interested in a sustainable effective improvement – you cannot seriously explore improvements without really understanding what you are making better i.e. the less effective starting point or problem.
I have experimented with being Problem Focused with some participants in some cases and Solution Focused with others – to get some anecdotal evidence of what is more effective. So far, I think both are equally effective. But hugely dependent on how the conversation is facilitated and also the openness and empathy in the groups.
Ultimately I am learning that you start where you feel most comfortable and what really matters is the commitment to continue the conversation.
#2. People have day jobs, respect that
Every ‘Improvement Discovery’ session I have facilitated emphasises that everyone has day jobs that affect their bandwidth to work on the things we want to improve.
I say this to help set expectations of the level of involvement – at various times – that people may experience from themselves and others.
Despite knowing this in my core, I sometimes find that I feel deeply frustrated when I cannot see any evidence of progress on the items that people signed up to. I wonder to myself:
Don’t they care enough about this problem to drop everything and fix it?
Don’t they respect me enough to do what they committed to?
Then I catch myself and remember that they have day jobs and whilst this is important for them – because they said it was – they also may be having a tough time trying to balance both commitments. Immediately this triggers an empathic response. How can I help them find the time to make the thing they want better, happen?
#3. Being remote requires emotional control
One of the more difficult things that I am experiencing is that, because I’m remote and not physically around the organisation and people, I am less able to easily access the non-verbal communication that is abundant with co-located group. I struggle to sense what is keeping people busy or what is distracting them.
I react in various emotional ways to this lack of input. First I may feel angry – that they are not ‘keeping up their side of the bargain’.
I may also feel unappreciated because ‘don’t they know I am sitting here waiting for them to pull my help’.
My main learning here is to come back to the context – and this is why it is really important to have context – so that I know that this is not personal. I am also learning that recognising that I have a feedback gap is very important. It invites me to share what I am feeling with the group and invite help to address the feedback gap.
#4. Getting Invited is harder than simply barging in
The core of my approach is that people themselves address the exploration of the improvement they seek. We find what we want to improve, prioritise them and then form working groups around each one to frame, explore and discover what concrete actions can be taken to make the improvement. I can facilitate, guide, collaborate, teach, coach and listen – or not – to the extent that they need me to – but only if I am invited to do so. I call this ‘pull’. This is different from ‘push’ – which is more about me interrupting people – remember they have day jobs – imposing what I think they need. The coaching approach requires that participants understand this is the offer and are comfortable with pulling my involvement.
For the first bit – understanding the offer – I am learning that I need to be more explicit that I am available to be invited and this is really the main way I get involved and being clear about how they can make the invitation – scheduling a meeting, chatting on IM etc.
For the second bit – people feeling comfortable – I am learning that people find it hard to pull even when they are clear that is the way to get my help. My understanding of why this is the case is evolving but so far being ‘too busy’ keeps coming up as a primary reason.
#5. A month is not very long to change everything
All the groups I am working with have 30+ members and cover almost the entirety of the functions to get stuff out of the door.
You can imagine that so many people have many things they want to improve. Some of these things are cross functional like ‘understanding of the value of what we are building’, others are specific to functions like ‘we need to increase database unit test automation’.
This experiment is 30 days long and is designed almost exclusively for my learning. During this time I want to learn what works and what sucks about working remotely – both for me and my clients. The only way I can really learn is by doing it. So the doing is necessary but kind of no the aim. That said, once you ask people what they want to improve you better damn well have a plan to help them get those improvements.
So I am learning to be clearer that their journey of continuous improvement has no end date. It is neither constrained by time nor space, but simply by their commitment to work towards better versions of themselves. I simply jump off that line in 30 days as they continue.
Please share your experiences of working remotely in a coaching role or as someone working with a remote coach – I can use all the learnings I can get!
If you are interested in keeping up to date with what I am learning in this experiment – please consider signing up to my email list – I won’t ever spam, sell, share or otherwise pimp you details. Also consider following me on Twitter.
Featured Image By: squidish – CC BY 2.0