Anyone can build an AI prototype. Every role still owns its swimlane.
A governance framework for product teams now that anyone can build an AI prototype in an afternoon. A prototype is a great way to sell what you are thinking. It takes the whole team to refine it into the best outcome. Every role can prototype and contribute, and each role keeps the final say in its own swimlane.
The problem
Anyone can build an AI prototype. Not everyone owns what ships.
I keep hearing the same story. A PM uses AI to build a working prototype. Everyone gets excited and wants to ship it. Design is then left with two bad options.
- Design becomes the blocker because it pushes back after everyone is already excited.
- Design becomes the clean-up crew, polishing a prototype it never shaped.
Both come from the same gap. AI prototyping changed who can make things. It did not change who is accountable for them. Product managers would not want designers writing the roadmap or setting priorities. The same respect should run in every direction.
Core principle
Overlap is welcome. Overriding is not.
Anyone can contribute in any lane. The owner of that lane has the final say.
- Work produced outside your lane is a point of view or suggestion, not a deliverable.
- Owners take outside contributions seriously and respond quickly.
- A prototype is a great way to sell what you are thinking. It is the start of the conversation, not the end of it. The team refines it from there to get the best outcome.
Decision rights
Who has the final say in each lane
Engineering
Owns production code, architecture and technical feasibility. Anyone can contribute prototype code or AI-generated code. Nothing reaches production without engineering code review and merge approval.
Design
Owns UI artifacts, user flows, usability, visual polish and design system use. Any prototype or mockup is input. Design may redesign it, run usability tests and conduct user interviews.
Content design
Owns every word in the product, including UI text, microcopy, error messages, onboarding, notifications, and voice and tone. AI-generated copy is a draft. Content design may rewrite it and test it with users.
Project and program management
Owns project plans, timelines, scope sequencing, dependencies and resourcing. Others can propose estimates, risks and milestones. The project or program manager sets the plan.
Product management
Owns the roadmap, PRDs, the business case and feature prioritization. Anyone can bring feature ideas and customer signals. Product decides what makes the roadmap.
The flow
Every AI prototype enters through intake
An AI prototype reaches release only after each lane owner has reviewed it. The reviews run at the same time, so governance does not turn into a slow relay.
- Create. Anyone uses AI to build a prototype or draft. It is labeled as a concept before it is shared, and any copy in it is marked as placeholder.
- Intake. The project or program manager logs it and routes it to every lane it touches. Nothing goes to leadership demos or customers from this step.
- Parallel lane reviews. These run at the same time, not one after another.
- Product checks fit against the roadmap and PRD.
- Design reviews usability, user needs and polish, and may redesign or test with users.
- Content design reviews every word for clarity, voice and accuracy, and may rewrite it.
- Engineering checks feasibility and architecture.
- Build. Engineering builds from the design-approved direction and the content-approved copy. AI-generated prototype code is a reference only. Any of it that ships goes through standard code review.
- Release gate. Each lane owner signs off on their lane. If a lane has open gaps, the work goes back to that lane's owner, not to the person who made the prototype.
RACI
How each role takes part in the work
The decision rights say who owns each lane. This matrix shows how every role takes part in each activity. Every row has exactly one A.
R is Responsible and does the work. A is Accountable and has the final say. C is Consulted before the decision. I is Informed after it.
| Activity | Product | Design | Content | Engineering | Program |
|---|---|---|---|---|---|
| Roadmap and prioritization | A/R | C | I | C | C |
| PRD and business case | A/R | C | C | C | I |
| UI design and usability testing | C | A/R | C | C | I |
| Product copy and voice | C | C | A/R | I | I |
| Architecture and production code | C | I | I | A/R | I |
| Project plan and timeline | C | C | C | C | A/R |
| Release gate | A | C | C | C | R |
Whoever builds an AI prototype is Consulted on the lanes it touches. Building the prototype does not make them Responsible or Accountable for that lane.
Avoiding the blocker
Governance only works if owners move fast
Bring design and content in at intake
Both see the prototype before the excitement builds, not after.
Set a review turnaround
Each lane commits to a response time for outside contributions, agreed by the team.
Control fidelity in early sharing
Concepts shared for feedback use grayscale or boxes and arrows wireframes, or carry a visible concept label. Polished prototypes do not go to leadership before design review.
Treat the prototype as a brief
Design's first output is a response to the PM's intent. It covers what works, what needs testing and what will change.
Disagreements
When lanes overlap or disagree
- The lane owner decides and records the reasoning in one or two sentences.
- The contributor can disagree, and the owner still decides. The team disagrees and commits.
- If the decision affects another lane's commitments, both owners escalate together to their shared leader with the user evidence and business impact laid out.
- Repeated overrides of a lane are a process issue to raise in a retro, not a debate to rerun on every project.
AI rules
Rules for AI prototypes and AI-generated work
- Label AI prototypes and other AI-generated artifacts as concepts when they are shared outside your lane.
- No AI-generated code goes to production without engineering review.
- Prototype code is disposable by default. Engineering decides what, if anything, carries forward.
- AI-generated flows and visuals go through design review like any other UI artifact.
- AI-generated copy is a draft. Content design has the final say on every word that reaches users.
- Placeholder copy in a prototype stays marked as placeholder, so no one mistakes it for approved copy.
- Product owns whether an AI-proposed feature belongs on the roadmap, no matter how finished the prototype looks.
- Project and program managers own the timeline, even when a prototype makes the work look closer to done than it is.