Leading the team

How do I gather real input from my leadership team before we plan?

The short answer

Before quarterly or annual planning, the leadership team's real inputs are usually thinner than the planning meeting suggests, because people say what moves the meeting along. Halo, HaloVision's AI, holds confidential one-on-ones with each leader and, within 48 hours of the last conversation, shows the CEO each leader's priorities, assumptions and concerns, and where they conflict, so the plan starts from them.

Signs you're here

  • Planning meetings produce a list everyone accepts and nobody owns.
  • Last cycle's plan was agreed and then reinterpreted by each function.
  • The loudest voices set the priorities, and quieter leaders' concerns come out later.
  • Leaders' assumptions about the market, resources or timing differ and have never been compared.
  • You want planning inputs from leaders and senior team members who rarely speak in the room.

What changes

  • The plan starts from each leader's real priorities, assumptions and concerns.
  • You see conflicts between functions before they become arguments over the plan.
  • Fewer plans get agreed and then quietly reinterpreted.
  • Quieter voices are heard as well as the loudest.

Why the usual approaches miss it

Planning meetings and workshops

They collect inputs in front of colleagues, so people state what is easy to defend and skip what is risky or unresolved.

Templates and input forms

They collect the answers the template asks for. They do not follow up on the reasoning, or surface the concern nobody thought to put in the form.

The CEO's pre-planning one-on-ones

They are useful, but leaders tailor what they say to the CEO, and the CEO cannot compare all conversations side by side without bias.

Surveys

They reach many people with the same questions, but cannot dig into the why behind a leader's priority or the assumption underneath it.

How Halo helps

Halo surfaces what people know but aren't saying, including the assumptions behind each leader's priorities. As a neutral third party, it hears them straight from the source, and people share more when confidentiality is guaranteed.

Halo goes deeper into the why behind each view. Its questions get sharper after every conversation, so it cross-checks assumptions between leaders and digs into specific problems. It is not a fixed questionnaire that everyone goes through.

The CEO gets a report with each leader's inputs gathered and compared: where priorities line up, where they conflict, and what to decide before the plan is set. You can keep asking Halo questions about the findings, and run Halo again before the next cycle.

In every engagement so far, Halo has surfaced perspectives and differences of opinion the leadership team hadn't heard.

A person on the HaloVision team reviews every report before it goes out.

An example

Two functions, two different plans

Illustrative

Head of sales says…

“The plan should put new customers first. That is where growth comes from.”

Head of operations says…

“We cannot take on new customers until we fix delivery for the ones we have.”

What Halo surfaces

Where the priorities conflict, which assumption each leader is working from, and what to decide before the plan is set.

Who takes part and how it runs

The CEO, each of the three to five leaders who own plan priorities, and one or two senior team members who see the work up close.

About 30 minutes with each person, no prep, survey or software rollout, and the report lands within 48 hours of the last conversation.

Where Halo fits

Best when

  • A quarterly or annual planning cycle is coming and the plan needs leadership buy-in to hold.
  • Last cycle's plan was agreed and then drifted.
  • Priorities across functions seem to conflict, and you want to see why before the meeting.

Not the right fit when

  • You need market, financial or data analysis for the plan. Halo is not a data audit.
  • You want input from every employee. A first round starts with leaders and a few senior team members.
  • A small, tight-knit team is just trying Halo out, with no business priority behind it.

FAQ

Questions leaders ask

What's the best way to gather input from my leadership team before annual planning?
Gather it privately, before the planning meeting, and ask for more than a list. Ask each leader what their top priorities are, what they are assuming about resources and timing, what worries them, and where they expect conflict with other functions. Compare the answers, then use the planning meeting to settle the conflicts instead of discovering them. Halo, HaloVision's AI, does this through confidential one-on-ones and shows the CEO, within 48 hours of the last conversation, where inputs line up and where they conflict.
Why do plans get agreed and then ignored?
Often because leaders agreed with the wording and read it differently, or kept quiet about a concern. The plan then gets reinterpreted by each function. Gathering real inputs privately first shows where the interpretations differ while there is still time to settle them.
Is this worth it for quarterly planning?
Yes, when there is a business priority behind it. A round is about 30 minutes per person, and Halo is built to run again each cycle, with the same leaders plus whoever is new. Platforms usually also run it after each acquisition.
What stays confidential?
Every conversation is confidential. The report shares only what does not disclose sensitive information, and it stays at the level of the system. The CEO receives the report, can keep asking Halo questions about it, and decides what to share with the leadership team.

Related situations

See what Halo would find on your team

Talk to Halo now, in your browser, or book time with the HaloVision team. The report lands within 48 hours of your last leader's conversation.