The bottleneck in most product teams is not individual skills, it often is the absence of shared foundations: a common language for the core PM concepts, a common method for moving from problem to solution, and shared standards for what good work looks like.
When those foundations are missing, product leaders compensate. They become the implicit standard for every PM judgment in the organisation. The work gets done, but it flows through the leader in ways that limit what the team can do independently.
PM craft debt is what this accumulation costs, and training one PM at a time does not pay it down.
What is PM craft debt, and which type does your team carry?
PM Craft Debt is the accumulated cost of a product team that lacks shared foundations. It compounds quietly and is paid primarily by the product leader. There are three types, and most product organisations carry all of them at the same time.
Language debt
Language debt accumulates when the team does not share definitions for the core concepts of the work. What is a problem statement? What makes a roadmap decision final? When do you have enough evidence to move from problem to solution? When two PMs use "outcome" to mean different things, every conversation involving that word has a hidden step: first establish what we mean, then have the actual conversation. That overhead sits at the beginning of every meaningful discussion, and it is the product leader who resolves it each time.
Jean-Baptiste Mairy, Head of Product at N-Side, describes what changed after his team trained together: "It replaced the work of having to define what we mean by which terms, because it was already defined. This made exchanges and understanding more fluid, even between product team members."
Method debt
Method debt accumulates when each PM has developed a personal approach to the PM lifecycle through their own job history. These individual methods are often functional in isolation, but they do not compose. When the team needs to review discovery work, there is no shared standard to evaluate against. When a PM moves to a new initiative, the handoff creates friction because the incoming person cannot read the rationale behind decisions made through a different method. The product leader ends up functioning as the quality filter for work that should be self-sufficient.
Charlotte De Trez, Head of Products at Aware, captures what changes when this debt is resolved: "I could depersonalise certain processes by saying 'this isn't your process, it's just how it's done.'" When the team has a shared method, the leader no longer carries the personal authority of every standard. Disagreements about approach become conversations about whether the method is being applied correctly, not arguments about whose preferred style is better.
Confidence debt
Confidence debt is the subtlest of the three and is often misread as a seniority gap. It accumulates when PMs are not sure whether their approach is professionally grounded or just their best personal guess. The consequence is that decisions which should be made at PM level come upward, not because the PM cannot think through the problem, but because they do not feel they have the standing to make the call without validation. This shows up in one to ones full of "what do you think I should do?", in PMs who hesitate to hold the line with stakeholders without backing, in a team that waits for permission rather than acting on what they already know.
Sam Boribon, PM at Nodalview, describes the shift: "My team really saw a before and after. They could see I was proposing way more things, I dared to say no more often to respect the theoretical concepts." The theory gave him standing, the sense that his approach was professionally grounded, not just his best guess.
Why do Scrum and SAFe certifications not fix this?
Scrum and SAFe certifications are the most common first response when a product leader decides to invest in team development. They create shared process language: everyone knows what a sprint review is, what the product owner role entails, what a sprint backlog is for. That is useful when the goal is delivery framework alignment.
The problem is that shared process does not generate shared judgment. Two PMs who have both passed a Scrum certification can still hold entirely different mental models of how to decide what goes into the backlog, whether they are solving the right problem, or how to run discovery under delivery pressure. Certifications address a narrow slice of Language Debt — the vocabulary of ceremonies and roles. They do not touch Method Debt or Confidence Debt. The team runs Agile correctly and still escalates the same judgment calls. The underlying PM Craft Debt has not been paid.
Scrum certifications are the right tool for a specific job: ensuring that people who need to operate within an Agile framework can do so consistently. They are not designed to develop product judgment: how to identify the right problems, test assumptions before building, or make confident prioritisation decisions under uncertainty. A team that completes a certification and still carries Method Debt and Confidence Debt will continue to need the same arbitration, the same definitional negotiations, the same upward escalation. The nature of the debt has not changed.
What changes when a team trains together?
When a team trains together, the primary output is not individual skill uplift, it is a shared professional foundation that the team carries back into the work. This distinction is what matters most for a product leader evaluating the investment.
When a group of PMs who work together are in a learning environment with real cases, exercises, and discussions, they discover where they disagree in real time. They find that what looked like a personal quirk in how they approach a problem is actually a theoretical position and that their colleague holds a different one. The training gives them a framework to resolve it. They leave with a shared reference point: "the way we agreed to run discovery," "the problem framing approach from the training," "the stakeholder management framework we both know."
Jeroen describes the experience: "The training created a refreshing and collaborative atmosphere for our product team. It gave us the rare opportunity to step back, spend quality time together, and align on shared definitions and ways of working." The alignment on shared definitions is not a side effect, it is the output, and it only happens when the team is in the room together.
What should you look for in product management training?
Training that addresses PM Craft Debt has a few specific characteristics worth checking before committing.
It should cover the full PM lifecycle. Not just discovery, not just delivery, but how product work connects to company strategy, how problems get framed before solutions are explored, how delivery decisions are made, how measurement works, and how stakeholder management functions as a PM discipline rather than a soft skill. Partial coverage leaves partial debt. A team that aligns on discovery but still has no shared approach to roadmap decisions or stakeholder management will find that the Language and Method Debt simply relocates rather than disappears.
It should be grounded in the reality your team actually operates in. A lot of PM training is calibrated for well-resourced teams with dedicated discovery quarters, autonomous authority, and greenfield product work. European product organisations, particularly scale-ups with matrix structures, shared engineering capacity, and multi-stakeholder roadmap processes, face different constraints. The training should acknowledge them rather than assume them away.
It should create structured opportunities for the team to work through problems together during the session, not just absorb content in parallel. The shared standard is built in the moments where two team members discover they have been approaching the same problem differently and have to resolve it within a common framework. That requires a cohort format in small groups, not a lecture hall or an asynchronous online module.
One concern that sometimes comes up is whether it makes sense to send a team with different experience levels to the same training. Lucas Poot, a past participant, addresses it directly: "Whether you have 15 years of experience or none, there is something here to learn and apply for everyone." The more experienced PM brings context. The less experienced PM asks questions their senior colleagues stopped asking. The shared foundation tends to be stronger for the difference in perspective, not weaker.
dualoop's product management training runs in Brussels several times a year. It covers the full PM lifecycle, from strategy to discovery, delivery, measurement, and stakeholder management, in a cohort format designed for teams building shared foundations rather than individual credentials. Mathieu Thys leads the training with both theoretical rigour and direct applied experience.
FAQ
What is PM Craft Debt?
PM Craft Debt is the accumulated cost a product team pays for lacking shared foundations, a common language, a common method, and shared professional standards. It compounds over time and is typically absorbed by the product leader in the form of definitional arbitration, quality filtering, and permission-giving for decisions the team could make without them.
Why is training a team together more effective than individual courses?
When a team trains together, the primary output is a shared reference point they carry back into the work. Individual training gives one person new vocabulary that nobody else speaks, which tends to dissipate within a few months. Collective training gives the whole team a common foundation, one that changes how meetings run, how discovery reviews work, and how PMs hold the line with stakeholders.
How is this different from a Scrum or SAFe certification?
Certifications create alignment on delivery process, sprint ceremonies, backlog management, role definitions. They do not build product judgment: how to frame problems before moving to solutions, how to run discovery under pressure, how to make confident prioritisation decisions. PM Craft Debt is a judgment gap, not a process gap, and certification addresses the wrong layer.
Does this training work for teams with mixed experience levels?
Yes. The value of collective training is not only in the content each individual absorbs, it is in the shared foundation the group builds together. More experienced PMs bring context. Less experienced PMs ask questions their senior colleagues stopped asking. The resulting shared foundation is typically richer for the diversity in experience.
What needs to change after the training for the investment to hold?
The product leader needs to update how they operate: shifting product reviews to evaluate against the shared standards the team now holds, protecting time for the discovery and problem framing approaches introduced in the training, and moving one to ones from validation-giving to direction-setting. Without these structural changes, the investment converts into goodwill rather than changed behaviour.
