People Analytics

Organizational Intelligence: A Decision Context Worksheet

Build organizational intelligence around a decision, with traceable evidence, employee context, competing explanations and an accountable next step.

By Rachel FosterAutomated, source-grounded editorial method7 min read
Share
Organizational Intelligence: A Decision Context Worksheet

Short answer

Organizational intelligence helps leaders answer a defined question about how work is happening and what to do next. It combines relevant records, employee and stakeholder accounts, professional expertise and operating context. A useful process preserves the source, coverage and uncertainty of each input, tests competing explanations and records an accountable human decision without turning employees into profiles.

Start with the decision that is blocked

“Understand the organization” is not an actionable brief. Name the decision, the work moment and the evidence threshold before collecting more material.

Brief fieldExample entry
DecisionWhether to test a revised returns handover in three stores
Decision ownerRegional operations director
PopulationReturns colleagues and duty managers in the three stores
PeriodThe previous six weeks
Known observationUnresolved returns remained open past the next shift
Open questionIs the cause unclear ownership, missing information, system access or another condition?
Evidence neededHandover records, process version, employee accounts and manager context
Decision limitNo conclusion about an individual's capability
Review pointAfter two weeks of a controlled local test

The US Federal Data Strategy practices advise identifying the key question and the data needed to answer it, documenting quality and provenance, and aligning quality with intended use. These are federal data practices, not an employment standard, but the sequence is useful: a question gives data quality a purpose.

Use four evidence lenses

One source rarely carries enough context for an organizational decision. Build the decision file from evidence that answers different parts of the question.

  1. Organizational records: process dates, staffing coverage, work events or service measures. These can show what was recorded, under the definitions used.
  2. Employee and stakeholder accounts: recent examples, explanations, disagreement and local language. These show what participants report and how they interpret the work.
  3. Professional expertise: knowledge from HR, operations, legal, safety, data and other relevant owners. Expertise helps test feasibility and risk.
  4. External research: applicable research or guidance that informs the method or the proposed action.

The CIPD evidence-based practice factsheet describes research, organizational data, professional expertise and stakeholder perspectives as evidence sources to consider together. Agreement does not automatically mean independence. Two reports may repeat the same system record, while a manager summary may already include the employee account later counted as a second source.

For each input, record its origin and what it can support.

Source checkQuestion
ProvenanceWho or what created the record, when and for which purpose?
CoverageWhich people, places, events and dates are present or missing?
DefinitionWhat exactly does the field, theme or event mean?
TransformationWas the source translated, coded, summarized, joined or filtered?
IndependenceDoes this add evidence or repeat another source?
Decision fitWhich part of the decision can it reasonably inform?

Separate an account from an observation

An employee conversation can be current, detailed and valuable. It remains an account from a participant. It may describe a work event that can be checked against a record or observed in context, but follow-up questions do not automatically verify every statement.

Keep three fields distinct:

  • Source material: what a person said or what a record contains.
  • Observation: the bounded event or condition directly supported by the source.
  • Interpretation: a possible explanation that may require another check.

The GOV.UK research analysis guide recommends recording what was seen or heard separately from what it means before forming findings and actions. Use that separation for employee context too.

For example, “The approval owner was not listed in the handover document used on Tuesday” is a checkable observation. “Managers do not communicate” is a broad interpretation. The second statement requires a defined standard, wider evidence and counterexamples before it can guide action.

Copy this decision-context worksheet

Complete one row for each material claim in the decision brief.

FieldWhat to record
ClaimA bounded statement about the work, population and period
Supporting evidenceSource IDs and the relevant records or passages
Contrary evidenceA case that weakens, narrows or changes the claim
Missing perspectiveA role, shift, site or stakeholder not yet represented
Alternative explanationAnother mechanism consistent with the evidence
ConfidenceWhat is established, plausible and unresolved
Proposed actionA proportionate decision, check or reversible test
OwnerPerson accountable for the action and communication
ReviewDate, evidence to collect and continue/change/stop rule

For a shorter meeting-ready version of this structure, use the HRBP data briefing worksheet.

Avoid building a permanent employee label from a situational account. A comment about one handover is evidence about that event. It is not a stable trait, a forecast or a basis for an automated employment decision.

Fictional example: a returns handover

Northbank Retail is fictional. A regional HRBP is asked why unresolved returns are carrying into the next shift at three stores.

The initial dashboard shows 28 carry-overs in six weeks. The definition changed in week three, so the earlier and later counts are not directly comparable. Eleven voluntary employee conversations include seven accounts of an unclear approval owner, but evening-shift participation is low. Two duty managers say the owner is covered in the process document. A document check finds that one store still displays the previous version. Another store has the current document and still records carry-overs.

The HRBP writes a bounded finding: approval information may contribute at one store, while the current evidence does not explain all three. The evidence does not support ranking stores or identifying a “best” employee.

The operations director approves a two-week test at the store with the outdated document. The team replaces it, names the duty owner in the handover and records whether the next shift can resolve the same defined cases. Evening-shift colleagues are included in the review. The other stores continue source checks rather than receiving the same intervention by assumption.

Check freshness and quality separately

Recent information may be incomplete, inconsistently defined or based on a narrow group. Older material may be accurate for its original period but stale for today's decision. The UK Government Data Quality Framework defines quality as fitness for purpose and treats completeness, uniqueness, consistency, timeliness, validity and accuracy as separate dimensions. It also notes that timeliness can trade off against completeness or assurance.

Display the source date, availability date and decision period. If a definition or population changed, show that beside the comparison rather than smoothing it into one trend.

Where employee conversations fit

A focused employee conversation can add recent examples and missing work context to a defined question. Managers receive a prepared brief, not raw employee responses. HR uses grouped material only when at least five respondents are represented, and that floor does not remove the need to consider whether context could identify someone.

The Lontra product overview explains the employee conversation and manager-brief workflow. Use conversation material as one declared source in the decision file. Human owners still check provenance, compare relevant records, test alternatives and decide what follows.

Organizational intelligence becomes useful when a leader can see why a conclusion was reached, what remains uncertain and which evidence will determine the next step. Its value lies in better-framed decisions and institutional learning, not in producing more data or profiles.

Frequently asked questions

What is organizational intelligence?

Organizational intelligence is the ability to connect a defined business question with relevant records, employee and stakeholder accounts, professional expertise and operating context, then make a traceable human decision. It is a decision practice rather than a score assigned to people.

How can HR build organizational intelligence?

Start with one decision, define its population and period, inventory the evidence needed, preserve provenance, seek missing and contradictory perspectives, separate observations from explanations, and record an accountable next step with a review date.

Apply this question to your organization

Choose one team and a concrete work question. Explore how Lontra can help prepare conversations and review what people describe before deciding on an action.

More from Blog