See pricing
Unpacking Innovation
All Things Product with Teresa and PetraStrategy

Unpacking Innovation

Teresa Torres argues innovation is a byproduct of solving customer problems, not a goal, and that novelty carries a hidden learning cost for users. Petra Wille counters that simplicity is innovation too, and the history of the login screen tests both views.

September 29, 2026 · 15 min listen · 8 min read
0:00
–:––

Context

Petra Wille and Teresa Torres host All Things Product, a weekly show on product topics. This episode follows a conversation about Petra's "trash can tracking" idea for measuring discovery, where the question came up of how innovative a team's solutions are. Teresa was bothered by that framing, so the two dig into what "innovation" should mean for a product team. It matters to PMs because "be more innovative" is a common leadership ask, and it can push teams toward complex solutions that customers don't need.

The Big Idea

Innovation is not the goal. The goal is solving the customer's problem well, and a novel solution is only worth choosing when it is the best way to do that.

Teresa's worry is that treating innovation as the target pulls teams toward novelty for its own sake. Petra agrees, and adds that solving problems in ways that also make the company successful still counts as innovation.

Key Insights

Two definitions of innovation

The hosts start from different meanings of the word, and that explains much of the tension.

  • Teresa's reading: when people say innovation, they usually mean novel ways to serve the customer. She thinks we don't always need novel ways, and chasing them leads to complex solutions.
  • Petra's reading: shaped by design schools and Apple, simplicity is innovation too. Reducing complexity, leaving things out and cutting steps is where much product innovation came from.
  • Petra's phrase: "innovate on behalf of the user", which she uses with teams to push them to make things easier and simpler.

The login screen as a timeline

Teresa uses logging in to show how a good solution ages.

  • Username and password: a long-standing pattern everyone knew, so historically not a place to innovate.
  • Single sign-on: companies had to ask for a username first, then route the user to the right place. A one-step process became two steps, which added friction.
  • Slack's magic links: whether or not you use single sign-on, you enter your email and click a link. At that moment it was a real innovation.
  • 1Password: for people who use it, the login screen fills itself and one click logs you in. Now the magic link is annoying, because it forces a trip to your email.

The lesson is that yesterday's breakthrough becomes today's friction.

Novelty has a hidden user cost

Teresa says companies talk about the cost of building innovation but not the mental cost to the user. A new flow or system asks the user to learn something. Her example is passkeys: the average person does not know what a passkey is or how to use it, which is a lot of friction, even if it removes friction in the long run once implemented well.

Innovation can come from outside

Petra points out that the team building the login form did not always control the innovation. 1Password changed the game for how logging in feels, and the companies providing the form could not have solved that problem themselves. She also notes that pressure from competitors and weak security pushed logins to change, not only good product thinking.

Technically novel, invisible to users

Petra adds a second dimension. Something can be novel on the technical side, such as a new coding framework that fixes legacy issues, while looking familiar to the user. Novelty on one dimension does not have to show up on the others. Teresa agrees: not all innovation has a novel impact on the user.

Cross-functional teams spark innovation

Petra values truly cross-functional teams because innovation there often comes from conversations with engineers. The team observes where the customer struggles, then an engineer says there is a new way to solve it that is much easier. She calls this the "just now possible" moment, and it is the good type of innovation.

Mental Models & Frameworks

Innovate on behalf of the user

  • What it is: Petra's guiding claim when working with teams. Ask whether you can reduce something and make it easier or simpler for the user.
  • How it works: the test is the user's benefit, not how new the solution looks. Removing a step can be as innovative as adding a feature.
  • When to use it: when a team is tempted to add complexity to look innovative.

Best solution, not novel solution

Teresa's filter is to focus on the best solution to the customer problem. If the best solution turns out to be a pedestrian pattern, the team should be fine with that. Novelty is a possible outcome of that search, not the target of it.

Decision Principles

Principle: Consider novel, don't always choose it

  • When: you are choosing between solutions to a customer problem.
  • Why: both hosts agree you should push boundaries and consider innovative options, and ask whether a novel idea can make the problem go away. But novelty comes with a burden on the user to learn something new, so the novel option is not automatically the best.

Principle: Match the push to the team

  • When: a product leader is deciding what message a team needs about innovation.
  • Why: Petra says product teams often focus on small iterations and maintenance, so a push toward "new enough to talk about" can help when planning the next quarter. Leaders know which teams need that push and which need the opposite one, to stop innovating for its own sake.

Trade-offs & Nuance

Differentiation versus complexity

Petra notes that an innovative solution clearly differentiates you from competitors and gives customers a reason to pick you. Teresa agrees there are many advantages to novelty when it serves the customer. The tension is that chasing that differentiation can produce solutions too complex to serve customers better.

Login is a tricky example

Petra says login has limits as an example. In her Jeff Patton style story mapping work, no user ever said they wanted to log in. Users wanted to bookmark things, sync across devices and keep them persistent, and they tolerated login as a means to that. Innovating on the actual user goal, like bookmarking a job posting, is easier to reason about than innovating on a login form. Teresa replies that you could swap login for almost anything and the point still holds.

Common Mistakes

Mistake: Treating innovation as the target

  • Why it happens: companies build whole industries and departments around being "innovative enough".
  • Why it hurts: the team drifts toward novel solutions when a familiar pattern would serve customers better, and innovation only has value if it solves the customer problem.
  • Better approach: Teresa would rather help companies get better at solving customer problems, and Petra adds, solving them in ways that make the company successful.

Practical Application

Audit your next solution for novelty

Before committing to a solution, ask whether the team is choosing it because it is best for the customer or because it is new. Write down the plainer alternative and compare the two on user effort.

Name the user's learning cost

For any new flow, list what the user must learn or change. Use passkeys as the reference case: a benefit in the long run, but real friction for someone who has never heard of them.

Check for a simplifying option

Petra's "innovate on behalf of the user" prompt: ask whether a step can be removed, a decision left out, or the process made simpler before adding anything new.

Bring engineers into discovery early

Have engineers hear the customer struggles directly. Petra's experience is that a "just now possible" idea often comes from an engineer who knows a new way to solve the problem.

Questions to Consider

  • Where has our team picked a more complex solution to a customer problem mainly because it felt more innovative than a familiar pattern?
  • What new thing would a user have to learn to use our latest feature, and did we count that mental effort as a cost?
  • Which part of our product is a solved, familiar pattern (like a login screen) that we are still tempted to reinvent?
  • Which of our teams needs a push toward bolder ideas, and which needs a push to stop innovating for its own sake?

Bottom Line

Innovation is a byproduct of solving customer problems well, not a target. Push boundaries when choosing solutions, but remember that novelty makes users learn something new, so choose it only when it is truly the best way to serve them.

Resources Mentioned

ResourceTypeWhy it was mentioned
User story mapping (Jeff Patton)MethodPetra used it to explain why users never ask for a login, only for the goals a login enables.

Case Studies Mentioned

The evolution of logging in

Logins moved from username and password to single sign-on, which added a step, then to Slack's magic links, which felt like an innovation. Users of 1Password then found magic links annoying because they had to open their email. Passkeys are the newest change and still unfamiliar to most people. The lesson is that a good solution can become friction as user habits and tools change.

Tools & Products

Tool / ProductWhat it doesWhy it was mentioned
Slack magic linksLog in by entering your email and clicking a linkA moment of real innovation that later became friction for password manager users.
1PasswordPassword manager that fills login formsIt changed how logging in feels, outside the control of the companies providing login forms.
PasskeysPasswordless login methodAn example of novelty that carries a learning cost for users who do not know what a passkey is.

People to Follow

Jeff Patton

Creator of user story mapping, mentioned by Petra as the method that showed her why a login rarely belongs on a story map.

Notable Quotes

"Our goal isn't novelty. Our goal is to find the best way to serve the customer." (Teresa Torres)

"Innovation is only valuable if it solves the customer problem." (Teresa Torres)

"Innovate on behalf of the user." (Petra Wille)

AI PM course

Everyone hears the same episodes.
Few can do what they describe.

Start for free