
Project Management
This framework was generated using the Framework Builder methodology. It demonstrates the five-layer DNA architecture applied to project management across mixed project sizes.
Built with the Framework Builder methodology
Download markdownThis framework was generated using the Framework Builder methodology. It demonstrates the five-layer DNA architecture applied to project management across mixed project sizes.
Layer 1: Principles Foundation
Principle 1: The method serves the project. Do not force two-week cycles onto a three-day task, and do not run a six-month build without upfront discovery. Choose the method per project.
Principle 2: The client sees everything that matters. Your best relationships come from projects where the client always knows what is happening and why.
Principle 3: Every project ends with a retrospective, whatever its size. A one-hour review on a small job often saves weeks on the next large one.
Principle 4: Match planning depth to what you know. Plan in detail where the path is clear. Plan lightly and build in discovery where it is not. Importance does not set planning depth.
Principle 5: Late changes without new information are creep. Early changes are learning. Handle them differently.
Layer 2: Systematic Approach
Step 1: Run a 30-minute intake assessment. Score size, uncertainty, team distribution and client involvement.
Step 2: Route to a category. Quick-turn work (under two weeks, known scope) uses a simple task board with daily updates. Standard work (two weeks to two months, mostly known scope) uses two-week cycles with a client demo at the end of each. Complex work (over two months or high uncertainty) starts with a dedicated discovery phase and weekly working sessions with the client.
Step 3: Record the category and the reason. If the project turns out to be miscategorized, you can see why.
Step 4: Reconfirm scope at the midpoint. Late-stage changes are the largest schedule risk on standard projects, so check scope explicitly halfway.
Step 5: Close with a retrospective and one committed change. Implement at least one improvement before the next retro.
Layer 3: Force Multipliers
Multiplier 1: Blockers-first standups. Fifteen minutes, grouped by project manager so one session covers all of that manager's projects. Blockers come before status.
Multiplier 2: A decision log per project. Keep it in a shared channel so the client can see the reasoning behind every major call.
Multiplier 3: Uncertainty multipliers on estimates. Apply a higher factor to tasks with new technology and a smaller one to tasks that wait on the client. Adjust the factors after each pilot.
Multiplier 4: Leading indicators. How long blockers stay open, how fast open decisions close and how many items wait on an outside party.
Multiplier 5: Rename the work, not the team. Use plain category names, quick-turn, standard and complex, so clients and new staff understand the routing without learning a methodology.
Layer 4: Success Metrics
Positive indicators:
- On-time delivery tracked by category, not in one blended number
- Blockers close within a day or two
- Scope changes are logged, with early ones marked as discovery
- Each retro produces a change that is implemented
- Clients ask fewer "where are we" questions
Failure signals:
- Complex projects keep running late (the discovery phase is too thin, not the sprints too loose)
- "Standard" projects with unclear requirements run late
- Health is reported only as milestones passed
- Retros list the same issues each time
- The team describes itself by a method name
Layer 5: Implementation Guidance
Audit your last dozen projects first. Check which category each would have been in, and whether lateness lines up with uncertainty. It validates the categories and tightens the intake criteria.
Pilot on the next three projects. Run the full intake, record the category and rationale, then adjust the multipliers and add a kickoff workshop for complex work.
Common mistake: rejecting all scope changes. Rigid projects fail quietly. Separate learning from creep.
Edge case: a project grows in scope mid-flight. Re-run intake and move it to the right category, then tell the client what changes in cadence.
Edge case: a one-person project. Keep the intake, the decision log and the retrospective. Drop everything else.
Edge case: a client who disappears for weeks. Log the waiting items, apply the client-dependency multiplier and agree on a decision deadline.
Common mistake: adopting a method as an identity. "We are an Agile shop" turns a tool into a culture. Both rigid Agile and rigid Waterfall stop the team choosing the right approach for the project. Make method selection a conscious choice at intake.
Common mistake: inverted precision. Teams often plan uncertain work in great detail and known work barely at all. Plan in detail where the path is clear, and plan lightly with discovery loops where it is not.
Common mistake: milestones as the only health signal. A milestone slip is a problem weeks old. Watch blockers, open decisions and outside dependencies while you can still act.
Common mistake: retros that change nothing. After two or three of them the team stops being honest. Commit to implementing at least one change before the next one.
Built with the Framework Builder methodology. Get the skill →