Universal Project Management

A needs-driven approach. Most projects do not need epics, quarterly goals and exhaustive documentation. They need the few systems that serve a clear purpose, and nothing else.

A03.1 · Doctrine

Achieve efficiency by maintaining simplicity.

Never: add a system unless it serves a clear purpose.
Always: remove it again as soon as it no longer does.

A03.2 · Structure of the guide

Three parts, read differently

The Core: What is true for every project. Read it once.
The Triggers: Situations you will recognise, each pointing to a protocol. Read them when something goes wrong.
The Protocols: What to do about it, and when to stop doing it.

A03.3 · A trigger, as issued

The team feels overwhelmed by the number and complexity of systems.

Response: Identify the essential core systems and lighten the burden of managing them.
Protocol: 001 · Simplify to core systems

A03.4 · Protocol 001Simplify to core systems

List. Classify. Remove.

ListWrite down every system you use, and in one line what it actually does for you.
ClassifyMark each one necessary, optimising, stabilising, or unclear.
RemoveAbsorb what can be absorbed. Remove what is unclear. Then remove the list.

Full documentation is being simplified. It will be issued when there is less of it.