Skip to main content

Organiser pour la Complexité / Organize for Complexity

English version below. 

Nos organisations peuvent avoir des difficultés à définir une structure interne qui réponde aux contraintes sociales et économiques externes. Celles actives dans des domaines soumis à des contraintes de changements douces, peuvent se contenter d’améliorations continues. Par contre, dans la plupart des domaines technologiques, les structures managériales ne permettent pas d’affronter l’accélération créative/économique en cours.

Nos organisations IT ont trouvé des principes d’amélioration par la gestion en flux, le fast design et la validation anticipée (Agile, Devops, LeanStartup, etc.). Néanmois, d’un point de vue managériale haut niveau, il n’y a pas vraiment de principes adoptés et mis en place dans la globalité de l’entreprise. 

L’année dernière, grâce au mouvement #stoos, j’ai redécouvert le mouvement “Beyond Budgeting” (première rencontre ALE2011) et ai vraiment apprécié le document de Beta Codex “Organiser pour la complexité”. J’ai décidé de le traduire, suite à l’appel de Niels, mais les mois suivants, j’ai préféré me concentrer sur la traduction de “Commiment”. Il y a quelques mois, Sylvain a rejoint Pierre et moi pour terminer cette traduction que vous trouverez ci-dessous.

Si vous n'avez pas de connaissances en management, vous trouverez ce document très dense. Je vous conseille de le lire chapitre par chapitre.
Copie sur Slideshare de Niels et copie sur Slideshare de Sylvain

Today, organisations could struggle to define a internal structure that fits current external economical and social constraints. Those active in domains which move at a slow pace, can handle change with a continuous-improvement mindset. But in most technological domains, the current managerial structure cannot bear the increasing creative/economical pace.

Our IT organisations found improvement principles in flowing, fast design and early validation principles (Agile, Devops, LeanStartup, etc.). However, from a high level management point of view, no principles are really adopted and implemented in the whole enterprise. Last year, due to the #stoos movement, I rediscovered the “Beyond budgeting” people (first met in ALE2011) and really appreciate the Beta Codex document “Organize for Complexity”.

I decided to translate it, after a call from Niels, but during the following months I was too busy and focused only on the “Commitment book” translation. A few months ago, Sylvain joined Pierre and me to finish the translation that you can find below.

This document is really heavy to read if you don’t have any knowledge of management principles. So take the time to read it chapter by chapter to nourish your brain.



History :
15/09/2013: Published
03/11/2013: Add Zobrist example


Popular posts from this blog

Learning about Data Science?

This is the end of a beautiful summer, and also one of the warmer recorded in France. I’m continuing my journey in the product management world and today I’m living in the product marketing one too.
I will blog about this later.

During this first half of this year, I read several articles on big data and started to understand how important the data science discipline is. Being able to define a direction/goal to search, collecting the proper data, then using a collection of techniques to extract something others can’t see - it sounds like magic.

Also, when I listened to the Udacity Linear Disgression podcast episode “Hunting the Higgs”, I understood people with these skills can be better at solving a problem than the domain experts themselves. Katie Malone explained that in a competition to solve a particle physics problem, the best results came from machine learning people.

Then I read the article about Zenefit on the vision mobile website:
“Zenefits is an insurance company that offer…

Didn't register yet to the European Agile event 29-31 August in Paris?

I tell you, I’m not an expert in agile, just someone who found solution to my professional problems using agile methodologies. If you are convinced too and want to move further, please join us at the end of august, for a lot of open discussions and fun.

Things are moving forward in the ALE 2016 organisation. Already, a great diversity of people answer to our call as shown below, but we need more.
Yes the ALE 2016 will be great as it has always been since 2011 in Berlin. For those who do not know about the yearly ALE event, please find below a few tips.

What is it? 
If you do not know yet about the Agile Lean Europe event, here a few tips.
ALE is a event for practitioners, meaning people who already practice agile methodologies like developers, modern CEO, teachers, leaders, etc. Sharing ideas and solving problems are the ALE mains goals: people can propose topics where they share their experience, other can ask to solve a problem the can’t alone The event formats helps the participant…

New personal goals for next years

Happy new year 2015.

After 10 years inside the walls, I’m moving outside!!

Time is running and I have been working in the software world for 13 years and promoting the “software agile thing” in my area, for 6 years. Today, I need to step back. As my professional life has moved from R&D management to Product Marketing Management, my professional focus has shifted and I need  to improve my skills in this area.

I’m writing this article because I would like to thank my growing network and  make sure you won’t be surprised by my new area of interest, that could be outside of your own.

I imagine a few of you, shaking your heads, uttering a pfff of disappointment and saying: Franck and his books, his constant learning curve. For what?

This is really simple: Without a sense of progress, I get bored in my professional activity.

In 2009, for the first time since beginning in this sofware development world, I had a sense of accomplishment. As Agile was the main change we had implemented, I …