-
Read more: He documented everything before he left, and most of it went unusedBefore a product leader left a company, he recorded walkthroughs of features it had retired: use cases, operation, design reasoning, documentation. The recordings sat in the company’s shared folders, a complete starting point for anyone who rebuilt. A few years later the company did rebuild, and the team used only part of one feature.
-
Read more: My process listed every step and made my team put off starting any of themEarly in my product leadership, I drafted a 20-page document that pulled together every step of our product launch process, from the first idea to a customer using it. Leadership was excited, and the team was glad to have a list they could count on. When it came time to start a new release, the…
-
Read more: The 10-minute fix that made the release lateDuring standup, one engineer on my team reported finding and fixing a longstanding problem in one of our core modules. It might have added 10 minutes to his work, and the team celebrated. We had better code, and a customer didn’t have to report it to us. The release still went out a few days…
-
Read more: What a complete handover still leaves outA product leader joining a new organization inherited the product objectives and the backlog. He also inherited the way the team had been organizing and connecting the backlog tasks to the problems they solved. When the leader who had been managing all this walked him through it, he immediately saw that the connections between objectives…
-
Read more: The component passed every test and users still couldn’t use itA team finished work on a component that passed all its tests. The next project was already waiting for them. The component let one set of core functions run in many different user contexts, and a presentation layer still had to connect it to the user’s daily work. It made sense to reassign the team…
-
Read more: You can meet the customer outcome and still failThe team had a clear picture of what the customer needed and designed an approach to deliver it. Every function wrote its plan: the solution, the customer-facing teams, the market launch, the sales team. Outside the project, the steering committee had committed to including AI in future work. When the plans were read side by…
-
Read more: The better he ran operations, the less there was to hand offAn operations leader I worked with left after years of doing the job well. His team prepared for weeks: every operation with a procedure was transitioned, and the logs, playbooks, tickets and alerts were categorized and handled. The handoff still missed one category of work, the “support the operation here and there” tasks. Those were…
-
Read more: Where you put a small change decides whether it sticksA team I know set up a very light project management system: a short list of the work, an owner on each item, and a status to change when something happened. A few weeks later, the list and the work didn’t match. Nobody skipped it on purpose. The team did its work together in one…
-
Read more: A fiddly step we hated was doing a job we neededSome years ago I inherited a way of tracking a coarse-grained backlog. It ran across three separate places, held together by a method that was fiddly and undocumented. Eventually we dropped the fiddly part. The change-over was easy, the backlog functioned, and I would do the same thing again. The backlog has also grown steadily…
-
Read more: Writing it down isn’t enoughI observed a team decide to transfer ownership of a shared responsibility to one of the team members. They wrote down the decision but didn’t change any of the processes. The responsibility still lacked a strong owner, and everything operated the way it always had. Nothing changed about the problems that prompted the decision in…