Leadership is not reserved for people with a particular title, and a leadership coach can help you develop it. It is a practical workplace skill: helping people move toward a useful outcome, making sound decisions with incomplete information, and building the [leadership qualities like trust, judgment, and accountability](/career/leadership-qualities-for-new-managers-build-trust) others can count on. It develops through ordinary moments—meetings, handoffs, trade-offs, difficult conversations, and the commitments you keep.

1. Choose a Leadership Situation to Practice First

“Become a better leader” is too broad to practice effectively. Begin with a recurring situation in which your actions influence other people’s work. The aim is to make progress visible: you should be able to identify what you did differently and whether it changed the result.

  1. Look for a repeated point of friction.

    Choose something that occurs often enough to give you several opportunities to practice. It could involve gaining cooperation, making a decision, or maintaining confidence when plans change.

    Common starting points include:

    • Running a weekly project meeting that ends without clear owners.
    • Coordinating a handoff between two teams with different priorities.
    • Recommending a change that peers may see as extra work.
    • Explaining why a deadline, scope, or priority needs to change.
    • Raising a project risk before it becomes an emergency.

  2. Choose something within your current responsibilities.

    Formal authority is not required. A contributor can improve a meeting, clarify a decision, organize work across a group, or bring an overlooked risk to the surface.

    For example, a project contributor may need design, engineering, and customer support to agree on a revised release date. They cannot order anyone to cooperate. They can, however, bring the relevant information, understand each group’s concerns, and suggest a workable next step.

  3. Define the behavior, not the personality.

    Goals such as “be more confident” or “be more persuasive” are hard to measure. After one awkward conversation, they are also easy to judge harshly.

    Name an action that someone could observe instead:

    • “Before asking for agreement, I will ask each affected person what the change means for their workload.”
    • “At the end of each meeting, I will confirm the decision, owner, and due date.”
    • “When I recommend a course of action, I will state the main risk and how we can manage it.”
    • “If I cannot meet a commitment, I will flag it early and propose a revised plan.”

  4. Decide what a better outcome would look like.

    Keep the outcome realistic. Leadership does not mean everyone agrees immediately or every plan works perfectly. It means people understand the situation, know what happens next, and can see that you are handling the work responsibly.

    A useful outcome might be fewer last-minute surprises, clearer handoffs, faster decisions, or more constructive disagreement.

Short Practice Exercise

Write one sentence that completes this prompt:

Over the next two weeks, I will practice leadership by __ in situations where __. I will know it is improving when __.

For example:

Over the next two weeks, I will practice leadership by confirming decisions and owners at the end of project meetings. I will know it is improving when fewer follow-up messages ask who is doing what.

Real story

I once walked into a meeting determined to “lead” by speaking first, so I printed a neat agenda and handed it out like I was running a city council session. Ten minutes later, I realized I had built an entire plan around a deadline that was actually next month, not next week. I spent the rest of the meeting pretending to “facilitate” while quietly dying inside and sliding my agenda back into my folder like evidence. The only thing I influenced that day was how carefully everyone checked my dates after that.

Have a story of your own? Share it in the comments below.

2. Build Influence by Making It Easier for Others to Act

Workplace influence is not about winning an argument or finding a clever way to pressure people. It comes from understanding what others need, explaining the case clearly, and removing practical obstacles to action.

People are more likely to support a proposal when they can see how it relates to shared work, what it asks of them, and how their concerns have been taken into account.

Start With the People Affected

Before making a request or recommendation, map the situation. You do not need a complicated stakeholder diagram worthy of a consulting slide deck. A few candid notes will do.

Ask these questions:

  • Who will be affected by this decision or change?
  • What does each person or team need to protect: time, quality, customer commitments, budget, workload, or reputation?
  • What concerns are likely to come up?
  • What information do they need before they can act?
  • What decision or contribution are you actually asking for?

This preparation changes the conversation. Rather than saying, “We need everyone to use the new process,” you can say, “The current handoff creates duplicate work for both teams. This version adds one required field, but it removes the back-and-forth that happens after requests arrive.”

Make the Request Concrete

A vague proposal tends to produce vague responses. Explain the objective, the practical effect, and the next action you need from others.

A useful structure is:

  1. State the shared goal.
  2. Describe the problem or constraint.
  3. Recommend a specific action.
  4. Explain the likely impact.
  5. Ask for a clear decision, contribution, or concern.

For example:

We need to protect the customer launch date while giving the testing team enough time to review the changes. I recommend moving the internal deadline by three days and reducing the first release to the highest-priority items. This gives testing a stable build and keeps the most important customer commitments. Can each team confirm by tomorrow whether that plan creates a critical conflict?

The request is specific, but it still leaves room for useful information. Influence is not a monologue with better formatting.

Listen for the Real Objection

When someone resists, do not assume they dislike the idea or are being difficult. They may have identified a risk you missed, lack the capacity to help, or be unsure what is expected.

Try questions such as:

  • “What would make this difficult for your team?”
  • “Which part of the proposal concerns you most?”
  • “What information would help you decide?”
  • “Is there a smaller version we could test first?”
  • “What would need to be true for this to work?”

You may have to change the approach. That is not a failure of influence; it is often how better decisions are reached.

Workplace Example: Revising a Project Deadline

A cross-functional project is behind schedule. Instead of announcing a new date, the project contributor meets briefly with the affected teams.

They learn that engineering needs a clear list of what can move, customer support needs advance notice for customer communication, and marketing needs confirmation before changing campaign materials. The contributor proposes a revised timeline, identifies the work that will be deferred, and assigns owners for each update.

The new deadline may still disappoint someone. But people can act because the plan is specific, the trade-offs are visible, and the work has not been quietly dropped into someone else’s lap.

Short Practice Exercise

Before your next request for support, write down:

  • The outcome you need.
  • The people affected.
  • One likely concern from each person or group.
  • The exact action you want them to take.
  • How you will follow up.

Then notice what changes when you enter the conversation ready to understand, not merely persuade.

3. Strengthen Judgment Through Structured Workplace Decisions

Good judgment is not the same as always being right. Work often involves incomplete information, competing priorities, and outcomes no one can fully control. Sound judgment means following a clear process, seeking relevant input, and making the best call possible with the information available.

  1. Clarify the decision before discussing solutions.

    State what must be decided and why it matters. This keeps the conversation from becoming a general exchange of opinions.

    For example, frame the decision clearly: “By Friday, we need to decide whether to fix this issue within the current project or escalate it because it could affect the launch date.”

  2. Separate facts from assumptions and preferences.

    These categories are easy to mix together, particularly when deadlines are close.

    Sort the information into four groups:

    • Facts: What is known and verifiable.
    • Assumptions: What seems likely but has not been confirmed.
    • Constraints: Limits involving time, budget, staffing, policy, or technical capacity.
    • Preferences: What different people would ideally like to happen.

    This can expose a preference being treated as a requirement or an assumption being treated as a fact.

  3. Consider the decision’s scope and reversibility.

    Some decisions are easy to change. Others create lasting costs, commitments, or customer effects. The harder a decision is to reverse, the more carefully it should be considered.

    Ask:

    • What happens if we wait?
    • What happens if we act now?
    • Can we test a smaller version first?
    • Who bears the risk if this goes wrong?
    • What signals would tell us to change course?

  4. Seek targeted input, not endless consensus.

    Ask people with direct knowledge of the problem, especially those closest to the work or most likely to experience the consequences. Be precise about the question you need answered.

    “What do you think?” may lead to a broad discussion. “If we choose option A, what customer or technical risk are we missing?” is more likely to produce useful input.

    Gathering input does not mean giving away ownership. If the decision is yours to make, explain how you weighed what you heard and state the next step.

  5. Record the reasoning and review the result.

    Keep a short decision log for choices that matter. Include the decision, the information available, the main trade-off, the expected outcome, and the date you will review it.

    Later, consider whether the process was sound. A reasonable decision can still produce an unfavorable outcome when circumstances change. A lucky result does not prove the process was good, either. Luck is a poor manager, though it occasionally gets credit in meetings.

Workplace Example: Escalate or Solve Locally?

A team finds a problem that may delay a deliverable. One option is to fix it quietly within the team; the other is to raise it immediately with a broader group.

The team lists the facts: the issue affects a key feature, the local fix would take several days, and the deadline is close. The assumption is that no other team depends on the affected component. Before deciding, they ask the relevant technical owner whether that assumption is correct.

They learn that another workstream is affected. Escalating early creates an uncomfortable conversation, but it gives the wider group time to adjust. The decision was not “avoid bad news.” It was “protect the project by making the risk visible while choices still exist.”

Reflection Prompts

After an important decision, ask yourself:

  • What information did I have, and what did I assume?
  • Whose perspective did I seek out? Whose did I miss?
  • Did I make the trade-off clear to the people affected?
  • What early signal should I watch next time?
  • Was the outcome poor because of the decision process, changing conditions, or both?

4. Earn Trust Through Consistency, Candor, and Follow-Through

Trust is built through repeated evidence. People notice whether you meet commitments, communicate changes early, give credit fairly, and address problems without making someone else the convenient villain.

Perfection is not required. In fact, pretending everything is fine when it is not usually damages trust faster than a candid update.

Set Expectations You Can Meet

Do not agree too quickly simply to be helpful. Before committing, check what the work requires and what other obligations are already in place.

When you make a commitment, be clear about:

  • What you will deliver.
  • When you will deliver it.
  • What dependencies or risks could affect the timeline.
  • What you need from others.
  • When you will provide an update.

This gives others something concrete to plan around. “I’ll try to get to it soon” is not a commitment; it is a weather forecast with no location.

Communicate Changes Before They Become Surprises

If you are likely to miss a deadline or cannot complete the work as planned, raise the issue early. Explain what happened without turning the update into a defense of your character.

A straightforward update might sound like this:

I will not be able to complete the full analysis by Thursday because the data review is taking longer than expected. I can deliver the key findings Thursday and the full report Monday. If Thursday’s meeting requires the full report, I need help validating the remaining data today.

The message identifies the problem, provides a revised plan, and makes the needed support clear.

Handle Mistakes and Conflict Directly

Trust weakens when people hide errors, shift blame, or raise concerns indirectly. Address the work and its impact without assuming someone’s intent.

Workplace Example: Rebuilding Confidence After a Missed Deliverable

An employee misses a deadline for a report that another team needed for planning. Rather than waiting to be asked, they contact the affected colleague, acknowledge the missed commitment, explain the current status, and give a revised delivery time they can meet.

They also identify what caused the miss: an unclear data dependency discovered too late. For the next reporting cycle, they schedule the data review earlier and flag the dependency at the start.

Trust is repaired through the full response: ownership, a realistic recovery plan, and a change that reduces the chance of repetition.

Workplace Example: Addressing a Missed Handoff

A colleague repeatedly sends work without the information the next team needs to proceed. A frustrated response might be, “You never provide complete requests.”

A more useful approach is:

The last two requests arrived without the customer details and approval notes, so the team had to pause and follow up. Could we agree on a short intake checklist before requests are handed over? That would help us start the work without delay.

This describes the pattern and its effect while leaving room to solve the problem together.

Practice Exercise: Make One Promise Smaller and Clearer

This week, choose one commitment that feels vague. Rewrite it with a deliverable, date, dependency, and update point.

For example, replace “I’ll look into the issue” with:

I will review the recent support tickets, identify the three most common causes, and send a summary by Wednesday afternoon. If I need product data to confirm the findings, I will ask by Monday.

5. Turn Feedback and Reflection Into a Continuing Leadership Practice

Leadership improves through a cycle: act, observe, ask, adjust, and try again. Feedback becomes more useful when it focuses on a specific situation, an observable behavior, and the effect it had, rather than a broad judgment about whether you are “good at leadership.”

Ask for Feedback People Can Answer

After a meeting, decision, or cross-team effort, ask one or two people a focused question.

Try prompts such as:

  • “Was the decision clear by the end of the meeting?”
  • “Did you understand what I needed from your team?”
  • “What part of my update made the work easier or harder to act on?”
  • “When I raised that concern, did it feel early enough?”
  • “What could I do differently next time to make collaboration smoother?”

Give people room to be candid. If you ask for feedback and argue with the answer, you may receive less of it in the future.

Compare Intent With Impact

You may intend to be efficient, while others experience you as rushed. You may intend to be transparent, but your message can create uncertainty if it does not include a clear next step.

After important interactions, write down:

  • What I intended to accomplish.
  • What I said or did.
  • How people responded.
  • What outcome followed.
  • What I will repeat, change, or stop next time.

This takes only a few minutes. Over time, it helps reveal patterns that are difficult to see in the moment.

Use a Simple Development Cycle

Choose one behavior to practice for two or three weeks. Keep the experiment small enough to repeat often.

A practical cycle:

  1. Pick one situation and one behavior.
  2. Define what evidence of improvement would look like.
  3. Practice the behavior several times.
  4. Ask for targeted feedback.
  5. Review the results and adjust.
  6. Take on a slightly more complex version of the same challenge.

For instance, you might start by clarifying owners in a small team meeting. Later, you could apply the same skill to coordinating a larger project with several teams and competing deadlines.

Reflection Prompts for the End of Each Week

  • Where did I help people move from discussion to action?
  • Which decision did I make with a clear process rather than instinct alone?
  • Did I communicate a problem early enough for others to respond?
  • What commitment did I keep, revise responsibly, or fail to manage well?
  • What is one behavior I will test next week?

Leadership becomes credible when it appears in the work people share with you. Start with one recurring situation, practice a visible behavior, and learn from the result. With time, influence, judgment, and trust stop feeling like abstract career goals and become part of how you work every day.