Knowledge Center

Home Find the next useful answer A starting point for employees looking for a practical guide, an authoritative reference, or help preparing a support question. This fictional Northstar Services knowledge center shows three routes through a large organization's information: follow a task guide, use a topic to locate its authoritative source, or prepare a clear question when you remain stuck. Choose a route Go directly to the kind of help you need. How-to Guides Follow a practical shared-folder example and choose the right next step. Resource Hub Use topic routes to identify the authoritative source for your question. Request Support Organize what you need, what you checked, and what happened. How the routes fit together Use the topic index to find a source, not to replace it. Guidance: How-to Guides offers a worked example for a repeatable task. Authoritative information: Resource Hub helps you identify the relevant approved source. Shared policies and forms stay in their authoritative home; this site does not reproduce them. Unresolved questions: Request Support helps you prepare useful details before using the support route your organization actually provides. A practical self-service path Move from a task to a source, then to a focused question if needed. Start with the task Use How-to Guides when you know what you need to do and want a clear example. 1 Check the relevant source Use Resource Hub to identify the topic and locate the authoritative resource that applies to your situation. 2 Prepare the handoff If the guide and source do not resolve the question, use Request Support to describe your goal, what you checked, and what happened. 3 How-to Guides Follow a practical guide A portable example for organizing shared project files. This fictional Northstar Services example uses the Lakeside Open Day project. It demonstrates an everyday information-organizing approach, not a required storage product, access rule, or company policy. For a related topic or authoritative source, visit Resource Hub . If the example does not fit or you cannot resolve a question, see how to prepare a support question . Example: organize a shared project folder A small, understandable structure makes it easier to find the working draft and final version. For the fictional Lakeside Open Day project, the folder is for planning materials. Use names your team recognizes, and place information only in locations approved for that information. State what belongs Write a short purpose, such as “working materials for planning the Lakeside Open Day.” Use it to decide whether a file belongs here. 1 Create a few recognizable folders Start with Planning, Drafts, and Final if those categories match the team's work. Add another folder only when it solves a real finding problem. 2 Name files for their content and state For example, name a file “Lakeside Open Day - room plan - draft.” Avoid labels such as “new version” that do not distinguish it from other files. 3 Check whether the structure works Ask a colleague who uses the folder to locate the room plan and explain which file appears to be the current draft. If they hesitate, clarify the folder or file names. 4 Match the guide to the task Examples of useful inputs and observable outcomes. Task Useful input Expected result Organize a shared project folder The folder's purpose and recurring file types A small structure a colleague can navigate Distinguish a draft from other files The file topic and its current state A descriptive name that makes the distinction visible Find the source for a workplace-process question The process name and the question to resolve The relevant authoritative source identified through Resource Hub Questions while following the example Use the approach where it fits; do not guess when an important detail is unclear. What if my tools use different names? Use the equivalent labels in the tools your organization provides. This example describes a way to organize information, not a required product or configuration. What if two files could be the current version? Do not decide from the name alone. Check the relevant project context or authoritative source available to your team. If the uncertainty remains, describe the files and what you checked when you prepare a question on Request Support. Where can I find a related process or policy? Use Resource Hub to identify the topic and locate the authoritative source. This guide does not copy or replace policies, forms, or approved procedures. Resource Hub Find the source that applies Choose a topic route, then consult its authoritative resource. Resource Hub is a topic index, not a collection of copied policies or forms. Use the routes below to identify what to look for and what context to check. Read the authoritative resource itself before acting; applicability can depend on the resource's stated audience, location, role, or eligibility. For a practical organizing example, see How-to Guides . If you cannot identify the right source or its meaning remains unclear, prepare a focused support question . Choose a reference area These topic summaries help narrow a search; they are not links to policies or a substitute for the authoritative source. Everyday tools Identify the tool, file type, or screen involved. Compare the resource's scope or version with the tool you are using. Use How-to Guides for the shared-folder example; consult the tool's authoritative guidance for product-specific steps. If the resource does not match, note the difference before asking for help. Collaboration Name the work item another person needs to find, review, or update. Check the team's approved location and naming conventions in their authoritative guidance. Use How-to Guides for a portable example of descriptive folder and file names. If ownership or the current version is unclear, record what you checked. Workplace processes Identify the process and the decision or action you need to understand. Locate the published, authoritative process or policy source rather than relying on a copied excerpt. Check the source's stated audience, location, role, and effective context before applying it. If scope or interpretation remains unclear, prepare a focused question through Request Support. Record what you checked A short source note makes the next conversation more useful. Before asking for help, capture these details: Topic and task: what you are trying to do, and which reference area seems relevant. Source: the title or location of the authoritative resource you consulted, if you found one. Scope: any stated audience, location, role, or eligibility limits that may affect your situation. Uncertainty: the specific step, term, or mismatch you could not resolve. Include only information needed to explain the question. Leave out passwords, access tokens, and unrelated personal or confidential details. Use Request Support to turn these notes into a clear handoff. Continue from the topic Open a practical guide or prepare a question about the source you checked. How-to Guides See the shared-folder example and practical task guidance. Request Support Describe the source, scope, and point that remains unclear. Request Support Prepare a useful support question Describe the task, the source you checked, and the result you observed. This page helps you organize a question; it does not submit a request. After preparing your notes, use the support route your organization provides. Before writing, check the relevant How-to Guide or use Resource Hub to identify the authoritative source. Include only the context needed to explain the issue; never include passwords or access tokens. Include the details someone needs Keep the handoff factual, scoped, and easy to investigate. State your goal Name the task you want to complete, such as finding the current room-plan draft for the Lakeside Open Day project. 1 Say what you checked Name the guide or authoritative source you consulted and the steps you took. If you could not locate a source, say which topic route you checked. 2 Describe what happened Report the visible result or message in plain language. Separate what you observed from what you think may have caused it. 3 Add only relevant context Mention the tool, file type, or stated scope detail that changes the question. Exclude passwords, access tokens, and unnecessary personal or confidential information. 4 Make the question specific A fictional shared-folder example shows the difference. Too broad “The project folder is confusing. Can someone fix it?” The reader's goal, checks, and point of uncertainty are missing. The task is not identified. The source or folders checked are not named. There is no observable result to investigate. More useful “I’m trying to find the current room-plan draft in the Lakeside Open Day folder. I checked Planning and Drafts, and both contain similarly named files. I reviewed the folder-naming example, but I still cannot tell which file is current. What project detail should I check next?” States the goal and where the reader looked. Names the guidance checked and the unresolved point. Asks a focused question without including sensitive information. Return to a useful route Review the example, check a topic, or start again from the center. How-to Guides Revisit the shared-folder example. Resource Hub Identify the authoritative source for a topic. Knowledge Center home Choose a different self-service route.