FLOWCON 2025

From Wild Bets to Solid Forecasts: Mastering Predictability

Tired of unreliable forecasts and missed deadlines? This workshop will show how managing the age of your WIP can stabilize cycle times and improve delivery predictability. Together, we'll tackle common forecasting pitfalls and uncover actionable ways to make your work more predictable.

Sum up the session in only 1 sentence
In this workshop, we’ll explore how controlling the age of work in progress can help teams improve predictability, avoid delays, and make more reliable forecasts.

What are the 3 top takeaways from your session or workshop?
Key Takeaways from My Workshop: 1. Controlling the age of work in progress (WIP) is the simplest, most effective way to improve predictability. By keeping WIP age in check, teams can reduce cycle times and avoid delays. 2. Predictability starts with improving single-item forecasting. Instead of guessing delivery dates for large groups of work, focus on accurately forecasting one item at a time. 3. Stable cycle times make forecasting easier and more reliable — for both single items and larger projects. By managing WIP age and stabilizing cycle times, teams can confidently make both short-term and long-term delivery predictions.

Painting the software green: A GreenOps approach!

In the fast-paced world of digital product development, the quest for sustainability is more than just painting the UI green or fighting for the efficiency of programming languages.

Green Ops merges sustainability principles with DevOps methodologies, emphasising efficient resource management, resilience, lifecycle sustainability, collaborative culture, and measurable impact.

It goes beyond superficial changes, focusing on optimising resource use, building resilient systems, and fostering a sustainability mindset throughout the development lifecycle. By embracing Green Ops, organisations can achieve better outcomes without overhauling their entire infrastructure, driving innovation while making a positive impact on the planet.

Sum up the session in only 1 sentence
The world can be a better place if you wish to, so start painting the software green!

What are the 3 top takeaways from your session or workshop?
1. Lifecycle Sustainability – Sustainability spans the entire product journey, from design to decommissioning. Every stage offers opportunities to reduce environmental impact and build long-lasting, efficient systems. 2. Code vs Operational Efficiency – Writing efficient code is just one piece of the puzzle. True sustainability comes from balancing optimised software with resource-efficient infrastructure and runtime environments. 3. Starting the Conversation– Change begins with awareness. Embedding sustainability into engineering discussions ensures it becomes a core consideration, driving greener decisions at every level.

DORA, Flux et Engagements : Le Cadre de Performance des Équipes Produits chez Cdiscount

Sum up the session in only 1 sentence
Engineering Value : Mesurer et Maximiser la Performance des Équipes Produit

What are the 3 top takeaways from your session or workshop?
L'importance de l'Engineering Value dans la performance des équipes produits Les outils et indicateurs pour mesurer la performance des équipes La fiabilité et la prédictibilité comme piliers du succès dans un environnement B2B

Impact Mapping Workshop

"Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and stakeholders visualise roadmaps, explain how deliverables connect to user needs and communicate how user outcomes relate to higher-level organisational goals." (source: https://www.impactmapping.org/)

Impact Mapping is a unique technique (described in a book by Gojko Adzic) which enables every organisation or team facing a new problem, a new challenge to not only find unexpected ideas but also to make sure that these ideas address those challenges instead of fulfilling other interests.
By following the steps, Impact Mapping helps find ways to experiment, innovate, and compare possible ideas by focusing on the outcome rather than the output. It gives the group the means to verify the progress the whole time - to fail fast or stop investing because they have reached their goal.

In this workshop, we will discuss and map a fictive problem. At the end of the workshop, you will know how the technique works and when to use it, how much fun such Impact Mapping can be and how creative people are when the only constraint is time :)

Sum up the session in only 1 sentence
We will learn how to analyse and manage to prove that our assumptions about the users' problems are correct before investing a lot of work in fixing the wrong problem.

What are the 3 top takeaways from your session or workshop?
1. The method is easy. The key is asking the right questions outside of our silo. 2. The right questions and the right metrics. 3. Assumptions are hindering, experiments are enabling.

L'entreprise, un terrain politique comme les autres ?

Sum up the session in only 1 sentence
Si l'entreprise était un sujet politique, lequel serait-elle ?

What are the 3 top takeaways from your session or workshop?
1) L'entreprise est un acteur politique, au sens où elle participe à l'organisation de la vie dans la cité 2) Les salariés de l'entreprise sont des citoyens qui ont des valeurs et des convictions 3) Les sujets politiques ne doivent pas être tabou, tout au contraire !

Title: Non-Blocking Continuous Code Reviews, a Case Study

The problem with the current most commonly accepted way of running code reviews using Pull Requests is that they have the nasty habit of blocking the flow of delivery. They introduce a cost of delay. Delays reduce feedback and drive down quality.

The usual way to achieve fast efficient and effective Continuous Code Reviews without disrupting the flow of delivery is through Pair Programming or Team Programming. However, for various valid reasons, these are often a cultural stretch for many teams and organisations.

In 2012, a novice team practising trunk-based development set up a fairly uncommon but efficient alternative to implementing continuous code reviews on mainline without ever blocking the flow of delivery. This team went from a bunch of rag-tags to becoming a reference team in the organisation, with auditors falling on the floor because of the amount of quality the team delivered.

Sum up the session in only 1 sentence
How to run code reviews with trunk-based development when pair programming is a cultural stretch?

What are the 3 top takeaways from your session or workshop?
Be able to explain how Pull Requests disable the benefits of Continuous Delivery. Be able to enumerate the key ideas behind non-blocking code reviews. Understand how non-blocking code reviews are an enabler for Continuous Delivery.

Dompter la Dette Technique : de fardeau à atout stratégique

La "dette technique" — on en entend parler partout, et nombreux sont ceux qui en subissent le poids. Mais soyons honnêtes : n’est-il pas temps d’arrêter de la voir comme un fardeau insurmontable ? Et si nous transformions ce concept souvent perçu négativement en un moteur de progrès ?

Dans cette session de 45 minutes, inspirée par la méthodologie concrète développée chez TheFork, nous plongerons dans les défis réels de la dette technique et vous montrerons comment la gérer sans perdre pied — ni ralentir l’élan de vos équipes.

Nous aborderons :

Ce qu’est réellement la dette technique (indice : ce n’est pas juste du vieux code que vous détestez).
Comment la localiser et la mesurer : Pas de jargon flou, juste des idées claires et actionnables.
Des façons concrètes d’agir : Des petites victoires avec la "Règle du scout" aux migrations complexes.
Les outils qui rendent tout ça possible : Automatisation, tableaux de bord, et même un bon vieux document Notion pour passer du chaos à la clarté.
Il ne s’agit pas de solutions miracles ou de théories abstraites, mais de faire face aux imperfections de votre système et d’en tirer le meilleur parti. Rejoignez-nous pour apprendre à affronter la dette technique, en faire un atout stratégique, et peut-être même commencer à apprécier le processus.








Sum up the session in only 1 sentence
Apprenez à transformer la dette technique, souvent perçue comme un obstacle, en un levier stratégique grâce à des outils pratiques, des méthodologies claires et une culture d'amélioration continue.

What are the 3 top takeaways from your session or workshop?
Redéfinir et mesurer la dette technique : comprendre que la dette technique est un choix stratégique et apprendre à la qualifier, quantifier et localiser pour en faire un atout exploitable. Adopter des outils et des pratiques efficaces : découvrir comment des outils comme Beacon, des tableaux de bord visuels, et des processus automatisés peuvent simplifier la gestion et la priorisation de la dette technique. Fédérer une culture d'amélioration continue : créer un environnement où équipes techniques et dirigeants collaborent pour intégrer la gestion de la dette technique dans la stratégie globale de l’entreprise.

Cf. Didier Girard

Sum up the session in only 1 sentence
cf. Didier Girard

What are the 3 top takeaways from your session or workshop?
cf. Didier Girard

Titre : Les standards de travail Lean/TWI pour développer l'autonomie et l'apprentissage

Résumé : Comment permettre à chacun de s'assurer que le travail réalisé est bon ou pas ? Comment donner les moyens à chacun d'être acteur dans l'amélioration du processus manipulé ? En utilisant les standards de travail !

Sum up the session in only 1 sentence
Redonner de l'autonomie aux personnes avec les standards de travail Lean / TWI.

What are the 3 top takeaways from your session or workshop?
- Le manque d'autonomie est un des risques psychosociaux - Le standard de travail permet à chacun de savoir si son travail est OK ou KO - Le standard de travail est la meilleure pratique d'une équipe à un moment donné

“If you hate OKRs, someone is doing them wrong. Maybe you, maybe your boss.” -Christina Wodtke.

Many organisations struggle with OKRs, often finding them frustrating and ineffective. But the problem isn’t the framework—it’s how it’s implemented. Cascading goals, task-focused execution, and rigid structures create silos and disengagement, stifling the true potential of OKRs.

In this talk, we’ll start by uncovering common dysfunctions that derail OKR initiatives and demystify why they fail to deliver results. Then, we’ll introduce a fresh, proven approach: the OKR Solar System. This dynamic model replaces top-down cascades with cross-team collaboration, enabling strategic alignment that adapts to your organisation’s evolving needs.

You’ll learn how the OKR Solar System fosters aligned autonomy, breaks down silos, and empowers teams to focus on shared outcomes. Real-world case studies will showcase its transformative impact on strategy execution. Whether you’re just starting with OKRs, scaling them, or looking for a reset, this session will inspire you to reimagine what’s possible.

Key Takeaways:

- Why cascading OKRs fails and how to avoid it.
- Introduction to the OKR Solar System with practical examples.
- Models for creating cross-team collaboration and strategic alignment.
- How to prevent or fix common OKR implementation challenges.

Let’s turn frustration into inspiration and make OKRs work for you!

Sum up the session in only 1 sentence
Why cascading OKRs fails, and how the Solar System can help you break silos, align strategically, and adapt dynamically.

What are the 3 top takeaways from your session or workshop?
- Why traditional OKR approaches often fail to deliver results.
- How to implement the OKR Solar System for strategic alignment.
- Practical models for fostering cross-team collaboration and innovation.

Dans un environnement de start-up au rythme effréné, il est essentiel de prendre des décisions rapidement.
L'intuition est la recette secrète des responsables de produits pour accélérer la prise de décision. Mais d'où vient notre intuition ?
En examinant les biais dans la sélection et le recrutement de projets dans le monde des start-ups, nous pouvons comprendre que notre intuition est un handicap et ne devrait pas être notre seule méthode de prise de décision.

Sum up the session in only 1 sentence
Les start-ups croient trop en la qualité de l'intuition pour prendre des décisions, mais l'intuition est influencée par l'expérience et peut conduire à des résultats désastreux si elle n'est pas remise en question.

What are the 3 top takeaways from your session or workshop?
- L'intuition n'est pas une donnée mais une construction
- Les employés des start-ups ont tendance à former un groupe cohérent
- Les start-ups ont tendance à répondre aux besoins de certains utilisateurs plus que d'autres

So You’ve Built It, Now Support It. From Chaos to Happy Customers - Doing the Gardening At Bloom & Wild

Humans make mistakes, it’s a fact of life. Despite our best intentions, and no matter how many checks we put in place, sometimes things go wrong. It’s no different with software. To move at speed then it’s inevitable that production issues will happen. Sometimes it’s your code that doesn’t work as expected, sometimes dependencies break, sometimes infrastructure breaks. Sometimes that once in a lifetime event happens. Again.

This talk is a story about support. It’s a real life story of how what was a chaotic situation, with unhappy customers and developers, has been turned around to something that keeps our customers happy, and is even fun to be a part of.

Sum up the session in only 1 sentence
All teams should support their systems in production and I'm going to explain what I've learnt about doing that, with added flowers :)

What are the 3 top takeaways from your session or workshop?
1. Why they’ll always be some need for production support, why needing it isn’t a indication of failure and how we can make it a nicer experience
2. The different ways that we've supported our systems at Bloom & Wild and what we've learnt as we've rapidly scaled the team
3. A little about flowers and a lot about learning

No Code, Low Code, Machine Code

What level of abstraction is just right?

Everything looks solvable if you ignore most of the complications. Many things look impossible if you’re stuck in the weeds. The current fashion for low/no code solutions heralds the cyclical return to looking for solutions that require softer skillsets. When is this appropriate and when is it a recipe for disaster?

Sum up the session in only 1 sentence
There is no silver bullet (reprise)

What are the 3 top takeaways from your session or workshop?
- Essential complexity cannot not be simplified away - No code/low code solutions are only beneficial in limited domains - AI and ML are tools not solutions

Seeing the world through a different lens

We see the world through the lens of all our experiences. This is probably obvious to most, but what is probably less apparent is that we also carry a coherent mental model of how we expect the world around us to behave. A preconceived notion of what to expect in any given situation, one that even goes beyond the basic laws of nature and common human behaviour. It is so ingrained that we do not know we even have it until made aware of it. Like do you assume predictability because science assumes determinism, or do you accept unpredictability because everything is contextual?

In this talk, we will have a look at some of these lenses, called world hypothesis, and we will explore how profoundly different we interpret the world by choosing one over the other. How does it play out assuming social systems behave like machines, like when blindly copying an approach from others; or trying to create a canonical data model when all have their own context; or how about giving a team orders and designs and then expecting them to self-manage?

We shall see that the lenses are complete and should not be mixed as we constantly seem to do; to our detriment, creating massive confusion and dysfunction. Awareness of these world views and understanding their fitness in any given situation can take us a long way to make the world a better place. Imagine that.

Sum up the session in only 1 sentence
To collaborate and codesign better we need to understand other peoples world views and how they compare and contrast with ours.

What are the 3 top takeaways from your session or workshop?
You need to understand at least the four different world views, seeing how they differ, and understand the issue of mixing them.

Title: Power Structures and Their Impact on Software
Abstract: Code is literally knowledge made manifest, and therefore offers a history of knowledge; it is a record of how people understood a problem over an extended period of time.

But code is also power, and the ability to write/approve/deploy it can be used for ill or good, (intentionally or unintentionally). In so doing, code solidifies power structures; embedding that which is inevitably unequally distributed (unintentionally or intentionally) but embedded all the same.

Code is therefore also a geology (genealogy?) of power structures. Code forms the landscape where records of our old ways of (dis)organising, and ideas that won, continue to shape everything because this code is where teams live *now*.

We experience this “code-as-knowledge-and-power” every day; our freedom to act restricted or permitted.

In this talk I’ll dissect what is at play here. I’ll consider what is happening with “code-as-knowledge-and-power” and show how to work with it intentionally, instead of suffering/benefitting disproportionately at the hands of it.

Your code, and your life, will be better as a result.

Sum up the session in only 1 sentence
“We live in capitalism. Its power seems inescapable. So did the divine right of kings. Any human power can be resisted and changed by human beings.” Ursula K. Le Guin

What are the 3 top takeaways from your session or workshop?
1) Societal power structures make our code bad - code is structured knowledge and power 2) To see where the power lies, pay attention to who has control - of punishment, information, and who is charismatic 3) Fight uneven power distributions - by protecting everyone's freedom to reorganize, move and disobey.

Atelier Domain Storytelling

Domain Storytelling permet de transcrire les histoires racontées par les experts métiers à l'aide d'un langage pictographique facile à comprendre. En regroupant tous les acteurs ayant une connaissance du produit ou du problème à résoudre, Domain Storytelling va permettre de diffuser la connaissance au sein de l'équipe. Les schémas produits sont d'excellent moyen pour les différents participants de se remémorer les discussions autour de points particuliers de l'espace du problème tout en produisant une documentation simple et claire.

Le but de cet atelier va être de vous donner les éléments théoriques et pratiques nécessaires pour animer des ateliers de Domain Storytelling. Il est donc destiné à n'importe quel acteur d'un projet informatique.

En maîtrisant Domain Storytelling vous allez pouvoir simplifier:
la compréhension d'une problématique
définir un langage commun entre les différents acteurs d'un projet
évoquer les éléments de spécifications
identifier les différents contextes de la solution

Sum up the session in only 1 sentence
Apprendre à faciliter des sessions de "Domain Storytelling" pour améliorer la compréhension du métier.

What are the 3 top takeaways from your session or workshop?
- Apprendre à mener des conversations pour découvrir le métier avec des experts du domaine.
- Transcrire dans un langage pictographique les discussions.
- Maitriser un nouvel outil pour concevoir la bonne solution.

Comment faire converger des dizaines d'applications informatiques existantes vers une plateforme IT cible commune ?

Au-delà des principes et des frameworks, cette conférence est un retour d'expérience sur la transformation innovante d'une division IT de plusieurs centaines de personnes.

Un défi technologique, organisationnel et... culturel !

Note : this conference will be given in French but with materials written in English to allow everyone to follow 🇬🇧

Beyond agile: Product Innovation at Google, Airbnb, Spotify, Vinted, & Amazon
What truly distinguishes Google, Airbnb, Spotify, Vinted or Amazon as world-class product companies? This talk goes beyond the conventional "agile" framework to explore how these organizations create a seamless flow across discovery, delivery, and innovation, ensuring that impactful products are delivered consistently.
We'll explore how these companies:

• Blur the lines between discovery and delivery: By integrating user research, data analysis, and rapid experimentation into every step of the product lifecycle, creating a constant feedback loop.
• Foster cross-functional synergy: High-performing teams collaborate seamlessly across product, design, engineering, and data science, ensuring that work flows continuously across disciplines and silos are eliminated.
• Embrace a data-driven culture: Data informs every decision, from shaping product strategy and prioritizing the roadmap to development and post-launch optimization, ensuring that each step is based on real insights.
• Prioritize user-centricity: Understanding user needs and behaviors deeply, translating these insights into intuitive, delightful experiences that evolve with real-time feedback.
• Master the art of experimentation: Using A/B testing, multivariate testing, feature flags, and gradual rollouts to experiment quickly, validate assumptions, and minimize risk—ensuring that the product evolves without disrupting flow.

We’ll also dive into the key enablers behind their success:

• Clear alignment on business objectives: Empowering teams to flow autonomously while staying aligned with overall company goals, ensuring strategic focus without bottlenecks.
• Robust technical foundations: Microservices, cloud-first architectures, and CI/CD pipelines are leveraged to support continuous, scalable delivery, enabling smooth transitions between development phases.
• Design systems that ensure consistency at speed: Reusable design components and patterns enable rapid development while maintaining a high-quality user experience, ensuring flow without compromise.

This session provides a behind-the-scenes look at how these companies create a continuous, harmonious flow between product discovery, delivery, and innovation. Whether you’re a product manager, engineer, designer, or anyone involved in product development, you'll leave with actionable insights to optimize your own processes and foster a smoother, more effective flow within your team and organization.