PHI⑊PIN · Domains · Pulse WIP Iconography
Pulse
You already collect data. The problem is not the collection - it is what happens next.
Data sits in a report. The report sits in a folder. Someone asks a question six months later and nobody can answer it, because the moment has passed and the context has gone with it.
That is what we mean by a 'System of Record'. Collect, file, forget.
Pulse is different. It is a structured, recurring engagement with your audience - individuals, teams, customers, members, citizens - designed not to capture a moment but to track movement. What do people think now? How has that changed? What is driving it? Where is it heading? Pulse surfaces those answers at individual, team, and organisational levels.
Every time someone responds to Pulse, they add to a living record. Their answers are timestamped, contextualised, and connected - to their previous responses, to the people around them, to the wider cohort. Over time, fixed questions become trend lines. Individual responses become journeys. Aggregate data becomes organisational intelligence.
This is not a survey with a better name.
The thinking underneath is different.
A survey is designed to collect answers. A Pulse is designed to build understanding - and it compounds every time someone engages. Data is the foundation, not the output. From data comes information. From information, knowledge. From knowledge, the organisational intelligence to act.
That progression - what we refer to as the DIKW model - is not something we apply after the fact. It is baked into how we structure every Pulse from the start: what we ask, when we ask it, how we connect responses across time, and how we surface what matters to the people who need to act on it.
A Pulse is one of many inputs into a system of engagement. It sits alongside other modules - each capturing a different dimension of the audience, each feeding the same underlying structure - to produce a picture no single data point could deliver. Rich, layered, and precise enough to show not just where people stand, but where they are heading.
You do not need a new technology stack to do this. You need a new way of thinking about what data is for.