Design a shared-drive or workspace structure the whole team can navigate: folder logic, naming conventions, and the archiving rule that stops the mess returning.
Design an organisation system for: {{workspace}} (shared drive / project tool / physical space — current state, team size, what people can never find).
Deliver: the structure (folders/areas by how people SEARCH, not by org chart — max 3 levels deep; show the tree), naming conventions with examples (dates as YYYY-MM-DD, versions, no 'final_v2_REAL'), the ownership rule (every top-level area has one owner), the archiving rhythm (what moves where, when — the system that prevents re-cluttering), the migration plan for the existing mess (don't reorganise everything: archive the old world wholesale, build clean, move things as touched), and the one-page team guide. Design test: can a new hire find last quarter's {{example_item}} in 60 seconds?
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...