Teams Team engagement and project drift
Team engagement on a project is not a human resources topic set beside steering: it is one of the best-documented and least-equipped causes of drift. A project does not drift through scope or estimation alone. It also drifts because the team disengaged before it did, and nobody saw it written down anywhere.
What engagement surveys do.
They do a job that pylotik does not do, and it is better to say so right away.
They poll regularly
Climate surveys, short questionnaires, repeated measures. They give a picture of collective sentiment.
They compare
With the previous period, with other entities, sometimes with an external benchmark. This is useful to a human resources department.
They feed a policy
Training, organization, quality of working life. They inform company decisions, at company scale.
Their limit is structural and is no flaw: a survey does not know projects. It knows that a team is doing worse this quarter. It does not know that this is the third week of overload on work package 2 of a fixed-price contract whose milestone was brought forward.
What the topic really weighs.
The second figure is the most instructive. The gap between 22% and 79% says that engagement is not a mystery of personality: it plays out in something observable, which can be worked on. The detail of the studies is on value lost in projects.
Two accounts, on the same scope and the same week.
What we equip is not a measure. It is a confrontation: over the same week and the same project, two independent accounts exist. The manager's, which describes what they observe. The team member's, which describes what they live.
These two accounts are not supposed to coincide, and that is the whole point. Their gap becomes readable, and it is far more informative than a score: a project where the manager sees a calm team and where the team describes three weeks of tension does not have a morale problem, it has an escalation problem.
No survey can produce this, because it knows neither the project, nor the week, nor the work package. That is why the human thread lives here in the same place as the project thread, in what we call operational commitment management.
Nobody is rated, nothing is scored.
This is not a precaution of wording. It is the design rule, and it explains what the product will never do.
No individual score
Nobody receives a grade, a ranking or an index. There is no figure attached to a person.
No inference of emotion
Nothing analyzes a tone, a mood or a psychological state. A text is read by humans, not interpreted by a machine.
No prediction
The product does not claim to anticipate a departure or to single anyone out. That would be false, and it would be a fault.
No rewriting
The words stay attached to their author, as written. They are neither summarized nor silently rephrased.
The processing of personal data is described in the privacy policy. Setting up a feedback mechanism is also a matter for each organization's social dialogue (employee representation), and we have no instruction to give on this point.
In pylotik.
Four mechanisms, all based on dated writing rather than on measurement.
The weekly report
A few minutes on Friday: what moved forward, what got stuck, in what tone. See the weekly team report.
The managerial review
The manager writes what they observe on the same scope and the same week. The two accounts coexist without correcting each other.
A two-level reading
Once sent, the report is read by the manager and by the human resources department. The words do not travel up through the manager alone.
Workload, alongside
A lasting overload is read in the workload plan, not in a feeling. See the project workload plan.
The complete tour is on the product page.
A manager without instruments is not a bad manager.
When 70% of a team's engagement depends on its manager, the usual conclusion is that we need better managers. It is one reading, and it is unfair in most cases.
A team lead in a services company supervises people they do not see every day, spread across several projects and sometimes at the client's. They have neither the time for continuous observation, nor the ritual that would produce it. What they lack is not the will: it is a place where what they observe gets written down, and where what their teams live comes back to them.
That is also why the mechanism is symmetrical: it does not only ask team members to speak, it asks the manager to write what they see. A mechanism that solicited only one of the two sides would be a mechanism for watching people, not for listening to them.
What we are asked about the human side.
Does pylotik measure team engagement?
No. It produces no index, no score, no comparison. What it carries is two written accounts on the same scope and the same week, whose gap becomes readable. It is not a measure, it is a confrontation.
Are team members rated?
Nobody is rated, nothing is scored. No figure is attached to a person, and no ranking exists. It is a design rule, not a setting.
Does the manager see the individual reports of their team?
Yes, once sent, and that is the point: the words are addressed to them first. The draft, for its part, stays strictly private until it is sent.
What happens when the manager is the problem?
That is the reason for the two-level reading. Once sent, the report is read by the manager and by the human resources department. The words do not depend on the goodwill of a single relay.
Do we need to inform employee representatives?
Setting up a feedback mechanism is a matter for each organization's social dialogue (employee representation), and we have no instruction to give on that ground. What we can say is factual: no score, no rating, no prediction. See the privacy policy.
How long does the weekly report take?
A few minutes, because it covers one person's past week and not a company form. A mechanism that cost more would not be kept up, and a mechanism that is not kept up says nothing.
Going further.
- The weekly team report: the template and how it is used.
- The workload plan: lasting overload, read as a signal.
- Operational commitment management: the definition of the category.
- The privacy policy: what is collected, and what is not.