Managing people is only one part of leadership.

The other part happens above you.

Once you become a manager, it is easy to assume your responsibility begins with the people on your team and ends with your own work. But your manager still has expectations, priorities, pressures, and people they need to answer to. If you only focus downward, you leave a gap between what is happening on your team and what your manager understands about it.

That gap is where managing up becomes important.

Managing up is not about pleasing your boss, agreeing with everything they say, or making yourself look important. It is about understanding the world your manager operates in and making sure the information, context, decisions, and support they need can move in both directions.

Your team sees things your manager cannot see. Your manager sees things your team cannot see. Good managing up connects those two views.

And the simplest rule is this: think from your manager’s perspective.

Imagine you are responsible for a team working on several competing priorities.

You know that one project is delayed because another issue became more urgent. You know the team is already dealing with a technical problem. You know why a decision was postponed. You know what is being worked on behind the scenes.

Your manager may know none of that.

From their perspective, they might simply see a deadline approaching with no visible progress.

That does not necessarily mean your manager has misunderstood the situation. It may mean you have not given them enough information to understand it.

This is one of the most important parts of managing up: your intentions do not automatically become other people's perceptions.

You may believe you are being thoughtful, prioritizing correctly, protecting the team, or solving a difficult problem. But if nobody knows what you are doing or why, they have to interpret your behavior using the information available to them.

That interpretation may be completely different from your intention.

Consider a team that changes how product, design, and engineering collaborate. Bringing engineers into early discussions may make perfect sense because it prevents technically infeasible ideas from reaching implementation and creating expensive rework later.

But engineers might initially see it as more meetings and less time writing code.

The change may be sensible. The intention may be good. Yet the perception can still be negative.

That is why managing up is partly about making your reasoning visible.

You do not need to constantly explain yourself. But when your decisions affect other people, especially when those decisions could be misunderstood, providing context can prevent unnecessary friction.

Tip: When your decision could reasonably be misunderstood, explain the problem you are solving, not just the decision you made.

A useful way to understand managing up is to reverse the situation.

Imagine you are the manager.

You have someone reporting to you. What would make that person easy to trust?

Probably not constant agreement.

You would want someone who is capable, dependable, thoughtful, communicative, and willing to raise problems before they become emergencies. You would want someone who understands their responsibilities without requiring constant supervision. You would want someone who helps move work forward rather than simply describing everything that is wrong.

That perspective changes how managing up feels.

Instead of asking, “What does my manager want from me?”, ask:

“What would I need from someone in my position if I were responsible for their work?”

The answer usually starts with competence and reliability.

Be good at the job. Understand what your manager expects. Make sure your priorities are aligned with the work that actually matters.

This sounds obvious, but misalignment can happen surprisingly easily. A manager may think a particular problem deserves immediate attention while you spend most of your time on something else because you believe it is more important.

Neither side necessarily has bad intentions.

The problem is that the priorities were never aligned.

A short conversation about expectations can prevent weeks of work moving in different directions.

Tip: Make expectations explicit early instead of discovering a priority mismatch after the work is already done.

Being reliable does not simply mean completing assignments.

It means giving the other person confidence that they do not have to constantly check whether something is happening.

That confidence comes from consistent follow-through.

If something is assigned to you, take ownership of it. If it is progressing, provide an update. If the deadline changes, communicate it. If you need help, say so. If the work is finished, close the loop.

The key is to communicate before someone has to ask.

A manager should not have to send, “Any update?” every time they want to know what is happening.

A simple message can eliminate that uncertainty:

The work is progressing. This is what has been completed. This is what remains. This is the next step. There is one issue that may affect the timeline, and this is how it is being handled.

That kind of communication does something subtle but important.

It reduces the amount of mental tracking your manager has to do.

The work still belongs to you, but your manager no longer has to wonder whether it is under control.

Tip: Communicate progress before someone needs to chase you for it.

One of the easiest ways to damage trust is to allow a problem to become a surprise.

Problems happen in every team. A deadline slips. A dependency breaks. A project becomes more expensive than expected. A technical decision creates an unexpected consequence.

The problem itself may be manageable.

The surprise is often what makes it dangerous.

When a manager discovers a serious issue at the same time everyone else does, they suddenly have less time to react. They may need to make decisions without context, explain the situation to their own stakeholders, or change plans that could have been adjusted earlier.

That is why communicating problems early matters even when you believe you can fix them yourself.

You do not need to escalate every minor issue.

But when something could affect priorities, deadlines, people, customers, or commitments, visibility matters.

And there is an important difference between bringing a problem and bringing a problem with a plan.

Instead of saying:

“We have a problem.”

Try:

“This is what happened. This is the impact we see. This is what is being done about it. Here are the decisions or support needed.”

Now your manager has something useful to work with.

Tip: Never let a meaningful problem become a surprise when you could have given your manager time to respond.

There is another trap.

Some people become excellent at identifying everything that is wrong but never move beyond describing the problem.

That can be frustrating for a manager because awareness alone does not create progress.

If you see a problem, think about what should happen next.

Maybe there are two possible solutions. Maybe the team needs another person. Maybe a deadline needs to move. Maybe a decision needs to be made by someone else. Maybe the current approach should be abandoned.

Bring that thinking with you.

This does not mean pretending to have an answer when you do not. Sometimes the right move is to say, “Here is the issue, here are the options, and a decision is needed.”

That is much more useful than simply dropping the problem onto someone else's desk.

Managing up works best when you become a source of clarity rather than another source of noise.

Tip: When raising a problem, include your recommended next step or clearly identify the decision or help you need.

Leadership becomes messy when commitments disappear between meetings.

Someone agrees to do something. Another person takes ownership of something else. A deadline is mentioned. Everyone leaves the room. Two weeks later, nobody remembers exactly what was agreed upon.

This is where closing the loop becomes a powerful leadership habit.

At the beginning of the next meeting, briefly revisit the previous conversation.

What was discussed?

What was agreed?

Who owned each action?

What has been completed?

What remains outstanding?

This is not about policing people.

It is about creating shared memory.

When you consistently document and revisit commitments, you demonstrate that you take ownership seriously. At the same time, you make it easier for everyone else to do the same.

It also protects the team from a common organizational problem: decisions becoming vague because nobody remembers who was responsible for what.

A simple recap can turn an informal conversation into an accountable commitment.

And accountability should work in both directions.

If your manager said they would resolve something, provide an introduction, make a decision, or follow up with another stakeholder, it is reasonable to bring that commitment back into the conversation.

Managing up is not just about making yourself accountable to your manager.

It is also about helping the relationship function as a reliable system.

Tip: Start important follow-up meetings by briefly reviewing previous commitments, owners, progress, and outstanding actions.

The phrase “managing up” can sound strange because your manager is still your manager.

You are not trying to control them.

You are trying to make the relationship work better.

Your manager has information you need. You have information they need. They have organizational pressures you may not see. You have operational problems they may not see.

The strongest relationship is one where those gaps are reduced deliberately.

That means giving context when context matters. Raising risks early. Following through on commitments. Understanding expectations. Bringing solutions instead of only problems. Making progress visible. And making sure important decisions do not disappear into the space between meetings.

None of this requires self-promotion.

You do not need to constantly advertise everything you have accomplished. In fact, excessive self-promotion can make communication feel transactional.

The better approach is simply to make important work visible enough that the people responsible for supporting you can understand what is happening.

Because your manager will form an opinion about your judgment, reliability, and leadership whether you actively manage that perception or not.

You cannot completely control how people perceive you.

But you can give them better information from which to form that perception.

And that is the real value of managing up.

It creates a bridge between what you intended, what you actually did, and what your manager can reasonably understand about it.

For a busy leader, that bridge can make the difference between constantly having to explain yourself and simply being trusted to get the job done.

Tip: Make your manager's job easier by consistently providing the context, progress, risks, and decisions they need before they have to ask for them.

What’s your next spark? A new platform engineering skill? A bold pitch? A team ready to rise? Share your ideas or challenges at Tiny Big Spark. Let’s build your pyramid—together.

That’s it!

Keep innovating and stay inspired!

If you think your colleagues and friends would find this content valuable, we’d love it if you shared our newsletter with them!

As the world becomes increasingly digital, this question will be on the minds of millions of people seeking new income streams in 2026.

The answer is—Absolutely!

Thank you for taking the time to read today’s email! Your support allows me to send out this newsletter for free every day. 

 What do you think for today’s episode? Please provide your feedback in the poll below.

Share the newsletter with your friends and colleagues if you find it valuable.

Disclaimer: The "Tiny Big Spark" newsletter is for informational and educational purposes only, not a substitute for professional advice, including financial, legal, medical, or technical. We strive for accuracy but make no guarantees about the completeness or reliability of the information provided. Any reliance on this information is at your own risk. The views expressed are those of the authors and do not reflect any organization's official position. This newsletter may link to external sites we don't control; we do not endorse their content. We are not liable for any losses or damages from using this information.