quantitative-analysis

Featured

Answers a business question with data without fooling yourself — framing the question so an answer would change something, choosing the right comparison, checking the data before trusting it, recognizing the traps that produce confident wrong answers (aggregation reversals, survivorship, regression to the mean, multiple comparisons), and reporting uncertainty honestly. Use this to run an analysis, review one before acting on it, or work out why two people looking at the same data reached opposite conclusions.

AI & Automation 1,356 stars 209 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Quantitative analysis A wrong answer here is rarely an arithmetic error. It is a correct calculation on the wrong comparison, or on data that does not mean what the field name suggests. ## Frame the question so that an answer changes something Start from the decision. "How is retention doing" has no answer; "is the cohort we changed onboarding for retaining better than the one before it, enough to justify rolling it out" does. Write down what you expect to find and what you would do in each case before you look. If every possible result leads to the same action, the analysis is not worth running — and knowing that in advance is worth more than the analysis would have been. ## Choose the comparison before the metric Almost every meaningful number is a comparison, and the choice of what to compare against does more work than the calculation. - **Against what it was** — needs a period long enough to see through seasonality and noise. - **Against what it would have been** — the strongest comparison and the hardest to construct. A holdout group, a matched segment, a pre-trend extended forward. - **Against a peer or a benchmark** — only useful if the definitions genuinely match, which they usually do not. **Name the counterfactual explicitly.** "Revenue rose after the campaign" is a comparison against nothing, and it is the single most common way credit is claimed for a trend that was already happening. ## Interrogate the data before you trust it Look at the raw row...

Details

Author
cbrock84
Repository
cbrock84/headcount
Created
1 weeks ago
Last Updated
1 weeks ago
Language
Markdown
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category