Sense
Collect signals from plans, meetings, risks, dependencies, decisions, metrics, and external requirements.
Working framework · v0.1
Technical Program Management, augmented by AI.
A practical methodology for using AI as part of the operating system of a complex technical program—improving synthesis, decision support, execution visibility, and learning while keeping accountability with the TPM.
This is an early public working draft. The goal is to develop and test the methodology before turning it into a broader body of guidance.
The idea
Do not automate the TPM. Augment the program.
AI-Augmented TPM is not an attempt to replace judgment, leadership, stakeholder management, or technical accountability. It treats AI as a program-level capability: a structured layer that helps the TPM process more information, expose contradictions, maintain context, and make better decisions faster.
The scope is intentionally bounded. A TPM cannot redesign the operating model of every organization around the program. External processes, requirements, governance, and constraints are accepted as inputs. The methodology focuses on what can be optimized inside the technical program itself.
Operating model
A program-level intelligence loop
The framework organizes AI use around a continuous cycle rather than isolated prompting.
Structure
Turn fragmented inputs into traceable program context: constraints, commitments, assumptions, owners, and interfaces.
Reason
Use AI to surface gaps, conflicts, scenarios, hidden dependencies, and questions that require human judgment.
Act
Convert decisions into aligned execution: actions, communications, escalation paths, and measurable outcomes.
Learn
Feed outcomes back into the program model so future analysis reflects what actually happened, not only what was planned.
Design principles
What makes the approach different
Human accountability remains explicit
AI can recommend, summarize, challenge, and simulate. The TPM remains responsible for decisions, commitments, and stakeholder alignment.
External reality is a constraint, not a prerequisite
The method does not depend on the rest of the enterprise adopting the same tools or processes. The program can ingest external requirements and operate coherently within them.
Context beats isolated prompts
The value comes from maintaining a structured program model over time, not from asking a chatbot disconnected questions.
Evidence before automation
Every high-impact recommendation should remain traceable to source information, assumptions, and human validation.
Methodology before tool lock-in
The operating model should survive changes in vendors, copilots, foundation models, and enterprise tooling.
Start with one technical program
Prove measurable value locally before trying to standardize the approach across a PMO or enterprise.
What this should improve
From program exhaust to program intelligence.
Less reconstructionSpend less time rebuilding context from meetings, documents, and messages.
Earlier contradiction detectionExpose incompatible assumptions, dates, ownership, and interface expectations before they become execution failures.
Higher decision qualityBring evidence, alternatives, dependencies, and historical context into the decision process.
Better organizational memoryPreserve why a decision was made, not only the decision itself.
Research & development
This framework is being developed in public.
The next iterations will turn the concept into a usable methodology with artifacts, workflows, measurable outcomes, and implementation patterns for technical program managers.
NowDefine the operating model
Clarify scope, principles, terminology, and differentiation from generic AI project-management tooling.
NextBuild the practitioner toolkit
Program memory, decision records, risk/dependency reasoning, meeting synthesis, status generation, and review workflows.
ThenValidate through practice
Test where AI augmentation materially changes execution quality, decision latency, and TPM cognitive load.
AI-Augmented TPM
A working methodology for the next generation of technical program leadership.
More research, practical patterns, and framework updates will be published here.