Skip to content

Research Plan

Purpose

Time-boxed plan for answering specific uncertainty before requirements, design, or investment decisions harden. One plan per study. A study with people can carry its scenarios, success criteria and screener under Methods, and its claims under an optional Findings section once it has run. A project’s existing single docs/helix/01-frame/research-plan.md stays valid.

Example

Show a worked example of this artifact
---
ddx:
  id: example.research-plan.depositmatch
  authoring:
    home: repo
  depends_on:
    - example.opportunity-canvas.depositmatch
    - example.feasibility-study.depositmatch
    - example.business-case.depositmatch
---

# Research Plan: DepositMatch Pilot Validation

**Research Lead**: Product Lead
**Time Budget**: 2 weeks

## Research Objectives

### Primary Research Questions

1. **Question**: Do bookkeeping firms with 5-25 employees spend enough weekly
   time on deposit reconciliation to make DepositMatch a top-three workflow
   problem?
   - **Why Important**: The Business Case assumes reconciliation is a capacity
     bottleneck, not a minor annoyance.
   - **Success Criteria**: Record reconciliation time and recent close-cycle
     failures reported by interviewed firms, including contrary evidence.

2. **Question**: Can representative pilot firms provide CSV exports that are
   consistent enough for column mapping and suggested matches?
   - **Why Important**: The Feasibility Study identifies CSV variability as the
     largest technical risk.
   - **Success Criteria**: Sample files from at least 3 firms can be mapped into
     the target import schema with fewer than 2 unsupported required fields per
     firm.

3. **Question**: Will pilot firms pay for a narrow reconciliation workspace
   before bank-feed integrations or ledger writeback exist?
   - **Why Important**: The Business Case pricing and obtainable market are
     low-confidence assumptions.
   - **Success Criteria**: Record reactions to $149/month and the reasons for
     accepting or rejecting it. Negative pricing evidence is a useful result.

### Knowledge Gaps

| Gap | Impact | Current Confidence |
|-----|--------|--------------------|
| Actual weekly reconciliation time for target firms | High | Low |
| CSV field variability across accounting systems and bank portals | High | Low |
| Willingness to pay for CSV-first workflow | High | Low |
| Which exception states reviewers need on day one | Medium | Medium |

## Scope

**In Scope**: Interviews with target firms, sample CSV collection, lightweight
workflow observation, pricing reaction, and exception-state discovery.

**Out of Scope**: Full usability testing, production onboarding, bank-feed
integration research, and accounting-ledger writeback.

**Assumptions**: Product Vision target segment and pilot scope remain stable
through the research window.

**Decision Enabled**: Which import assumptions, workflow priorities, and
pricing hypotheses to revise based on the findings.

## Research Methods

### Target Customer Interviews

- **Objective**: Address Questions 1 and 3.
- **Approach**: Conduct five 45-minute interviews with bookkeeping firm owners
  or reconciliation leads. Focus on recent close cycles, current tools, time
  spent, failure modes, and pricing reaction.
- **Participants/Sources**: Five U.S.-based bookkeeping firms with 5-25
  employees and recurring small-business clients.
- **Duration**: 1 week for recruiting and interviews.
- **Deliverable**: Interview notes, problem-intensity summary, pricing signal.
- **Decision Use**: Confirms whether to proceed with the pilot PRD or return to
  opportunity discovery.

### CSV Sample Review

- **Objective**: Address Question 2.
- **Approach**: Ask interview participants for anonymized or synthetic samples
  matching their real bank deposit and invoice exports. Map fields into the
  target import shape and record unsupported fields.
- **Participants/Sources**: At least three firms using different accounting or
  bank export patterns.
- **Duration**: 3 days.
- **Deliverable**: Import-compatibility matrix and required field list.
- **Decision Use**: Defines FEAT-001 import requirements and feasibility risk.

### Exception Workflow Probe

- **Objective**: Identify day-one exception states for FEAT-003.
- **Approach**: Walk participants through recent unresolved deposits and ask
  what owner, next action, and evidence they needed.
- **Participants/Sources**: Same interview participants; use recent examples.
- **Duration**: Included in interviews.
- **Deliverable**: Exception-state candidates and vocabulary.
- **Decision Use**: Prevents the PRD from inventing exception states detached
  from real reviewer work.

## Timeline

| Activity | Duration | Activities | Deliverables |
|-------|----------|------------|--------------|
| Planning | 1 day | Finalize screener, interview guide, data-handling plan | Approved plan |
| Investigation | 6 days | Interviews, CSV sample collection, workflow probes | Notes and sample inventory |
| Analysis | 3 days | Synthesize findings, map CSV compatibility, summarize pricing signal | Findings summary |
| Validation | 2 days | Review with product, engineering, and compliance | PRD readiness recommendation |

**Total Duration**: 2 weeks

## Research Risks

| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| Firms cannot share representative CSVs | Medium | High | Accept anonymized or synthetic samples with real column shape. |
| Interviewees overstate willingness to pay | High | Medium | Ask for pilot commitment and compare against current cost/time. |
| Sample size is too small to generalize | High | Medium | Treat findings as pilot-scope evidence only; require follow-up before scale claims. |
| Compliance review limits data collection | Medium | High | Use synthetic/anonymized samples and avoid live financial data during research. |

## Completion Criteria

- [ ] All three primary research questions answered with evidence or deferred
  with rationale.
- [ ] Interview notes summarize problem intensity and current alternatives.
- [ ] CSV compatibility matrix identifies required fields and unsupported
  cases.
- [ ] Pricing signal is explicit enough to confirm or revise the pilot Business
  Case.
- [ ] PRD readiness recommendation reviewed by product, engineering, and
  compliance.

Reference

ActivityFrame — Define what the system should do, for whom, and how success will be measured.
Default locationdocs/helix/01-frame/research/{study}.md
RequiresNone
EnablesNone
InformsPRD
Principles
Feature Specification
Stakeholder Map
Risk Register
Generation prompt
Show the full generation prompt
# Research Plan Generation Prompt
Plan the smallest useful research effort that will close the key knowledge gaps.

## Reference Anchors

Use these local resource summaries as grounding:

- `docs/resources/nng-ux-research-methods.md` grounds matching research
  methods to questions, evidence types, and product activity.
- `docs/resources/sba-market-research-competitive-analysis.md` grounds demand,
  pricing, customer, and market evidence expectations.

## Focus
- Frame the primary questions and the evidence needed.
- Keep methods, timeline, and risks lean.
- Make the deliverable and success criteria specific.
- Tie every method to a decision that will change if the evidence changes.
- Write one plan per study at `docs/helix/01-frame/research/[study].md`. A
  project's existing single `research-plan.md` stays valid.

## Studies With People

These sections are optional; add them when the study puts people in front of
the product or a prototype.

- **Scenarios** under Methods: each is a goal in the participant's words. Use
  no interface words, so the scenario does not tell them where to click.
- **Success Criteria** under Methods: what the participant has achieved when a
  scenario succeeds, citing the `US-<n>-AC<m>` IDs it exercises.
- **Screener** under Methods: who qualifies, who does not, and the mix of user
  segments.
- **Findings**, once the study has run: a Claims table, one row per claim,
  named by what it says.
  - Raw material (recordings, transcripts, session notes) is never copied into
    the repo; it stays where the study keeps it.
  - Name participants by pseudonym (P1, P2) and mask every excerpt: no names,
    contact details, employers or other detail that identifies a person.
  - Every claim has a Source (which session or document) and a Basis (what it
    rests on, such as "observed in 4 of 6 sessions"). The validator rejects a
    claim with no Source.
  - Rate Confidence apart from Direction, mark a claim Verified only once a
    second person has checked it against its source, and record what
    contradicts it and what the study could not establish.

## Role Boundary

Research Plan is not a PRD or Business Case. It defines how the team will
close uncertainty before downstream artifacts commit to scope, pricing,
metrics, or design assumptions, and its optional Findings record what the
study showed. The PRD, ADRs and designs cite those claims; they do not copy
them.

## Completion Criteria
- Questions are bounded and answerable.
- Methods fit the uncertainty level.
- The plan is short enough to execute.
- Success criteria say what decision the evidence will enable.
Template
Show the template structure
---
ddx:
  id: research-plan-[study]
  type: research-plan
  authoring:
    home: repo
---

# Research Plan: {{research_topic}}

**Research Lead**: {{research_lead}}
**Time Budget**: {{time_budget}}
**Created**: {{date}}

## Research Objectives

### Primary Research Questions

1. **Question**:
   - **Why Important**:
   - **Success Criteria**:

2. **Question**:
   - **Why Important**:
   - **Success Criteria**:

### Knowledge Gaps
| Gap | Impact | Current Confidence |
|-----|--------|--------------------|
| [Gap] | High/Med/Low | Low/Med/High |

## Scope

**In Scope**: [What will be investigated]
**Out of Scope**: [What will not]
**Assumptions**: [What we're taking as given]
**Decision Enabled**: [What downstream decision this research will unlock]

## Research Methods

### [Method Name]
- **Objective**: [Which question this addresses]
- **Approach**: [How it will be executed]
- **Participants/Sources**: [Who/what]
- **Duration**: [Time required]
- **Deliverable**: [Specific output]
- **Decision Use**: [How the finding changes scope, design, pricing, or go/no-go]

### Scenarios

<!-- Optional, as are Success Criteria and Screener below: for a study with
people. Each scenario is a goal in the participant's
words, with no interface words: "find last week's rejected rows", not "open
the Rejected tab". -->

| Scenario | Goal |
|----------|------|
| [scenario name] | [What the participant tries to achieve] |

### Success Criteria

| Scenario | Succeeds When | Acceptance Criteria |
|----------|---------------|---------------------|
| [scenario name] | [What the participant has achieved] | [US-XXX-AC1] |

### Screener

- **Include**: [Who qualifies]
- **Exclude**: [Who does not, and why]
- **Mix**: [How many of each user segment]

## Timeline

| Activity | Duration | Activities | Deliverables |
|-------|----------|------------|--------------|
| Planning | | Define scope, recruit | Scope and research questions clear |
| Investigation | | Execute methods | Raw data |
| Analysis | | Synthesize findings | Findings report |
| Validation | | Review with stakeholders | Validated conclusions |

**Total Duration**:

## Research Risks
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| | | | |

## Findings

<!-- Optional; add once the study has run. Raw material (recordings,
transcripts, notes) stays out of the repo. Name participants by pseudonym
(P1, P2). Mask any excerpt: no names, contact details, employers or other
detail that identifies a person. Every claim has a Source and a Basis. -->

### Claims

| Claim | Source | Basis | Confidence | Direction | Verified | Contradicting | Unknown |
|-------|--------|-------|------------|-----------|----------|---------------|---------|
| [What the study found] | [P3, session 2; or a document] | [Observed in 4 of 6 sessions; a masked excerpt] | [high / medium / low] | [supports / weakens / refutes: the assumption or decision] | [yes / no] | [Evidence against, or none] | [What this study could not establish] |

## Completion Criteria
- [ ] All research questions answered with evidence
- [ ] Findings documented and validated
- [ ] Recommendations are actionable
- [ ] Stakeholders aligned on conclusions
Innsigle seal: model-primary by HELIX

The signature covers the markdown source of this page, not these HTML bytes. This page quotes that seal; verify it against the source file.

Composition
model-primary
Issuer
HELIX helix
Signing key
ed25519:b0865d76d834a52c48506414d16f4e5a (build key)
Signed source
artifact-types/frame/research-plan.md
Signed
2026-11-16T15:52:45Z
Content digest
sha256:f872a37e…49fd2ec1

This build key is endorsed by the human key for build signing; the signature is not a detector and not a truth guarantee.

Raw attestation JSON
{
  "payload": {
    "innsigle": "1",
    "type": "https://innsigle.dev/claim/colophon/v1",
    "issued_at": "2026-11-16T15:52:45Z",
    "issuer": {
      "id": "helix",
      "name": "HELIX",
      "key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
      "key_url": "https://documentdrivendx.github.io/helix/.well-known/innsigle/keys.json"
    },
    "subjects": [
      {
        "uri": "https://documentdrivendx.github.io/helix/artifact-types/frame/research-plan/",
        "digest": {
          "alg": "sha256",
          "value": "f872a37ee4a934b9206914f39bc1c5b198c75eb115490f21cd0a1f1049fd2ec1"
        }
      }
    ],
    "colophon": {
      "schema_version": "1",
      "composition": "model-primary",
      "ingredients": [
        {
          "kind": "model",
          "name": "Claude",
          "role": "draft"
        },
        {
          "kind": "tool",
          "name": "sloptimizer",
          "role": "rewrite"
        },
        {
          "kind": "human",
          "name": "operator",
          "role": "structure-edit"
        }
      ],
      "notes": null
    }
  },
  "payload_encoding": "json",
  "signatures": [
    {
      "key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
      "alg": "ed25519",
      "sig": "Oakz9J_aNKzkU9H6osVe5gnBFXTfzq5Iq_V8sB2eKIKuidGKFSO3u1rBzs7LW-Czk2CHaow47FA26EPnQFvHDQ",
      "signed_at": "2026-11-16T15:52:45Z"
    }
  ]
}