Why I coach Climate Tech.

First and foremost, I have always worked in tech. I started my career as a software developer way back in the late 90s. I was lucky at that time to join a team that was practicing something that was considered cutting-edge at the time – Extreme Programming, the grand-daddy of Agile Software Development.

Working on an agile software team delivering products to users and customers taught me so many valuable lessons. In particular, I learned how important it is that the people who make decisions about work priority and scope be trusted and collaborative with the people who actually do the work. I also learned that it is deeply painful (dare I say heartbreaking?) to learn that the work you do hinders or holds back the people that you intend to help. To me, the connection between customer, product/program/project management, and delivery is a “win for all” relationship that is always worth developing.

After 10 years of writing code, I came to realize that I was happier and frankly better at navigating complex people systems than software systems. I transitioned my career to coaching and consulting on digital transformations. This involved being parachuted (I mean this, I worked at a startup) into client environments along with a small team of really smart software developers, aiming to initiate a change in both technology and ways of working. In this deeply empowering environment, I grew to become a senior leader and people manager – all while being one of the top billing consultants at the company. It’s hard to reduce that experience into a handful of lessons, but I will say this… this is where I learned to fully accept responsibility for my words, feelings, and actions. Where I learned hard lessons of what can happen when power is held unconsciously. It’s also where I came to another clear realization, that “coaching” is a profession and that I needed to learn and claim that craft for myself. I’ve learned so much from Integral Coaching Canada, Strozzi Institute, as well as the amazing coach trainers of ICAgile.

Throughout it all, the importance of teamwork in the truest sense of the word became clear. When working on uncertain and complex problems, having a team that you can depend on and that you trust – this is where magic happens. Whether at the leadership table or working together on a complex piece of software or connecting with some of my favourite coaches – gather smart, motivated, trustworthy people together around a goal or a problem… and then, get the hell out of their way.

Three years ago, now a Professional Coach and having launched my own business (InsideOutAgile) five years prior -coaching and consulting with private and public sectors on digital transformations – I came to another very clear realization: if we do not come together to address the impacts of climate change, nothing else we do will really matter within a few generations. At that moment, I decided that I would work exclusively with the mission-driven companies that are addressing humanity’s most pressing problem. I haven’t looked back.

So – finally – why do I coach Climate Tech?

  • Because I know what it takes to make a shift from scientist/technologist into leadership/management. I’ve done it. I’ve helped others to do this more than once.
  • Because I know that the complexity of tackling climate change means leaders of Climate Tech must be able tap into a high level of trust and collaboration (inside and outside their organization) to get the job done. That’s work. Especially as you scale up.
  • Because I know that we are asking Climate Tech to operate with a level of accepted responsibility that is above and beyond what we experience in most organizations. This doesn’t happen by accident. It starts at the top and is designed into the organization’s way of being and working – both inside the org and outside the org.
  • Because I know Climate Tech leaders sometimes need a steady hand to work with them through tough times by leaning into their mission and values. In such moments, a little coaching can go a long way…

Just Tell Them What You See

So much of coaching and leadership is defined in those moments when our circumstances are most difficult.

When it comes to difficult circumstances, there are many schools of thought. There are no lack of well intentioned and thoughtful ideas, opinions, and frameworks to support us: crucial conversations, emotional intelligence, integral theory, radical candour, psychological safety, conscious leadership, systems thinking, spiral dynamics, etc.

While these are good things… they are, at the same time, also “a market”. And these markets are constantly calling on our time and energy on the topic of difficult circumstances. To say the market is overwhelming would be understating the case. So that I would humbly offer that when circumstances are difficult – the most impactful and compassionate way to approach is really quite simple.

Just tell them what you see.

Telling them what you see isn’t controlling, clever, or kind… it is purposeful and humble. It means holding the truth of what you see, while at the same time holding the truth of your partial sight with purpose and intention. In my experience, telling them what you see naturally invites others to offer what they see as well.

The hardest part for me in these moments is letting go. Letting go means freeing myself of all the beautiful ideas, opinions, and frameworks intended to support me. It means letting go that there is a “right way” or “best way” to address difficult circumstances.

Letting go also means digging deep within myself so that do not offer what I see from a place that seeks to feed my insecurities. It also means accepting myself when I realize (too late) that I did feed my insecurities. It also means accepting myself (and the other) when I realize that my offer surfaced an insecurity in the other person. The more I practice this, the more I find myself both apologizing and forgiving with genuine love and integrity. There’s love and forgiveness involved in this core practice.

And so, when I reflect on the difficult circumstances in my life… I now intentionally seek out the space to distill with simplicity: What is it that I see? Who do I need to tell? What do I need to let go?

And then… I tell them what I see.

Manager, Mentor, or Coach – What’s my leadership style?

Last week, a group of us gathered for our very first Leaders’ Circle Session – where we discussed and shared collectively our experiences with developing and growing our leadership style inside Agile organizations. The discussion was framed around three different leadership stances…

Armed with these different approaches, we each explored our “current way” as leaders in more detail. Throughout this exploration, we surfaced pressures (internal and external) that drew us as leaders more towards the left (Management). We also surfaced an invitation to shift to move towards the right (Coaching) from our Agile mindsets. This lead us to each defining our unique “new way” and to determine what actions we might wish to take to transition from the left towards the right skillfully.

While it is difficult to replicate the experience of our session, it’s worthwhile sharing the actions we surfaced during our coaching circle. For deeper exploration of your leadership style… please consider the practices proposed below and choose what serves you best.

Actions for exploring (and developing) your Agile leadership style:

  • Take a moment in your day to reflect on that day’s interactions. How much time did you spend managing, mentoring, and coaching today? What was the impact of those interactions?
  • Did you engage in a different approach depending on the situation? Depending on the person? What patterns do you observe stepping back? What assumptions underlie your approach?
  • Have you ever clarified for yourself AND with your colleagues / boss the expectations in your role? How do you know “what’s needed” in the moment?
  • If your colleagues / boss were to describe your leadership style in a few words, what words would they choose? What impact does your leadership style have within the team from their point of view?
  • Identify a situation where your desire is to establish more of a servant leadership approach (leaning more on coaching skills than mentorship and avoiding management approaches)… what conditions would need to exist to support? What can you do to create those conditions? Take the time to prepare yourself (and possibly others) before trying it out.
  • Become more aware of your approach “in the moment” by building awareness of what you offer in response moment to moment. Are you “instructing” (Managing)? Are you “suggesting” (Mentorship)? Are you “exploring with curiosity” (Coaching)? Note: Building this muscle of awareness doesn’t need to happen in the workplace – can just as well be applied to personal relationships like parenting and friendship.

To close, I would like to offer gratitude to those who participated in this inaugural Leaders’ Circle session… your engagement and courage to build upon the ideas presented improved the calibre of the topic for us all. I am looking forward to the next Leaders’ Circle session… stay tuned – coming in May!

New Leaders Series – Part 1: Shift in Stance

After years of hard work as a software developer and high performing team member, you’ve found yourself facing a whole new set of challenges. You are a leader (architect, team lead, scrum master, mentor, manager) on your team.

Looking back, everything that you’ve done along the way has supported you to get to this point. You’ve never backed down from challenge and have embraced the uncertainty of solving problems in code. You love the focus that comes with being able to tackle these problems with confidence. You’ve enjoyed the satisfaction that comes each and every time you’ve transformed an idea into a solution.

However, all the skills you worked hard to hone in yourself reflect your stance as “expert practitioner” and while expert practitioner skills are foundational to your role, these are not the skills that you will need to grow in order to succeed as a leader.

And no one told you this. When you got the promotion, no doubt your manager told you of the confidence he had in your abilities; however, your leadership up to this point has been fundamentally built on your ability to hone your craft expertly.

Your new role requires a shift in stance. You are now responsible for supporting others to do what you did so well. There is a hidden assumption there; indeed, a fundamental change in how you perceive your value on the team.

Your work is less “about you” and more “about them”.

This shift from “me” to “we” isn’t a small change in thinking and being. It’s one that I’ve seen many new leaders struggle with as they are drawn instinctually back to the joy derived in expressing their craft…. the satisfaction and joy they experienced in being “the guy who solves the problems” rather than “the guy who enables others to solve problems”.

In this series, I plan to explore some of the new skills that young leaders might consider as part of their new practice – assisting them to make this shift from “me” to “we”. It is my sincere hope that my own lessons (sometimes learned the hard way) can be of service to others beginning on this journey.