Why AI projects fail twice, and what Luciano Floridi can teach us about the second failure I have followed Luciano Floridi's work with interest for years, long before artificial intelligence became a boardroom topic. What has always struck me is ...
The Blog
54 articles · page 1 of 5
The pre-mortem flips optimism on its head: assume the project already failed, then work backward to find why, while there is still time to fix it.
You do not need a 40-column risk register to manage risk well. You need four verbs and a small grid. Spot, rate, respond, review.
Household labour is invisible until it isn't. A simple Kanban board on the fridge makes the work visible, shareable, and a lot harder to silently dump on one person.
You measure burndown, velocity, and budget for the project. Here is how to turn that same instinct on yourself, and the four metrics actually worth tracking.
Project managers map stakeholders before they spend a single hour. Why not do the same for the people in your own life, and engage each of them deliberately?
Task-switching feels productive and costs you dearly. Here is why attention residue makes it expensive, and a simple way to measure your own switching tax.
Add a person to a slow team and it usually gets slower. Here is the communication math behind Amazon's two-pizza rule, and how to use it on your own work.
The urgent/important grid is a great first cut and a poor final answer. Add a third dimension, leverage, and your task list starts sorting itself.
Teams pause every two weeks to ask what worked and what did not. You can run the same ritual on yourself, alone, in twenty minutes a week.
You are not bad at estimating because you are careless. You are bad at it because your brain runs a story that quietly deletes everything that could go wrong.
Hours are identical; energy is not. Learn to read your ultradian rhythms and spend your peaks on the work that actually matters.