Town hall meetings for companies: a practical guide for tech teams

A change in company direction eventually becomes a question for a team: what does this mean for the work we are doing?

A useful town hall helps people answer that question. It gives employees the context behind decisions, room to challenge what they hear and a clear way to find out what happens next.

My background spans web development, Scrum and product ownership. That is the perspective I bring to this guide: how company communication translates into priorities, delivery decisions and the day-to-day experience of people doing the work.

What is a town hall meeting for companies?

A company town hall is a meeting where leaders explain developments affecting the organisation and employees can ask questions. It might cover business performance, a change in strategy, investment decisions or concerns shared across teams.

It can involve the whole company or a business area, in person, online or through a hybrid format. The important feature is the opportunity for employees to question and understand what they hear.

You may also hear the term all-hands meeting. Companies use these names differently, sometimes interchangeably. Check the invitation for the purpose and format rather than assuming the label guarantees an open discussion.

How does it fit with team meetings?

A town hall provides company context. A team planning session decides what that context means for particular pieces of work. A retrospective gives a team space to examine how it works and agree improvements.

These conversations support each other. A town hall announcement still needs a route into the team’s planning, especially when it affects commitments already made.

When is a town hall worth holding?

Start with what employees need to understand or discuss. A live session is useful when an update affects several teams, raises difficult questions or needs explanation from someone accountable for the decision.

For example, teams may need to understand why the company is investing in reliability, how customer feedback has changed product priorities or which work will be reviewed after a budget change.

If you only need to distribute routine updates, consider a written summary. If one team needs to solve a detailed delivery problem, arrange a focused working session. Choose the format that gives people the right conversation.

Before sending an invitation, finish this sentence: “By the end, people should understand ___ and know how to ___.” If that is difficult to complete, clarify the purpose first.

A practical 45-minute town hall agenda

This is a starting point to adapt. Protect the question time when presentations overrun, and choose speakers because they can explain the decisions under discussion.

Share the purpose, agenda and question channel in advance. Assign a facilitator to manage time and participation, and another person to capture decisions and follow-up. Ask presenters to explain unfamiliar terms and show why each metric matters.

A worked example: a product priority changes

This is an illustrative scenario, not a case study or a claim about a company I have worked with.

A software company wants to improve the experience for new customers. At its town hall, leadership announces a focus on onboarding: the steps customers take to get started with the product.

Development and data teams already have a full set of commitments. Hearing that onboarding is “the priority” leaves them with an unresolved question: are they supposed to fit it around everything else?

Explain the decision and its limits

The leader could give a more useful explanation:

“Customer feedback and usage data suggest people are struggling to complete account setup. We are prioritising an investigation into that problem. We have not yet agreed the solution or delivery date. Product and engineering leads will review existing commitments this week and identify what should move before new work is agreed.”

This separates the problem, the decision and the unanswered questions. It also gives teams permission to discuss trade-offs before a broad direction becomes an assumed deadline.

Translate the message into team decisions

Afterwards, the product owner can review the backlog, the ordered list of work being considered for the product. Developers can identify technical dependencies, while the data team checks what evidence is available and what needs further investigation.

The next conversation should establish what starts, what pauses and who needs to agree a change. If your team uses Scrum, take the announcement into the relevant planning conversations rather than treating it as an automatic instruction to add work to the current Sprint.

The town hall has provided direction. The delivery conversation makes that direction realistic.

Make it easier for people to contribute

An invitation to “ask anything” does not remove the difficulty of questioning a senior leader. New starters, people in junior roles and anyone who has previously been interrupted or dismissed may need a different route into the conversation.

For women entering tech, speaking in a large meeting can also mean weighing up whether a question will be taken seriously. Make room for contributions without expecting anyone to represent an entire group.

Offer more than one question channel

Accept written questions before and during the session, alongside spoken contributions. If you offer anonymous submissions, check the settings and explain what organisers can see. A form without a name field is not, by itself, a guarantee of anonymity.

The facilitator should explain how questions are selected. Group repeated themes without removing the concern behind them, and include difficult questions alongside popular ones. Keep individual employment matters out of the public discussion and offer an appropriate private route.

Include people joining remotely

Test room audio from a remote participant’s perspective. Use microphones for questions, repeat anything that was not captured clearly and ask someone to monitor the online question channel. Provide captions and accessible materials, and consider time zones when scheduling.

Share a written recap for people who cannot attend. If a recording is appropriate, explain the arrangements before the session and provide a way to contribute afterwards.

Handle uncertainty honestly

Sometimes the answer is not ready. Explain what is known, what remains undecided and when the next update will come. If information cannot be shared, explain the boundary as clearly as possible.

A useful response might be: “We have not agreed the revised scope. The product and engineering leads are reviewing it on Thursday, and we will share the outcome on Friday.”

Useful questions to ask at a company town hall

Choose a question that helps you understand a decision or its effect on your work. You do not need to sound senior to ask something useful.

• Priorities: Which existing commitment should we reconsider to make room for this?
• Evidence: What customer problem or business result led to this decision?
• Capacity: How will teams raise concerns if the proposed scope exceeds the people or time available?
• Success: What result would show that this change is working, and when will we review it?
• Uncertainty: Which parts are agreed, and which are still open to input?
• Development: What support will be available for people learning the skills this change requires?

If you are attending your first town hall, read the agenda and write down one thing you want to understand. A simple opening is: “You mentioned X. What will that mean for Y?” Submit it in writing if that suits you better. Listening and following up afterwards are valid ways to participate too.

Turn the discussion into visible follow-up

Agree when the recap will be available. As a practical starting point, aim for two working days, even if some answers are still pending. Include decisions, unanswered questions and the next update date.

For the onboarding example, an entry could read: “Review planned work before agreeing onboarding changes. Product and engineering leads to publish the revised priorities in the team workspace by Friday. Status: in progress.”

Give team leads enough context to discuss implications with their teams. Revisit open actions before the next town hall, and say when an action will not proceed, including the reason.

Check whether it helped

Attendance tells you who joined. To learn whether the meeting was useful, ask employees whether they understand the priorities, know what happens next and had a workable way to raise questions. Track whether promised updates were delivered, and use the feedback to change the next session.

Choose the frequency around the organisation’s needs. Monthly or quarterly sessions may suit a regular rhythm, but important changes need timely communication between those dates.

Your next town hall checklist

• Write one clear purpose and share it with the agenda.
• Explain the effect on priorities and existing commitments.
• Protect question time and offer written contributions.
• Check access for remote colleagues and people who cannot attend.
• Give unanswered questions an owner and an update date.
• Follow through on commitments and ask what needs to improve.

For your next session, start with one change: make the effect on current work explicit. People should leave knowing what they need to discuss with their team, who can answer the remaining questions and when they will hear more.