A french Lean/Agile coach living and working in Sweden.
Helping companies to improve continuously in the right direction using the full potential of their employees.
How to grasp the real purpose (“why”) behind your Kanban system and understand the quest you’re really on.
Great conversations with passionate people.
The look they have at the end of the session: focusing far away on the horizon, contemplating the possibilities opening before them, eager to start.
Sustainable! Especially when coupled with “change”. I’ve done my share of quick “implementations” that collapse as soon as you look somewhere else, leaving the place an even bigger mess than before. I want my efforts to stay, to be “sticky” and impact the bottom line for real.
Implement, as in “let’s implement method X”. To ‘implement’ something actually means: “It’s too time consuming and tiring to think for ourselves, so let’s force someone else’s model right into our context. What could possibly go wrong?”. I do prefer the word “adopt” (“let’s adopt method X”) that convey a sense of reflection, focusing on the intent of the method and less on its actual steps.
“Ahaa!”: the sound made by someone that just ‘got’ it!
“Holy Cow”. It just sounds really too weird in french…
Ada Lovelace: the very first programmer ever, ushering the world into the area of knowledge work, and, moreover, a woman.
A programer in a big company in an alternate reality without any Agile/Lean movement. A kafkian, “Brazil”-esque nightmare.
A cat! They seem to just enjoy life.
It really all was just a simulation…
How can I use Kanban to ask big questions about what I want?