Sub-workstreams (all within L1)
Restructured 2026-05-31. Previously these were separate top-level agendas (L1–L5). They are now sub-workstreams within this single L1 agenda. Future frameworks get L2, L3 etc.
<table header-row="true"> <tr> <td>Workstream</td> <td>What it is</td> <td>Status</td> </tr> <tr> <td>Video / content</td> <td>LinkedIn video series on OCPA for MSME operators</td> <td>Active — in production via Cowork</td> </tr> <tr> <td>Conceptual model</td> <td>v0.5 structural lock — seven-element architecture, Decision Map as deliverable</td> <td>Locked — triage of 10 open questions next</td> </tr> <tr> <td>Evidence layer</td> <td>Real-world validation of the framework's claims. Gates B4 (NGA Lag Audit).</td> <td>Planned — awaits conceptual triage</td> </tr> <tr> <td>Diagnostic tool</td> <td>Practical MSME diagnostic instrument built on v0.5</td> <td>Planned — awaits evidence layer</td> </tr> <tr> <td>Distribution</td> <td>Workshops, speaking, publishing, go-to-market</td> <td>Idea — premature until evidence exists</td> </tr> </table> ## What this is The conceptual model workstream for NGA’s Extended Critical Path Method (CPM) framework — a structured approach to helping MSME operators map, stress-test, and focus their project and operational workflows. ## Current state: v0.5 — STRUCTURAL LOCK (2026-05-28) Dishant declared structural lock on v0.5 during the same Cowork session that produced v0.3. The conceptual architecture is now stable. L3 (evidence) and L4 (diagnostic) can be designed and built on this foundation without waiting for further framework revision. **What structural lock means:** The seven-element architecture below is finalised. Future versions may refine language, sharpen descriptions, or add examples — they do not restructure the core. This is the same class of decision as the HSIPL report template lock or the practice philosophy lock. **What v0.5 changes from v0.3:** Gantt elevated to co-equal fourth tool (not a v0.1-output layer). Multi-resource synthesis becomes the normal case (not an edge case). Lead/lag minimisation becomes an explicit step. TOC produces a constraint *sequence*, not a single identification. PERT sensitivity added as a distinct analytical step. Capacity analysis added (the realistic ceiling beyond bottleneck identification). Decision Map named as the final deliverable — the thing the client pays for. Prior-art defensiveness dropped; posture shifts to utility-first. *Note: v0.5 was captured as L2_v0.5_*[*delta.md*](http://delta.md)* in the Cowork outputs folder. Full document rewrite to v0.5 pending Dishant's "lock v0.5" signal.* ### Version progression (2026-05-28, single session) **v0.1** — First formal draft **v0.2** — Restructured around three-step sequential workflow (CPM → PERT → TOC). Integrated four PDM dependency types, lead/lag, Total vs Free Float. **v0.3** — Added: (a) complex-internal/simple-external design principle, (b) six-class resource taxonomy splitting Labour from Key Personnel, (c) joint Total Float / Free Float formulas for parallel-constrained pairs, (d) lag reduction as both framework feature AND standalone NGA offering. Ten open questions in §10. **v0.4** — **OM repositioning.** Framework reframed from project management tool to **Operations Management tool for MSMEs**. Internal name assigned: **OCPA (Operational Critical Path Analysis)**. Gantt chart integrated as a framework output layer. **v0.5** — **Structural lock by Dishant.** Architecture finalised. This is the version L3 and L4 build on. ### What OM repositioning means The shift from CPM-as-project-management to OCPA-as-operations-management is significant: - **Competitive landscape changes.** OCPA no longer competes with MS Project, Primavera, or standard PM software. It competes with operational consulting frameworks — lean, TOC-based consulting, ERP implementations. That's a far less crowded space. - **Audience changes.** The primary user is not a project manager. It's a business owner or COO trying to understand why their operations run the way they do. The diagnostic is operational, not project-level. - **Dishant's signal confirmed.** *"It will soon be a concept on which businesses will run. I will be redesigning MSME's working strategies."* OM repositioning is the structural basis for that claim. - **Gantt as a surface.** The Gantt chart in v0.4 is not the framework — it's the output surface the business owner sees. The framework runs underneath; the Gantt makes it legible. ## Version history: v0.3 (superseded) Three iterations produced in a single Cowork session (2026-05-28). Five files now live in Dishant’s local Cowork outputs folder: - `L2_conceptual_model_v0.1.md` - `L2_conceptual_model_v0.2.md` - `L2_conceptual_model_v0.3.md` - `L2_conceptual_model_v0.4.md` — OM repositioning, OCPA name, Gantt - `L2_conceptual_model_v0.5.md` — *full v0.5 rewrite pending Dishant's "lock v0.5" signal* - `L2_v0.5_delta.md` — **CURRENT — delta capturing 7-element structural additions** - `L2_v0.4_pending_changes.md` — v0.4 pending changes log - `L2_handoff_prompt.md` - `mother_ship_handoff.md` **These files should be uploaded to Google Drive for permanent storage.** Not yet in Project Files or Drive as of 2026-05-28. ## Framework architecture (v0.5 — CANONICAL) *Seven elements. Declared structural lock 2026-05-28. L3 and L4 build on this.* ### The four tools (Gantt elevated in v0.4) OCPA integrates four tools as co-equal components: 1. **CPM** — network mapping, dependency analysis, critical path identification 2. **PERT** — probabilistic estimation, sensitivity analysis, range of outcomes 3. **TOC** — constraint identification and sequenced intervention planning 4. **Gantt** — continuous visualisation layer across all three analytical steps The Gantt is not a Step 1 output. It is maintained and updated continuously: initial state (CPM output) → PERT-adjusted state → post-TOC future state. The business owner sees the Gantt at every stage. It is the legible surface of the framework. ### Element 1 — Multi-resource critical-path synthesis Every resource class gets its own critical path analysis. The output is a single synthesised critical path that respects all resource constraints simultaneously, with optimum allocation across all of them. This is the key extension beyond standard CPM: OCPA treats multi-resource constraint as the normal case, not the edge case. The prior framing ("one path through the scarcest resource, with multiple co-active paths as an edge case") is dropped. ### Element 2 — Lead/lag definition and minimisation (explicit step) Lead and lag are not annotated — they are explicitly identified, quantified, and their minimisation is a formal analytical step. The question is not just "what are the leads and lags?" but "which are reducible, by how much, and at what cost?" This element is the structural foundation for B4 (NGA Lag Audit) as a standalone offering. ### Element 3 — TOC constraint sequence (not single identification) TOC produces an ordered sequence, not a single constraint identification: - What is the currently binding constraint? - Once relieved, which constraint becomes binding next? - And the one after that? Output: a sequenced intervention plan. The owner acts on the current bottleneck while already knowing what to prepare for. ### Element 4 — PERT sensitivity on the critical path PERT analysis identifies the sensitivity of the critical path itself — not just probabilistic durations: - Under which probability scenarios does the critical path change routes? - Under which scenarios does the optimal resource allocation change? - Which activities are robust across scenarios? Which are fragile? This separates activities that look equivalent on the base-case Gantt but carry very different risk profiles. ### Element 5 — Capacity analysis Given current resource limits across all six classes — what is the realistic achievable output? This is beyond bottleneck identification. It gives the business owner the ceiling: the maximum throughput achievable without additional resource investment. It also identifies which resource class yields the largest capacity improvement per unit of investment. ### Element 6 — Six-class resource taxonomy (from v0.3, carried forward) 1. Labour (elastic — can be added, shifted, substituted) 2. Key Personnel (inelastic — specific individual, not substitutable) 3. Materials 4. Equipment / Machines 5. Space / Facilities 6. Capital *Labour and Key Personnel have different elasticities and different interventions. This split is a v0.3 MSME-specific extension, carried into v0.5 unchanged.* ### Element 7 — Decision Map (the final deliverable) The output is not a diagnostic. Not a Gantt chart. Not a report. The output is an **ordered list of decisions for the owner**. Each decision specifies: <table header-row="true"> <tr> <td>Field</td> <td>Content</td> </tr> <tr> <td>What to do</td> <td>The specific action</td> </tr> <tr> <td>Which constraint it addresses</td> <td>The binding constraint this relieves</td> </tr> <tr> <td>Expected impact</td> <td>Days saved / throughput gained / capital freed</td> </tr> <tr> <td>Dependencies</td> <td>What must happen first</td> </tr> <tr> <td>Cost</td> <td>Investment, resource reallocation, or process change required</td> </tr> </table> The Decision Map is what the client pays for. CPM, PERT, TOC, Gantt — all methodology that produces it. ### Design principle (from v0.3, carried forward) Complex-internal / simple-external. The framework is architecturally sophisticated internally but presents a simple, actionable surface externally. The business owner sees the Decision Map and the Gantt — not the network diagram. ## Strategic posture (v0.5) Dishant's words (2026-05-28): *"I am not concerned about naming or if this already exists, makes it even easier for me. 99.99% of entrepreneurs won't know it. And they are my market."* **Prior-art and originality: not the point.** CPM, PERT, TOC, and Gantt all have established foundations. OCPA's contribution is their integration in a specific sequence for MSME operators producing a Decision Map. Whether that combination has an existing name is irrelevant to the business owner who needs it. **Defensive positioning: dropped.** v0.4 §7 contained explicit "this is not CCM" argumentation — written for an audience of PM professionals and academics who know what CCM is. The target market doesn't know and doesn't care. Defensive positioning signals insecurity. It is gone from v0.5. **What confidence comes from:** The Decision Map. The named binding constraint. The sequenced intervention plan. The quantified expected impact. These are what no standard CA engagement produces. Confidence comes from utility, not intellectual lineage. **Prior art acknowledgement (kept, made brief):** One honest paragraph, factual. These tools have established foundations in project and operations management literature. OCPA's contribution is their integration in a sequence designed for the MSME operator, producing a Decision Map that translates analysis into action. ## Open questions — status relative to v0.5 *The v0.3 §10 open questions were written before v0.4 and v0.5. Some may be partially or fully resolved by the v0.5 architectural additions. Some may be newly opened by them.* **Triage is needed before treating these as the current working list.** Dishant's recommendation (2026-05-28): tomorrow's review starts with triage — what from the session's five iterations survives a second look, and what was exploratory thinking that doesn't. The original ten open questions are in the Cowork outputs folder (L2_conceptual_model_[v0.3.md](http://v0.3.md) §10). The v0.5 delta captures any new questions introduced in v0.4 and v0.5. **Questions known to need re-examination against v0.5:** - Lag Audit workstream sequencing — now clarified that lead/lag minimisation is Element 2, and B4 is the standalone entry product. May be resolved. - Machine sub-classification — still open (what constitutes 'machine' vs 'equipment' for MSME context) - The Decision Map format — what does the client actually receive? Level of detail, format, delivery mode — not addressed in the seven elements. - Ten questions from v0.3 — need triage: which survive v0.5's additions? Which are now moot? Which are new? ## Mid-session additions from Dishant (all embedded in v0.3) 1. The tool must account for real MSME complexity 2. Machine and labour are first-class resources distinct from key personnel 3. Parallel activities change float calculations 4. Lag reduction is itself a major offering ## Connections - **L1** — L2 is the substance that L1 explains in video form - **L3** — evidence layer must validate the framework’s claims before public release - **B4** — NGA Lag Audit is a productised sub-offering emerging from §5 of v0.3 - **C5** — framework will eventually be applied in client engagements (HSIPL, future Virtual CFO clients) - **A4** — if Dishant publishes a book on MSME strategy, this framework is its intellectual core ## Next action Open the L2 chat using the handoff prompt. **v0.5 structural lock is the starting point** — not v0.3. First task in the L2 chat: **triage**. The session produced five iterations of the framework in one sitting. Before working on refinement or evidence design, review the seven elements and the v0.4/v0.5 delta against a second read. Confirm what's genuinely locked vs. what was exploratory thinking that doesn't survive fresh eyes. Second task: re-examine the v0.3 §10 open questions against v0.5. Which are resolved? Which changed shape? Which are newly opened? ## L2 chat handoff prompt See the L2 chat in the My Office Tool project. Handoff prompt is in `L2_handoff_prompt.md` in Dishant’s Cowork outputs folder, or use the Mother Ship’s version (generated 2026-05-28).