Be a Lighthouse

I’ve always thought of myself as a problem solver. I enjoy solving puzzles, mending broken things, finding ways around an obstacle… you name it, I’ll fix it (or try at least). I love a good challenge; I’d fixate on a problem until it’s fixed! (or at least until my enthusiasm runs out).

Reflecting on lessons from Coaching 101 made me realise, when it comes to coaching, we “fixate” on the person, NOT the problem. “Coach the person, not the problem”, echoes in my head. I learned that it’s simply because, people have insights, problems don’t.

 

So how do you coach a person? I’m still learning but picked up a few pointers during the session.

1.    Clarity – There must be clarity on the objectives of coaching. What are we trying to achieve?

2.    Care – The person we’ll be coaching, needs care. We need to be concerned for them, and their well-being. The focus is on the person, not the problem.

3.    Forward – We want to help the coachee move forward. Help them find a path towards their destination.

 

The picture of a lighthouse came to mind as I reflected on these points. A lighthouse helps to provide clarity on a foggy night, guiding a ship towards its intended destination. And just like a lighthouse, a coach isn’t responsible for steering the ship, a coach is just a shining light to provide clarity.

 

“Be a lighthouse rather than a lifeboat. Guide by example, and let others find their own way.” -Barbara Kipfer













Comments

Post a Comment

Popular posts from this blog

Questions... Questions... Questions

Image
Asking good questions is a key skill in coaching. I learnt in webtorial 12 that questions have the power to trigger a mental reflex known as “instinctive elaboration”. An “instinctive elaboration” is when the brain, for a brief moment focuses its resources solely on answering the question asked. This got me curious and I decided to look into “instinctive elaboration” a little further to see how I could leverage this mental reflex in a coaching conversation.  I discovered that while questions can cause the coachee to experience “instinctive elaboration”, something they have no control over, their response is absolutely under their control. The quality of the questions we ask as a coach could either lead the coachee to think deeper and initiate profound shifts in thinking OR it could cause further confusion and maybe even anxiety for the coachee. Good or even power questions allow us to harness the power of the coachee’s brain to spark deep thinking, creating opportunities for perspe...
Read more

Explore Coaching Models

Image
Coaching models… what are they and why do we need them? Coaching models are essentially a framework of sorts to provide a structured approach to the coaching process. A coaching model can help a coach prepare and plan for a coaching session, help guide the coaching conversation and help a coach stay focused.  I realised there are many models out there and there isn’t a “one size fits all” model. But, while looking at some of the models, I found some similarities. They each have some form of the following components; - Establish a goal - Explore options - Enact a plan While coaching models are designed to provide a framework, a structured approach to coaching, I believe as coaches, we should allow a model to constrain us. Coaching isn’t a “linear” process, coaches need to be flexible and flow with the coachee… not the coaching model.  The model is like a vehicle we use to get our passenger (the coachee) to their destination. As the driver, we need to pay attention to wher...
Read more

Neurological Levels

Image
  It took me quite some time to properly process the lesson and it dawned on me to try and find something familiar or a metaphor, something I can easily relate to, to help summarise my learnings for the webtorial. To help me understand the lesson better in this particular instance, I realised applying this framework in coaching is like trying to “debug” a faulty software code. Software codes are basically a collection of “instructions” and algorithms that are put together to perform a certain task. Without going into much technical detail, software codes are structured into parts or levels, each part/level is designed to perform a certain function. Some parts/levels need to work with other parts to complete a function, while others may work independently. Collectively, they come together to make the software whole. Like most software (or applications), there is a “user interface” that we interact with, the part that we see, touch and feel, and then there’s the part we don’t see, th...
Read more