Category: Ways of working
-
Learning > Winning: Rethinking Experiment Failure
When every experiment “fails,” it’s not the process that’s broken—it’s how you’re learning. Discovery isn’t about winning. It’s about getting…
-
Understanding the work before automating it: A survival skill for the AI age
AI boosts productivity, but blind trust in its output is risky. Knowing the craft behind the tools helps us think…
-
The Impact of AI on UX Design Work
UX is being transformed by AI-powered tools that speed up design work—but speed isn’t everything. The real challenge remains: solving…
-
How to Scale Research When You Don’t Have Enough Researchers
Good product discovery needs good research. Most teams don’t have enough researchers, so here’s how to scale quality research by…
-
Can Your Team Really Own Time to Revenue?
“Time to revenue” sounds useful—but in complex orgs, it’s rarely something teams can influence directly. Before you measure it, ask:…
-
From Behavior to Business Impact: Tracking ROI in Product Practice Change
How do you measure ROI when product teams are just starting to change? This article offers a 3-level framework to…
-
How to make your boss care about your initiative
Two quick tactics for ensuring your boss is paying attention to the great work you’re doing
-
“This Is Value-Based Delivery”: Teaching Customer-Centric Delivery to Technical Teams
Value based delivery is exactly how outcome-focused work should be phrased. Here’s why.
-
The Hidden Costs of OKRs: When goal-setting becomes a burden
OKRs aren’t a magic fix—they can even be a burden. This post highlights three cases where OKRs create more hassle…
-
5 So What’s instead of 5 Why’s
We use 5 Why’s to look into the past. What do we do when we need to look into the…