Skip to main content

6.1 · Fix a definition for everyone

Remember the metric mismatch from Module 2? Make the right definition permanent.
Prompt
You’ll see: a change proposal (patch) created for your org’s context library — like a pull request for business logic. Once an admin approves, everyone’s answers use your definition. In most sessions no approver is present — that’s normal. After approval lands (ask your admin), re-ask your Module 2 reconciliation question and watch it route through your definition.
Governed by designYou propose, an owner approves, every change is versioned and revertible. That’s why teaching the platform is safe.

6.2 · Teach it your vocabulary

Prompt
You’ll see: a patch proposing the glossary additions. After approval, asking “how did the big three trend through EOQ crunch?” just works.

6.3 · Set your personal preferences

Prompt
You’ll see: your personal context file created/updated. Future threads pick it up automatically. (Personal vs. role vs. org context — and full role personas — get their own workshop: The Context Stack.)

6.4 · Capture a recurring workflow

Prompt
You’ll see: the workflow documented in your context. One sentence now replaces a 30-minute ritual.

6.5 · Know the escalation path

You want to…Path
Fix a metric definitionPropose a patch (6.1) — admin approves
Add vocabulary / context docsPropose a patch (6.2)
Personal preferences and workflowsYour own context — immediate
New data source connectedAsk your admin (Connectors page)
New governed metric surfaceData team — see the ontology workshop
Save it findableWhen you save a definition or preference, give it the words people actually use — the metric’s name and its synonyms (“NRR”, “net revenue retention”, “retention rate”). Future threads find saved knowledge by search, so the phrasing you save it under is the phrasing that gets it found — save it findable.

✅ Checkpoint

  • You proposed at least one definition or vocabulary patch
  • You set personal preferences
  • You know org-level (reviewed) vs personal (immediate) context
  • You know where self-service ends and the data team’s ontology work begins