Methodology
A defined project-delivery model that connected activities, inputs, outputs, responsibilities, controls, and closeout into one repeatable execution structure.
Historical project-delivery methodology and PMIS
The manual-era foundation for a continuing body of work about execution, evidence, context, and accountable decisions.
Before AI could maintain project context or prepare executive evidence, Michael Kaplan built a structured methodology for defining, planning, mobilizing, monitoring, controlling, and closing consequential work.
What SoftPMO was
SoftPMO was commercialized through MAK CON as a project-execution methodology and SharePoint-based PMIS. Its value was not any single template. It was the relationship between defined delivery logic, reusable work products, and the environment used to operate them.
A defined project-delivery model that connected activities, inputs, outputs, responsibilities, controls, and closeout into one repeatable execution structure.
A 170-page implementation guide supported by 46 commercial templates for planning, agreements, financial control, risk, quality, communications, procurement, delivery, and governance.
SharePoint, Microsoft Project and Project Server, Office 365, dashboards, project controls, and collaboration sites translated the methodology into a working enterprise environment.
The execution lifecycle
The Project Execution Guide organized delivery into six connected stages. Each stage produced or governed records needed by the next, creating continuity from initial definition through acceptance and closeout.
Establish the project concept, intended outcome, stakeholders, constraints, and initial decision basis.
Develop the integrated plans, work structures, agreements, controls, budgets, schedules, and responsibilities.
Mobilize people, suppliers, infrastructure, operating procedures, and the project-management system.
Collect evidence about progress, performance, deliverables, commitments, risks, issues, and changing conditions.
Interpret variance, manage change, resolve exceptions, maintain accountability, and protect the approved basis.
Complete acceptance, transition outcomes, settle commitments, preserve the record, and capture what the organization learned.
Leadership evidence
SoftPMO demonstrates Michael’s experience designing delivery systems, translating them into technology, and making the operating logic usable by project organizations.
See the enterprise PMO leadership path →The ability to turn broad delivery practice into an integrated operating model rather than a disconnected set of templates.
Experience translating methodology into SharePoint, Project Server, Teamsites, dashboards, and working project controls.
Practical attention to implementation, customization, operating fit, and the records teams need to execute consistently.
A sustained record of codifying how work moves from definition through planning, execution, control, acceptance, and closeout.
One continuing body of work
Each stage changes the governing question while preserving the concern underneath it: what evidence should people trust before authorizing what happens next?
Execution methodology, governed records, reusable work products, and a working PMIS.
Open record →AI-assisted context and evidence without transferring human authority.
Open record →The RRI’25 Executive War Room, paid Black Box Edition, and later teaching simulator.
Open record →What leadership must see before the next commitment of capital.
Open record →How the governed record carries evidence into accountable decisions.
Open record →Applying schedule risk analysis, contingency and traceable evidence to a capital-delivery decision.
Open record →Current professional relevance
SoftPMO supports Michael's candidacy for senior program, portfolio, EPMO, PMO, and enterprise-transformation leadership. It demonstrates how he designs and implements delivery capability.