Welcome, Subject Matter Expert
You've been assigned as a domain expert for the Synapse Design Partner program. As an SME, you'll work across two platforms — Synapse Prompt Playground and Testiment — to drive product improvements. This page covers your role, tools, and how you'll work with Design Partners.
Complete these steps to be fully set up as an SME.
You're the bridge between raw user feedback and actionable product improvements. You never attend DP sessions directly — you review the raw data and write the improvement documents. You'll work across two platforms:
1. Synapse Prompt Playground
View all prompts used on the platform and improve them where needed — on a per-venture level or globally. This gives you complete flexibility to improve the quality of results from research, intelligence, and how the agents currently run.
2. Testiment
Review session recordings, analyze user behavior with AI, and generate structured fix documents. This is where all DP session data lives and where you create actionable improvements.
- Review raw session recordings, transcripts, and logs from Design Partner test sessions
- Generate structured fix documents that translate friction into actionable improvements
- Improve prompts via the Synapse Prompt Playground — per venture or globally — to enhance research, intelligence, and agent quality
- Own specific features and be accountable for their improvement arcs across sprints
- Review AI-drafted fixes, refine with your domain expertise, and submit for core team approval
- Coordinate retests after fixes ship to confirm the improvement landed
- Never attend DP sessions — this ensures unbiased, independent analysis
Your time is split between reviewing sessions, generating fixes, and coordinating with the core team.
Your work begins after DP sessions wrap up. Here's the weekly flow.
DP Sessions Run
Design Partners complete their scheduled test sessions. You're not involved during this phase — sessions are run independently.
Session Data Delivered
Recordings, transcripts, bug reports, and NPS results are compiled in Testiment and handed off to you for review.
SME Review Window
Watch recordings, read transcripts, analyze logs. Identify patterns, friction points, and opportunities. Draft your fixes.
Fix Submission
Submit completed fix documents with evidence, root cause analysis, and proposed changes. Core team reviews on Wednesday.
The Prompt Playground lets you view all prompts used across the Synapse platform and refine them to improve the quality of results. You can edit prompts on a per-venture level or globally, giving you complete flexibility over research output, intelligence quality, and agent behaviour.
🔎 View All Prompts
Browse the complete library of prompts used across the platform. See exactly what instructions drive each agent, research task, and intelligence output so you know where improvements are needed.
✎ Per-Venture Editing
Customise prompts for individual ventures. If a specific Design Partner's venture needs tailored research instructions or adjusted agent behaviour, you can override the defaults at the venture level.
🌐 Global Editing
Apply prompt improvements across the entire platform. When you identify a systemic quality issue — like research depth or output formatting — a global edit fixes it everywhere at once.
⚡ Impact on Quality
Your prompt changes directly improve the quality of research, intelligence outputs, and how agents run. This is the most direct lever SMEs have to improve the results Design Partners experience.
Testiment (testiment.io) is the platform where all DP session data lives. It's your primary workspace for reviewing sessions, analyzing feedback with AI, and generating fixes.
🔑 Get Access
You'll receive an invitation to Testiment via email. Accept the invite to create your account. If you haven't received it, contact your program lead. Once in, you have full access to all test data for your assigned features.
📋 View Tests & Sessions
Browse all tests and their recorded sessions. Each session includes the full video recording, screen capture, audio transcript, developer logs (console + network), NPS scores, and debrief answers. AI-generated summaries give you the key findings at a glance before you dive into raw data.
- Session recordings with timestamped events
- AI summaries of each session's key findings
- Bug reports with full context captures
- NPS scores and trend data per DP
- Think Aloud transcripts with word-level timestamps
- Developer logs: console errors, network failures, action steps
🤖 Chat with AI on Each Session
Every test and session has an AI assistant you can chat with. Ask it to highlight friction points, compare sessions across DPs, identify patterns, or draft sections of your fix document. AI acts as your copilot — you bring the domain expertise, it handles the data crunching.
- "What were the top 3 friction points in this session?"
- "Compare NPS trends for this feature across all DPs"
- "Draft an issue description based on the transcript at 2:34"
- "What console errors occurred during task 3?"
🛠 Generate Fixes
After reviewing a session, use Testiment to generate a fix proposal. The AI analyzes the session data, your notes, and the codebase context to draft a concrete fix. Generated fixes are submitted to the Synapse core team for approval — once approved, they go into the improvement pipeline.
- AI drafts the fix based on session evidence
- You review and refine before submitting
- Synapse core team approves or requests changes
- Approved fixes enter the sprint and get built
Testiment uses a structured template system to capture every finding. When you review a session and identify an issue, AI drafts a fix document from the session evidence. You refine it, and the core team approves it. Every fix follows one of these templates.
The Template System
There are two categories of fix documents. Use ICD for bugs and broken functionality. Use A1–A16 for feedback-area findings (quality, UX, trust, etc.). AI selects the right template automatically based on the session data.
Bug / Issue Template
Feedback Area Templates (A1 – A16)
Document ID Format
Every fix document gets a unique ID auto-generated by Testiment. The format encodes the template type, year, and sequence number.
Step-by-Step Process
Review the Session Data
Open the session in Testiment. Watch the recording, read the AI-generated summary, check console logs and network activity. Note specific friction points with timestamps and exact quotes.
Chat with AI to Dig Deeper
Use the AI copilot to analyze patterns: “What friction points appeared across all sessions for this feature?” or “Compare NPS trends for F2 across all DPs.” Let AI do the data crunching while you bring domain expertise.
Identify the Core Issue
Isolate the specific problem. Be precise: “Canvas fails to load when venture has no competitors” beats “Canvas doesn’t work sometimes.” Classify whether it’s a bug (ICD) or a feedback area finding (A1–A16).
Generate the Fix
Click “Generate Fix” in Testiment. AI analyzes the session evidence, selects the right template, and drafts the full document — including observation, evidence, root cause, and proposed fix. You get a complete first draft in seconds.
Review & Refine
Read the AI-drafted fix carefully. Add your domain expertise: refine the root cause analysis, adjust the proposed fix strategy, correct any inaccuracies. The AI is your starting point, not the final word.
Set Priority & Submit
Assign a priority (P0–P3) based on the framework below. Submit the fix document. The Synapse core team reviews it, approves or requests changes, and approved fixes enter the sprint pipeline.
Template: ICD — Bug / Issue Report
Use when something is broken, throws an error, or a workflow fails. This template captures the full technical picture.
Meta
01: What Happened
02: Technical Evidence
03: User Sentiment
04: Root Cause Analysis
05: Impact & 06: Proposed Fix
07: Review & Approval
Template: A1 — User Experience Finding
Use when a feature works but the experience is poor — users get lost, confused, or can’t find what they need.
Meta
01: Observation + UX Dimension
02: Evidence
03: Analysis
04: Impact & 05: Recommendation
Template: A2 — Output Quality Finding
Use when the system produces output that is inaccurate, irrelevant, or incomplete. The feature works mechanically but quality is insufficient.
Meta
01: Observation + 02: Quality Breakdown
03: Evidence + 04: Root Cause
05: Impact & 06: Fix Strategy
Template: A8 — Reliability & Trust Finding
Use when results are inconsistent, users can’t predict what they’ll get, or confidence levels are miscalibrated.
01: Observation + 02: Reliability Assessment
03: Evidence + 04: Root Cause
05: Recommendation
Priority Framework
All templates use the same 4-level priority scale. Assign based on severity and impact on the DP’s ability to get value from the feature.
What Every Template Shares
Regardless of template type, every fix document follows the same lifecycle and includes these common elements.
Common Structure Across All Templates
Data Sources AI Uses to Draft Fixes
When you click “Generate Fix,” Testiment’s AI pulls from all available session data to populate the template.
Writing a Strong Fix — Tips
- Always quote the DP directly when describing the issue — “I don’t know why this scored 72” is more compelling than “scoring felt opaque”
- One fix per issue. If you find 3 problems in one session, generate 3 separate fix documents
- Let AI draft first, then refine. Don’t start from scratch — AI handles the data assembly, you add domain expertise
- Include timestamps when referencing session recordings so the core team can jump to the exact moment
- Be specific about code changes. “Fix the bug in canvas” is vague. “Add null coalesce in canvas-summary.tsx:142” is actionable
- When in doubt, over-document. It’s easier for the core team to skim than to ask for missing context
Each SME owns specific features and generates fixes for their domain. Find your assignment below.