I often work with product teams who have conversations—sometimes very difficult ones with stakeholders—that are full of unstated assumptions, subjectivity, and a lot of unsubstantiated “I think…” comments. For a startup with few people the conversations aren’t often difficult, but poor subjective judgements can sink the company. For larger organisations with a product team and … Continue reading
I’ve worked with a few organisations that wanted to create a framework for reporting on and governing projects or programmes. The intention is generally good: we have lots of projects and programmes across the organisation; if we can standardise the approach to governing them and reporting upwards then we can ensure they are run to … Continue reading
Sometimes a development team has to make a technical decision. Actually, a development team has to make techical decisions all the time, and 99% of the time those decisions are focused entirely on the development process and therefore entirely at the discretion of the developers. But sometimes it’s not so easy. Perhaps they are thinking … Continue reading
I’ve been having fun this week watching some conference talks about my current favourite language, Elm, at Elm Europe 2017. And I enjoyed seeing an important idea discussed—important not just for coding, but for product and project development generally. The lesson is: solve the actual problems experienced by actual people. Don’t generalise—at least not without … Continue reading
I’d love to say all the projects I’ve ever worked on have run perfectly smoothly, but that would be a lie. There are plenty of times I’ve been involved with a project where a deadline is looming, and as we get closer and closer we have to ask harder and harder questions about what to … Continue reading
Earlier this year I was involved in a talk led by Gayatri Kamath in which she discussed a serious incident at the Apollo Theatre in London in 2013. A large number of people were injured after part of the building collapsed due to water build-up in the plaster. On speaking to one of those with … Continue reading
Last week I wrote about the value of stopping work to tackle tech debt, and more specifically when we might expect to recover from the temporary stoppage. In the ensuing discussion a question came up about one of my assumptions, which was that the team was delivering at a constant rate (albeit below its potential). … Continue reading
A colleague pointed me to a nice article by Sue Davis about writing for the public, and among the suggestions was the idea of timeboxing feedback: “If you don’t, the polishing process can be never-ending and you risk delaying getting the content to your users.” Timeboxing is really valuable not just for getting feedback, but … Continue reading
If you can’t do the most important project work first, expect to overrun. Doing project work generally yields any of three results: either you complete the work in good time, you overrun, or more work comes out of it. They are not all mutually exclusive. The problem with projects is that work tends not to … Continue reading
When we measure our progress there are—by some perspective—three kinds of things we might be measuring. The most immediate things to measure is our activity: Are we doing what we said we would do, and at the rate at which we said we’d do it? This is about measuring ourselves against our plan and is … Continue reading
