The Loop

What are the heuristics for separating “important” product changes from minor changes that are essentially background noise? If this question sparks your interest, keep reading. Everyone who works at a software company must perpetually ask the question: “How did our product change?” The folks who sell, market, or support the

Accountants have ledgers. Scientists record their experiments. Marketers have CRMs. Engineers have code version history. Product builders, however, lack a sufficient source-of-truth for their past work. It’s a fundamental gap that holds back product management craft. What is a “source-of-truth” (SoT) for product iterations”?A SoT for product iterations

Babies are born with exogenous attention. This means that the external world dictates what they pay attention to. A baby could be playing with the best toy ever, but when another toy drops next to them, their attention uncontrollably shifts to the new shiny object. In The Philosophical Baby, Alison

Innovation requires a combination of work and meta-work. By “work” I mean doing things that tangibly impact your product; designing, coding, marketing, etc.. “Meta-work,” in contrast, involves improving how you’re working. This often looks like meetings to synchronize the activities between teams or applying frameworks like OKRs or lean

Making the transition from hands-on product management to leading a PM team can be disorienting. On the one hand, if you get overly involved with projects, you’ll stifle the creativity of the team. And it’s unsustainable to be on top of every detail, especially with products that require