Who Can See What in Pulse? A Plain-Language Guide to Data Visibility

The most important question about any alignment tool is not what it measures — it is who can see what. If team members believe their individual responses can reach leadership, they will answer the way leadership wants to hear, and the data becomes useless. Here is the exact breakdown of who sees what in Pulse, and why the design produces honest data.

What individual team members see and what they can see about others

When a team member completes a Pulse check-in, they see only their own submission confirmation. They do not see their own score or response history in a way that leadership can cross-reference. They do not see how other team members answered. They cannot see aggregate team results, their own trend over time in a leader-visible format, or any data that would allow them to position themselves relative to colleagues.

This is an intentional design choice, not a permission setting. The goal is not to hide information from team members for its own sake. The goal is to remove the social incentive to perform alignment rather than report it honestly. When team members know that nobody else's answers are visible to them, they are less likely to anchor on what they think the "right" answer is, and more likely to say what is actually true.

If you are a team member reading this and wondering whether your individual response can be traced back to you: it cannot. This is not a promise made in terms of service. It is the technical architecture of the system, which we call the Trust Architecture. Individual responses are aggregated before they ever surface anywhere in the leader view.

What leaders see (aggregate patterns, not individual responses)

Leaders see patterns. Specifically, they see how alignment reads across the team as a whole on any given check-in, how those readings shift over time, and where comprehension or belief in a particular strategic direction is strong versus fragile. They do not see who said what. They do not see individual response data. They cannot drill down into a specific person's answers.

This matters for the quality of the data. The moment a team member suspects that leadership can access their individual answer, their response changes. MIT Sloan research on strategy comprehension found that 97% of senior leaders in one organization said they understood the company's strategy clearly. When tested on specifics, more than half of the top leadership group could not describe it accurately. The gap exists in part because social pressure produces stated alignment, not measured alignment. Pulse is built to measure what people actually believe, which requires removing the social pressure first.

The leader view shows aggregate alignment readings, trends across check-in cycles, and comparison across teams (where multiple teams are using Pulse within the same organization). This gives leaders something genuinely useful: an early signal of where strategic direction has and has not penetrated, without requiring a one-on-one listening tour or guessing from anecdotal signals.

For more on what leaders can learn from this data, see what is alignment intelligence and how honest feedback drives team alignment.

What HR and administrators see vs frontline leaders

HR and administrator roles can see organizational-level summaries: aggregate alignment readings across multiple teams, trend data at the department or org-wide level, and configuration settings. They cannot see individual response data either. The privacy floor is uniform across all role levels.

Where HR and administrator access differs from frontline leader access is in scope, not depth. A frontline leader sees their team's aggregate data. An HR or administrator role can see across multiple teams in a normalized view that helps with organizational planning. Neither view exposes individual responses.

This distinction matters most in larger organizations where the HR function uses alignment data to inform planning across multiple departments. The org-level summary helps HR identify where alignment is strongest across the organization and where resources for strategic communication or reinforcement might be needed, without requiring HR to access individual team member data.

What happens when a team is small enough that patterns might identify individuals

This is the question that matters most and gets asked least. If a team has four people and three of them answered a particular check-in the same way, a leader looking at the aggregate might reasonably infer who the outlier was. Aggregate data on small teams can inadvertently function as individual data.

Pulse applies a minimum threshold before surfacing any team-level results. If the number of responses for a given check-in falls below that threshold, results for that cycle are withheld entirely rather than displayed in a partial or potentially identifying form. The specific threshold is set during configuration and can be adjusted, but the default is designed to protect privacy in realistically small teams.

This means that very small teams or teams with low participation on a given cycle will not see results for that period. From a leadership perspective, this produces a gap in the data rather than misleading data. That gap is preferable to presenting results that could be traced back to individuals, even indirectly.

For details on how check-in participation works and what completion rates look like in practice, see how the Pulse check-in works.

Why this design produces better data, not worse

Every design choice in the Trust Architecture serves one purpose: getting honest answers. The instinct when building an alignment tool is to collect as much granular data as possible. More data, more visibility, more granularity. But alignment measurement does not work that way. The act of observation changes what is being observed.

Teams who know their individual responses are private answer differently than teams who suspect a leader might see their specific data. The research literature on honest feedback in organizations is consistent on this point. Survey fatigue is frequently misdiagnosed. The real problem is that people stop answering honestly when nothing changes after they do, or when they believe their honest answer carries personal risk. Pulse addresses both conditions: the data produces real patterns that leaders act on, and the architecture removes individual risk from honest reporting.

The practical outcome is that the aggregate data leaders see is closer to what people actually believe than what they would report under individual visibility. An alignment score that reflects genuine comprehension and belief is useful for planning. An alignment score inflated by social pressure tells you nothing except that your team is capable of performing agreement. You can feel that difference in the room. But you cannot manage it without honest data.

This is why leaders who use Pulse describe the aggregate patterns as more surprising than they expected. The anonymity protections built into the data design are not a concession to staff comfort. They are the mechanism that makes the measurement reliable.

Frequently Asked Questions