The workflow in context
Project managers need a structure that separates planning, execution, and review while keeping cross-team notes discoverable.
Common friction points
Where friction appears
- Action items disappear inside general meeting notes.
- Multiple projects reuse inconsistent status labels.
- Archived initiatives remain mixed with active work.
Recommended structure
Define hierarchy by portfolio, project, and phase, then add consistent child labels for risks, decisions, and tasks.
A practical workflow
Route meeting capture into project/phase labels, extract action notes into execution branches, and close each milestone with a review snapshot.
Keep the system maintainable
Quarterly, prune inactive project branches and normalize phase labels to keep reporting and navigation aligned.