Your analysis is completed using the Findings Analysis Report in your project document.

Use 1–2 key findings from each research part (A/B/C).
Each row must include:

• Claim – what you found (a key finding, not a topic)

• Evidence – what supports it (source, quote, data, example, feedback)

• Reasoning (Design Impact) – what it means for your proposed outcome (requirements, constraints, priorities, what to include/avoid)

What counts as a strong “Claim”?

A claim is a clear takeaway that answers your Big Question in some way.

✅ “Teen users engage more when onboarding is short and interactive…”
❌ “Onboarding” (too vague)

What counts as strong “Evidence”?

Evidence should include a specific detail plus the source:

• a statistic, quote, or key example

• a pattern from primary research (survey/interview observations)

• a comparison to existing outcomes
  (Include the source name/URL in your research log - you don’t need to paste URLs into the table.)

What counts as strong “Reasoning (Impact)”?

This is the “so what?” that turns research into project direction:

• “Therefore my outcome must…”

• “This means I should prioritise…”

• “To address this, I will avoid/include…”

CER Tables (what you complete)

Part A Findings (User & Human)

Use your Part A research to create 1–2 key findings about:

• user goals, needs, barriers, and preferences

• accessibility considerations

• where perspectives agree/disagree (Merit support)

Part B Findings (Technical & Practical)

Use your Part B research to create 1–2 key findings about:

• feasibility, tools, approaches, constraints

• conventions/standards you should follow

• key technical risks and trade-offs

Part C Findings (Wider Implications)

Use your Part C research to create 1–2 key findings about:

• legal/IP/privacy responsibilities

• ethics, fairness/bias, cultural considerations

• sustainability/future-proofing constraints