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