From f35c5873fe9191d2522c0291963051e10e968082 Mon Sep 17 00:00:00 2001
From: modji <info@modji.ca>
Date: Thu, 23 Jul 2026 15:17:59 +0200
Subject: [PATCH] vault backup: 2026-07-23 15:17:59

---
 .../Building My PM System.md                  | 32 +++++++++----------
 .../Project Management/Capacity and WIP.md    | 21 +++++-------
 .../Project Management/Closing Projects.md    |  1 -
 .../Estimation and Forecasting.md             |  4 +--
 .../Meetings and Follow-up.md                 | 14 ++++----
 .../Project Management/Milestones vs Tasks.md |  7 ----
 .../Outcomes and Definition of Done.md        | 17 +++-------
 .../Ownership and Delegation.md               | 10 +++---
 .../Portfolio Management.md                   | 16 ++++------
 .../Project Management/Prioritization.md      | 21 +++++-------
 .../Project Management/Project Health.md      | 12 +++----
 .../Projects vs Operations.md                 | 16 +++-------
 .../Project Management/Risk Management.md     | 14 ++++----
 .../Project Management/Status Reporting.md    | 12 +++----
 Untitled.canvas                               |  1 +
 15 files changed, 74 insertions(+), 124 deletions(-)
 create mode 100644 Untitled.canvas

diff --git a/10 Knowledge/CTO Academy/Project Management/Building My PM System.md b/10 Knowledge/CTO Academy/Project Management/Building My PM System.md
index ae0aded..ad36459 100644
--- a/10 Knowledge/CTO Academy/Project Management/Building My PM System.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Building My PM System.md	
@@ -1,5 +1,3 @@
-# Building My PM System
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -253,18 +251,18 @@ stale because you are still expected to update everything.
 
 ## Related Concepts
 
--   \[\[Projects vs Operations\]\]
--   \[\[Outcomes and Definition of Done\]\]
--   \[\[Scope and Scope Creep\]\]
--   \[\[Milestones vs Tasks\]\]
--   \[\[Dependencies\]\]
--   \[\[Estimation and Forecasting\]\]
--   \[\[Prioritization\]\]
--   \[\[Capacity and WIP\]\]
--   \[\[Risk Management\]\]
--   \[\[Project Health\]\]
--   \[\[Status Reporting\]\]
--   \[\[Meetings and Follow-up\]\]
--   \[\[Ownership and Delegation\]\]
--   \[\[Portfolio Management\]\]
--   \[\[Closing Projects\]\]
+-   [[Projects vs Operations]]
+-   [[Outcomes and Definition of Done]]
+-   [[Scope and Scope Creep]]
+-   [[Milestones vs Tasks]]
+-   [[Dependencies]]
+-   [[Estimation and Forecasting]]
+-   [[Prioritization]]
+-   [[Capacity and WIP]]
+-   [[Risk Management]]
+-   [[Project Health]]
+-   [[Status Reporting]]
+-   [[Meetings and Follow-up]]
+-   [[Ownership and Delegation]]
+-   [[Portfolio Management]]
+-   [[Closing Projects]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Capacity and WIP.md b/10 Knowledge/CTO Academy/Project Management/Capacity and WIP.md
index 23f8eed..a360780 100644
--- a/10 Knowledge/CTO Academy/Project Management/Capacity and WIP.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Capacity and WIP.md	
@@ -1,5 +1,3 @@
-# Capacity and WIP
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -80,18 +78,15 @@ operational load, improving automation, or accepting risk.
 
 ## How It Fits Into the Bigger Picture
 
-This lesson builds on \[\[Projects vs Operations\]\], \[\[Outcomes and
-Definition of Done\]\], \[\[Scope and Scope Creep\]\], and
-\[\[Milestones vs Tasks\]\]. It prepares the project system to become
+This lesson builds on [[Projects vs Operations]], [[Outcomes and Definition of Done]], [[Scope and Scope Creep]], and [[Milestones vs Tasks]]. It prepares the project system to become
 more predictable and scalable.
 
 ## Related Concepts
 
--   \[\[Milestones vs Tasks\]\]
--   \[\[Dependencies\]\]
--   \[\[Estimation and Forecasting\]\]
--   \[\[Prioritization\]\]
--   \[[Capacity and WIP](#capacity-and-wip)\]
--   \[\[Risk Management\]\]
--   \[\[Project Health\]\]
--   \[\[Portfolio Management\]\]
+-   [[Milestones vs Tasks]]
+-   [[Dependencies]]
+-   [[Estimation and Forecasting]]
+-   [[Prioritization]]
+-   [[Risk Management]]
+-   [[Project Health]]
+-   [[Portfolio Management]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Closing Projects.md b/10 Knowledge/CTO Academy/Project Management/Closing Projects.md
index 46d6c6d..c19e3f0 100644
--- a/10 Knowledge/CTO Academy/Project Management/Closing Projects.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Closing Projects.md	
@@ -1,4 +1,3 @@
-
 Duration: 30--40 minutes
 
 ## Definition
diff --git a/10 Knowledge/CTO Academy/Project Management/Estimation and Forecasting.md b/10 Knowledge/CTO Academy/Project Management/Estimation and Forecasting.md
index f13160d..dd39f0e 100644
--- a/10 Knowledge/CTO Academy/Project Management/Estimation and Forecasting.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Estimation and Forecasting.md	
@@ -89,9 +89,7 @@ dependency acceleration, or increased risk.
 
 ## How It Fits Into the Bigger Picture
 
-This lesson builds on [[Projects vs Operations]], [[Outcomes and
-Definition of Done]], [[Scope and Scope Creep]], and
-[[Milestones vs Tasks]]. It prepares the project system to become
+This lesson builds on [[Projects vs Operations]], [[Outcomes and Definition of Done]], [[Scope and Scope Creep]], and [[Milestones vs Tasks]]. It prepares the project system to become
 more predictable and scalable.
 
 ## Related Concepts
diff --git a/10 Knowledge/CTO Academy/Project Management/Meetings and Follow-up.md b/10 Knowledge/CTO Academy/Project Management/Meetings and Follow-up.md
index 8a755cc..dc2d272 100644
--- a/10 Knowledge/CTO Academy/Project Management/Meetings and Follow-up.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Meetings and Follow-up.md	
@@ -1,5 +1,3 @@
-# Meetings and Follow-up
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -49,8 +47,8 @@ and use synchronous time for two blockers and one scope decision.
 ## How It Fits Into the Bigger Picture
 
 Status reporting communicates project state. Meetings resolve what
-cannot efficiently be resolved asynchronously. \[\[Ownership and
-Delegation\]\] determines who follows through afterward.
+cannot efficiently be resolved asynchronously. [[Ownership and
+Delegation]] determines who follows through afterward.
 
 ## My Company / Real-World Context
 
@@ -98,7 +96,7 @@ most discussion is detailed implementation.
 
 ## Related Concepts
 
--   \[\[Status Reporting\]\]
--   \[\[Ownership and Delegation\]\]
--   \[\[Decision Log\]\]
--   \[\[Project Health\]\]
+-   [[Status Reporting]]
+-   [[Ownership and Delegation]]
+-   [[Decision Log]]
+-   [[Project Health]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Milestones vs Tasks.md b/10 Knowledge/CTO Academy/Project Management/Milestones vs Tasks.md
index fc4fd74..d5a2c8f 100644
--- a/10 Knowledge/CTO Academy/Project Management/Milestones vs Tasks.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Milestones vs Tasks.md	
@@ -657,17 +657,10 @@ And because DevOps doesn't report to the project owner, that may be exactly the
 ## Related Concepts
 
 - [[Projects vs Operations]]
-    
 - [[Outcomes and Definition of Done]]
-    
 - [[Scope and Scope Creep]]
-    
 - [[Milestones vs Tasks]]
-    
 - [[Dependencies]]
-    
 - [[Capacity and WIP]]
-    
 - [[Project Health]]
-    
 - [[Portfolio Management]]
\ No newline at end of file
diff --git a/10 Knowledge/CTO Academy/Project Management/Outcomes and Definition of Done.md b/10 Knowledge/CTO Academy/Project Management/Outcomes and Definition of Done.md
index 984cb1b..6bc147a 100644
--- a/10 Knowledge/CTO Academy/Project Management/Outcomes and Definition of Done.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Outcomes and Definition of Done.md	
@@ -542,17 +542,8 @@ Even better is preventing this situation by defining those criteria **when the p
 ## Related Concepts
 
 - [[Projects vs Operations]]
-    
-- [[Project Outcome]]
-    
-- [[Definition of Done]]
-    
-- [[Scope]]
-    
-- [[Scope Creep]]
-    
-- [[Milestone]]
-    
+- [[Outcomes and Definition of Done]]
+- [[Scope and Scope Creep]]
+- [[Milestones vs Tasks]]
 - [[Project Health]]
-    
-- [[Stakeholder Management]]
\ No newline at end of file
+- [[Stakeholder Managemen]]
\ No newline at end of file
diff --git a/10 Knowledge/CTO Academy/Project Management/Ownership and Delegation.md b/10 Knowledge/CTO Academy/Project Management/Ownership and Delegation.md
index feeb519..0db2fd7 100644
--- a/10 Knowledge/CTO Academy/Project Management/Ownership and Delegation.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Ownership and Delegation.md	
@@ -1,5 +1,3 @@
-# Ownership and Delegation
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -128,7 +126,7 @@ immediately asks you what to do.
 
 ## Related Concepts
 
--   \[\[Portfolio Management\]\]
--   \[\[Meetings and Follow-up\]\]
--   \[\[Status Reporting\]\]
--   \[\[Project Health\]\]
+-  [[Portfolio Management]]
+-  [[Meetings and Follow-up]]
+-  [[Status Reporting]]
+-  [[Project Health]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Portfolio Management.md b/10 Knowledge/CTO Academy/Project Management/Portfolio Management.md
index c6fd2ff..1edeb31 100644
--- a/10 Knowledge/CTO Academy/Project Management/Portfolio Management.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Portfolio Management.md	
@@ -1,5 +1,3 @@
-# Portfolio Management
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -68,8 +66,8 @@ six, queue the others, and make the trade-off explicit.
 
 ## How It Fits Into the Bigger Picture
 
-\[\[Prioritization\]\] decides relative importance. \[\[Capacity and
-WIP\]\] determines how much can be active. \[\[Project Health\]\]
+\[\[Prioritization]] decides relative importance.[[Capacity and
+WIP]] determines how much can be active.[[Project Health]]
 identifies where intervention is needed. Portfolio management combines
 them.
 
@@ -129,8 +127,8 @@ team can begin.
 
 ## Related Concepts
 
--   \[\[Prioritization\]\]
--   \[\[Capacity and WIP\]\]
--   \[\[Project Health\]\]
--   \[\[Status Reporting\]\]
--   \[\[Ownership and Delegation\]\]
+-  [[Prioritization]]
+-  [[Capacity and WIP]]
+-  [[Project Health]]
+-  [[Status Reporting]]
+-  [[Ownership and Delegation]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Prioritization.md b/10 Knowledge/CTO Academy/Project Management/Prioritization.md
index 1d477c5..9396b36 100644
--- a/10 Knowledge/CTO Academy/Project Management/Prioritization.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Prioritization.md	
@@ -1,5 +1,3 @@
-# Prioritization
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -81,18 +79,15 @@ items are valuable. Ask:
 
 ## How It Fits Into the Bigger Picture
 
-This lesson builds on \[\[Projects vs Operations\]\], \[\[Outcomes and
-Definition of Done\]\], \[\[Scope and Scope Creep\]\], and
-\[\[Milestones vs Tasks\]\]. It prepares the project system to become
+This lesson builds on [[Projects vs Operations]],[[Outcomes and Definition of Done]],[[Scope and Scope Creep]], and [[Milestones vs Tasks]]. It prepares the project system to become
 more predictable and scalable.
 
 ## Related Concepts
 
--   \[\[Milestones vs Tasks\]\]
--   \[\[Dependencies\]\]
--   \[\[Estimation and Forecasting\]\]
--   \[[Prioritization](#prioritization)\]
--   \[\[Capacity and WIP\]\]
--   \[\[Risk Management\]\]
--   \[\[Project Health\]\]
--   \[\[Portfolio Management\]\]
+-  [[Milestones vs Tasks]]
+-  [[Dependencies]]
+-  [[Estimation and Forecasting]]
+-  [[Capacity and WIP]]
+-  [[Risk Management]]
+-  [[Project Health]]
+-  [[Portfolio Management]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Project Health.md b/10 Knowledge/CTO Academy/Project Management/Project Health.md
index a620847..b12fcd7 100644
--- a/10 Knowledge/CTO Academy/Project Management/Project Health.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Project Health.md	
@@ -1,5 +1,3 @@
-# Project Health
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -108,8 +106,8 @@ been missed, but a critical vendor deliverable has no confirmed date.
 
 ## Related Concepts
 
--   \[\[Milestones vs Tasks\]\]
--   \[\[Risk Management\]\]
--   \[\[Dependencies\]\]
--   \[\[Status Reporting\]\]
--   \[\[Portfolio Management\]\]
+-  [[Milestones vs Tasks]]
+-  [[Risk Management]]
+-  [[Dependencies]]
+-  [[Status Reporting]]
+-  [[Portfolio Management]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md b/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md
index 1e4ecc0..a609409 100644
--- a/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md	
@@ -449,16 +449,8 @@ That is considerably more useful than simply saying the team is busy.
 
 ## Related Concepts
 
-- [[Project Outcome]]
-    
-- [[Definition of Done]]
-    
-- [[Scope]]
-    
-- [[Milestone]]
-    
-- [[Capacity]]
-    
-- [[WIP]]
-    
+- [[Outcomes and Definition of Done]]
+- [[Scope and Scope Creep]]
+- [[Milestones vs Tasks]]
+- [[Capacity and WIP]]
 - [[Portfolio Management]]
\ No newline at end of file
diff --git a/10 Knowledge/CTO Academy/Project Management/Risk Management.md b/10 Knowledge/CTO Academy/Project Management/Risk Management.md
index 13c73d2..caa7769 100644
--- a/10 Knowledge/CTO Academy/Project Management/Risk Management.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Risk Management.md	
@@ -1,5 +1,3 @@
-# Risk Management
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -53,7 +51,7 @@ deserve Yellow health.
 
 Dependencies tell you what the project needs. Estimation exposes
 assumptions. Risk management asks what could make those assumptions
-fail. \[\[Project Health\]\] then reflects important risks before
+fail. [[Project Health]] then reflects important risks before
 deadlines are actually missed.
 
 ## My Company / Real-World Context
@@ -103,8 +101,8 @@ production is approaching.
 
 ## Related Concepts
 
--   \[\[Dependencies\]\]
--   \[\[Project Health\]\]
--   \[\[Estimation and Forecasting\]\]
--   \[\[Capacity and WIP\]\]
--   \[\[RAID\]\]
+-   [[Dependencies]]
+-   [[Project Health]]
+-   [[Estimation and Forecasting]]
+-   [[Capacity and WIP]]
+-   [[RAID]]
diff --git a/10 Knowledge/CTO Academy/Project Management/Status Reporting.md b/10 Knowledge/CTO Academy/Project Management/Status Reporting.md
index 5a8d292..1f547ad 100644
--- a/10 Knowledge/CTO Academy/Project Management/Status Reporting.md	
+++ b/10 Knowledge/CTO Academy/Project Management/Status Reporting.md	
@@ -1,5 +1,3 @@
-# Status Reporting
-
 Duration: 30--40 minutes
 
 ## Definition
@@ -61,7 +59,7 @@ Better:
 
 ## How It Fits Into the Bigger Picture
 
-\[\[Project Health\]\] tells you whether attention is required. Status
+[[Project Health]] tells you whether attention is required. Status
 reporting explains why, what changed, and what action is needed.
 
 ## My Company / Real-World Context
@@ -115,7 +113,7 @@ blocker.
 
 ## Related Concepts
 
--   \[\[Project Health\]\]
--   \[\[Milestones vs Tasks\]\]
--   \[\[Risk Management\]\]
--   \[\[Portfolio Management\]\]
+-   [[Project Health]]
+-   [[Milestones vs Tasks]]
+-   [[Risk Management]]
+-   [[Portfolio Management]]
diff --git a/Untitled.canvas b/Untitled.canvas
new file mode 100644
index 0000000..9e26dfe
--- /dev/null
+++ b/Untitled.canvas
@@ -0,0 +1 @@
+{}
\ No newline at end of file