Historical project-delivery methodology and PMIS

SoftPMO

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

Methodology, implementation guidance, and a working information system.

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.

01

Methodology

A defined project-delivery model that connected activities, inputs, outputs, responsibilities, controls, and closeout into one repeatable execution structure.

02

Project Execution Guide and templates

A 170-page implementation guide supported by 46 commercial templates for planning, agreements, financial control, risk, quality, communications, procurement, delivery, and governance.

03

Teamsites and PMIS

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 logic came before the software.

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.

01

Define

Establish the project concept, intended outcome, stakeholders, constraints, and initial decision basis.

02

Plan

Develop the integrated plans, work structures, agreements, controls, budgets, schedules, and responsibilities.

03

Start

Mobilize people, suppliers, infrastructure, operating procedures, and the project-management system.

04

Monitor

Collect evidence about progress, performance, deliverables, commitments, risks, issues, and changing conditions.

05

Control

Interpret variance, manage change, resolve exceptions, maintain accountability, and protect the approved basis.

06

Close

Complete acceptance, transition outcomes, settle commitments, preserve the record, and capture what the organization learned.

Leadership evidence

What building SoftPMO demonstrates.

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 →

Methodology architecture

The ability to turn broad delivery practice into an integrated operating model rather than a disconnected set of templates.

PMIS implementation

Experience translating methodology into SharePoint, Project Server, Teamsites, dashboards, and working project controls.

Enterprise adoption

Practical attention to implementation, customization, operating fit, and the records teams need to execute consistently.

Long-form systems thinking

A sustained record of codifying how work moves from definition through planning, execution, control, acceptance, and closeout.

One continuing body of work

The research lineage

Each stage changes the governing question while preserving the concern underneath it: what evidence should people trust before authorizing what happens next?

  1. 01Manual-era foundation

    SoftPMO

    Execution methodology, governed records, reusable work products, and a working PMIS.

    Open record →
  2. 02Published December 2025

    The Sentient PMO

    AI-assisted context and evidence without transferring human authority.

    Open record →
  3. 03Workshop to self-paced product

    The Sentient Architect

    The RRI’25 Executive War Room, paid Black Box Edition, and later teaching simulator.

    Open record →
  4. 04Governing the Funded Belief

    Volume I

    What leadership must see before the next commitment of capital.

    Open record →
  5. 05Forensic Governance OS

    Volume II

    How the governed record carries evidence into accountable decisions.

    Open record →
  6. 06Synthetic case / In progress

    Project Mesquite

    Applying schedule risk analysis, contingency and traceable evidence to a capital-delivery decision.

    Open record →

Current professional relevance

A historical system with a current leadership signal.

SoftPMO supports Michael's candidacy for senior program, portfolio, EPMO, PMO, and enterprise-transformation leadership. It demonstrates how he designs and implements delivery capability.