Structure an internal knowledge base people actually use: the architecture by question-type, the ownership rules, and the rot prevention.
Structure our internal wiki. Context: {{context}} (team size, tool, what knowledge is scattered where, what people can never find, past wiki attempts: {{graveyard}}). Design: the architecture by question-type not org-chart (How do I…? / What's our policy on…? / Who owns…? / Why did we…? — people search by question), the page-type templates (the SOP, the decision record, the how-to — consistent shape makes writing and reading faster), the ownership rule (every page has one name and a review date — orphan pages are where trust dies), the rot prevention (the quarterly stale-page report, the archive-don't-delete rule, the it's-wrong flag anyone can raise), the seeding sprint (the 15 pages that answer the most-asked questions FIRST — from my scattered list; a wiki launches useful or launches dead), and the culture hook: the link-don't-retype norm — answers given in chat get a wiki link or become one.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekCompare options against weighted criteria to decide.
Turn 'how we do this around here' into a standard operating procedure anyone can follow on their fir...
Onboard a new supplier properly: the verification file, the terms confirmed in writing, the trial-or...
A sustainability audit that finds real savings: energy, waste, and procurement wins ranked by paybac...
Plan the end-of-year shutdown: customer notice, leave mechanics, skeleton coverage, and the January...
Audit your SaaS stack for overlap and waste: the inventory, the consolidation candidates, and the mi...