First-Principles Thinking for Data Analysts
What first-principles thinking means for a data analyst, with worked examples: questioning a metric, a benchmark and a dashboard request.
The non-technical half of the job — storytelling, portfolios, metric definitions and prioritization that make analysis land.
What first-principles thinking means for a data analyst, with worked examples: questioning a metric, a benchmark and a dashboard request.
The recurring SQL interview patterns behind most data analyst interviews, how to approach each, and how interviewers actually grade the answers.
How the RICE scoring framework works, a worked example ranking three features, and where it breaks down as a decision tool.
Most dashboards get built, launched and forgotten. Design for decisions, keep the metric count low, define every number, keep data fresh and review usage.
What hiring managers look for in a data analyst portfolio, how to choose three strong projects, and how to present each one around a business problem.
Which tool for which job? A practical way to choose between Excel, SQL and Power BI, based on data size, repeatability, audience and who needs to reuse the work.
How to present analysis so busy, non-technical people act on it. A simple structure, slide habits, and the mistakes that make good analysis get ignored.
Stop dashboard debates with a one-page metric definition. Includes a copy-paste template, a filled-in example and the owner, grain and exclusion rules that matter.
AI can write valid SQL in seconds, but it can't know which definition of revenue your CFO approved. Why a governed metrics layer matters, with benchmark data.