Running Work That Matters

Choosing What Actually Matters

As a manager working across teams, you sit in the middle of a constant stream of requests, updates, and competing goals. Every team believes their work is the m

Level
Manager
Setting
Cross-team
Core skill
Ruthless prioritisation
Common pitfall
Treating everything as urgent
Practice to try
A one-big-thing week

What this looks like in real work

As a manager working across teams, you sit in the middle of a constant stream of requests, updates, and competing goals. Every team believes their work is the most important, and every deadline feels like it needs to be met yesterday. In this environment, ruthless prioritisation means you deliberately choose which few things truly matter and let go of the rest. It is not about working harder or faster; it is about making clear, sometimes uncomfortable, choices about where you and your team will focus your limited time and attention.

In practice, this looks like saying no to a project that seems valuable but does not align with your top objectives. It means pushing back on a meeting that could be an email, or asking a stakeholder to wait until next quarter. It also means being transparent about what you are not doing, so others can plan accordingly. When you prioritise ruthlessly, you protect your team from constant context switching and give them the space to do deep, meaningful work. You also build trust by being consistent and predictable about what you will and will not take on.

This is especially challenging in a cross-team setting because you rarely have direct authority over everyone involved. You must influence, negotiate, and sometimes escalate. But the core of the work remains the same: decide what matters most, communicate that clearly, and stick to it even when pressure mounts.

Why it trips people up

The biggest trap in prioritisation is treating everything as urgent. When every request comes with a tight deadline or a loud voice behind it, it is easy to fall into firefighting mode. You start believing that if you just move fast enough, you can do it all. But urgency is often a feeling, not a fact. Many things that feel urgent are simply important to someone else, or they are poorly planned and now need rescuing. If you treat every urgent request as a top priority, you will constantly be pulled away from the work that actually moves the needle.

Another reason this trips people up is the fear of disappointing others. Saying no can feel like letting your colleagues down, or like you are not being a team player. In cross-team settings, relationships matter, and you may worry that pushing back will damage your reputation or make future collaboration harder. So you say yes to everything, hoping to keep everyone happy. But overcommitting leads to missed deadlines, lower quality work, and burnout. Ultimately, you disappoint more people than if you had been honest from the start.

Finally, many managers lack a clear framework for deciding what matters. Without explicit criteria, every request seems equally valid. You end up prioritising based on who asked last, who is loudest, or what feels easiest. This reactive approach leaves you and your team exhausted and unfulfilled, wondering why you are so busy but not making real progress.

The mistake that quietly hurts

The mistake that quietly hurts is saying yes to everything while secretly hoping you can fit it all in. You might tell yourself that you will figure out the details later, or that you can work extra hours to make it happen. But this approach erodes your credibility and your team's capacity over time. When you consistently overpromise and underdeliver, stakeholders stop trusting your commitments. They may start going around you or escalating every request, which further undermines your authority.

On a personal level, treating everything as urgent leads to chronic stress and shallow work. You never get to focus deeply on the complex problems that require sustained attention. Your days become a series of interruptions, and you end up feeling busy but ineffective. Your team notices this chaos and may start to mirror it, creating a culture where firefighting is the norm. The quiet harm is that you slowly lose control of your own agenda and become a victim of everyone else's priorities.

Perhaps the most damaging aspect is that you neglect the truly important work. The strategic initiative that could transform your team's impact gets pushed aside because you are too busy handling a dozen small crises. Over time, this can stall your career and your team's growth. The mistake is not malicious; it comes from a desire to be helpful and responsive. But without ruthless prioritisation, you end up serving everyone except the mission you are actually responsible for.

A practice you can repeat

A practice you can repeat is the one-big-thing week. At the start of each week, identify the single most important outcome you and your team need to achieve. This is your one big thing. It should be specific, measurable, and directly tied to your team's top goal. Write it down and share it with your team and key stakeholders. Then, for the rest of the week, treat this as your primary filter for every request and decision. If a task does not directly support the one big thing, it either gets delegated, deferred, or declined.

To make this work, you need to be realistic about what you can accomplish. The one big thing should not be so large that it is unachievable in a week, but it should be substantial enough to make a real difference. For example, it might be finalising a critical design document, resolving a blocking issue that has stalled another team, or completing a prototype that will inform a major decision. Once you have defined it, block time on your calendar to work on it, and encourage your team to do the same. Protect that time fiercely.

At the end of the week, review what you achieved. If you accomplished the one big thing, celebrate it. If not, ask why. Was the goal too ambitious? Did unexpected urgent matters derail you? Use those insights to refine next week's one big thing. Over time, this practice builds your prioritisation muscle and helps you and your team consistently deliver meaningful results. It also makes it easier to say no, because you have a clear, defensible reason: it does not align with this week's one big thing.

What to say and do

When you need to push back on a request, be clear, respectful, and firm. You can say, "I can see why this matters to you. Right now, my team is focused on our one big thing for the week. Can we revisit this next week, or is there someone else who could take it on?" This acknowledges the other person's need while protecting your priorities. Another phrase: "That sounds important. Let's look at what we would need to drop to make it happen. What would you suggest?" This invites collaboration and makes the trade-offs explicit.

If you are being pressured to treat something as urgent when it is not, try: "I understand the urgency from your side. Help me understand the impact if this waits until our next planning cycle. That will help me decide how to prioritise it against our current commitments." This shifts the conversation from emotion to evidence. You can also set expectations proactively: "I want to be upfront: we are at capacity this week. I can either do X or Y, but not both. Which would you prefer?" This forces a choice and prevents you from silently overcommitting.

In cross-team meetings, make prioritisation visible. Say, "Our team's top priority this quarter is Z. If we take on this new request, it will delay Z. Is that a trade-off you are comfortable with?" This puts the decision in the hands of the group and ensures everyone understands the consequences. Finally, follow through on your commitments. When you say no to something, offer an alternative if possible, such as a later date or a different resource. This shows you are not just blocking, but problem-solving.

When the stakes get higher

When the stakes get higher, prioritisation becomes even more critical. Perhaps your team is facing a major deadline, or a cross-team project has executive visibility. In these moments, the temptation to say yes to everything intensifies because the pressure is on. But this is exactly when you need to be most ruthless. High-stakes situations often come with more noise, more opinions, and more urgency. Without a clear framework, you risk spreading your team too thin and failing on all fronts.

Start by clarifying the single most important outcome for the high-stakes period. What does success look like? What is the one thing that, if achieved, would make everything else easier or irrelevant? Communicate this relentlessly to your team and stakeholders. Then, be prepared to make tough calls. You may need to pause lower-priority projects, renegotiate deadlines, or ask for additional resources. Do not be afraid to escalate if other teams are not respecting your priorities. Your job is to protect your team's focus, even when it is uncomfortable.

Also, remember that high stakes do not mean you should abandon your team's well-being. In fact, sustainable pace becomes more important, not less. Encourage breaks, set clear working hours, and model healthy boundaries yourself. If you burn out your team now, you will pay for it later. Finally, keep a close eye on what is truly urgent versus what merely feels urgent. In high-pressure environments, people often default to panic mode. Your calm, deliberate prioritisation can be a stabilizing force for everyone involved.

Questions new leaders ask

Q: How do I say no to my boss or a senior leader without damaging my career? A: Start by acknowledging their request and showing you understand its importance. Then explain your current commitments and the trade-offs. For example, "I want to make sure we deliver on the top priority you gave us. If I take this on, it will delay that. Would you like me to reprioritise?" This puts the decision back on them and demonstrates that you are thinking strategically, not just being difficult. Often, they will appreciate your honesty and may even help you say no to others.

Q: What if everything really is urgent and I cannot choose just one thing? A: It is rare that everything is equally urgent. Force yourself to rank items by impact and deadline. Ask: If I could only accomplish one thing this week, which would create the most value or prevent the most harm? That is your one big thing. For the rest, delegate, delay, or delete. If you truly cannot decide, escalate to your manager and ask for guidance. Remember, trying to do everything is a recipe for doing nothing well.

Q: How do I get my team on board with ruthless prioritisation? A: Involve them in the process. Explain why prioritisation matters and how it benefits them—less chaos, more meaningful work, better results. Use the one-big-thing week as a shared practice. Celebrate when you achieve it and discuss openly when you do not. When team members see that saying no to low-priority work leads to wins on high-priority work, they will become your strongest allies. Lead by example: let them see you decline requests that do not align with your top goals.