Search within a document

Search within a document in Google Docs — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need to find a line I wrote in the product spec last month that mentioned ‘dynamic throttling’.…
I need to find a line I wrote in the product spec last month that mentioned ‘dynamic throttling’. Search within the spec document for the exact phrase dynamic throttling and return the paragraph and the heading above it. If there are multiple hits, show the three most recent edits where it appears so I can pick the right version before tomorrow’s meeting.

Improve — make it easier to accept

+
Before I share the spec with engineering, surface the most relevant instances of our keyword.…
Before I share the spec with engineering, surface the most relevant instances of our keyword. Highlight the first use of dynamic throttling near the top, list any contradictory statements about limits, and show the surrounding sentence with the author and timestamp so reviewers won’t argue over which paragraph is authoritative.

Decide — diagnose the stuck moment

+
I ran a search for dynamic throttling and pulled up three paragraphs that define it differently,…

I searched and found three different definitions for the same term

I ran a search for dynamic throttling and pulled up three paragraphs that define it differently, edited by three people across two weeks. I don’t know which definition the product lead prefers and the deadline is tomorrow. What’s the quickest way to reconcile these differences and who should I ask to sign off so engineering doesn’t implement the wrong behavior?

Become — change the pattern

+
Across specs we keep ending up with multiple near‑identical paragraphs describing the same behavior…

Search returns too many near‑matches and no clear canonical text

Across specs we keep ending up with multiple near‑identical paragraphs describing the same behavior and no single canonical definition. Teams waste time debating phrasing instead of implementing. How should I set a simple rule and workflow so future searches surface one authoritative paragraph—who owns the canonical copy, how are edits submitted, and what tagging stops duplicates from proliferating?

Next to this one

Other word processor work people do in Google Docs.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.