
Two big events coming up: a Chicago Product Alliance meetup this week & the Mind the Product Chicago conference on October 7 🧵

Product transformation consultant and leadership coach. Cofounder/co-lead of Chicago Product Alliance. Formerly @prodify @DoorDash @FetchRewards @eBay.

Two big events coming up: a Chicago Product Alliance meetup this week & the Mind the Product Chicago conference on October 7 🧵

If you missed it, see part 1 here.
Empowerment in product teams is both coveted and rare. Everyone wants it. Few attain it. Teams want more ownership, but aren't trusted by leadership. Leaders don't want to micromanage, but it feels risky to let go. Both sides want the same thing. Neither knows how to get there.

Leaders can't just disappear. They need to enable a gradual shift from directing to enabling as the team earns more autonomy. Part 2 of my series on building empowered product teams. buildcrescendo.com/blog/empo…

As Marty Cagan puts it: empowering teams doesn't mean less management. It means better management. That means choosing a pilot team carefully, matching your involvement to their needs & making it safe to fail with smaller bets. Delegation without follow-through is abdication.

Empowerment in product teams doesn't happen by stepping back. A company formed new squads and gave teams a lot of freedom. The teams became overwhelmed and totally lost. Progress stalled. Their biggest issue wasn't desire. It was setup and support.

The fix has more in common with behavior design, habit formation and agile principles. Empowerment works the same way, if you let it. Part 1 of my series on building empowered product teams. buildcrescendo.com/blog/empo…

There's an established "formula for organizational change" that explains where this breaks down. The failure to build empowerment is usually not for a lack of desire or even vision. It's something much smaller. And it's fixable.

Empowerment in product teams is both coveted and rare. Everyone wants it. Few attain it. Teams want more ownership, but aren't trusted by leadership. Leaders don't want to micromanage, but it feels risky to let go. Both sides want the same thing. Neither knows how to get there.

“The difference between successful people and really successful people is that really successful people say ‘no’ to almost everything.” -- Warren Buffett Q3 planning is a great moment to break the pattern. Here's how to start. 3/3 buildcrescendo.com/blog/over…

They don't even have time to save themselves. Changing this requires top down and bottom up discipline. Leaders: cut ruthlessly, double down on what remains, plan to 80% capacity. Teams: own your scope, surface tradeoffs, push back before you commit — not after. 2/3

Overcommitment in product teams is insidious. It leads to big compromises: PMs skip discovery, designers skip exploration & user testing, engineers optimize for velocity over understanding. Teams have more goals than people. Everyone feels harried. Actual progress is slow. 1/3

Part 2: Paths & Competencies buildcrescendo.com/blog/path…

I wrote two blog posts on this — one on why it matters, one on how to actually build it. Both links are below if this is something your product team needs. Part 1: Standards, Levels & Paths buildcrescendo.com/blog/stan…

A clear standard tells your team what great looks like. Levels put that in context of where each person is. Together they create a visible path forward. If people can see that path, they stay. If they can't, they look for one elsewhere.

Bill Walsh built an NFL dynasty in San Francisco by defining his Standard of Performance before the wins came. Mikel Arteta is doing that at Arsenal. Most product & engineering leaders do this for their products: OKRs, KPIs & principles. Fewer do it for the teams building them.

Early in my career I got a strong performance rating. My boss said "you're doing great, keep it up" and that was it. I walked out proud yet frustrated. I had no idea what the next level looked like or what it would take to get there.