---
name: methodology-explainer
description: Explain analysis methodology to diverse audiences. Use when documenting 'how we did this' sections, building trust through transparency, or teaching analytical approaches to stakeholders.
title: methodology-explainer
canonical_url: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/methodology-explainer
last_updated: 2026-09-28T07:40:54.000Z
---

> **Skill from skilld.dev.** Follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [assets/methodology_slide_template.md](https://skilld.dev/api/skills-raw/nimrodfisher/data-analytics-skills/methodology-explainer/assets/methodology_slide_template.md), [assets/methodology_writeup_template.md](https://skilld.dev/api/skills-raw/nimrodfisher/data-analytics-skills/methodology-explainer/assets/methodology_writeup_template.md), [references/audience_depth_guide.md](https://skilld.dev/api/skills-raw/nimrodfisher/data-analytics-skills/methodology-explainer/references/audience_depth_guide.md), [references/methodology_explanation_patterns.md](https://skilld.dev/api/skills-raw/nimrodfisher/data-analytics-skills/methodology-explainer/references/methodology_explanation_patterns.md).
>
> If the user asked to install this Skill, run `npx skilld install nimrodfisher/data-analytics-skills/methodology-explainer`. Install writes the Skill files into the project, so every session loads them.

# When to use

Any time you deliver findings that require the audience to trust the method — A/B tests, attribution models, forecasts, statistical analyses, or anything where "how did you get that?" is a likely question. Write the methodology section before distributing results, not after questions arrive.

# Process

1. **Identify the audience tier** — use `references/audience_depth_guide.md` to determine the appropriate level: executive (why/what), business analyst (what/how at high level), or technical peer (full detail).
2. **Select the explanation pattern** — use `references/methodology_explanation_patterns.md` to pick the structure: narrative, layered (short summary + appendix), or Q&A format.
3. **Draft the core explanation** — cover: what question was asked, what data was used, what method was applied, what assumptions were made, and what the key limitation is.
4. **Apply plain-language rewrites** — replace statistical terms with business equivalents per the translation table in `references/methodology_explanation_patterns.md`.
5. **Add a limitations paragraph** — every methodology explanation must include at least one honest limitation and what it means for the conclusions.
6. **Produce deliverables** — write-up using `assets/methodology_writeup_template.md`; if the methodology will be presented, use `assets/methodology_slide_template.md`.

# Inputs the skill needs

- Description of the analytical method used (technique, data, steps)
- Audience type (executive / business / technical)
- Any assumptions or known limitations

# Output

- Plain-language methodology write-up
- Limitations section
- Completed `methodology_writeup_template.md` or `methodology_slide_template.md`