AI for Product Management & Design
AI changes product work twice. It speeds up your own craft, from research synthesis to working prototypes, and it becomes a material you design with, one that behaves differently every time.
How AI is changing this work
- Prototypes are built from a prompt in an afternoon, so ideas are tested with something real.
- Research synthesis across hundreds of interviews and tickets takes hours, with quotes linked to sources.
- AI features need a new skill: defining good output and measuring it, because the same input can give different results.
Your layers: the 4 that matter most
1. Layer 9 · Applications & Interfaces
Why it matters
This is your own layer: the interface where people meet AI. Chat, voice, a button inside a page or an assistant beside the work are design choices with different costs.
What to do here
- Choose the form. A chat box is not the default. Often a button, a suggestion or a filled-in field serves better. AI features inside products
- Design for being wrong. Show sources, make edits easy and give people a way back, because some outputs will be wrong. Copilots
- Synthesis with receipts. Cluster interviews and feedback into themes, each linked to the clips and quotes behind it. Chat assistants
Examples as of 2026-11-11
2. Layer 8 · Agents
Why it matters
Agents that write code turn a described idea into a working app. They let you test real behaviour before engineering time is spent, and they are a feature type you may ship.
What to do here
- Prompt to prototype. Describe the app, refine by chatting, share a live link with five users this week. Coding agents
- Plan before build. Ask the agent for a plan first, correct it, then let it write. The agent loop
- Agent features need limits. If your product acts for users, decide what it may do alone and what needs a tap to confirm. Agent permissions & sandboxing
Examples as of 2026-11-11
3. Layer 7 · Orchestration & Tooling
Why it matters
For an AI feature, this layer is the product: the instructions, the data it is given and the tests it must pass. Product owns the definition of good.
What to do here
- Evals as the spec. Write 50 to 100 example inputs with what a good answer looks like; that set is your requirements. Guardrails & evals
- Context is the lever. Most quality gains come from what you put in front of the model, not from a bigger model. Context engineering
- Ground it. Give the feature your real content to answer from, and show the source. Retrieval-augmented generation (RAG)
Examples as of 2026-11-11
4. Layer 6 · Inference & Optimization
Why it matters
Every AI feature has a price and a wait per use. Both are set here, and both belong in the product decision.
What to do here
- Price per action. Estimate cost per use from input and output length before you design the pricing page. Model APIs & routers
- Right-size the model. Use a small fast model for simple steps and a large one only where quality demands it. Model APIs & routers
- Cache what repeats. Reusing the long, unchanging part of a request cuts cost and wait. Batching & KV caching
Examples as of 2026-11-11
High-leverage use cases
- Clickable prototypes. Working prototypes from a prompt or an existing design, for user tests the same week.
- Research synthesis. Themes, quotes and clips from interviews, tickets and reviews, traceable to the source.
- Specs and first drafts. Requirement docs, release notes and user stories drafted from notes, then edited.
- Eval sets for AI features. A maintained set of examples that defines good output and runs on every change.
- Cost and speed modelling. A simple model of cost and wait per user action, before committing to a design.
Start here: the next 30 to 60 days
- Week 1 to 2. Build one prototype with a prompt-to-app tool and put it in front of five users.
- Week 3 to 4. Run your last ten interviews through an AI synthesis tool and compare with your own notes.
- Day 30 to 60. For one AI feature, write 50 examples of good and bad output with engineering, and run them on every change.
- Day 30 to 60. Work out the cost and wait per use for that feature at your expected volume.
Risks and pitfalls
- Prototype mistaken for product. Generated apps demo well and hide gaps in security, data handling and edge cases. Label prototypes as prototypes.
- Shipping without evals. If you cannot measure quality, every model or prompt change is a gamble. Build the test set first.
- Synthetic users. A model's guess at what customers think is not research. Use it to prepare interviews, not to replace them.
- Costs that scale with success. AI features cost money per use. A popular feature with no cost model can erase its own margin.
- Features that act on untrusted text. If your feature reads web pages, emails or uploads, hidden instructions in them can steer it. (OWASP Top 10 for LLM Applications)
Sources
A product named on this page is an example, not a recommendation.
- Figma Make (figma.com) (2026-11-11)
- Dovetail (dovetail.com) (2026-11-11)
- Notion Agent (notion.com) (2026-11-11)
- Lovable (lovable.dev) (2026-11-11)
- v0 by Vercel (v0.app) (2026-11-11)
- Cursor (cursor.com) (2026-11-11)
- LangSmith (LangChain) (langchain.com) (2026-11-11)
- Braintrust (braintrust.dev) (2026-11-11)
- promptfoo (now part of OpenAI) (openai.com) (2026-11-11)
- OpenRouter (openrouter.ai) (2026-11-11)
- Amazon Bedrock (aws.amazon.com) (2026-11-11)
- Claude API pricing (platform.claude.com) (2026-11-11)
- OWASP Top 10 for LLM Applications (2026)
- NIST AI Risk Management Framework (AI RMF 1.0) (2023-01-26)
Other roles
HR & People · Finance · Sales · Marketing · Engineering · Cybersecurity · Legal & Compliance · Operations · Customer Support