PRD Template
Use the template below as a starting point for writing PRDs that define how the agent should guide users, propose actions, and execute workflows. #
Agentic Experience
Owner(s): Date: Target Release: Rollout: (alpha %, beta %, GA %) Status: Draft / Review / Final
1. Outcomes
What is the user outcome we want to drive? What should the agent do end-to-end?
- Provide a one-prompt flow that simplifies a complex workflow.
- Identify gaps or missing info and propose next-best actions.
- Execute approved updates directly in the product.
- Generate a summary or artifact (e.g., report, plan, or notes).
Example: From a simple chat prompt (“Create a task to follow up with ACME”), the agent:
- Surfaces missing info (due date, owner).
- Proposes next steps.
- Writes back a new Task record in the system.
- Generates a short summary of “what changed.”
2. User Role
Who is this for?
Primary:
- End User (e.g., Sales Rep, Customer Success Manager)
3. Scenario Description
3.1. Current Flow (without AI)
What steps would the user take today?
Example:
- Navigate to Task module.
- Manually enter due date, owner, and description.
- Save and assign task.
3.2. AI-Enabled Flow (with Agent)
How should the agent automate and simplify this flow?
Example:
- User: “Create a task to follow up with ACME tomorrow.”
- Agent:
- Detects missing info (assignee).
- Opens a Chatterblock to confirm details.
- On approval, writes back to Task module.
- Generates a recap in Canvas.
4. AI Interaction Modes
Which modes does this experience use? Check all that apply.
- Text (chat)
- Voice (hands-free)
- Navigation (agent moves app view)
- Chatterblock (embedded UI approval)
- Interactive (agent updates screen directly)
- Canvas (workspace for notes, briefs, drafts)
5. Suggested UX Design(s)
What should the user see/hear?
- Conversational tone: propose → confirm → execute.
- Show proposed changes in Chatterblock with Approve/Reject.
- Navigate to updated record after confirmation.
Attachments:
- Wireframes / mockups
- Demo video (optional)
6. Success Metrics
How do we measure user success/adoption?
Goal | Metric Example |
---|---|
Save time | Avg. minutes saved per workflow |
Increase adoption | % of users triggering this flow |
Improve accuracy | % of fields auto-filled correctly |
Satisfaction | Thumbs-up rating / CSAT score |
7. Business KPIs
How does this tie to business outcomes?
KPI | Product Attribution |
---|---|
Bookings | AI flows make demos/trials easier to close |
Retention | Higher adoption of key workflows |
Expansion | AI features drive upsell opportunities |
Margins | Reduced support/onboarding costs via automation |
Updated 4 days ago