
#ProductManagement / #SaaS / #B2B / #MarTech SaaS Product Manager before it was cool.
Joined December 2008
- Tweets1.5K
- Following855
- Followers257
- Likes552
Loïc Dilly retweeted
🌻BLAST FROM THE PAST: While I have recorded two more conversations with @caveofapelles , it is still the first one that seem to resonate most with people.
Many interesting subjects brought up like the climate friendliness of beauty! Link to full video in thread.
Loïc Dilly retweeted
Google Cal translates cryptic meeting names so you actually know what the agenda is
Loïc Dilly retweeted
In every relationship there is one person who loads the dishwasher with the precision of a surgeon, and another who loads it like a squirrel on meth.
Loïc Dilly retweeted
You cannot build trust by not delivering. "Put it on the backlog" is the opposite of delivering.
Loïc Dilly retweeted
🌍 Une question me taraudait : pourquoi certains pays sont masculins et d'autres féminins ?
Pourquoi LA Chine et pas LE Chine ? LE Brésil et pas LA Brésil ? LA FRANCE ET PAS LE FRANCE ???
Du coup j'ai fait ce que j'aurais du faire depuis longtemps : je me suis ren-sei-gné ⬇️⬇️
Loïc Dilly retweeted
Les dénominations de l’amas de poussière en français, variantes selon les régions. Comme dit chez nous. Le grand livre du français de nos régions 🫠
Loïc Dilly retweeted
The RICE prioritization framework is flawed.
Purely ROI-driven prioritization can lead to worse outcomes.
Ranking features on cost vs value is often usually worse than just looking at the value side of the equation.
Ask: What really matters to customers?
Loïc Dilly retweeted
Rien ne se perd, tout se transforme
Au Super U Saint Léger, le magasin propose non seulement des paniers anti-gaspi, mais propose des compotes et soupes à partir des produits invendus.
Loïc Dilly retweeted
Ça c'est de l'information bien à jour à la station de Pont-de-Bois !
@ilevia_metro @ilevia_actu @actus_lillois @UsagersTranspol – at Villeneuve-d'Ascq, France
Loïc Dilly retweeted
Scrum is a cancer.
I've been writing software for 25 years, and nothing renders a software team useless like Scrum does.
Some anecdotes:
1. They tried to convince me that Poker is a planning tool, not a game.
2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing.
3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention.
4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint.
5. I had to use t-shirt sizes to estimate software.
6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points."
7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this.
8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously.
9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind.
I believe in Agile, but this ain't agile.
We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it.
The result was always the same: It didn't work.
Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control.
But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team."
Sure it is.
Loïc Dilly retweeted
Ce qui nous a donné notre ostéo-charlatan
N°1
🎉🪇 L'OSTEO-ESTHETICIENNE 🪇🎉
Spécialité méconnue de l'ostéopathie : on te fait craquer le dos et on t'épile le SIF en même temps, hop crac, comme ça une seule douleur. Pratique.
/12
nitter.cf/DocPepper_FR/status/16…
Loïc Dilly retweeted
As Product Managers, we often debate:
• KPIs vs. OKRs
• Best PM books
• Top frameworks
• Dates on roadmaps
But at the end of the day, what matters most is:
• Shipping features that delight our customers.
Don’t lose focus.
Loïc Dilly retweeted
Keeping the team size small enhances productivity.
As team size increases, the individual contribution of the team members decreases.
This is an interesting phenomena in human behaviour, known as Ringelmann effect.
Loïc Dilly retweeted
Working on discovery?
Chat with your operations/customer support team.
I've been amazed at how well our operations team (what we call the CS team) is in touch with our customers.
They can point to specific customer stories or trends that we'd never know about without them.
Loïc Dilly retweeted
Sorry but the age of “be embarrassed by your first MVP” is gone. – at Los Angeles, CA
Loïc Dilly retweeted
The "skateboard MVP" mental model is broken.
What are the odds that a person who’s interested in buying a car will be excited to buy a skateboard or bike?
MVP has to share core features with your final product. They should explore key ideas for the final version.
Loïc Dilly retweeted
You might have the best product ideas, but if you can't deliver them fast enough, you are doomed to fail.
Luckily, you can easily improve the flow.
6 key metrics you should know:
1. Lead Time
2. Time to Market (TTM)
3. Cycle Time
4. Work In Progress (WIP)
5. Throughput
6. Bonus: Velocity
Now in detail:
1. Lead Time
A Kanban metric that measures the total time between an idea placed in a Product Backlog until the work in a specific process is completed.
For example, if Microsoft decides to use ChatGTP in Bing, Lead Time would be the time between deciding on a specific approach and when the feature is production-ready.
2. Time to Market (TTM)
TTM is a broader concept. I'd argue it's the most important metric for a PM, encompassing idea generation, experimentation, product delivery, and pre-launch activities that might be required before an idea is shipped.
For example, if Microsoft decides to incorporate ChatGPT into Bing, the Lead Time would be the period between having a draft idea and when customers can use a new capability.
3. Cycle Time
A Kanban metric that is a component of Lead Time. It measures the time it takes from when the implementation of an idea begins until it's done.
For example, if Microsoft decides to incorporate ChatGPT into Bing, the Cycle Time would be the period between when developers start implementing a specific idea and when it becomes production-ready.
4. Work In Progress (WIP)
WIP is a Kanban metric that represents the number of ideas that your team is currently working on.
The goal is to limit WIP to reduce context-switching and minimize the Cycle Time. This ultimately minimizes the Time To Market (TTM).
5. Throughput
The rate at which ideas pass through your team's workflow over a given period.
It’s essential to know Little’s Law:
Average Cycle Time = Avg. WIP / Avg. Throughput
The key to maximizing throughput lies in identifying and managing bottlenecks - where work piles up because it arrives faster than it can be done.
Insight: working on too many ideas simultaneously will negatively affect the time to finish each. So limit your WIP.
6. Bonus: Velocity
Valocity refers to the amount of work, e.g., Story Points, completed by a team during an iteration, typically Sprint.
It’s essential to remember that Velocity corresponds to the amount of work, not the value of work. It is an internal metric and should never be used outside the team. In particular, you should never use it to compare teams or set expectations.
-
While those metrics can be extremely useful, remember that your goal is to optimize the flow of value, not the flow of work.
So, for example, if you use User Stories and sub-tasks, focus on tracking the whole User Stories.
Hope that helps.
How can you use it in your work?
-
P.S. I will dive deep into 50+ product metrics in my newsletter Tomorrow (free, extended edition).
Join 21,001+ professionals to get a notification. The link is under my profile: @PawelHuryn
































