AI can assemble a status update, phrase it clearly, flag risks, and propose corrective actions. That's genuinely useful. But the success of a project depends on the cooperation. It cannot be automated. It requires a jointly agreed procedure — and that's why the PM² methodology is needed, even as the tools around it evolve quickly.
Parts Working Together
PM² is built from interlocking parts: the pillars (the Governance Model, the Lifecycle, the Processes, the Artefacts & Templates), and the 'glue' (the Mindsets). They are not separate tools that you can arbitrarily use — but only work when used together. AI can make each part more efficient on its own, but it cannot replace what holds them together: people's shared agreement on how the project is actually run.
| PM² component | Where AI can help? | What AI can't do for you? |
|---|---|---|
| Governance Model | Compiling meeting minutes and decision logs | Decide who has the authority to approve a change or close a phase |
| Lifecycle | Visualising the schedule and milestones | Agree what "done" means at each phase gate |
| Processes | Reminding and scheduling recurring activities | Ensure every stakeholder follows the same decision procedure |
| Artefacts & Templates | Populating a report template | Guarantee the document describes the essential issues and meets audit needs |
| Mindsets | – | Build trust, commitment and shared accountability |
The Value of a Methodology Shows Up Before Reporting
An AI tool does not create a common language or ensure project predictability. It only happens when the project and steering groups use the same method. Everyone knows when each decision will be made, who will make it, and where it will be recorded. This is not bureaucracy, but a structure that makes project implementation and reporting reliable.
A methodology doesn't compete with AI but defines roles and responsibilities - between humans and AI.
A Perspective from Squared Methodologies
A recent article in the Squared Methodologies series discusses the barriers to the application of methodology and how the methodology itself affects its adoption. One key point is this: when the parts of the method are compatible and the terminology is consistent at different levels of the structure, the organization does not have to start from zero with every new area.
The same applies to PM². When in EU projects (such as ERDF, ESF+ and JTF) the governance model, processes and templates (artifacts) are parts of the same methodology, also funding specialists at the elinvoimakeskukset also recognise the logic from one project to the next. Controlled implementation, traceability and predictability are things that the funder requires – and they cannot be outsourced to AI.
Source
This article draws on perspectives from the Squared Methodologies article "The Squared Advantage in Methodology Adoption".
Join Us at the PM² Finland Meetup
Welcome to hear about the benefits of the PM² methodology and how Finland's own PM² community can support you in your own projects. The PM² Finland's inaugural meetup takes place on 25 August 2026.
Français (France)
Finnish (FI)
English (United Kingdom) 
