Challenge: Changing the way, or better totally revising the way, we are used to

code/program speciﬁc parts of our application ecosystem is not easy. Many times you had

sedimented programs and behaviour, but you know deep inside something could be done

in a diﬀerent way. This kind of activities were increasing, but with no leverage on

experience, with higher costs and maintenance.

Lot of options on the table : new coding approaches, new tools. Where to go ?

Selection: So, we have many ideas, but with no clear idea on beneﬁts and costs => which

one to choose ? And most of all, which business case to bring to our leadership ? Too many

stakeholders and possible eﬀects to have a decent plan. As well, some technological

doubts…. will it work ?

We therefore used “Learning Launches” to test our best ideas and conﬁrm them.

Application: We initially applied our ideas to a small set of code, to learn what it means to

implement, get the real costs, and see outcomes. We did not spend a lot of time trying to

document and to scale up, but rather we focused on experience itself and on its results.

Insight: Experience actually made us realize that an initial idea, put on hold after the ﬁrst

tests, was the best one. Failures help. And maybe discarded options may become the best

one you still have.

Approach: Next time I will make sure that in the experiments team I am having a

representation for ALL stakeholders.

