Introduction
When pulse survey results make you think "something may be going on in this department," what should you do next?
A common misunderstanding is to treat a pulse survey as a way to "find out who is likely to leave." But because COCKPITOS pulse surveys collect responses anonymously and aggregate them by department, what they show is the overall trend of a department — not the condition of any specific person, and not when anyone might resign.
This article explains how to use pulse surveys not as a prediction tool, but as a way to decide what a team should talk about, based on department-level changes.
1. What COCKPITOS Pulse Surveys Can and Cannot Tell You
| What you can see | What you cannot see | |
|---|---|---|
| Unit | Category averages by department, and how they change over time | Any individual's answers or scores |
| Nature | Department-wide trends and changes since the last survey | Whether, or when, someone will resign |
| Use | A starting point for choosing team conversation topics | Performance evaluation, compensation, or judgments about individuals |
In COCKPITOS pulse surveys, response data does not store employee IDs or other personal identifiers. Results are aggregated by department, and departments with too few responses are not displayed, to protect anonymity. The admin screen does not show who answered what.
Keep it separate from the Stress Check
Under Article 66-10 of Japan's Industrial Safety and Health Act, individual Stress Check results are not provided to the employer without the employee's consent. Pulse survey results and individual Stress Check results are never matched at the individual level. In COCKPITOS, the pulse survey and the Stress Check simply appear side by side on the dashboard; their data is not linked.
2. The Six Standard Categories and Possible Conversation Topics
The COCKPITOS pulse survey provides a standard template with questions in the following six categories (each company can adjust the questions in the admin screen). The question wording below is an English rendering of the Japanese template.
| Category | Standard template question | Conversation topics when a department's score changes |
|---|---|---|
| Workload | Was your workload this month appropriate? | How work is assigned, number of meetings, how priorities are set |
| Colleague support | Can you easily ask colleagues for help when you are stuck? | Whether there are easy opportunities to ask for help; how handovers work |
| Retention intent | Do you want to keep working at your current workplace? | What makes this workplace easier or harder to keep working in |
| Manager support | Do you receive enough support from your manager? | Timing of consultations, frequency of feedback |
| Growth opportunities | Are there opportunities to grow and build skills here? | Work people want to take on, time for learning |
| Psychological safety | Can you share your opinions without worry? | How easy it is to speak up in meetings; how dissenting views are handled |
"Retention intent" is the category most easily associated with individual resignations, but here too you are looking at a department average. Treat it as material for the team to think about: "What is making this department a harder place to keep working in?"
3. Three Perspectives for Reading Department-Level Changes
Perspective 1: Look at several surveys, not a single rise or fall
A single change can come from busy seasons, transfers, or a different mix of respondents. First line up several survey cycles and check whether the movement is temporary or an ongoing trend. In COCKPITOS, the admin screen shows category scores by department and the change from the previous survey.
Perspective 2: Check whether several categories are moving together
Whether one category is moving alone or several are moving together changes how broad the conversation should be. For example, if "workload" and "psychological safety" are both falling, you can raise the possibility that people find it harder to ask for help or speak up while busy.
Perspective 3: Check the context behind the numbers first
- Has the number of responses or the response rate changed significantly since last time?
- Has anything happened to the department — reorganization, transfers, a busy season?
- Do the free-text comments add context? Avoid sharing details that could identify a respondent.
Rather than drawing conclusions from numbers alone, go into the conversation with a hypothesis about what may be happening. Your questions will be more concrete.
4. Choosing Conversation Topics by Type of Change
The following examples illustrate how to choose conversation topics when department-level results change. None of them predict what will happen; they are a way to organize what to talk about.
Type A: Retention intent and manager support fall together
Possible background: Changes to evaluations or roles, shifts in direction, or changes in how much the manager and the team communicate.
Example topics: - Is anything about recent changes (direction, structure, roles) unclear or worrying? - How easy is it to consult the manager, and when?
How to proceed: - In the next team meeting or 1on1, talk about "recent changes" rather than scores - Because manager support is involved, the manager should not handle it alone — consult HR on how to proceed
Type B: Workload or psychological safety stays low
Possible background: Uneven workloads, too many meetings, unclear scope of responsibility, or an atmosphere where it is hard to speak up.
Example topics: - Is the volume of work itself too high, or are priorities and roles unclear? - In which meetings or daily interactions is it hard to share opinions?
How to proceed: - Do not treat it as a matter of individual effort; review structures such as work allocation, meetings, and roles - Start from team members' views rather than imposing fixes from above
Type C: Growth opportunities stay low
Possible background: Work content has become fixed, there is no time for development, or career paths are not shared.
Example topics: - What work would people like to try, and where do they feel something is missing? - What learning opportunities or chances to expand roles can the department offer?
How to proceed: - Deliberately set aside time in 1on1s to talk about careers - Show concrete opportunities the department can actually provide
5. Using Results in Team Conversations and 1on1s
Example flow when raising a team trend in a 1on1
| Step | Time | Content |
|---|---|---|
| Opening | 5 min | Start with "How have things been lately?" (no scores, no evaluation) |
| Sharing the team trend | 5 min | "In the team-wide survey, answers about workload were lower than last time. How does it feel from your side?" (share it as a team-wide trend) |
| Listening to the background | 10 min | Hear, in the person's own words, how work and the team are going |
| Next step | 5 min | Agree on one thing to try before the next meeting |
Because pulse surveys are designed to be anonymous, managers cannot know individual answers — and should not try to. Understand each person's situation from what they tell you.
What to avoid
- Trying to find out "who gave the low scores"
- Trying to identify respondents and using their presumed answers in individual performance, pay, or placement decisions
- Treating results as a prediction, e.g. "someone on this team is about to quit"
- Noticing a change but postponing any conversation about it
6. Know the Limits of Pulse Surveys
- Only department averages are visible: If only a few people in a department are struggling, it may not show in the average
- Results depend on candid answers: If people are not confident their answers are anonymous, responses tend to look better than reality
- Small departments are hard to see: To protect anonymity, departments with few responses are not displayed
- Numbers do not explain why: Numbers alone cannot establish the reasons. Check them through conversation and information about workload or organizational changes
Pulse survey numbers are not answers — they are material for asking better questions.
Summary
| Change seen in a department | Example conversation topics | Main setting |
|---|---|---|
| Retention intent and manager support fall together | Concerns about recent changes; ease of consulting the manager | Team meeting / 1on1 (with HR) |
| Workload or psychological safety stays low | Work allocation; ease of speaking up in meetings | Team meeting |
| Growth opportunities stay low | Work people want to try; learning opportunities | 1on1 |
A COCKPITOS pulse survey does not tell you who will leave. It is a tool for noticing department-level changes and deciding what to talk about next. Using the numbers as a starting point, and confirming the background through conversation, is what helps build a better workplace.
COCKPITOS aggregates anonymous pulse survey responses by department so you can review category scores, changes since the last survey, and free-text comments. For an overview, see COCKPITOS in Japan. If the numbers are clear but the next conversation is not, contact us to discuss how to use department-level results.