← Glean-ia-acs · Day 22 of 56
Level 300 — Power user30 minNIST MAP

Operator-Stacking Mastery

Narrowing a noisy query one constraint at a time

You'll be able to

Read first

Day 1 Lab

  1. Run a deliberately broad query — one that returns hundreds of mixed results.
  2. Add one operator (type:, app:, owner:, or after:) and note the new count.
  3. Add a second operator and note the count again.
  4. Identify which single operator cut the most noise — that is your highest-value constraint.
  5. Drop the weakest operator and confirm the result set barely changes.

Working Example: Stacking Constraints in Sequence

Each operator is one constraint. Stack them one at a time and the result count tells you which constraint actually mattered. Verified against search_filters.

roadmap                                  → 520 results (docs, chats, tickets, decks)
roadmap type:document                    → 180 results (cut the chatter)
roadmap type:document app:gdrive         →  74 results (one source of truth)
roadmap type:document app:gdrive after:2026-01-01  → 19 results (this year only)

Read the deltas:
  520 → 180   type: did the heavy lifting (the wrong KIND was the noise)
   74 →  19   after: was the precision finisher
Start with the constraint that removes the wrong kind of thing first.

Check for understanding

Given a 500-result query, which single operator would you add first, and why?

Check yourself

Pick an answer — you'll see if it's right and why.

1. When stacking operators on a 500-result query, how do you know which constraint did the real work?

2. You're exploring an unfamiliar result set and don't yet know which apps have hits. What's the better tool?

3. A trusted document ranks at #8. What's the honest way to investigate the ranking?

4. What three things must a written search recipe include so a teammate reproduces your exact result set?

5. Which question best justifies Glean's multi-step thinking mode over a quick answer?

Pass threshold 80% · week 4 quiz

In 10 seconds

“A noisy query isn't a dead end — it's a starting point. Add one operator at a time, watch the count fall, and you'll know exactly which constraint earned its keep.”

Next · Week 4 Day 2
Facets vs. Operators
← W03D07all lessonsW04D02 →