When a company outsources product development, project management isn’t automatically outsourced as well. Someone must plan, prioritize, and make decisions, and that choice determines visibility, control, and results. If the company wants to manage outsourced projects using Critical Chain Project Management, the role it assumes vis-à-vis the supplier changes everything: it determines who plans, who updates the buffer, and who takes action when the project is at risk.
This article explains the three possible models, what changes when CCPM is applied to each one, and what questions a company should ask itself before making a choice.
Table of Contents
- Why doesn't outsourcing development mean delegating management?
- What are the three models of supplier relationships?
- What changes when a company wants to use CCPM for management?
- What are the most common mistakes made when defining the role?
- What questions should the company answer before making a decision?
- Frequently Asked Questions
- Which model is the best fit for your project?
Why doesn't outsourcing development mean delegating management?
Most companies that outsource their product development automatically assume the role of client: they define deliverables, set deadlines, and wait. The vendor manages the project on its own and only reports problems once they have already affected the timeline.
This model has one clear risk: visibility comes too late. In a project with many dependencies or multiple vendors, problems quietly pile up until they become apparent in the form of delays.
Key idea: Outsourcing execution is not the same as outsourcing management. The company must always decide what role it wants to play, even though it often does so without realizing it.
What are the three models of supplier relationships?
The company has three real options: to act as a client, to take over management directly, or to co-manage the project with the supplier.
Act as a customer
The company defines deliverables and conditions. The supplier is responsible for planning, managing, and delivering. Progress is tracked through milestones, KPIs, and progress reports. This model requires the least amount of internal capacity but offers the least visibility into the project’s actual status.
Take direct charge of management
The company manages overall planning, priorities, and monitoring. The supplier carries out the assigned tasks, checks its priorities, and updates the status of its work. This is the appropriate model when there are multiple suppliers or many dependencies between internal and external activities. It requires trained personnel, real-time information, and decision-making authority.
Co-manage the project
The company and the supplier share management responsibility. Together, they define a high-level plan: key milestones, major tasks, dependencies, target dates, and overall buffer. Each party manages the details of its own activities. This requires clearly defining who plans, who updates, and who prioritizes.
| Model | Visibility | Required internal capacity | Recommended when… |
|---|---|---|---|
| Client | Cancel | Minimum | The supplier has a proven track record in management |
| Direct Manager | Sign Up | Sign Up | There are several suppliers or many departments |
| Co-manager | Medium-high | Media | The project is complex, and the supplier has operational autonomy |
Key idea: The client model offers simplicity but limits the ability to respond quickly. The co-management model requires more prior agreement and reduces surprises during implementation.
What changes when a company wants to use CCPM for management?
CCPM requires coherent planning, clear priorities, regular updates, and visibility into the critical chain and buffer consumption. The role of a passive client is rarely sufficient to effectively manage outsourced projects when using Critical Chain Project Management.
Depending on the model chosen, integration with the provider takes different forms.
Option 1. The company acts as the customer and requires CCPM from the supplier
The supplier manages the project under a CCPM contract and must provide visibility into:
- Critical path of the project: the sequence of tasks that determines the total duration, taking into account the actual availability of resources.
- Fever Chart or Time Chart: a chart that shows buffer consumption in relation to project progress, allowing you to detect whether the project is at risk before it's too late.
- Weekly buffer consumption: how much of the safety margin has been used up and at what rate, to determine whether action is needed.
- Status of critical tasks: Which tasks on the critical path are currently active, pending, or blocked.
- Risks, remedial actions, and an updated estimate of the completion date: what problems exist, what is being done, and when the project is actually expected to be completed.
This model requires the supplier to be proficient in CCPM and to commit to a genuine level of transparency.
Option 2. The company manages the project using CCPM
The company manages the CCPM system: it maintains the overall plan, sets priorities, and analyzes buffer usage. The supplier checks the priorities, updates its tasks, and reports bottlenecks. This model offers the best integrated visibility and is especially useful when there are multiple suppliers or many cross-dependencies.
Option 3. The company and the supplier co-manage the process with CCPM
They agree on high-level shared planning: deliverables, macro-tasks, dependencies, the critical path, the project buffer, update frequency, and escalation rules. Each party manages the details internally. This approach can provide a good balance between control, autonomy, and collaboration.
Key point: CCPM only works if the information reflects the actual situation. Without visibility into the buffer and priorities, the system cannot detect risks in a timely manner or make recovery decisions.
What are the most common mistakes made when defining the role?
Most companies do not consciously choose this model. They assume the role of client by default, without assessing whether they have sufficient visibility to manage outsourced projects using CCPM.
- Automatically assuming the role of the client without assessing the supplier's actual capabilities or the level of visibility the project requires.
- Getting involved in management just to increase control, without having the trained staff, the time, or the authority to actually manage.
- Requiring the provider to use CCPM without verifying that they have mastered it. The system won't work if the provider doesn't understand the priorities or correctly update the status of their tasks.
- Failure to specify who manages the CCPM software. Someone must maintain the project structure, manage users, ensure data quality, and protect confidential information—especially if multiple vendors, who may be competitors, are involved.
- Failing to agree on who makes decisions when the buffer is depleted. If it is unclear who takes action when the project is at risk, monitoring becomes meaningless.
Key idea: The most common mistake isn't choosing the wrong model—it's not choosing one at all and acting out of inertia.
What questions should the company answer before making a decision?
- Will the supplier allow us to review its process? Without visibility into planning, challenges, and resource status, management or co-management using CCPM is not feasible.
- Who will administer the CCPM software? The organization responsible must maintain the project structure, manage permissions, and protect confidential information.
- Is the company prepared to manage the development? If it takes on management or co-management, it needs trained personnel, real time, and the authority to set priorities.
- Is the supplier prepared to work with CCPM? If they are not familiar with the method, they will need to be trained and supported during implementation.
- Who will make the decisions when the project is at risk? This must be determined before the buffer begins to be used up.
Key idea: The decision regarding the role does not depend on the organizational chart. It depends on each party’s actual capabilities, the level of visibility the project requires, and the speed of decision-making that the situation demands.
Frequently Asked Questions
Can a company use CCPM even if the supplier does not?
Yes. In the direct management model, the company manages the overall planning and the buffer. The supplier acts as the executor: it updates the status of its tasks and reports any bottlenecks. It is not essential for the supplier to have knowledge of CCPM if the company manages the priorities and the supplier provides accurate updates.
Is it possible to co-manage a project with CCPM when there are multiple vendors?
It is possible, but it requires careful management of permissions. The system must allow each provider to access the information it needs without seeing that of others, especially if they compete with each other in the same market.
What if the supplier isn't willing to share its schedule?
In that case, co-management and direct management with CCPM are not feasible in practice. The company will have to act as a client and limit its oversight to milestones, KPIs, and progress reports.
Is it always better to manage the project directly?
No. If the company lacks trained personnel, time, or real decision-making authority, taking over management could create more problems than the client model. The important thing is for the company to make a conscious choice, carefully assessing its own capabilities and those of the supplier.
Which model is the best fit for your project?
In some cases, the best option is to act as a client and require the supplier to manage the CCPM process transparently. In others, the company must manage the process directly. And in complex projects involving multiple suppliers, co-management may be the most effective approach.
If you're implementing CCPM in projects with external suppliers or want to structure the client-supplier relationship using the Critical Chain method, check out Teocé's CCPM course or request a consultation with the team.