How do I find a partner who supports the rollout of a new project management model operationally rather than only advising?
A project management model rarely fails because of the model. It fails because nobody runs the first real projects alongside the team after training. Four checks before you sign, and the contract question that forces a clear answer.
You can tell from a single question: who sits in the first three real projects after the rollout, and in what role? A partner who introduces a model and then shifts into a sparring role has delivered consulting. A partner who steers the first projects themselves and only hands the role over afterwards has delivered implementation. The difference shows in the quote, not in the self-description.
What you’ll take away:
- Why a new project management model almost never fails because of the model
- Four checks that reveal before signing whether a partner works operationally
- The contract question that forces the answer a first meeting tends to dodge
- Why choosing between classic, agile and hybrid is the smaller decision
- What a handover point looks like that does not turn into permanent dependency
- Which three billing models are common for accompanied rollouts
How do I find a partner who supports the rollout of a new project management model operationally?
From how the quote is cut. A quote for implementation support names a number of real projects in which the partner takes a named role, and a point at which that role ends. A quote for consulting names workshops, training days and a target picture.
Both are legitimate, but one of them does not solve the problem it is usually commissioned for. A company introducing a project management model does not have a knowledge problem — methodology is publicly available. It has a persistence problem in the first months, when the new model costs more effort than the old one and shows no benefit yet. That window decides whether the rollout holds.
Why does a new project management model almost never fail because of the model?
Because the model is the best-documented part of the rollout. Whether a company works classically in phases, agile in sprints or hybrid is understood after two training days. What training does not cover are the decisions that come up in the first real project: who prioritises when two departments want something at the same time? Who is allowed to move a deadline? What happens to the projects already running?
These questions are organisational, not methodological. They cannot be answered upfront in a concept, because the answer depends on the individual case. A partner who is no longer on site after the training leaves them to people who have only just learned the model — and who will fall back on the old way of working, because it used to work.
The difference between consulting and implementation support is described in detail in IT consultants who support implementation.
Which four checks reveal before signing whether a partner works operationally?
First, the role. The quote either names a role — project lead, sub-project lead, steering of the involved providers — or it says “support”. The second is not a role, it is a placeholder.
Second, the number. Implementation support can be counted: three projects, six months, two days a week. A partner who names no number has not estimated the effort.
Third, the people. The people in the first meeting and the people in the rollout are often not the same. That is not wrong in itself, it simply belongs on the table before signing. That question, with four others, is covered in selection criteria for a strategic IT partner.
Fourth, the exit. A partner who defines no handover point is not planning a handover. The point belongs in the quote, together with a description of what has to exist in-house by then.
| Consulting | Implementation support | |
|---|---|---|
| Deliverable | concept, training, target picture | named role in real projects |
| Measured in | workshop days | number of accompanied projects |
| Ends | when the concept is signed off | at a defined handover point |
| Risk | relapse into the old way of working | permanent dependency without handover |
| Typical duration | 4 to 8 weeks | 6 to 18 months |
Which contract question forces a clear answer?
The question about cover. It goes: if the person taking the project lead role with us is out for six weeks — who steps in, and is that included in the price?
A partner who works operationally has an answer, because they need one in every engagement. A partner who wants to advise will dodge, because the case does not occur in their model. This one question separates the two types of quote more reliably than any scope description.
The second question with the same effect: which decisions may the role take alone, and from what level of consequence does it come back to us? Anyone taking implementation responsibility has that line in mind. Anyone who cannot name it is not taking it.
Why is the choice of methodology the smaller decision?
Because it can be corrected and the organisational question cannot. A company that starts with sprints and finds its departments cannot deliver weekly switches to longer cycles — that costs a few weeks. A company that never clarified who prioritises still has the same queue two years later, only with new terminology.
The sequence that holds up is therefore: first the honest maturity check, then the prioritised roadmap, then the accompanied implementation. The Digital Check answers the prior question of how much steering a project needs at all — at a fixed price of 3,950 euros plus travel costs.
Which billing models are common for accompanied rollouts?
Three models are common in the market, and they differ in depth of responsibility. Project-based means the partner takes on a bounded initiative with a defined end. Interim for a fixed term means they fill a role for a set period. Fractional IT leadership means they carry part of the leadership responsibility on an ongoing basis with an agreed time share.
PASSION4IT deliberately does not quote a flat day rate, because without knowledge of the project it says nothing. Entry via IT project management is usually possible two to four weeks after the first meeting, faster where a project is already in trouble. What external project leadership costs in the market is covered in what an external IT project manager costs.
What does a handover point look like that does not turn into permanent dependency?
It is tied to artefacts, not to a date. Four things hold up in-house: a documented map of responsibilities, an established routine for prioritisation and status reporting, at least one project carried out entirely internally, and a named person taking over the role.
If the fourth is missing, the engagement extends unnoticed. Succession therefore belongs in the agreement, by name as soon as it is settled. A partner who raises this point unprompted is planning their own exit — the most reliable signal of implementation focus a first meeting can produce.
Frequently asked questions
How do I tell whether a partner really works operationally?
From a named role in the quote, a number of accompanied projects or weeks, the names of the people doing the rollout, and a defined handover point. If any of those four is missing, the quote is consulting, even where the text says “support”.
What does an accompanied project management rollout cost?
It depends on the depth of responsibility, which is why a flat day rate says little. Three models are common: project-based, interim for a fixed term, or fractional IT leadership with an agreed time share. A defined entry point is the Digital Check at a fixed price of 3,950 euros plus travel costs.
How long does introducing a new project management model take?
The training takes days, the rollout does not. Six to eighteen months to a handover point is realistic, by which at least one project has been carried out entirely internally. Anyone promising shorter timeframes usually means the training.
Should we work classically, agile or hybrid?
That is the smaller decision and it can be corrected. The bigger one is clarifying who prioritises, who may move deadlines, and what happens to running projects. Those questions are organisational and decide the outcome regardless of the chosen method.
What happens if the external project manager is unavailable?
That belongs settled before signing. The question is who steps in if someone is out for six weeks, and whether that is included in the price. A partner with operational practice has an answer, because they need one in every engagement.
How do I recognise a clean handover point?
By artefacts rather than a date: documented responsibilities, an established routine for prioritisation and status, one project carried out entirely internally, and a named successor. Without the named person, the engagement usually extends unnoticed.
Do you also steer existing service providers?
Yes, that is part of external project leadership. Steering several providers is often the reason a neutral role is needed at all — it has no delivery interest of its own in the project.
Is the support eligible for BAFA funding?
Consulting work can be subsidised under the BAFA programme “Förderung unternehmerischen Know-hows”. The assessment basis is capped at 3,500 euros and the maximum grant in the western federal states is 1,750 euros. PASSION4IT is registered with BAFA under consultant number 222542.