Huddle asks different questions than traditional engagement or culture surveys. Instead of infrequent, top‑down diagnostics, Huddle captures what teams are experiencing right now and focuses on conditions that leaders can directly influence.
Our recommended best practice design principles draws on decades of research into Employee Voice (Morrison, 2011), alongside best-practice questionnaire design synthesised by Imperial College London (Gehlbach & Brinkworth, 2011; Gehlbach & Artino Jr., 2018) and foundational survey science (Krosnick & Presser, 2010; Schwarz, 1999).
Use neutral,
non-judgemental language and focus on experience, not blame. This lowers the
perceived risk of speaking up and encourages more honest input.
❌Bad practice
· How effectively does your leader support you?
✅Good practice
· How supported do you feel in managing your current job demands?
2. Action-Linked Intent
Design questions that surface insights leaders can act on quickly. Example high-value focus areas include:
· Workload sustainability
· Communication and clarity
· Support, resources and work efficiency
· Team trust and safety
· Coordination and teamwork
·
Improvement
and learning
❌Bad practice
· How happy are you at work?
✅Good practice
· How energised are you by your work right now?
3. Behavioural or Experiential Framing
Focus on observable conditions and lived experience rather than abstract opinions. This improves accuracy and actionability for leaders.
❌Bad practice
· How satisfied are you with culture?
✅Good practice
· How effectively does your team take action when faced with challenges?
4. Neutral, Question-Based Wording
Use neutral, direct questions instead of agree/disagree statements. “How”
questions create a more human-centred, reflective response. This reduces bias
and cognitive effort.
❌Bad practice
· Leadership communicates changes effectively.
✅Good practice
· How effectively are changes affecting your work being communicated?
5. One Construct Per Question
Each
question should measure one idea only. This preserves clarity and construct
validity.
❌ Bad practice
· How satisfied are you with opportunities to give feedback and see action taken?
✅ Good practice
· How satisfied are you with opportunities to provide feedback in your team?
· How effectively is action taken from feedback in your team?
6. Short Recall Windows
Short recall
improves accuracy and trend sensitivity. Anchor questions in current or recent
experience as this improves reliability and strengthens trend monitoring.
❌ Bad practice
· How effectively does your team work together?
✅ Good practice
· How effectively is your team working together right now?
7. Consistent Item-Specific Response Scales
Avoid
generic “Strongly disagree → Strongly agree” scales. Use consistent scales
tailored to the construct being measured. This improves interpretability and
ease of response.
❌ Bad practice
· Strongly agree → Strongly disagree
·
Negatively
indexed responses mixed with positive indexed responses
✅ Good practice
Example question – How clear is your teams’ goals…
· Very clear > Mostly > Somewhat > Not very > Not clear
8. Consise by Design
Shorter surveys support sustained participation and data quality, critical in continuous pulse measurement.
❌ Bad practice
· More than 7 metrics per submission
·
All
metrics remain static over extended periods (creates survey fatigue)
✅ Good practice
· 7 metrics per submission cycle:
o 3–5 core metrics (always on across all teams)
o 2–4 rotational metrics responding to context, change or risk
o ~7 total metrics per submission per cycle