For the Project Manager

A12A18A24A30A36A42K2026-04-18 DecisionSequenced behind A12 toavoid scaffold clash with A30.— EvangelosDecision memory attaches to the node — never lost, never re-asked
Decision memory attaches to the activity — never lost, never re-asked.

“I am really struggling to remember why we made the sequencing decisions we did six months ago.”

What it feels like today

  • Decisions get made in workshops, then evaporate. The schedule remembers the result, not the reason.
  • Six months later, when a stakeholder asks ‘why is this in front of that?’, everyone shrugs.
  • Hand-overs to new PMs are slow because the why lives in the previous PM’s head.

What CosmosPM does for this role

  • We attach a decision log to every activity and dependency it constrains — so the why travels with the work.
  • Facilitated review sessions where decisions are recorded as they’re made, not reconstructed later.
  • A knowledge graph of the project: people, decisions, dependencies, risks — all linked.

How we engage

  • Workshop: 1-day decision-capture session at any phase of the project.
  • Audit: review the existing schedule and tag the decisions implicit in it.
  • Tool: LogicReader — see logicreader.io.

Want to talk about this in detail? Get in touch — Evangelos reads every enquiry directly.

Back to all nine roles

Scroll to Top