The GFunnel Methodology
Project Management Algorithm
The steps
- Direct. State the project’s outcome in one sentence. If you cannot, the project is not yet defined.
- Guide. Structure the project into phases. Each phase has a clear deliverable, owner, and falsifiability condition.
- Gather. Identify all dependencies, constraints, stakeholders, and risks before the first build action.
- Organize. Build the dependency graph. Sequence work by what must precede what, not by what is most exciting.
- Apply Fibonacci sequencing. The first cycle establishes foundation. The next cycle is informed by the first. The third is informed by both. Do not parallelize work whose dependencies have not been resolved.
- Identify the critical path. The longest chain of dependent tasks determines minimum project duration. Optimize the critical path before the parallel paths.
- Apply Layer V BEAS at the project level. Score Correctness, Complexity, Patience, Resilience for the project itself.
- Run weekly cycles per Shepherd’s Way. Direct (this week’s focus), Guide, Gather progress, Organize remaining work, Create deliverables, Database (write it down), Repetition.
- Document scope changes explicitly. Scope creep is uncalibrated dynamic middle drift. Re-establish the middle deliberately.
- Close the project. Per Repetition: capture lessons learned for the next project’s baseline.
Articles on this
No articles on this one yet.
From the GFunnel Methodology v5.1 by Cameron Garlick, licensed CC BY 4.0. Steps are reproduced word for word.