How to State Recommendations with Conviction
Taking a position is where judgment shows. Leaders are paid to recommend a path, not narrate the options, and conviction is the discipline of forming a view, stating it plainly, then holding or revising it on the argument rather than the pressure. This playbook moves you from tentative musing to clear recommendations, teaches you to hold them when challenged, and ends with building the same conviction in your team.
Developing
Start here. Build the foundation.- 1
When you have a view, say 'I recommend we consolidate the two teams,' not 'I think maybe we should possibly look at combining them.' Decide your recommendation before you open your mouth, then lead with it. The room can follow your reasoning from the recommendation backward, and you will notice people responding to the position instead of asking what you actually think.
- 2
When you give a read, cut 'I could be wrong, but' and 'this might be a dumb question.' Ground the view instead: 'Based on the information we have, pricing is the blocker.' Practice on small, low-stakes decisions first so the muscle is there when the decision is big. If you are genuinely unsure, name what would change your mind, which is precise rather than self-discounting.
Proficient
Build consistency and rhythm.- 3
When you raise an issue, bring a starting option. Say 'Margins are slipping, and I recommend we revisit the discount policy first,' not 'margins are slipping, what should we do?' The recommendation can be one you expect to be improved, but it has to exist. You will know it is working when problems you raise turn into decisions instead of open-ended discussions.
- 4
When someone pushes back, restate the recommendation and give the reason: 'I still recommend the phased rollout, because it limits exposure if the integration fails.' The judgment call is whether the pushback is a real new argument, which should move you, or just pressure, which should not. The test: when you change your mind, can you name the specific argument that changed it? If you can, you reasoned; if not, you caved.
Mastered
Operate at the highest level.- 5
When you lead a decision, ask 'what do you recommend?' and hold the silence until they answer. If you fill the pause with your own view, you teach people to wait for it. Over time the team learns to arrive with a position instead of a question, and you will see it when problems reach you already paired with a proposed path.
Common Pitfalls
Avoid the common failure modes.- Treating conviction as never changing your mind. The skill is holding for good reasons and yielding to better ones, not digging in. Stubbornness is not conviction.
- Mistaking visible deliberation for thoroughness. Thinking out loud can look like rigor, but it reads as not having decided. Show the reasoning in the recommendation, not in the live arrival at it.
- Recommending without reasoning. A position with no 'because' behind it is just an assertion, and it collapses at the first hard question. Pair the recommendation with the one reason that most supports it.