Knowledge & Wikis
Part of Team knowledge and wiki software
Comparing a team wiki with a shared document folder
Decide whether a team needs maintained wiki answers, a shared document folder or both, using a practical retrieval and update check.
Choose a wiki when colleagues need one maintained answer to a recurring question. Keep a shared document folder when the main task is creating, reviewing and storing files. Many teams need both: a knowledge page for the instruction, and a file system for the form or working document it uses.
Compare the reader's task
Suppose someone asks, “How do I request a replacement laptop?” A folder might hold a form, an old instruction document and a supplier spreadsheet. A wiki page could bring the current steps, exception route and form together.
That is a choice the team must maintain, not a result the software guarantees. A neglected wiki can be as confusing as a folder.
| Reader need | Wiki page approach | Shared folder approach |
|---|---|---|
| Follow a procedure | Present the steps and exceptions in one maintained answer. | Identify the correct instruction file and establish that it is current. |
| Work on a deliverable | Point to the working file and its owner. | Keep the editable file in its agreed working location. |
| Find an old record | Identify the current rule while retaining context if needed. | Distinguish records from live instructions through clear labels. |
| Maintain the answer | Assign a page owner and review trigger. | Assign a document owner and release rule. |
Check what the folder already provides
A shared document folder can keep related files together. That helps with file organisation, but it does not identify which file contains an approved answer.
A wiki can make the answer itself the main object. Notion wiki pages can show an owner and verification status. Confluence pages have an owner who can be changed when the proposed new owner has the required access.
Neither status confirms the underlying instruction. A page that points to a separate form also needs a check that intended readers can open that form.
Give each item one job
Put the maintained instruction on a knowledge page and leave an editable form, spreadsheet or template in its working file location. State which item people should change. When the procedure changes, check the page and the supporting file together.
Avoid copying the whole instruction into several folders merely to make it visible. Give readers a route to one authoritative answer. Keep a dated copy only when it serves a distinct record purpose, and label it accordingly.
Make the choice with a retrieval task
Give a colleague the question without telling them the page or file name. Ask them to find the current answer, identify the first action and see whom to ask if their case differs.
Ask the owner to explain how that answer would be corrected after a process change. Use the accounts and permissions the team would actually have.
If the folder route is clear and its release rule is maintained, a wiki may add upkeep without solving a problem. If readers must open several plausible files to find the instruction, a maintained answer page addresses that. Record the route and the upkeep each option requires.
