Qual Quant Triangulation

Reconcile what the numbers say with what users say, and design the study that settles it rather than restates it. Use when behavioural data and research findings point different ways. For reading the data on its own, use `behavioural-analytics`; for synthesising interviews on their own, use `affinity-diagram`.

3,414 stars 447 forksData & Analytics Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill qual-quant-triangulation
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/design-research/skills/qual-quant-triangulation ~/.claude/skills/qual-quant-triangulation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Qual-Quant Triangulation
You are an expert in what to do when the dashboard and the interviews disagree.
## What You Do
You take two accounts of the same behaviour — one measured, one reported — and work out what their disagreement means, which one answers the question actually being asked, and what the next study has to look like to settle it. The output is a decision about what to believe and one study design, not a summary of both sources.
## Disagreement Is Information
Teams treat a conflict as a problem with one source. It is usually a signal in its own right, and the shape of it tells you where to look:
| What you see | What it usually means |
| --- | --- |
| Data shows abandonment; users report no difficulty | They abandoned for a reason they do not attribute to the interface — price, timing, or a decision made before arriving |
| Users report a serious problem; data shows no effect | The affected segment is small, or the problem happens before instrumentation starts |
| Data improved; users report it feels worse | You optimised a proxy. The metric moved, the experience did not |
| Users are enthusiastic; retention is flat | Stated preference, not revealed. Enthusiasm in a session is not a return visit |
| Both look fine; the business outcome does not | You are measuring the task, not the goal the task serves |
The last two are the expensive ones, because nothing looks wrong until much later.
## Which Source Answers Which Question
Read the full skill on GitHub

Details

Skill name
qual-quant-triangulation
Path
design-research/skills/qual-quant-triangulation/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Qual Quant Triangulation skill do?

Reconcile what the numbers say with what users say, and design the study that settles it rather than restates it. Use when behavioural data and research findings point different ways. For reading the data on its own, use `behavioural-analytics`; for synthesising interviews on their own, use `affinity-diagram`.

How do I install the Qual Quant Triangulation skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Qual Quant Triangulation popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Crw

1.3k

fastcrw/crw

Scrape, crawl, map, search, parse, and extract web data with fastCRW — the open-source, self-hostable Firecrawl alternative (single Rust binary, ~14 MB RAM, Firecrawl-compatible /v1 + /v2 API). Use whenever the user needs page content, site-wide extraction, URL discovery, web search, PDF parsing, structured JSON from pages, or change tracking. Also use when the user mentions Firecrawl, Tavily, Crawl4AI, or "scrape/crawl/map/fetch/get the page/read this site/search the web" — crw is a drop-in for the Firecrawl SDKs.

Data & AnalyticsIn 1 list102

Data Visualization

3.4k

Owl-Listener/designer-skills

Select chart types and design data encodings — marks, axes, labels, and accessible chart styling. Use when presenting data graphically. Owns chart selection and encoding only; the categorical colour ramp itself belongs to `color-system`.

Data & Analytics447

Crw Crawl

1.3k

fastcrw/crw

Crawl an entire website or section and extract content from every page. Use when you need content from many pages under a common URL prefix: "crawl the whole site", "get all docs pages", "scrape every blog post", "download the full docs for RAG", "extract all pages under /api". Async BFS — starts a job and polls for results. Step 4 of the crw workflow ladder.

Data & AnalyticsIn 1 list102

Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.