The recording of the closing keynote I delivered at VoxxedDays Singapore is published!
Let me know what you think!
I would be happy to deliver an improved version of this talk for you event 🙂
The recording of the closing keynote I delivered at VoxxedDays Singapore is published!
Let me know what you think!
I would be happy to deliver an improved version of this talk for you event 🙂

I tried a new experiment last month! I recorded a few podcast episodes:
Of course, I am interested in your feedback about that experiment.
Maybe you have ideas about change, or you have questions to ask, and maybe even you want to record the answer to a question with me?

When agile adoption struggles, cultural differences are often the first explanation that comes up.
Different countries. Different mindsets. Different ways of working.
But are cultural differences really the problem?
In this episode of Le Podcast on Emerging Leadership, I explore this question with Jérôme Bourgeon, an agile coach at Zenika, based in Singapore.
Jérôme and I share a similar conviction: national culture is rarely the real blocker when agile practices fail to take root.
What we see far more often is that:
Building trust, in particular, can take very different amounts of time depending on context. But that difference is not primarily explained by nationality.
In our conversation, we discuss several elements that have a much stronger influence on agile adoption than country-level culture:
We also explore the power of Appreciative Inquiry as a way to approach change differently.
Rather than focusing on what is broken or missing, Appreciative Inquiry helps teams:
This approach is particularly useful when working across perceived differences.
Not all differences need to be resolved or normalized. Some differences are deeply important to people and deserve to be respected.
Agile adoption becomes more sustainable when teams can:
If you are working in a multicultural environment or facing resistance to agile adoption, this episode offers a different lens.
Instead of asking “What culture are we dealing with?”, it invites a more useful question:
“What beliefs, relationships, and conditions need attention right now?”
If this topic resonates with you, feel free to reach out and share your experience or propose a question for a future episode. We can even record the answer together.




























Setting goals is easy. Creating goals that actually help teams focus, align, and make progress is much harder.
Over the past weeks, I have been asked the same question several times:
How do you create great goals?
In this episode of Le Podcast on Emerging Leadership, I explore this question through a very practical lens, using the OKRs approach (Objectives and Key Results).
OKRs are often introduced as a framework or a process to comply with. When that happens, goals quickly become disconnected from real work.
In this episode, I take a different approach: starting from impact, not from metrics or activities.
Rather than asking “what should we measure?”, the real question becomes:
To make this concrete, I use a simple example and the Impact Mapping approach to walk through the process of creating OKRs step by step.
We look at:
The goal is not to get the wording “right”, but to create goals that support better conversations and better decisions.
Used well, OKRs are not a management tool. They are a leadership practice.
They help teams:
If you are struggling with vague goals, misalignment, or goal fatigue, this episode will give you a practical starting point to rethink how you create goals.

Where to listen:
Using Narakeet, a product created by Gojko Adzic, the author of Impact Mapping. I created a less than two-minute video to explain the whole process.




























Making change in a team is often associated with authority, hierarchy, or formal leadership roles. But in practice, some of the most meaningful change starts from the inside, through everyday actions and choices.
In this episode of Le Podcast on Emerging Leadership, I sat down with Michael Reid, the narrator of the audiobook edition of Changing Your Team From The Inside, to celebrate its release and reflect on the ideas behind the book.
Beyond the audiobook itself, our conversation explored what it really means to act as a practitioner of change inside a team or an organization.
We discussed the importance of:
These are not abstract leadership concepts. They are concrete levers that anyone can use, regardless of role or title.
One of the key points we come back to in this episode is that Changing Your Team From The Inside is not a book for managers only.
It is written for practitioners.
People who want to:
The book, and this conversation, are grounded in the idea that leadership is not a position. It is a practice.
If you are looking for ways to improve collaboration, alignment, and satisfaction at work without waiting for permission or a reorganization, this episode will resonate with you.
It is an invitation to look at what is already within your reach and to start changing your team, from the inside.
Where to listen:




























In addition to electronic, paperback, hardcover, and team edition, Changing Your Team From The Inside is now available as an audiobook!
Michael Ried did an excellent job in narrating the book. I was even caught listening to him forgetting that I was on a review mission 🙂
The book is available on the platform you usually use to find your books like Amazon, Audible, or iTunes.
Please let people know about it!
And let me know what you think!

Forming a team is often treated as a logistical task: bring people together, give them a goal, and get started.
In reality, forming a team is a leadership act. And when people come from different functions, backgrounds, or organizations, it quickly becomes a real challenge.
In this episode of Le Podcast on Emerging Leadership, I sat down with Valentin Yonchev and Matt Takane from Red Hat Open Innovation Labs to explore a deceptively simple question:
How do you actually form a team?
Valentin and Matt have extensive experience building cross-functional teams in a wide range of contexts. Teams assembled:
Rather than sharing abstract principles, they describe practical ways to move from a group of people to a team that can actually work together.
In this conversation, we discuss:
Whether you are assembling a temporary working group or launching a longer initiative, you will find concrete ideas you can apply immediately in your own context.
During the discussion, Matt mentions the Open Practice Library, a valuable resource for discovering concrete practices that support collaboration, learning, and experimentation:
👉 https://openpracticelibrary.com
We also refer to the idea of pulling the Andon cord. Originally coming from Lean manufacturing, this practice is about making problems visible early, so teams can stop, reflect, and improve together rather than pushing through dysfunction.
If forming teams is part of your role, this episode is a reminder that teams don’t just happen. They are shaped deliberately, through attention, intention, and small but meaningful leadership choices.
Where to listen:




























While I was travelling to Singapore, I have been invited to discuss innovation with Eliott Danker on MoneyFM.
Thanks to Eliott interviewing talent, we touched on a lot of different aspects:

I had the great pleasure to deliver the closing keynote of Voxxed Days Singapore. During the talk, Going Open, I introduced Douglas McGregor theories on human motivation and management that he developed at the MIT Sloan School of Management in 1957.
The assumption in Theory X is that workers are lazy; they dislike and don’t want to work and do all they can to avoid it. As a consequence, if you agree with that assumption, your way of managing people, who have no intrinsic motivation and no ambition, the system needs to be “command and control.”
The assumption in Theory Y is that work could be as natural as play and rest; people seek responsibility and are able to direct themselves to deliver on their commitments. As a consequence, if you agree with that assumption, your management style is radically different, and the system could tend toward self-organization.
Theory X and Theory Y are self-fulfilling prophecies. Acting accordingly to the theory causes it to come true.
Reconsidering the way we are managing people in an organization is an essential ongoing exercise.
As an example, our actual reward system might perfectly fit the Theory X assumption, while we would prefer our whole team to live under Theory Y.
What about you?
What type is your organization?
What type are you?
Could I behave like X, because my organization is X?
Do you think my organization could change if I change my behavior?
It could be really interesting because X organizations suffer from a centralization flaw. And like spiders, if you cut the head, the organization dies.
By contrast, Y organizations are resilient like starfishes, if you cut an arm, the starfish will regrow it, and even more interesting the arm will regrow a whole new starfish, as all the knowledge needed is available to do exactly that.
Y organization are really like Open Organization.
Open Organization is the term coined by Jim Whitehurst, CEO of Red Hat for his eponym book published in 2015. The book written primarily for organizational leaders, demonstrates how open source principles are changing the nature of working and managing in the 21st century.
There are five characteristics of Open Organization:
How can we adopt those characteristics in our organizations?
I then proposed some of the approaches that you can find in the book, Changing Your Team From The Inside, to foster the change in your team and organization.

On May 31, 2019, I had the pleasure to deliver the closing keynote of Voxxed Days Singapore: Going Open!
Thank you to all the participants and organizers for a fantastic event!
I had the opportunity to sign my book, Changing Your Team From The Inside on the Red Hat booth, and to meet great people!

The title of the talk is Going Open to Support Your Digital Transformation, the slides are available here and I will update the post as soon as the recording is available.
The pitch of the talk: “Do you feel your organization, your team, and yourself are focusing on the right things or are you overwhelmed by the thousands of tasks that you need to do? What do you need to get your organization, your team, and yourself to continuously improve to get to the point of doing the things right? Going open is the best way to support your organization’s digital transformation. Going open is applying the principles of the open organization. Open is the antidote of the lack of focus and the lack of continuous learnings that is ailing organizations today. What are the differences between a centralized organization and an open organization? Learning about these differences can help you advance your objectives in your digital transformation. The open source development model is the root of the Open Organization. The diversity the open source model brings is an endless source of inspiration to transform your organization–and this is what this session will expose.”

Ratings and reviews contribute significantly to the success of a book — not a rocket science fact. When we go to platforms like Goodreads, we choose our next book based on the category, the title, the cover, the abstract, AND the ratings and reviews!
It seems that ratings and reviews account for a lot in our choices.
And because of all that, I need your help!
Could you please help the book Changing Your Team From The Inside to reach a wider audience?
It is straightforward:
I am asking that now because I am really proud of the second version of the book published at the beginning of April! I worked on the second version during the previous months with a fantastic team! John Poelstra and Michael Doyle did a tremendous job to help me improve the book! Thank you!
To celebrate, the second edition, the book is now available in Hardcover version on Lulu!
I chose to end all the chapters of the book, Changing Your Team From The Inside, with a section titled “Summary and Action”. The goal of those sections is to give you keys to act immediately on your environment. I heard great feedback about one of the practice. The practice is a way to guide one-on-ones when meeting new people. Another one is The Matrix of Principles that you could also test with the principles of the agile manifesto.
I also answered in a post to a question on how to create Team Agreements efficiently.
At the beginning of the month, I had the pleasure to participate in a fantastic event: Agile Games 2019. Here are three posts about the adventure: The worst presentation ever, OKRs! OK What?, Agile Games New England 2019!
A friend forwarded you the message? You can subscribe to the mailing list here!

In two previous posts, OKRs! OK What?, and The worst presentation ever, I covered sessions proposed during the Open Space on the third day of Agile Games 2019.
In this post, I would like to highlight the other sessions in which I found interesting “nuggets”, to use a term that my friend and colleague, Matt Takane often uses.
Jason Tice opened the event with a keynote about games for high performing teams. The games are built on the learning from Patrick Lencioni’s book The Advantage. In a nutshell, trust is the foundation of high performing teams. The ten ways collaboration builds trust are:
Jason had us played at each table.
The first player rolls two regular 6-sided dices and adds the total rolled to determine the storytelling topic:
2. A time you have made a mistake or failed
3. A time that you have received recognition
4. A time that you have helped a team member/coworker
5. A time when your manager or a coworker made you angry
6. A time that you had a great day at work
7. A time when you let someone down
8. A time when you were singled out or excluded
9. Something outside of work that brings you joy
10. A time when you were inspired
11. A time when you contributed to team success
12. A time when you recognized or appreciated someone else
The player then rolls the story cubes to establish common visual metaphors upon which stories for the topic will be based.
Each participant at the table tells a short story based on the cubes that were rolled. Everyone listen (recording the story by taking note is an option).
When the story is complete, the participants respond by providing ONLY appreciations.
Conclude with a round table in which participant share how they felt during the exercise and what they learned about themselves.
The last nugget. When you receive an appreciation, take a picture, if you use a service like google photo, the photo will show up in your feed in one year!
Erica Maguire proposed two activities.
The first one was the classic low-tech social network with a speed dating twist to run quickly the introduction and create the connection. For more details on how to run the activity, consider this post by Dave Gray.
The second one was about building bridges.
The goal is for two teams to each create half of a complete bridge. The acceptance criteria are:
You have 2 minutes to plan.
You have then 8 minutes to build the bridge.
You are not allowed to look at what the other team is doing.
You are not allowed to communicate with them.
After the build phase, each team brings his half of the bridge on the integration table for a review.
You then have 2 minutes for a retrospective with the other team.
You can propose another iteration with the adaptation proposed during the retrospective.
Matt Takane and Tim Beattie proposed an interactive session that simulates what they do at Red Hat Open Innovation Labs‘ 6-12 week Residencies.
A lot of activities covered in a short amount of time. The activities are described in the Open Practice Library (in which you can contribute your own practices by the way).
We built a city with Lego and while doing that we experimented activities like:
A lot of fun, and a lot of learnings!
Chris Diller, from the Target Dojo, proposed to play the cooperative board game Pandemic. What do you think playing a cooperative board game could teach us? They use the game as a starter in retrospective asking questions about similarities and differences with the work of a real team. We then discussed the roles in the game, and in real life, which was a rich discussion. After that, we discussed our behaviors, were we playing like an agile team during the game? Were we more or less agile than at work? Were we focused on an MVP (minimal viable product) or were we trying to do everything, and finally achieve nothing? (the latter, unfortunately…)
The debriefing phase was simple and powerful. Very well done!
Scott Showalter proposed a session to share tips and tricks for effective meetings.
Some are designed for when people start trickling down the room:
Some are designed for the meeting itself:
And lastly, some to close the meeting:
Another great session!
Shahin Sheidaei proposed a session to harness the power of conflict to improve our organization.
He started with a simple question: “pick a color that represents conflict from the color cards on the table”.
Four of us picked red, one picked black, and one orange.
We then explained what the color represented for us: Anger, fear, absence of hope, and… creativity for the person who picked orange!
An interesting difference of perspectives at our table.
From another table, we heard a person picked green, and then explain that it represents an opportunity.
The exercise is simple enough to be introduced quickly to any team. A great opportunity to have a conversation about what represents conflict for the team, and what to do the next time we will have, or maybe we should have one.
Shahin then introduced Thomas Kliman model and invited us to identify what was our default mode:

We then played with a partner with fake scenarios trying to use the different mode.
In the end, we studied one real story brought by one of the people of a group of three.
Another excellent session!
Jenny Tarwater closed the last day before the open space with a session highlighting the importance of a structured debrief.
She introduced Thiagi Six Phases of Debriefing.
As Thiagi said: “People don’t learn from experience; they learn from reflecting on their experience.”
The six phases are meant to balance the structure and the need for the free flow of the debriefing.
Phase 1: How Do You Feel?
Phase 2: What Happened?
Phase 3: What Did You Learn?
Phase 4: How Does This Relate To The Real World?
Phase 5: What If?
Phase 6: What Next?
And, of course, we had the opportunity to test the debriefing after short games at each table:
A great session!
Scott Showalter and David Bujard proposed an open space session using the board game Terraforming Mars.
The idea of the session was to study the gameplay of the existing game, to then, adapt it for an enterprise transformation.
Interesting session. A lot of work to be done to be able to get to a result for a specific organization. And, yes, I added that in my Someday / Maybe column 🙂
Lastly, we played Kanjis with Isabel Monville, and it was a great session.
Tell me if you would like to play the game!