Back to database

Marily Nika, Google's AI use case

AI Product Lead at Google

Uses a multi-tool AI product management workflow to take a product idea from user research to PRD, clickable prototype, and stakeholder-ready vision video in about 20 minutes.

The problem

What was broken before AI

Early product work is slow because each step usually lives in a different mode. Research takes time, a PRD takes writing, a prototype takes design and engineering help, and a vision video usually requires a separate creative process. Even before a team can debate whether an idea is good, the PM has to spend days or weeks turning the concept into something concrete enough for other people to react to.

What changed

What the use case made possible

Marily chains specialized AI tools together so each part of the product loop hands off to the next. Perplexity surfaces real user concerns from forums and stages a debate between pro and skeptical viewpoints. A custom GPT turns the minimum feature set into a PRD. v0 converts that PRD into an interactive UI prototype. Flow or Sora then turns the concept into a short video that communicates the experience more vividly than a slide deck.

Why this matters

Why this use case is worth studying

Marily’s workflow is useful because it does not treat AI as one giant product manager. Each tool gets a specific job: research, structure, interface, video, or judging. That makes the workflow feel more like a product assembly line than a chatbot conversation. The PM still makes the calls, but AI helps turn a loose idea into artifacts that are easier to critique.

Use this when

When this pattern applies

Use this pattern when a product idea needs to become concrete quickly enough for a team to debate it. It works especially well for early discovery, product reviews, hackathons, demo days, or moments when stakeholders need more than a written concept before they can give useful feedback.

Exponential Builder analysis

01

Separate the jobs before choosing the tools.

Marily’s workflow works because research, critique, specification, prototyping, and storytelling each get their own step; that keeps AI output easier to inspect and less likely to blur weak evidence into polished strategy.

02

Make the idea survive opposition early.

The pro-versus-skeptic debate is a useful pressure test because it turns vague enthusiasm into concrete objections, then forces the feature set to answer those objections before anyone writes a PRD.

03

Ship artifacts for judgment, not certainty.

A PRD, clickable prototype, and concept video in 20 minutes can improve the quality of discussion, but the package should be treated as a fast learning object rather than proof that the product should be built.

Who this is for

Best fit

Product managers

Founders testing early product ideas

Product designers

Innovation teams

Startup teams preparing demos

Product leaders running demo days or bootcamps

Anyone who needs to turn research into a prototype and story quickly

What to avoid

Mistakes and warnings

Where this pattern can go wrong if you copy it too literally.

Do not confuse speed with validation.

Avoid treating forum comments as a replacement for real user research.

Watch for AI-generated PRDs that sound polished but skip tradeoffs.

Do not let the video make the product seem more proven than it is.

Keep the PM responsible for judgment, prioritization, and what happens next.

Public workflow preview

The shape of the workflow

A high-level look at how the use case works, with the reusable pattern made clear.

01

Start with a real product spark

Marily begins with a concrete user experience problem, like a fridge warning that a soda is 80 days old.

02

Research the user conversation

Perplexity’s discussion-focused search helps surface what real people say in places like Reddit.

03

Force the idea to defend itself

She asks AI to create opposing viewpoints so the product has to survive skeptical arguments.

04

Turn the research into a PRD

A custom GPT uses her preferred structure to generate a first-pass product requirements document.

05

Make the idea clickable

v0 turns the PRD into an interactive UI prototype that people can inspect and react to.

06

Sell the experience visually

Flow or Sora turns the feature list into a short vision video that helps stakeholders feel the product.

Copy the pattern

The reusable idea

Pattern in one sentence

Chain specialized AI tools so one product idea becomes research, a PRD, a prototype, and a vision asset in one fast loop.

Reusable idea

Marily’s workflow is a good reminder that product work gets better when the artifacts arrive earlier. You do not need to wait until research, specs, design, and storytelling happen in separate phases. If each AI tool handles one step well, a PM can create a rough but useful product package quickly enough to learn whether the idea deserves more time.

Steal this workflow

Use this as a 20-minute product discovery sprint:

1

Write one specific user pain in a single sentence.

2

Search discussion-heavy sources for real user language and recurring concerns.

3

Ask AI to create two opposing agents: one in favor of the idea, one skeptical.

4

Have them debate until the strongest objections are clear.

5

Extract the minimum feature set required to answer those objections.

6

Generate a first-pass PRD using your preferred structure: problem, target users, user needs, core features, priorities, rationale, and open questions.

7

Paste the PRD into a UI-generation tool and create a clickable prototype.

8

Turn the same feature set into a short concept-video prompt.

9

Share the research notes, objections, PRD, prototype, and video together, with a clear note that these are discovery artifacts for critique.

Suggested prompt

“I’m exploring this product idea: [specific product idea]. First, summarize what real users appear to care about based on discussion-style evidence I provide or ask me to collect. Then create two agents: one strongly in favor of the idea and one skeptical. Have them debate the idea for at least 20 turns, using the user concerns as evidence. After the debate, give me: 1) the strongest objections, 2) the minimum feature set needed to address them, 3) a first-pass PRD with problem, users, core features, priorities, and open questions, and 4) a concise prompt I can paste into a UI prototype tool.”

Field notes

Get new AI use cases in your inbox

A short weekly note on how real people are using AI to save time, make money, build tools, and run their lives.

No spam. Just useful AI use cases.

Related use cases

Keep exploring nearby systems.

Browse all