Definition of the project-based organisation
The project-based organisation is a structure in which the company, or part of it, is arranged around its projects rather than around its disciplines. Each project has a team entirely dedicated to it. The project manager is its line manager: they set priorities, hold the budget and are solely answerable for the result.
Anglo-Saxon project management frameworks speak of a projectized organization, sometimes translated into French as structure projet or organisation orientée projets. In the typology of structures, it occupies the opposite end from the functional organisation, with the matrix organisation sitting between the two.
Why organise a company around its projects
For some companies, projects are not one activity among others: they are what they sell. An engineering firm, a construction company, a systems integrator or a film producer lives by delivering unique works to clients. Organising by project then means aligning the structure with the contract.
Other companies use it on an occasional basis, for a project whose stakes exceed the usual framework: building a site, replacing a core system, merging two companies. They create a project directorate with its own team, alongside a structure that remains functional or matrix for everything else.
What characterises this structure
- A single line of authority. Each team member has only one manager, the project manager, for the duration of the project.
- A full-time team. People do not split their time between several projects or with the day-to-day tasks of a department.
- Its own budget and resources. The project manager commits expenditure within the delegated framework.
- Physical or virtual co-location. The team works together, often in the same open-plan space.
- A temporary existence. The team is disbanded when the project ends, and its members are reassigned.
Advantages and limits of the project-based organisation
Its advantages lie in simplicity. There is no trade-off to negotiate between a project manager and a functional manager. Decisions are made as close to the work as possible. The team develops an identity and a commitment that partial assignments do not produce. The client or sponsor has a single point of contact.
Its limits are the flip side of this autonomy.
- Duplication. Each project wants its own experts, even when it does not keep them busy all the time. The overall cost rises.
- Erosion of expertise. Without a functional centre, specialists exchange little between projects, and practices diverge.
- The post-project period. As the end approaches, the team worries about its future. The best people leave before closure if nothing is planned.
- Silos. Each project tends to create its own tools and rules. The project becomes a silo, as the functional department was.
These shortcomings can be partly corrected: communities of practice maintain expertise between projects, a PMO maintains a common framework, and reassignments are prepared before the end of the project.
When to choose a project-based organisation
Five criteria guide the choice.
- Size and duration. The project occupies people full time over a long period.
- The stakes. Its failure would jeopardise a major contract or the company’s strategy.
- Uncertainty. The project is new, and decisions must be made quickly, without waiting for trade-offs between departments.
- Interdependence of tasks. The disciplines must work together day to day, rather than passing files to one another.
- Availability of skills. The company can second the necessary experts without disrupting its other activities.
When the last criterion is not met, because the same experts are essential to several projects, the project-based structure becomes costly, and a matrix form is preferable.
Project-based organisation and strong matrix: not to be confused
Both structures give the project manager extensive power, which explains why they are confused. The difference concerns the reporting line of the people.
| Question | Project-based organisation | Strong matrix |
|---|---|---|
| Who is the line manager of the team members? | The project manager | The functional manager |
| Who appraises their work? | The project manager | Both, according to rules to be set |
| What becomes of them at the end of the project? | They await a new assignment | They return to their department |
| Where is expertise maintained? | In the projects, or in cross-functional communities | In the functional departments |
The variants of the matrix and the comparison with the functional structure are detailed in our entry on the matrix organisation.
Nor should the project-based organisation be confused with the long-lived product teams of scaled agile frameworks, such as the trains of SAFe. A project team is disbanded on delivery. A product team is stable and stays with its product over time.
A typical case: replacing a core system
A distribution company decides to replace the system that manages its stock and orders. A first attempt, carried out by drawing part time on people from the logistics, finance and IT departments, gets bogged down: everyone prioritises their day-to-day activity, and design decisions wait for weeks.
Management then sets up a dedicated team. A project director is appointed, with authority over a team seconded full time from their original departments and located in the same open-plan space. Each secondment comes with a written commitment on the return position. Design decisions are made within the team. In return, the original departments had to temporarily replace the seconded staff: this is the cost of the formula, and it was accepted knowingly.
For running projects of this scale, see our page on programme management.