Concept Testing Feedback Record

Template Overview

Before writing production code or committing engineering roadmaps, concept testing evaluates whether a proposed product solution resonates with genuine user problems. The Concept Testing Feedback Record organizes qualitative reactions, comprehension barriers, desirability ratings, and willingness-to-pay insights in structured Markdown.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Concept Test: [Concept Name] — [Participant ID]"
date: [YYYY-MM-DD]
researcher: "[[Researcher Name]]"
concept_name: "[Proposed Feature / Product Concept]"
participant_id: "[P01 / Pseudonym]"
participant_persona: "Engineering Team Lead"
desirability_rating: "High / Medium / Low"
comprehension_score: "1 to 5"
tags: [ux-research, concept-testing, discovery, product]
---

# Concept Testing Feedback — [Concept Name]

## 1. Study Goals & Concept Overview
- **Core Value Proposition Tested:** [Brief description of the proposed solution].
- **Primary Hypothesis:** Users will value [Feature X] sufficiently to switch from [Current Workflow].
- **Presentation Medium:** [Static wireframes / clickable prototype / narrative pitch].

## 2. Initial Participant Reactions
- **Immediate First Impressions:**
  - *"Quote capturing participant immediate emotional or cognitive response."*
- **Comprehension Assessment:**
  - What does the participant think this product does within 30 seconds of inspection?
  - Where did conceptual confusion or misalignment occur?

## 3. Detailed Feature Breakdown & Ratings
| Feature Element | Comprehension (1-5) | Perceived Value (1-5) | Key Friction or Concern |
|---|---|---|---|
| **Local Knowledge Graph** | 5 | 5 | Inquired how large vaults perform on mobile |
| **Instant Offline Transcription** | 5 | 5 | Expressed strong relief about meeting compliance |
| **Automated Meeting Summaries** | 4 | 3 | Wanted manual override of summary formatting |

## 4. Trade-Offs & Willingness to Pay
- **Feature Prioritization (Must-have vs Nice-to-have):**
  - **Critical:** Local storage, fast full-text search, hotkey recording.
  - **Optional:** Automatic tag hierarchy suggestions.
- **Willingness to Adopt:** Would participant replace existing tools? Why or why not?

## 5. Researcher Synthesis & Next Iteration
> [!NOTE] Synthesis Summary
> Participant showed intense interest in the offline privacy guarantee, but struggled to understand how tags interact with vault folders. Recommend revising the information architecture diagram.

## 6. Action Items
- [ ] Log participant session highlights in the research repository.
- [ ] Update prototype wireframe for iteration 2.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Concept Test: Offline Local Vaults — P14"
date: 2026-10-06
researcher: "[[Elena Rostova]]"
concept_name: "Hardware-Accelerated Offline Vaults"
participant_id: "P14"
participant_persona: "Principal Security Architect"
desirability_rating: "High"
comprehension_score: "5"
tags: [ux-research, concept-testing, discovery, security]
---

# Concept Testing Feedback — Offline Local Vaults

## 1. Study Goals & Concept Overview
Elena Rostova tested the offline local vault concept with P14, a principal security architect managing clinical research compliance. The session focused on local-first audio transcription and encrypted Markdown note generation.

## 2. Initial Participant Reactions
P14 immediately grasped the architecture: *"The fact that the model weights run on Apple Silicon with zero outbound network calls completely bypasses our vendor risk assessment bottleneck."*

## 3. Detailed Feature Breakdown
P14 rated hardware-accelerated transcription at 5/5 for value, noting corporate policies forbid cloud-hosted audio tools during confidential engineering reviews.

## 4. Key Takeaways
P14 confirmed readiness to pilot the desktop build across their 18-person security audit committee immediately.

When to Use and When to Avoid

When to Use

• Use during discovery sprints to evaluate unreleased product concepts and value propositions.
• Use when comparing alternative UX directions before engineering allocation.
• Use to preserve raw participant verbatim quotes alongside structured desirability ratings.

When to Avoid

• Avoid using for pixel-level UI usability bugs on existing production software.
• Avoid using for statistical quantitative surveys across thousands of users.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the concept testing interview transcript:
1. Extract verbatim quotes illustrating participant comprehension hurdles and moments of delight.
2. Group feedback into value proposition clarity, feature desirability, and adoption barriers.
3. Generate a structured Markdown summary table with numerical comprehension scores and action items.

Your data remains securely on your Mac with zero cloud exposure.