Updated
On this page
What this site covers
A short answer to how ASI OS organises work, routes ideas and keeps projects manageable.
This site documents four decisions about how work is organised in ASI OS. Each has its own pages.
When an activity grows into a project, the activity itself becomes the master. It keeps its name, history and message thread, and new work is created as member activities that point back to it. You still decide when work is escalated; nothing escalates on its own. Read The master rule.
The system suggests where an idea belongs, you confirm, and only then is the idea copied to its destination. Read Routing an idea.
Projects and programs are tidied by proposing lists, never deleting anything, and moving activities before retiring the containers. Read Narrowing projects and programs.
Other parts of the system adjust to these rules over time. None of that adjustment holds up the rules themselves.
Words used here
- Activity. One piece of work with its own thread and documents.
- Project and program. Groupings of activities. A project holds related activities; a program holds related projects.
- Master. The activity that oversees a project or program and its member activities.
- Route. The system's choice of work type, phase and first result for a piece of work.
The full list is on the Terms page.
Where a statement is an inference rather than a measurement, the source material says so. Treat the numbers on these pages as design targets, not guarantees.