Stakeholders, confidentiality and the right to challenge
3 min read
Lesson objectives
- Design stakeholder participation and collect accounts without turning an advisory inquiry into individual surveillance
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
In HR consulting, it is inadequate to call management the client and workers merely 'data sources'. A decision can change their hours, opportunities, and trust in formal channels. Before interviews, build a stakeholder–decision–impact–voice map: who commissions, decides, implements, bears a disproportionate consequence, and can challenge a finding safely? Draw it from the actual situation rather than the organization chart alone. A site manager may control a roster, while care workers who rely on one transport service bear most of the effect. Their absence from an executive meeting does not make their constraint irrelevant.
Confidentiality is a bounded commitment, not an absolute slogan. Specify why each field is collected, who sees raw material, how long it is held under organizational policy and applicable law, and how results are presented for small groups. In a group of three, 'the only Friday-shift worker' may identify a person without a name. Aggregate the pattern or omit the illustration if reidentification cannot be controlled. Do not promise that no statement can ever reach another function in any circumstance; explain the limits created by safety, investigation, and local legal duties before the interview, with qualified advice on those limits. Informed participation helps a person understand purpose and boundaries; it does not by itself resolve every lawful-basis question for data processing.
Use a balanced interview protocol: ask for a specific event and context, then seek examples that contradict the first explanation, and finally ask what the adviser has not seen. If a manager attributes mistakes to a skills deficit, ask workers about instructions, workload, and tools; ask the manager for examples of different performance on the same task. Record an observation separately from its interpretation: 'three handovers were late after the system change' can be checked; 'people resist change' is a hypothesis. Do not turn one person's account into a percentage. Nor should qualitative evidence be discarded simply because it is not a representative survey: it may reveal a mechanism to test elsewhere.
When presenting findings, let affected parties correct a fact about their work or explain a constraint omitted from the draft, without granting a veto over an inconvenient but supported conclusion. Record what changed after a challenge and what did not, with reasons. This step improves inference: a low response rate on one shift may reflect a survey link unavailable in that team's language or working hours rather than 'indifference'. Watch for conflicts of interest as well. If the sponsor owns the policy under review, disclose decision criteria before seeing the results and retain a change record.
Lesson summary
Design stakeholder participation and collect accounts without turning an advisory inquiry into individual surveillance