AI Mindset Shift · 11:00 · 24 min

The Six Traps of AI Adoption (and How to Get Out of Them)

Faith ForsterFounder and Chief Maker, Discoveree

AI made building fast, so teams skip the thinking; name the six traps and use the Makers Manifesto principles to rethink instead.

Faith Forster
Chapters
Highlights

The moments worth replaying.

Short clips, each a complete thought. Share them, or jump to the spot in the full talk.

Faster builds, skipped thinking

The core diagnosis of the talk: engineering speed pushes product to skip discovery, and it only feels like progress.

2:23 IN THE TALK · 48 S
Uber burned a year's AI budget in four months

The token maxing story with the COO quote that made executives start asking what the spend buys customers.

7:39 IN THE TALK · 59 S
You would never abandon a graduate

The onboarding analogy that reframes agent setup as teaching, and the PM's job as sharing rationale and outcomes.

9:54 IN THE TALK · 67 S
Fin shipped faster than customers could absorb

A concrete 3x productivity story that turns into a lesson about customers as the real bottleneck.

14:54 IN THE TALK · 59 S
Humans sign the work

Principle 16 in one breath, backed by the Deloitte case and the post-mortem that blamed the model.

16:19 IN THE TALK · 37 S
Six traps, one instruction: rethink

The recap of all six trap names and the closing argument that the build will only get faster.

21:06 IN THE TALK · 49 S
In short

What Faith argued.

Faith Forster opens with a familiar Monday morning. Engineers or their agents have built three features over the weekend, nobody knows who asked for them, sales want to demo, and the CEO has seen a competitor's release video. Her diagnosis: AI has made engineering much faster, which puts pressure on product to keep up, so people shortcut or skip discovery and nobody asks whether the feature should exist. It feels like progress and often is not. In spring she spoke to 96 product leaders about their AI use and found wildly different levels of understanding. The old rule book was gone, so she gathered 45 cross-disciplinary operators and wrote the Makers Manifesto: four values, 16 principles, an Agile Manifesto for the AI age.

The talk was announced with four traps and grew to six, each a kind of thinking teams skip when they rush, each paired with a principle. Tokenmaxxing is measuring activity instead of value, with Uber as the cautionary tale: a leaderboard ranked teams by AI usage, the year's budget was gone in four months, and when asked what customers got, COO Andrew Macdonald said that link is not there yet. Principle 7, measure what drives value. The Abandoned Junior is handing agents work with no context, then concluding AI does not work, as she saw on the board of an HR tech scale-up. The way we like it had never been written down. Principle 6, make context explicit. Onboard your agent the way you would onboard a graduate.

It's Live is calling a feature done when it ships. Faith's line is that distribution, adoption, monetization and retention are not what comes after the making, they are the making now. Omio put a subscription live within three months and then spent six months refining packaging and revenue impact until average order value and tickets per customer rose. Principle 9, make for adoption. The Fire Hydrant is shipping faster than customers can absorb. Fin, formerly Intercom, tripled throughput and shipped nine tier one releases in two months until customers complained that the product no longer made sense; they now run one major release per quarter. Principle 8, match pace to readiness. Humans are the bottleneck, and often those humans are your customers.

AI Ate My Homework is letting the model decide and hoping for the best. Deloitte Australia repaid half a million dollars after an unsourced AI statistic landed in client work, and Air Canada tried to blame its own chatbot in a tribunal, which called that a remarkable submission. Principle 16, humans sign the work: you can delegate decisions but not accountability. Lipstick on Legacy is adding a sparkle icon to last year's roadmap instead of asking what problem is worth solving. The winners rebuild: Fin sold to Salesforce for about 3.6 billion dollars, Pendo rethought analytics as an agent with Novus, and Faith rebuilt Discoveree in six weeks. Her closing ask: download the manifesto, give it to your agents, run a retro on one value, and name your trap.

Key takeaways

8 things to take back to your team.

  1. Replace AI usage leaderboards and percent of code written by AI with a metric that ties AI spend to customer outcomes or revenue.
  2. Write down what good looks like for your codebase and documents, then onboard agents with that context before judging their output.
  3. Share the rationale behind each feature and the outcome you expect with your agents, not just the ticket.
  4. Move the definition of done from shipped to adopted, and plan the months of refinement after launch into the roadmap.
  5. Set release pace by what customers can absorb, for example one major release per quarter with small refinements between.
  6. Put a named human on every consequential AI decision so the post-mortem never says the root cause was the model.
  7. Re-ask what problem is worth solving before adding AI to every roadmap line, because build speed now allows a fundamentally different solution.
  8. Download the Makers Manifesto, pick one value for your next retro, and ask the team which thinking you are skipping.

Yes, humans are the bottleneck, but often not the humans within your own business. It's your customers.

You can delegate decisions, but you cannot delegate accountability.

If the definition of done is shifted from shipping to adoption, that is a whole different way of working.

Q&A

Questions from the room.

The video ends with the talk. The questions are summarised here.

Any tips for the fire hydrant problem when even internal teams cannot keep up with the shipping pace?

Shift the definition of done from shipping to adoption and organise roadmap, planning and teams around it; she calls this the biggest mindset shift in the manifesto. Less discovery is fine if you build to learn and verify with customers that the problem and the impact are right. It has to come from the executive level, because a PM told to push features out cannot fix it alone.

When the backlog is empty and developers ask what to do next, do you have a slow-down list for them too?

Start with no-regrets moves, the work you know needs doing with low risk of being wrong. Then stop treating product as PMs and designers doing all the thinking up front and handing off; involve developers in building to learn, since you can create ten prototypes now where one used to be expensive, and test them with internal users and close customers.

Slides

The slides that carry the argument.

Download the deck (PDF, 23 slides)
Slide 6Slide 7Slide 9Slide 13Slide 15Slide 19Slide 20Slide 23
Show all 23 slides
Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23
Mentioned on stage

Names, numbers, sources.

About the speaker

Faith Forster

Faith Forster is a product leader in B2B SaaS and fintech, including Wise, Dext and Legl, with two exits. She is the founder of Discoveree, a shared context layer for product teams, co-hosts a weekly podcast on building AI native products, and organises the Makers Manifesto.