Leadership influence techniques from the ground up

A technique is worth having only if it attaches to a recurring moment. "Be more open to dissent" is a wish. "Ask the most junior person in the room for their objection before anyone senior speaks" is something you can do at eleven on Tuesday.

Everything below is written at that level and sorted by when it happens. Leaders who change their effect on a team change what they do at particular, repeated moments.

What to take away

At every decision

State what would change your mind. When you announce a decision, add one sentence: "If X turns out to be true, I would reverse this." It tells people what to watch for, gives them permission to bring it, and means a later reversal is a planned response rather than an embarrassment.

Say which kind of decision it is. Before the discussion: "This is mine, and I want your input", or "This is yours, and I will back it", or "We are deciding this together and I go last." Most damage from consultation comes from people not knowing which of the three they are in.

Give the reason to everyone, not to the objectors. The reasoning behind a decision usually gets explained privately to whoever pushed back. Put it in the announcement instead. People who never hear reasons cannot apply the decision to the cases you did not anticipate, and they learn that objecting is how you get told things.

At every meeting

Collect the objections in writing before the room. Send the proposal a day ahead and ask each person for their strongest objection in two lines. Read them before the meeting. You will hear things in writing that will never be said in front of you, and you can raise them yourself in the room without attributing them.

Ask one named person one specific question. "Does anyone have concerns?" produces silence in most rooms. "What is the part of this you think is most likely to fail?" put to one person produces an answer. Rotate who you ask.

Speak last on anything you have a view about. If you speak first, everything after is a response to you. If you must speak first, ask a question instead of stating a view, and mean the question.

Assume it failed. Before closing on a plan, ask the room to imagine it is six months on and the plan has failed, and to say why. The method has a name, the pre-mortem, and it works because it licenses a doubt rather than requiring a challenge. This is not a mood exercise. It changes the question from "do you agree" to "what do you know", and people know more than they will volunteer as disagreement.

At every handover

Hand over the boundary, not the task. "You decide. Come back to me if it costs more than this, slips past that date, or touches a customer." Three edges, stated once, replace a review stage and make it clear how far their judgment runs. That is what delegation means in practice: authority moved, with its limits named.

Hand over the context that made it hard. A decision passed down without the reasons it was difficult will be made badly, and the failure will look like evidence the person was not ready. Say what you would be weighing.

Do not take it back silently. If you reverse something you delegated, say so, say why, and accept that you have spent something. A quiet reversal teaches everyone that the handover was theater.

Every week

Ask what went badly. Not "how is it going", which invites a summary. "What went wrong this week that I have not heard about?" asked in the same words every week becomes a slot into which bad news can be placed without anyone having to decide to raise it.

Thank the early warning before acting on it. The first thing you do when someone brings you an unresolved problem is what teaches everyone whether to bring the next one. Thank them. Ask what they need. Do not take the problem away from them.

Check what you set in motion. "Did anyone start doing anything because of something I said this week?" You will be surprised at least once a month. Each surprise is a workstream you did not intend, created by a remark you did not label.

Every quarter

Audit what you asked about. Go through a quarter of meeting notes and list the questions you actually asked, then compare the list to what you would say your priorities are. Where the lists differ, the questions won, because what you ask about is what gets optimized.

Count the disagreements. How many times in the last quarter did someone tell you that you were wrong, to your face, about something that mattered? If the answer is close to zero, you are not getting agreement. You are getting silence in the shape of agreement.

List the exceptions. Every exception you made, and whether you labeled it as one at the time. Unlabeled exceptions have become rules by now, and you are the last to know.

The techniques by moment

Choosing two

The temptation is to adopt the whole table. Do not. Pick the moment where you are weakest, which you can usually identify by which row made you wince, and take the two techniques from that row. Run them for a month, in the same words each time, until people begin to expect them. Then add one more.

The reason for the same words each time is that the technique works partly by becoming a known slot. "What went badly this week" asked in the same form on the same day is a place people can put things. Asked differently each time, it is just a question.

The mechanics these techniques act on are filtering information upward and amplifying everything you say, set out in leadership influence. Saying a reason so it survives repetition is covered in executive communication.

Handover techniques are the practical side of control and influence. The disclosure test every technique here passes, and the ones that would not, is in positive influence.

Common questions

These feel artificial.

They are, for about a month. Then they are how you run meetings, and nobody remembers otherwise. The artificiality is the cost of replacing a habit with a better one, and it is paid once.

My team is small and informal. Do I need this?

Small teams filter less, which helps, and they read you more closely, which does not. The amplification techniques matter more in a small team, because there is nobody between you and the person who took your remark as an instruction.

What if I ask what went badly and nobody says anything?

Keep asking, in the same words, every week. The first real answer usually arrives after four or five empty weeks, once people have seen that the slot exists and that nothing bad happened to the person who used it.

Which single one matters most?

Thank the early warning before acting on it. Everything else on the page depends on information reaching you, and that technique is what decides whether it does.