Find a useful answer—or ask a better question
This worked example follows Northstar Works, a fictional distributed organization coordinating project documents. Start with distinctive terms, check whether a result fits your situation, and share what you need to know if the answer remains unclear.
Refine the query
Add useful detail a step at a time; use only filters that the search experience actually offers.
Start with distinctive terms
Replace a broad topic with words likely to appear in the answer or its title.
- Broad: “meeting”
- More focused: “Orion rollout handover notes”
Add context when results are mixed
Include the project, team, document type, or time period that separates your task from similar work.
- Try “Orion handover notes” if the rollout name is distinctive.
- Add “2025” only if you need material from that period.
Change one term if results are scarce
Broaden deliberately rather than removing all context at once.
- Try “handover” or “transition notes” if “Orion rollout handover notes” returns nothing.
- If your search supports filters, remove one filter at a time and compare the results.
Try a search pattern
The examples are adaptable query ideas, not special operators or guaranteed search syntax.
Search a phrase
Use a distinctive phrase from a document or conversation when you remember the wording.
- Example: “handover checklist”
Try a synonym
Different teams may describe the same kind of work differently.
- Try “handover,” then “transition,” if the first term misses relevant material.
Add a project or topic
Pair a general document type with the name people use for the work.
- Example: “Orion rollout notes”
Check whether a result is worth relying on
A result can match your words and still be out of scope or out of date.
-
1
Match the scope
Check whether the result covers your project, location, role, and time period. Do not assume a result for one team applies everywhere.
-
2
Inspect the source
Look for the owning team or role and the original source. If ownership is unclear, treat the answer as unverified and ask who maintains it.
-
3
Check the date
Look for a publication or review date. An undated result may still help with background, but it does not establish that the information is current.
-
4
Follow the references
Check that linked material opens and supports the same scope. If sources disagree, do not combine them into a new rule; explain the conflict in your question.
Worked example: a project handover answer
Fictional reference excerpt
Topic: Orion rollout handover notes
Scope: Shared planning documents for the fictional Northstar Works Orion rollout team. This example does not describe local operating procedures.
Source owner: Project Knowledge Editor role.
Sample last-updated date: 14 May 2025. This is illustrative, not a verified review date.
Current-context check: Use the latest project handover note for the current work period. A note labelled “Archive” records earlier decisions for context; it is not the current handover.
Example search: “Orion rollout handover notes”
This excerpt models useful scope and date cues. A real answer should be checked against its authorized source and current project context.
Prepare a question others can answer
Include the goal, the context, what you already checked, and the specific uncertainty.
-
1
Ask one clear question
Name the decision or information you need. Avoid a broad opening such as “Can someone explain the project?”
-
2
Give the relevant context
State the project or work area and, when it matters, the location, role, language, or time period involved.
-
3
Say what you searched
List the terms you tried and the most relevant result you found. Mention whether the result was undated, archived, or apparently out of scope.
-
4
Explain what answer would unblock the work
Describe the decision or next step the answer needs to support, without implying approval or a guaranteed response time.
A question with enough context
Compare a vague request with a focused one. The details make it easier to identify the right source and respond to the actual uncertainty.
Too broad
“Where are the handover documents?”
- No project or work period
- No indication of what was searched
- No explanation of what is missing
More answerable
“For the fictional Orion rollout, I searched ‘Orion handover notes’ and found a note marked Archive from May 2025. Is there a current handover note for this work period, and which project source should I check?”
- Names the project and search terms
- Identifies the result and its date label
- States the specific information needed
Questions and answers
When should I broaden a search?
Broaden when a specific query returns no useful results. Change one element at a time: remove a filter, replace a narrow term with a related synonym, or shorten the query while keeping the project or topic.
When should I narrow a search?
Narrow when results mix projects, teams, periods, or document types. Add the most distinctive context first. Use filters only if they are available in your search experience.
What if results conflict or have no date?
Check the scope, source owner, and dates on each result. Do not treat an undated or archived item as current guidance. Include the conflicting titles or details in a question so the source owner can clarify.
What if the answer depends on my location, language, or role?
State that context in your search or question. A result from another location or role may not apply. Ask the relevant source owner to identify the applicable reference rather than assuming the broadest result is universal.
Where do I send a knowledge request?
Use the knowledge-request route published by your organization. If you cannot find it, ask your local knowledge owner or workplace support contact where questions are received. Include your question, context, search terms, and the result that left it unresolved.