How I give the right amount of context (in any situation)
How I give the right amount of context (in any situation)Most people suck at managing up. They waste their manager's time with too much (or too little) information. Here’s how to give the right amount of context.
👋 Hey, it’s Wes. Welcome to my weekly newsletter on managing up, career growth, and standing out as a high-performing leader. ⛑️ Work with me 1:1 for executive coaching. If you’re interested in how I can support you or your team, hit reply or fill out this form. Today, we’re going to cover how to give the right amount of context:
I originally published a version of this essay in October 2019. Since then, I’ve expanded the post. If you find it helpful, please share with friends. Enjoy. Read time: 8 minutes Giving the right amount of context helps teams move faster. Too much context? Your manager can’t tell what’s important. They’ll need to wade through details, trying to sort information into a pile of what’s important vs what to ignore. Too little context? Your manager has to follow up and pull information out of you that you should have mentioned proactively. There is such a thing as being too concise. When you share the wrong level of context, you waste time on:
High-performing operators are exceptional at communicating and managing up. This is even more important in remote environments. This begs the question: How do you give the right amount of context? 1. Remind them where you left off.Task switching takes a tremendous amount of energy. Your manager is probably reading your note in between meetings (or during one!). Assume they’re reading with partial attention. Remind them where you left off so they can task switch faster.
You can top it off by saying, “Let me know if you have any other feedback. I’ll proceed unless I hear otherwise.” This makes it super easy for your manager to quickly say, “Looks great, thanks.” 2. Be specific about what you need.Years ago, I had a paid ad agency vendor say this in Slack:
What’s wrong with this statement? When I read this, I don’t know if:
Don’t assume your manager knows what you need from them. Be specific about what you need and what the next step is. Otherwise, they’ll assume you’re making progress–and will be surprised to find out you’ve been stalled for weeks.
3. Mention if it’s an FYI.Folks think they’re being helpful by forwarding a random email. But without context or next steps, these messages are useless. Don’t make people guess if they need to take action. If your recipient has to follow up to ask why you sent this, you’ve already slowed everyone down.
4. Avoid being too detailed in the wrong ways, but not detailed enough in the right ways.Details aren’t the problem. The problem is too many of the wrong details. This is mostly about the content of your argument, not the structure, so it’s hard to discuss without real examples that would be meaningless after redacting. Let’s say a customer asked why they got fewer students from the second cohort of their course. You could say this:
Notice how too many of the wrong details distract from the main point:
How do you tell what details to include? In this example, your recipient doesn’t need to know the exact dates of when the course was announced and when applications ended—they need to know the rough amount of time they were accepting students. Consider what the person needs to know vs what’s secondary. Every detail adds cognitive load for your audience because they need to discern what’s important. Now that you have this vocabulary about “too detailed in the wrong ways, not detailed enough in the right ways,” watch out for it in your own writing and help point it out in your peers’ writing. 5. Consider these variables to give more or fewer details.Giving the right amount of context is hard because what matters to you isn’t necessarily what matters to your audience. So when in doubt, put yourself in your recipient’s shoes. If the decision involves spending money or is customer-facing, err on the side of giving a bit more context. Customer or public-facing material affects your brand, and could lead to much bigger snafus, so it’s a higher stakes decision. What’s the magnitude and longevity of the impact if things go wrong? Do we lose a few hundred dollars—or are we signing a 5-year legally-binding contract? You can share LESS context when…
Aim for MORE context when the decision is…
6. Mention your criteria and assumptions.Most managers want to know that you did your due diligence and that you’re thinking ahead. Let’s say you need to recommend a new platform or tool. It’s not that helpful to simply send your manager a list of software tools. If you do that, they have to do the hard part of comparing the options, analyzing, and deciding what to do. When you show your thought process, your manager can point out gaps in your logic–or share information you’d find relevant.
The above format is extensible, meaning you can use this structure to explain your idea in 3 minutes or 30 minutes. 7. Aim for the minimum viable backstory.Tell me if you’ve told a story like this:
We’ve all been guilty of speaking like this with friends, but at work, this can make you look scatterbrained. Backstory scope creep is real. You start with the intent of sharing only the basics, but before you know it, you’ve gone down multiple tangents—and you’re embarrassed to admit you forgot the original question! It’s hard to be concise when you’re trying to process information, decide what to share, and speak the words—all in real time. By the time you realize you’ve shared too much context, you’re already in rambling territory. The solution: Don’t try to do multiple cognitive steps at the same time. Take a few beat to gather your thoughts, and when possible, prepare a few high level notes for yourself. More here: Start right before you get eaten by the bear. 8. Main point at the top, context below.This is one of my favorite ways to structure messages because it gives your reader agency. You let your recipient read as much or as little of the context as they need. The key is to visually put the context separately. This creates an obvious demarcation between the main point vs the supporting context. Personally, I love this structure because your final recommendation and supporting rationale are often equally important. Sharing your logic gives you more ammo to convince your reader.
9. Give a concise answer, then offer to elaborate.Offering to elaborate lets your manager chime in and tell you what kind of context they want. The key is to provide a brief list of options:
You are the expert here, so you should try to drive the conversation, including what questions you think they should be asking.
10. Ask yourself what your manager will ask you.What questions does your manager usually ask? Answer those questions yourself. If you take anything away from this article, make it this. Every manager has their own idiosyncrasies, worldview, values, etc. That’s why the best thing to do is to pattern match. Consider what they’ve asked you in the past, when talking to you or others. Try to give context through that lens. Ask yourself:
It's your job to do the heavy lifting. By providing the right amount of context, you’ll take the mental load off your manager and you’ll shine as a high performer. Win-win. Which of the items in this list do you already do? Which do you want to do more of? One of my favorite parts of writing this newsletter is hearing from you. If you’ve applied what I write about and would like to share a story/example, hit reply or share in the comments. I’d love to hear about it. Thanks for being here, and I’ll see you next Wednesday at 8am ET. Wes PS If you found this valuable, here are other ways I can help:
|
Older messages
No more awkward performance reviews: How to be honest without making your direct report rage quit
Monday, June 3, 2024
Your direct report thinks they are exceeding expectations. You think they're underperforming. Here's how to navigate the disconnect. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Emotional signposting: Why you should tell people how to feel
Wednesday, May 22, 2024
“Wait, is this good news or bad news?” When you don't give enough context, your audience can't always tell. To reduce cognitive load, remember to account for the emotional subtext. ͏ ͏ ͏ ͏ ͏ ͏
Delegating gets easier when you get better at explaining your ideas
Friday, May 17, 2024
Many managers suck at explaining things, then complain that other people don't understand. Here's how to explain a project when you delegate. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Why I have a love/hate relationship with scripts
Wednesday, May 8, 2024
Your script should serve you, not the other way around. Remember to stay present and use your judgment. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
How to be analytical—even if you’re "not a numbers person"
Wednesday, May 1, 2024
Analytical skills didn't come easily for me. Luckily, I found my way through. Here are 12 concepts to sharpen your analytical thinking. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
You Might Also Like
Broken engine?
Saturday, September 7, 2024
Hey friends, I'm back from my two-week trip to the US. I've been meaning to write you an update about my experiences in the podcast industry, hanging out with my co-founder in Chicago, and
Hunch
Saturday, September 7, 2024
A note app for product people to help with the discovery process BetaList BetaList Daily Hunch A note app for product people to help with the discovery process Too much email in your life? Switch to
💄 Building a million-dollar beauty brand
Saturday, September 7, 2024
Alicia Scott's inspiring story Hey Friend , Does it ever feel like your entrepreneurial dreams are just out of reach? Maybe you feel like the problem you're solving is too niche. Or the market
3+ Years of daily posting on X: Top Lessons
Saturday, September 7, 2024
+ DNA School Invite
What’s 🔥 in Enterprise IT/VC #410
Saturday, September 7, 2024
Speed mode + also, is the great unbundling of SaaS powered by agentic workflows? ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
🗞 What's New: Launch tips from Product Hunt's Head of Growth
Saturday, September 7, 2024
Also: Increasing your luck as a founder!
🚀 BlackSky To Reverse Split
Saturday, September 7, 2024
Plus Lynk Global delists from the Nasdaq, $ASTS mixed shelf offering, $PL and $SATX earnings, and more! The latest space investing news and updates. View this email in your browser The Space Scoop Week
my crazy idea…
Friday, September 6, 2024
Read time: 1 min. 18 sec. Today I want to tell you about something I've been working on. And to be honest… it might be the best thing I've ever built. Warning: Do not read this unless you'
Issue #125: Building $1K-$10K MRR Micro SaaS Products around Client Onboarding, AI Agent for online shopping, AI-b…
Friday, September 6, 2024
Build Profitable SaaS products!! ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
How to write a blog post (according to the Buffer Content team)
Friday, September 6, 2024
Plus tips, news & Buffer updates for your social media journey ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏