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

Comments

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 compan

Lancement de ProductTank Lyon

Tout d’abord, bonne année 2020. Je me suis investi ces dernières années dans les communautés/événements CARA Lyon, MiXiTConf, LyonDataScience et CaféDevOps sur Lyon, France. Ces activités m’ont permis de comprendre les experts de ces domaines, d’apprendre quelques notions fondamentales à travers leurs exposés et d'améliorer mes capacités d’échange avec eux. Product Manager depuis plus de 5 ans, je désire améliorer mes réflexes et compétences dans mon domaine. Le faire à travers des rencontres/meetup est ce que je préfère et j’aimerais retrouver la stimulation des communautés dans cette discipline. En cette année 2020, quelques Product Manager Lyonnais, lançons, le meetup ProductTankLyon à Lyon, France. Le réseau ProductTank compte plus de 150 meetup dans le monde et profite des conférences, blog et podcast MindTheProduct. Inscrivez-vous ici , si vous voulez vous joindre à nous.

Read bead experiment

The "Read bead experiment" was created by Dr. Edward Deming and aim to demonstrate the ineffectiveness (sometimes effectiveness) of the various management methods. At the end of the experiment, a statistical graphical tool is used to analyse the experiment's results. By following this exercise, you will understand that actions taken by the people playing the managers are detrimental to the employees, but after the analyses are shown to have no impact on the efficiency of the process . The conclusion proposes ways to properly use performance data in a quality environment in order to achieve continual improvement. The several videos by Fluor Hanford (Steve Prevette) posted below, will help you to understand what is really important in a process. Meet the  company  with its "willing workers", quality control personnel, a data recorder, and a foreman. All wish to produce white beads using a 50 holed paddle, but unfortunately there are bad quality red beads.