An MTO in project management is an employee satisfaction survey used within a temporary project team, rather than within a fixed department or the entire organisation. The goal is the same as a regular MTO: gaining insight into how people experience their work. But the context differs significantly, because project teams work under time pressure, with changing compositions and a clear beginning and end. In this article, we answer the most frequently asked questions about MTOs in project environments.
How does an MTO in project management differ from a regular employee survey?
An MTO in project management focuses on the experience within a specific, temporary team around a concrete project. A regular MTO measures the engagement and satisfaction of employees within a fixed organisational structure, over a longer period. The key difference lies in the time horizon, the team composition, and the questions you ask.
A regular MTO often covers themes such as career development, working conditions, and the relationship with the line manager. Those themes are relevant across multiple years. In a project environment, other matters take centre stage: is collaboration within the team working well, is the division of tasks clear, does everyone experience sufficient autonomy and support to achieve the project goal?
Another difference is the urgency of follow-up. With an annual MTO, you can plan improvement actions for the next quarter. Within a project of three or six months, you need to act faster. Signals picked up in week four must already lead to a conversation or adjustment by week five. The meaning of an MTO shifts in a project context from a periodic measurement tool to an active steering instrument.
What exactly does an MTO measure within a project team?
Within a project team, an MTO measures the experience across themes that directly influence collaboration, progress, and results. Think of clarity about roles and responsibilities, the quality of communication, experienced workload, trust in the project manager, and the degree to which team members feel heard.
Concrete topics that a project MTO maps out:
- Clarity of goals and expectations
- Collaboration and team atmosphere
- Experienced workload and balance
- Quality of decision-making and communication
- Degree of autonomy and ownership
- Trust in the project manager or steering committee
The shorter the project, the more you tailor the questionnaire to the current phase. In the start-up phase, clarity and expectations are most relevant. Halfway through the project, collaboration and workload take centre stage. Towards the close, the focus also shifts to learning and handover.
When do you conduct an MTO during a project?
You conduct an MTO at moments when feedback can still be used to make adjustments. For a six-month project, that means at least two measurements: one around the first month and one halfway through. For a longer project of a year or more, three or four measurement moments are worthwhile.
A one-time measurement at the end of a project adds little value for that project itself. You can only carry the outcomes forward to a future project. That is useful for organisational learning, but it does not help the current team.
Choose your measurement moments deliberately around project milestones. After an intensive sprint period, after a go/no-go decision, or after a major delivery, team members are sharply aware of what went well and what could be better. That yields richer and more honest feedback than a randomly chosen date.
What is the difference between an MTO and a retrospective?
A retrospective is a team reflection at the end of a sprint or project phase, in which the team collectively discusses what went well, what could be improved, and what they would do differently next time. An MTO is a structured, anonymous survey that measures individual experiences through a questionnaire. The difference lies in anonymity, structure, and depth.
In a retrospective, you speak openly with each other as a team. This works well for process improvements and team dynamics, but it requires psychological safety. Not everyone dares to say in a group conversation that the workload is too high or that collaboration with a particular team member is running into difficulties.
An MTO does offer that safety, because the answers are anonymous. As a result, more sensitive signals surface more readily. The two instruments complement each other: use an MTO to measure honest, individual experiences, and use the retrospective to reflect collectively on the outcomes and formulate actions as a team.
How do you use MTO outcomes to steer a project?
MTO outcomes are only valuable if you actually act on them. The step from score to action is precisely where things often go wrong in practice. A number tells you that something is going on; you need the context and the underlying stories to understand what is going on and what needs to change.
An effective approach in four steps:
- Identify the drivers: Which themes score low and have the greatest influence on the overall experience? Focus your attention there, not on everything at once.
- Discuss the outcomes with the team: Share the results transparently. Employees who see that their feedback is taken seriously are more willing to participate again in a subsequent measurement.
- Formulate concrete actions: Translate each point of attention into a specific measure. Not "we will improve communication", but "we will schedule a fifteen-minute weekly team meeting for progress updates".
- Follow up and measure again: Check at the next measurement whether the action has had an effect. This closes the loop and demonstrates that feedback leads to change.
This principle of continuous listening and follow-up is the core of effective employee research, including in a project environment.
Which tools are suitable for an MTO in project management?
A good tool for a project MTO is quick to set up, anonymous for participants, and gives the project manager direct insight into the outcomes without requiring a data analyst. Flexibility is important: you want to be able to adapt the questionnaire to the project phase and the type of team.
When choosing a tool, pay attention to the following criteria:
- Anonymity is guaranteed, even with small teams
- Reports are understandable for project managers without a research background
- You can adjust the questionnaire per measurement or project phase
- The tool supports follow-up, so that actions can be linked to outcomes
- The tool complies with GDPR requirements, especially when handling sensitive feedback
Avoid tools that only provide a total score without context. A score of 7.2 on team communication says little if you do not know which aspects of communication are causing the problem and which part of the team is experiencing it.
How CYS Group helps with MTOs in project management
CYS Group offers an approach that goes beyond sending out a questionnaire. With the cx.management platform and its own 3-question methodology, you can quickly and without complex statistics map out which factors determine the experience of project team members. The driver analysis shows which themes have the greatest impact on overall satisfaction, so that you as a project manager or HR Business Partner know where to focus your energy.
What CYS Group concretely offers for project environments:
- Short, focused questionnaires that fit the phase of the project
- Anonymous reports that protect privacy even in small teams
- A Priority Matrix that immediately shows which improvements deliver the most value
- Support for closed-loop follow-up: from signal to action to verification
- GDPR-compliant and ISO 27001-certified, ensuring that sensitive employee feedback is kept secure
Whether you are evaluating a one-off project or want to set up a continuous listening programme for all project teams in your organisation: CYS Group is happy to think along with you. Get in touch and discover what a well-structured MTO can mean for your project teams.
Make every experience count.
Frequently Asked Questions
Hoe groot moet een projectteam zijn om een MTO zinvol te maken?
Een MTO is zinvol vanaf ongeveer vijf teamleden, mits de anonimiteit gewaarborgd blijft. Bij kleinere teams loop je het risico dat individuele antwoorden herleidbaar zijn, wat de eerlijkheid van de feedback ondermijnt. Gebruik bij teams van drie of vier personen liever een vertrouwelijk één-op-één gesprek of een tool die specifiek ontworpen is voor kleine groepen met extra privacybescherming.
Wat zijn de meest gemaakte fouten bij het opzetten van een project-MTO?
De meest voorkomende fout is een vragenlijst maken die te lang is of te generiek, waardoor de respons laag uitvalt en de uitkomsten weinig bruikbaar zijn. Een tweede veelgemaakte fout is de resultaten niet terugkoppelen aan het team, waardoor medewerkers het gevoel krijgen dat hun feedback nergens toe leidt en bij een volgende meting afhaken. Houd de vragenlijst kort en gefocust op de actuele projectfase, en communiceer altijd wat je met de uitkomsten doet.
Hoe zorg je voor een hoge respons binnen een druk projectteam?
Respons begint bij draagvlak: leg vooraf uit waarom het MTO wordt uitgevoerd, wat er met de uitkomsten gebeurt en hoe de anonimiteit is gewaarborgd. Houd de vragenlijst kort, maximaal vijf tot tien vragen, zodat invullen niet meer dan drie minuten kost. Stuur een herinnering na twee of drie dagen en zorg dat de projectleider het belang actief uitdraagt, want steun vanuit de leiding verhoogt de deelnamebereidheid aanzienlijk.
Kun je een MTO ook inzetten bij een extern of hybride projectteam met freelancers?
Ja, een MTO is juist extra waardevol bij gemengde teams van interne medewerkers en externe freelancers, omdat onderlinge verwachtingen en werkbeleving sterk kunnen verschillen. Zorg er wel voor dat de vragenlijst neutraal geformuleerd is en niet uitgaat van een vaste dienstverband, en check of externe deelnemers vallen onder de AVG-afspraken van de tool die je gebruikt. Segmenteer de uitkomsten eventueel per groep om te zien of er structurele verschillen zijn in beleving.
Hoe bespreek je MTO-uitkomsten met een team zonder dat het een aanklacht wordt?
Presenteer de uitkomsten als gedeelde informatie, niet als oordeel over individuen of de projectleider. Begin met wat goed gaat voordat je aandachtspunten bespreekt, en formuleer het gesprek als een gezamenlijke zoektocht naar verbetering. Stel open vragen zoals 'Wat hebben jullie nodig om dit te verbeteren?' in plaats van 'Waarom scoort dit zo laag?', zodat het team eigenaarschap voelt over de oplossingen.
Wat doe je als de MTO-uitkomsten halverwege het project structurele problemen blootleggen die je niet meer kunt oplossen?
Zelfs als een probleem niet volledig oplosbaar is binnen de resterende projecttijd, is erkenning al een krachtige eerste stap. Communiceer transparant wat je wel en niet kunt veranderen, en leg uit waarom. Documenteer de bevindingen zorgvuldig voor het projectevaluatierapport, zodat de organisatie er bij toekomstige projecten van kan leren en dezelfde knelpunten voorkomt.
Hoe integreer je MTO-resultaten in de projectevaluatie of het eindrapport?
Verwerk de MTO-uitkomsten als een apart onderdeel in de projectevaluatie, naast de traditionele KPI's op tijd, budget en scope. Laat zien hoe de teambelevingsscores zich door het project heen hebben ontwikkeld en koppel dit aan concrete mijlpalen of gebeurtenissen. Dit geeft toekomstige projectleiders en stuurgroepen waardevolle context over hoe teamprestaties en menselijke factoren het projectresultaat hebben beïnvloed.
