INTERNAL TOOL
Argon: turning research into review-ready alignment PRDs
An internal ConnectWise tool that helps PMs turn interviews, notes, and docs into standardized 8-section PRDs without re-entering context every session.
Senior UX Designer · Jul 2026 - Oct 2026
A
ARGON
Dashboard
PRDs
BN
V1 PRD workbench
Start a PRD from your evidence
Upload or paste sources, generate eight sections, lock, and publish. Drafts stay private until published.
Start new PRD
Ready for you to publish
No PRDs ready to publish right now.
Your PRDs
Drafts only you can see.
Client Ticket Status View
Draft
You
Start →
Audit Trail Tables
Draft
You
Start →
Published PRDs
Visible to everyone in this environment.
Policy Assignment Model
Published
A. Rivera
View →
Callback Enhancements
Published
J. Park
View →
Cloud Services Migration
Published
S. Okonkwo
View →
Embedded AI Assistant (v1)
Published
M. Chen
View →
ARGON — v1
THE PROBLEM
PMs spent ~1 week of active effort per alignment PRD. Eng/UX estimated the full cycle at 3+ weeks.
Alignment PRDs were standardized on paper, but the path from interviews and notes to a director-ready artifact was still manual—copying context, hunting gaps, and rebuilding structure each session.
THE TARGET
≤3 hours active PM time to review-ready. ≤3,000 words / ≤10-minute read.
Standardized across all teams and simplified.
Map the workflow. Draw the line between human judgment and AI draft.
PM OWNS
Evidence, judgment, and lock decisions.
AI OWNS
Drafting sections and surfacing gaps.
MY ROLE
Senior UX Designer
01
Map PRD creation workflows PMs can follow
Define human vs AI ownership at each step—PM supplies evidence and judgment; Argon drafts and finds gaps.
02
Wireframe the lifecycle around core PRD mechanics
Context → generate → Questions gap-fill → score → lock → publish—wireframed as the core experience.
03
Focus context setup so drafts start grounded
Guide PMs to add notes and artifacts first so Argon extracts themes and surfaces gaps before any section is drafted.
Context first—fill the gaps before the draft
PMs bring notes, recordings, and supporting artifacts. Argon runs a guided context flow so as much as possible is captured—and missing pieces are surfaced—before any PRD section is generated.
ARGON
Dashboard
PRDs
BN
0 / 9
Context progress
Step 1: Choose how to add context
PRD Context Checklist
Source documents
Problem statement
Target personas
Business goals
Success metrics
Scope boundaries
Key assumptions
Stakeholders
Timeline constraints
Create PRD
Untitled PRD
Context setup — Your PRD assistant will guide you through adding context.
ARGON
Hi! I’ll walk you through adding context, then ask clarifying questions so we can draft a strong PRD together.
ARGON
First, how would you like to share context? You can mix and match — we’ll gather everything in one place.
A. Upload files
PDF, DOCX, TXT, MD, CSV — up to 25MB total
B. Paste or type notes
Drop research, transcripts, or rough ideas directly in chat
ARGON
Tip: The more context you share now, the fewer questions I’ll need to ask later.
01
Choose how to add context
Upload files or paste notes—mix and match. More context now means fewer questions later.
ARGON
Dashboard
PRDs
BN
1 / 9
Context progress
Step 2: Add source documents
PRD Context Checklist
Source documents
Problem statement
Target personas
Business goals
Success metrics
Scope boundaries
Key assumptions
Stakeholders
Timeline constraints
Create PRD
Client Ticket Status View
Context setup — add notes, recordings, and supporting artifacts.
ARGON
Add context here — files or pasted research. Click Done when this batch is enough to continue.
Files
Paste notes
Paste interview notes, research, or a rough problem statement…
Save notes
Pasted notes (9/30/2026)
Extracted — 3,179 chars
Done
02
Add notes & artifacts
Drop research into chat. A 9-item checklist tracks what’s captured as sources come in.
ARGON
Dashboard
PRDs
BN
4 / 9
Context progress
Step 3: Review extracted themes
PRD Context Checklist
Source documents
Problem statement
Target personas
Business goals
Success metrics
Scope boundaries
Key assumptions
Stakeholders
Timeline constraints
Client Ticket Status View
Context setup — edit anything that’s off before continuing.
ARGON
Here’s what I could extract from your context. Edit anything that’s off before we continue.
Summary
Clients call to ask “any update?” because the portal only shows internal statuses. Coordinators waste time resending updates already on the ticket.
Problem (from evidence)
No plain-language status for client contacts checking a single ticket on a laptop.
Target personas
Primary: client contact · Secondary: service coordinator. Out for v1: technicians, sales, finance.
Not found in the documents
No feature name · No baseline email volume · No rollout plan · No mobile requirement
Add more sources
Re-analyze
Start questions →
03
Review what Argon extracted
Edit themes, personas, and problem statements. Gaps not found in the documents are called out explicitly.
ARGON
Dashboard
PRDs
BN
9 / 9
Context progress
Step 5: Review & generate
PRD Context Checklist
Source documents
Problem statement
Target personas
Business goals
Success metrics
Scope boundaries
Key assumptions
Stakeholders
Timeline constraints
Plain-language ticket status for the client portal
ARGON
All set! Here’s what we gathered for your PRD:
Problem
Portal only shows internal statuses; clients open “any update?” contacts.
Personas
Primary: client contact · Secondary: service coordinator
In scope
Open tickets list · ticket detail · plain-language status mapping · empty / waiting / scheduled states
Out of scope
New ticket creation · attachments · live chat · SLA clocks · invoicing
Outcomes
Within 30 days, clients answer “who is this waiting on?” without activity threads; “any update?” volume drops by half.
ARGON
Ready to generate your PRD draft? Generation uses this brief. You can still edit sections after.
Generate PRD draft →
04
Close gaps, then generate
Clarify what’s missing until the brief is solid—then generate the eight-section PRD from that brief.
The bet: capture judgment before generation.
Context setup is where human vs AI ownership is clearest. PMs bring evidence and confirm extractions; Argon structures the brief and flags what documents never covered, so drafting starts from a filled-in brief, not empty boxes.
ARGON
Dashboard
PRDs
BN
4 / 9
Context progress
Step 3: Review extracted themes
PRD Context Checklist
Source documents
Problem statement
Target personas
Business goals
Success metrics
Scope boundaries
Key assumptions
Stakeholders
Timeline constraints
Client Ticket Status View
Context setup — edit anything that’s off before continuing.
ARGON
Here’s what I could extract from your context. Edit anything that’s off before we continue.
Summary
Clients call to ask “any update?” because the portal only shows internal statuses. Coordinators waste time resending updates already on the ticket.
Problem (from evidence)
No plain-language status for client contacts checking a single ticket on a laptop.
Target personas
Primary: client contact · Secondary: service coordinator. Out for v1: technicians, sales, finance.
Not found in the documents
No feature name · No baseline email volume · No rollout plan · No mobile requirement
Add more sources
Re-analyze
Start questions →
PM SUPPLIES
Notes, recordings, artifacts—and confirmation that extractions are right.
ARGON SURFACES
Structured brief, checklist progress, and gaps the sources never covered.
Score, close gaps, then lock—section by section.
The PM works each section with Argon closing gaps via Questions. A score gates lock. When all eight are locked, Final Review shows the full draft—ready to publish or export.
8 / 8
All locked
Exec Summary
Outcomes
Personas
Assumptions
Functional
Non-Functional
Out of Scope
Entitlements
Final Review
Review PRD Draft
Client Ticket Status View · All sections locked
Publish to Confluence
Export PDF
Title
Client Ticket Status View
Product
Client portal
Status
Draft · Locked
Owner
You
Date
Sep 30, 2026
1. Executive Summary
92/100
Locked
Plain-language ticket status in the client portal so contacts see who a ticket is waiting on—without opening activity threads.
2. Measurable Outcomes
90/100
Locked
Metric · Type · Target
Expand
“Any update?” contacts · Lagging · −50% / 30 days
Self-serve clarity · Leading · Answer “who waiting on?”
3. Personas
94/100
Locked
Primary: client contact (laptop). Secondary: service coordinator. Out: technicians, sales, finance.
4. Business Assumptions
91/100
Locked
Pilot on existing portal · desktop-only v1 · reuse ConnectWise status fields · no new entitlement.
5. Functional Requirements
93/100
Locked
ID · Requirement
Expand
FR-1 · Open-ticket list with plain-language status
FR-2 · Ticket detail: waiting-on, next step, schedule
FR-3 · Map internal CW statuses → client labels
6. Non-Functional Requirements
92/100
Locked
Topic · Threshold
Expand
Latency · List + detail < 2s
Auth · Inherit portal entitlements
Availability · Inherit portal uptime
7. Out of Scope
92/100
Locked
New tickets · attachments · live chat · SLA clocks · invoicing · proactive emails · mobile.
8. Entitlements
92/100
Locked
Product · Feature
Expand
Client portal · My tickets + ticket detail (v1)
No new SKU · Existing portal access
PRD Chat
ARGON
All eight sections locked. Ready to publish or export.
Ask about this draft…
Phase 1 shipped! But workbenches for other disciplines continue!
DELIVERED
Mapped PM workflows with stakeholders. Shipped Argon PRD Workbench as Phase 1.
NEXT
UXR and UXD workbenches are in progress. Ask me about the status of how they’re going!
FEEDBACK + OUTCOMES
Want to see more?
Next Case Study
Senior UX Designer based in Denver, CO
© 2026 All rights reserved.