Strategic Questions to Ask Your Team
For a manager or founder running a planning session, an offsite, or a quarterly review. Twenty questions about what the team is really trying to win, what should be dropped, where the plan breaks, and what nobody has said out loud yet.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
If someone outside the company asked what this team is for, what would you say?
The useful data is the spread, not the wording. If six people give six different one-sentence answers, that is your real finding. If everyone recites the same deck line, ask them to say it again without using any word from the deck.
- 2
What are we trying to be genuinely better at than anyone else?
A team that names three things has named none. Follow up with the harder half: what are we content to be mediocre at? People who cannot answer that are describing ambitions rather than a strategy.
- 3
Who is our work actually for, and how confident are we in that?
Teams drift toward serving whoever complains loudest, not whoever matters most. An answer that names a real customer or a real internal team is worth more than one that names a segment or a persona.
- 4
What did we say we would do this year that we have quietly stopped doing?
Abandoned work is rarely cancelled out loud. It just stops appearing in updates while everyone still budgets time for it. Naming it returns capacity you did not know you had and kills a running source of guilt.
- 5
What is on our plan only because it was on last year's plan?
Roadmaps inherit items the way houses inherit furniture. Ask who would notice if a given item vanished. If the honest answer is nobody, you have found free time, and usually some relief in the room.
- 6
If we had to cut a third of what we are doing, what goes first?
Forced ranking gets past the polite agreement that everything matters. Watch the emotional split: the items people argue hardest to keep, and the items they look visibly relieved to drop, are both telling you something.
- 7
What would we do differently if the budget doubled? What if it halved?
The halving answer is the real strategy; the doubling answer is a wish list. If halving only produces the same things done slower, the team has never actually prioritized, it has only sequenced.
- 8
What is the one number we should be watching, and are we watching it?
Most teams have a dashboard nobody acts on. Test it by asking which decision would change if that number moved twenty percent. If no decision changes, it is a report, not a metric.
- 9
Where are we winning without being able to explain why?
Unexplained success is the most fragile kind, because it usually rests on one channel, one relationship, or one person. Finding the cause is how you protect it before it disappears without warning.
- 10
Which of our assumptions would be most expensive to be wrong about?
This moves the conversation from risks in general to the one or two beliefs the whole plan sits on. The follow-up that matters: what would it cost to test that belief cheaply in the next month?
- 11
What do our competitors do better than us, and does it actually matter to anyone?
Two failure modes hide here. One is refusing to name anything. The other is chasing every gap. The second half of the question separates a real disadvantage from a feature comparison nobody outside the building reads.
- 12
If a new team started today with everything we know, what would they not build?
This is the cleanest way to surface sunk cost without accusing anyone. People will name things here that they would defend if you asked directly whether we should kill them.
- 13
If we changed nothing for a year, what would actually happen?
It establishes the baseline that every proposal should beat. If the honest answer is that we would be roughly fine, then the urgency in the plan is manufactured, and it is worth finding out who it is for.
- 14
What is the real bottleneck right now: people, money, decisions, or attention?
Headcount is the reflex answer. Push past it. If the constraint is decisions or attention, hiring makes the problem worse, and the fix is something a manager can do this week rather than next quarter.
- 15
Which decision are we avoiding because nobody wants to own it?
Every team has one, and the cost of leaving it open is paid quietly in rework and hedging. You do not need to resolve it in the room. You need it named, with one person's name attached and a date.
- 16
What are we assuming another team will do for us?
Cross-team dependencies are usually documented on only one side. Ask whether the other team has agreed in writing, and when they were last asked. Most plans break here rather than at the technical steps.
- 17
What would have to be true for this plan to work?
It converts opinions into claims you can check. Write the list down, because in three months it becomes the most useful page from the session: you can go through it and mark which ones held.
- 18
How would we know in three months that this is not working?
Agreeing on failure signals in advance is the only reliable defense against explaining bad results away later. Insist on a signal that could realistically appear, not one so extreme it never triggers.
- 19
If this fails, what will we say in the post-mortem?
People will say things in the imaginary past tense that they will not say in the present. Whatever comes out here is the objection they were not going to raise, and it is worth more than the rest of the session.
- 20
What do you think I am getting wrong?
Ask it last, ask it plainly, then stop talking. Expect silence the first few times you try it. If nobody ever answers it after several sessions, that is the finding, and it is about the room rather than the plan.
Running the conversation
Practical guidance for the conversation itself.
Setting it up
Setting it up
- 1Pick four or five questions, not twenty. A session that covers five questions properly beats one that touches all of them.
- 2Send the two hardest questions a few days ahead. The good answers to what we should cut, and to what you are getting wrong, are the ones people had time to talk themselves into.
- 3Separate the session about what is true from the session about what to do. Trying to settle both in two hours produces a compromise on both.
- 4Write the current plan on one page first, including the items nobody has looked at in months. Half the value here comes from people seeing the whole list at once.
- 5Decide in advance who makes the call if the room does not converge, and say so out loud at the start.
Getting past agreement
Getting past agreement
- Ask people to write their answer before anyone speaks. The first spoken answer anchors the room, and the most senior voice anchors hardest.
- Go around in reverse seniority. Junior people rarely contradict a director who has already answered.
- When someone gives a general answer, ask for the specific instance. Which customer, and which week, turns a comfortable statement into a checkable one.
- Let the silence run. Ten seconds of nothing after a hard question is normal, and filling it yourself is how leaders end up answering their own questions.
- Do not defend anything in the room. Write it down, say thank you, and respond next week with what you decided.
What happens afterwards
What happens afterwards
Publish the list of what you are not doing
The output people remember is the stop list, because it is the only part that gives them something back. If nothing was dropped, the session did not set strategy, it collected ideas.
Keep the assumptions where you can find them
The answers to what would have to be true, and to how we would know this is not working, are worth revisiting on a set date. Put that date in the calendar during the session, while the answers are still specific.
Close the loop on the uncomfortable answers
If someone told you what you were getting wrong and nothing visibly happened, you will not hear a second answer from that person or from anyone who watched. Report back on what you changed, and on what you decided not to change and why.