Unpacking Innovation

In this episode

• The problem with "innovation" as a target. Teresa explains why the word bothers her: when teams optimize for novel ways to serve customers, they often land on complex solutions that aren't the best ones. Petra reframes innovation as reduction — leaving things out, minimizing steps, "innovating on behalf of the user."

• The login timeline. A concrete walk through how one "boring" problem kept getting reinvented: username/password → single sign-on adding a two-step flow → Slack's magic links as a genuine moment of innovation → 1Password making magic links annoying again → passkeys, which most people don't yet understand. The lesson: an innovative solution changes the industry, then stops being innovative — and sometimes the company that changes the game (1Password) isn't even the one that owns the problem.

• Not all innovation is novel to the user. Something can be genuinely novel on one dimension — technical feasibility, a new framework, the business case — while looking completely ordinary to the customer. Novelty on one axis doesn't require novelty on the others.

• The cost of novelty. Beyond R&D, there's a cognitive cost: every novel flow asks users to learn a new system. Passkeys are the current example — friction now, in the hope of less friction later.

• Where good innovation comes from. The "just now possible" moment: in a truly cross-functional team, discovery surfaces a real customer struggle, and an engineer says, "there's a new way to solve that — and it's easier." Petra's pitch for cross-functional collaboration as the source of the good kind of innovation.

• The bottom line. The goal is to solve the customer problem. Innovation is only valuable when it does that. There's a whole industry built around helping companies "be more innovative" — Teresa would rather help them get better at solving customer problems.

Key takeaways

• Innovation is a means, not the goal — it only matters when it serves the customer better.

• Chasing novelty tends to produce complexity; optimizing for the best solution sometimes lands on a familiar pattern, and that's okay.

• Simplicity and reduction are a legitimate form of innovation.

• Every novel solution carries a cognitive cost — users have to learn it.

• A solution can be innovative for the business or the tech stack while looking totally ordinary to the user.

• The most durable innovation often emerges from cross-functional discovery, not an "innovation department."

• Differentiation through novelty is valuable — as long as you don't drop the "when it serves the customer" part.

Resources & Links:

• Follow Teresa Torres: ProductTalk.org

• Follow Petra Wille: Petra-Wille.com

Mentioned in this episode:

• Dieter Rams (rams-foundation.org) / Braun (braun.com) / Apple (apple.com) — design lineage where simplicity is the innovation

• Slack magic links (docs.slack.dev/authentication/sign-in-with-sla…) — a genuine login innovation in its moment

• Single sign-on (SSO) (en.wikipedia.org/wiki/Single_sign-on) — why login quietly became a two-step process

• 1Password (1password.com) — changed the game and made magic links feel like friction

• Jeff Patton (jpattonassociates.com) — User Story Mapping (jpattonassociates.com/story-mapping) — nobody asks to "log in"; they want their bookmarks saved and synced