How to run an all-hands meeting that surfaces real questions

Collect questions before the meeting, explain how you select them, and publish follow-up on unresolved issues. Give employees a credible route to ask difficult work questions without requiring a public performance of agreement.

An all-hands question process is a set of submission, selection, response, and follow-up arrangements that lets employees raise material work questions. This article uses the term as an applied working label. Its research reference is Weiner’s 2009 theory of organizational readiness, especially shared commitment to a specific change and belief in the ability to implement it. The proposed method below is advisory guidance rather than a tested psychological scale.

Recognize the decision behind the pressure

Composite recognition scene: You watch the all-hands recording alone that evening. The room sounds supportive, but the private manager messages concern questions that never reached the stage. This is an invented illustration of a leadership pattern, not a client story or evidence about a particular person. Use the scene to identify the work choice that needs attention, without drawing conclusions about anyone’s psychological condition.

An all-hands question process should let employees obtain useful answers about work that affects them. Identify which subjects executives can address and how other questions will be handled. A visible microphone alone does not establish access. Check what happens to difficult, anonymous, duplicated, and unanswered questions before inviting the company to rely on the event as a source of clarity.

A lively question session measures visible participation. An effective question process gives material issues a fair hearing and a response, including issues people will not raise at a microphone. Explain which questions can change a decision and which seek clarity about an approved direction. Do not invite participation under an implication that everything is open. Give unresolved questions a named destination, and show employees how they can locate an answer after the event ends.

What the research supports

Weiner’s 2009 theory distinguishes commitment to implementing a change from belief in the collective ability to implement it. Use that distinction when sorting all-hands submissions. A question about staffing may concern capability, while a question about priorities may challenge the proposed direction. Assign each to someone able to answer it. Do not summarize both as a request for the CEO to repeat the rationale.

Edmondson’s 1999 research defines team psychological safety around interpersonal risk. Use that lens to design a way for employees to correct facts and raise practical concerns. A question channel can coexist with clear decision authority. It should not become a performance in which people are invited to comment only on matters already settled without being told so.

Colquitt’s 2001 justice research separates the fairness of a decision from its procedure, interpersonal treatment, and explanation. Apply those distinctions to all-hands question selection. State why questions are combined, deferred, or routed privately. A respectful answer to a selected question does not establish that the selection process gave difficult issues a fair hearing. The submission and follow-up record should make that process inspectable.

The all-hands process applies concepts from industrial/organizational psychology, the psychology of work and organizations. These sources do not prescribe a validated town-hall format. Test the proposed submission route by following a material question from receipt to answer. If it disappears between the event and the responsible manager, repair that handoff before inviting another round of submissions. Attendance alone cannot verify that the question received a response.

The submitted-question follow-through process

Use the five steps to design the question route before preparing the executive’s opening remarks. Set the collection channel, selection criteria, answer ownership, and follow-up format. Explain which decisions are settled and which can still change. Plan how to handle private matters without turning a reasonable disclosure limit into a reason to ignore the underlying operational question.

1. Open advance submissions

Explain who can see identifying information and avoid unsupported anonymity promises.

Open advance submissions with an explanation of who can read identifying information and how questions will be used. Provide a separate route for individual employment or other sensitive matters. Do not promise anonymity merely because questions are collected through a form. Ask whether employees can submit a material concern without putting their name on a public slide.

2. Publish selection principles

Prioritize material work questions rather than choosing only those with comfortable answers.

Publish practical selection principles before the meeting. Give priority to questions that affect work, reveal a consequential uncertainty, or recur across groups. Combine similar questions without changing their meaning. Explain when a question belongs elsewhere, and avoid selecting only items that let executives repeat prepared messages. Keep an owner for material questions not selected for the live session.

3. Prepare honest responses

Distinguish confirmed facts, disclosure limits, and unresolved decisions.

Prepare answers in categories: confirmed facts, decisions not yet made, and information outside the authorized disclosure boundary. Ask the responsible person to check each substantive answer. Rehearse saying that an answer is not available without implying an outcome. Do not make the quality of the session depend on the CEO appearing to know every detail immediately.

4. Allow appropriate follow-up

Give employees a route to correct a misunderstood question without forcing public self-identification.

Give employees a route to clarify what their submitted question meant after hearing an answer. Do not require public self-identification to correct a misunderstanding. Name a moderator who can distinguish a follow-up from a different question needing review. Keep a sensitive individual issue out of the live discussion while making its appropriate route clear.

5. Close unanswered items

Assign owners and update points so the meeting does not become the end of the question process.

Maintain a list of unanswered material questions, with owners and response points. Publish answers through a channel employees can find after the event. When an answer changes, identify the earlier instruction it replaces. A successful stage performance should not be the end of the question process or an excuse to lose difficult items in a private backlog.

Language to use during submitted-question follow-through process

Use the proposed wording after the relevant executives and specialists confirm the event’s scope. Replace placeholders with the actual selection and follow-up process. Explain that individual matters need a separate private route. Check that the promised channel exists and has an owner before inviting employees to use it during or after the meeting.

We selected questions using [principles]. [Topic] remains unanswered, and [owner] will respond through [channel] at [checkpoint]. If we have misunderstood your question, use [route] to correct it without identifying yourself publicly. Some individual matters need [appropriate process]. We will explain that boundary rather than turning them into a different question for the stage.

Use this instruction to clarify the next action: prepare honest responses. Say what that means in the actual situation rather than reciting the method’s name. Invite correction of facts, and distinguish a request for correction from a demand for agreement.

If an employee says management changed their question, compare the submitted wording with the version used. Correct a material change and explain how it occurred. Do not ask them to accept an answer to a more comfortable question. Where the original item cannot be answered publicly, preserve its substance and identify the authorized process that can handle it.

Work through a hypothetical submitted-question follow-through process

In the hypothetical continuation, the meeting includes several friendly questions while a recurring workload concern is left out. Review the selection record against the published principles. Assign the workload question to a responsible owner and explain how it will receive an answer. Do not solve the omission by asking for more cheerful participation at the next event.

Suppose the CEO answers a question about staffing before the relevant decision is approved. Correct the answer promptly through the appropriate employment communication process. Record the current facts and what remains unresolved. The next meeting should use the corrected account rather than leaving employees to infer that a confident public answer created an authorized commitment.

Later, employees submit a question already answered in writing. Check whether they could find the answer and whether it addressed the actual issue. They may need a practical example rather than another link. Use the feedback to improve the reference, without treating repeated questions as proof that employees refuse to listen.

The record for submitted-question follow-through process

Maintain a question log with categories, answer owners, response status, and links to approved answers. Restrict private submissions to their proper audience. Record why a question was redirected or combined without labeling its author as difficult. Give employees a usable way to find the follow-up so the log helps them obtain answers rather than becoming an internal record nobody consults.

Keep the submitted question, selection reason, answer source, and follow-up status connected. Restrict identifying details according to the stated process. Preserve a way to correct an edited question without exposing its author. Report unresolved themes at a useful level instead of publishing a list of people who asked challenging questions.

Use this completion check before closing the discussion:

Can employees understand the submission and privacy rules?
Are selection principles applied to difficult questions?
Has each factual answer been checked by its owner?
Can a misunderstood question be corrected without public identification?
Do unanswered material items have a response route?

Participation and applause do not establish understanding. Review whether material questions received useful answers, while keeping individual and private matters in their appropriate processes.

Review submitted-question follow-through process in practice

At the next decision milestone or promised update, examine this specific signal: whether material questions receive an answer or a tracked unresolved status, including questions that challenge the leadership account. Compare the result with the original working note and inspect at least one completed action. Avoid reporting improved confidence or a calmer meeting as proof that the operating problem is resolved.

After the event, trace a difficult question from submission to its final response. Check whether the answer helped employees handle the work it concerned. Review omitted items and changes to the original wording. Use that evidence to improve the next session, rather than relying on the tone of the recording or the number of hands raised.

Route individual employment concerns and allegations of misconduct through appropriate HR and legal channels. Do not answer them publicly to demonstrate openness.

For related preparation, use How to explain company change so people know what to do, How to prepare managers before announcing a company change, How to tell a credible change story without company spin, Why employees stop telling the CEO what is going wrong. Choose the guide that addresses the next concrete decision, and keep responsibility with the person authorized to make it.