What is the best way to influence, based on my experience

Today I would like to share with you a few thoughts about the best way to influence others, based on my experience.

To give you more context, yesterday I came across an article with a very interesting quote from Albert Einstein saying:

“Leading by example isn’t a way to influence, it’s THE way to influence.”

This quote got me thinking, so I carried out a quick retrospective of all the leaders, managers and peers I came across during my career. The aim was to identify which was the most important characteristic that made them great influencers.

As you know, we live in a world of constant change and it’s vital that we keep inspecting and adapting to succeed from a business, professional and personal perspective. So, why is it that, with all our current resources (e.g. Training about Coaching, Influencing, Mindfulness, etc.) influencing others can still sometimes be so difficult? After all, we are already spending most of the time actively listening and communicating with people to influence them (The Art of Influence: Lesson 2 – Listening & Communication Skills).

What is missing to become a great influencer?

My personal belief is that the best influencers I have worked with (following Albert Einstein’s criteria above) were always the ones that led by example. The ones that didn’t ask or try to influence without doing it themselves. Can you ask a single person or a group of people to change or do something if you don’t do it yourself? Is it realistic to expect any behavioral change if you are not the first one demonstrating and giving the first step? How do you think they would see you, what would they think or how would they react in the long run?

For me, the best way to influence and create a huge impact on my day to day work is to show the strength of my convictions by doing myself what I would like others to do; e.g. Changes/Attitudes I would like to see in others.

One great example of influencing by doing is when working with non-development teams and convincing them to adopt Agile. Why I am saying this? Because non-technical teams’ common reaction will be “We are not developers and this doesn’t work for us!” At that moment, what I do is just showcase how my own team works (since we are not a development team) and help them see how adopting Agile could make their day to day work easier. After a few moments, they are the ones saying “Wow! Can we do the same? Can you help us?”. In the long run, the results are stunning and their feedback is great with the will to improve more.

Another example is how my team works, and our overall level of trust and commitment. It’s normal for a leader to provide feedback and challenge the team as well as team members. In our case, they know they can do the same with me. It took some time to build this level of relationship, but nowadays if we need to put in place any action or deploy any workstream, we challenge each other, and even if the solution is not the one initially proposed by me, I will be the first one doing it. This creates a sense of high engagement because they see me as an example.

So what made you be a successful leader? Why not share your experience on how you made it and why you think it worked? It would be great to hear your thoughts even if you don’t agree with this approach.

#Agile #Lean #Leadership #Influence #Change #ContinuousImprovement

Today’s Thought on Leading Change

While watching a training about Leading Change by Britt Andreatta where she shared an amazing thought that I totally agree with her. This is something that we need to keep always in our mind and that besides applying to driving change teams also applies to any team.

“If you deliver what you promised you build more trust to future change initiatives. If you don’t you have a more challenging run. So, listening to feedback is really important.”

Don’t forget that the real impact is very important to your team reputation.

#Agile #Lean #Change #ContinuousImprovement

Agile Coaches Myth or Reality?

This article is really interesting since the subject to write about this was born during one of the Lean Coffee Portugal sessions when someone raised the subject/question “What is a difference between a Scrum Master and an Agile Coach?”.

Meanwhile, seeing as this can potentially be a long and interesting debated subject after chatting with my colleague Cornelius Engelbrecht  I decided talk with him if he would like to accept the challenge. That he did 😉

So, we would like to start with a quick question where you ask  yourself:

“What is an Agile Coach? Are they a myth or reality?”

Excalibur

The reason why we are asking this is because we can say that Agile Coach is a recent role and when we say this we are talking a few years and not like Developer or Project Manager that are with us for a long period of time.

Also, we think that we have people that are confused regarding the role definition and what are the best characteristics for a good Agile Coach.

To start we want to give you some context behind our opinions. We are not sure if you realised that nowadays everyone have on their LinkedIn, CV or role Agile Coach. But do they know what is the real Agile Coach role?

Well… We can say that we became curious, so we started to dig and get more information around the label Agile Coach. Our first approach was discuss this topic with a lot of people around the world and by coincidence or not, we had the need to also hire Agile Coach’s for my team.

What we discovered was kind of funny. Well… Not funny but curious.

  • People that updated their role after reading Agile books.
  • People that use the label on their current role even what they do is not related.
  • People that use the table Agile Coach since they don’t like the name Scrum Master.
  • People using the table Agile Coach since in Kanban there is no Scrum Master.
  • Role updated just to apply to a job without any experience.
  • People who collect certifications to prove they are a Coach.
  • The main reason we see is people that updated their role because everyone is doing it (Buzz word from the moment).

So, we would like to return to the question made during the Lean Coffee Portugal session by providing the definition of what is a Scrum Master and as you can see we don’t need to invent the well since is already well defined as we can see by the Scrum Guide definition (image below).

SM Scrum Guide

 

Now let’s have a look at the Agile Coach role from our perspective:

An Agile Coach helps individuals/teams/departments/organisations so they can become better and be proud of what they do.  One does this through being a guide & change agent who applies Lean/Agile/Continuous Improvement practices which are relevant to people’s journey.

Attributes of an Agile Coach:

  • Great listener
  • Patient
  • Impartial
  • Humble & always learning
  • Respectful
  • Not so much directing, more guiding (i.e. helping people find ways/answers not giving answers)
  • Non-judgemental
  • Fearless (i.e. able to communicate  with confidence at all levels in the organisation be it CEO, management and team members)
  • Flexible (“being able to think outside the box”)

Quick re-cap:

Scrum Master is mainly focused on guiding one/two teams (including Product Owner)  in using Scrum.  Agile Coach is a very different role whereby he/she has a wider organisational view when coaching individuals/teams/organisations on improving (becoming better at what they are doing) whilst using Lean/Agile/Continuous Improvement practices.

Why did we want to become an Agile Coach?

Funny enough we did not know we wanted to become coaches, what we wanted  is to improve our ability to help people in achieving more.  We started to look into why people understand, react, how they learn, absorb and believe in what they do and how to embrace change  – this is where it began for us…