> ## Content Index
> Fetch the complete content index at: https://anukulsaini.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What Building Query Noir Taught Me About How PMs Learn SQL
- URL: https://anukulsaini.com/what-query-noir-taught-me-about-how-pms-learn-sql/
- Published: 2026-10-23T07:56:17.000Z
- Updated: 2026-10-23T07:56:17.000Z
- Description: I did not write another SQL cheat sheet. I built a detective game with 40 skills — and designing the wrong answers taught me more about PM learning than another SELECT tutorial.
- Author: Anukul Saini
- Tags: Guide, Product

**Short answer:** PMs do not fail SQL because they cannot memorize JOIN syntax. They fail because the first query that “runs” feels like success — even when it is confidently wrong. That is why Query Noir’s distractors are designed to execute and still be incorrect.

I already wrote the practical guide: [SQL for Product Managers](https://anukulsaini.com/sql-for-product-managers-with-queries/). This post is about what happened when I tried to teach the same ideas as a game instead of a blog.

Play it here if you have not: [Query Noir](https://anukulsaini.com/query-noir/).

## Why a game instead of another tutorial

Tutorials optimize for completion. Games optimize for stuckness. Stuckness is where learning actually happens — if you design the stuckness on purpose.

As a PM, I have watched smart people nod through dashboards and then freeze when someone asks, “cool, but can you pull the cohort yourself?” The gap is not intelligence. The gap is reps with feedback.

## The design constraint that changed everything

Every business skin in Query Noir — food delivery, SaaS, D2C, fintech — maps onto the **same four table roles**. 

Only the vocabulary changes. That means one teaching template can travel across worlds without me rewriting pedagogy every time.

That is product thinking disguised as content design: shared ontology, swap the skin, keep the skill.

## Distractors that run (the uncomfortable trick)

A lot of SQL quizzes punish you with syntax errors. Real work is meaner. Your query runs. The chart looks fine. Leadership ships a decision. Then someone notices the join duplicated rows.

So in Query Noir, the “wrong” options are not random typos. The first distractor is supposed to *execute* and still miss the point. That mirrors PM life more than a red squiggle ever will.

![Wrong SELECT * feedback next to correct name, city query](https://anukulsaini.com/content/images/2026/10/query-noir-wrong-vs-correct.png)

Wrong-but-running (SELECT \*) vs correct (name, city)

## What I think PMs actually need (in order)

1. **SELECT + WHERE** — filter reality before you aggregate fantasy
2. **GROUP BY** — the moment dashboards stop feeling magical
3. **JOIN** — where silent duplication lives
4. **Windows / CTEs later** — power tools after judgment exists

If you jump to window functions because they sound senior, you will perform seniority and still misread a funnel.

## Ranks are not vanity

Query Noir’s ranks track SQL Level thresholds. The point is not a badge for LinkedIn. The point is a visible ladder so “I am bad at data” becomes “I am between these two rungs.”

PMs love ladders when the ladder is honest. We hate ladders when the ladder is corporate cosplay.

![Query Noir progress card showing Intern rank and SQL level](https://anukulsaini.com/content/images/2026/10/query-noir-correct.png)

Rank / level progress after a solved lead

## What this taught me as a product person

- Learning products need deliberate failure modes, not only success paths
- Shared data models beat one-off lesson pages
- Motivation dies when feedback is late — games compress the loop
- Your “SQL for PMs” article and your game should sell the same worldview

## If you are building a learning product

Steal this checklist:

1. Define the ontology before the content calendar
2. Make wrong answers informative
3. Instrument where people stall (even qualitatively at first)
4. Ship one vertical slice end-to-end before you write “40 skills” on a landing page

Also: if system design is your other gap, that is why [SysDesign Ops](https://anukulsaini.com/system-design/) exists as a sibling experiment — same philosophy, different skill.

## FAQ

#### Do product managers need to learn SQL?

You need enough SQL to ask better questions and spot bad answers. You do not need to replace your analyst — you need to stop being helpless without them.

#### Is a game better than a cheat sheet?

Cheat sheets help you remember. Games help you notice when you are wrong. Use both.

#### Why make wrong queries still run?

Because production mistakes often look like valid SQL. Syntax errors are training wheels. Silent wrong results are the real hazard.

#### How long until Query Noir feels useful?

If you clear a few early ranks with honest attempts — not copy-paste — you will feel the difference in your next metrics meeting.