I used to focus only on the optimization part. My first book was even called Hack the Mobile Lifestyle. In my 30s, that lifehacking cost me. I wrecked my health and put real tension on my marriage, not because I wasn't optimizing (I was optimizing constantly) but because I wasn't prioritizing at all. I talk about that decade in my TEDx, The Relentless Pursuit of More.

Optimization is saving ten minutes in a meeting. Prioritization is asking whether the meeting needed to happen at all. That difference shows up everywhere once you start looking for it. Here are some places I still see clients get tricked, and a few for me too.

Why It Matters

• Most productivity advice makes the wrong things faster instead of asking whether they should happen at all.
• The relentless prioritization filter works on almost anything you're already trying to optimize, from a calendar rule to a grocery app.
• The research behind "keep your meetings small" is more specific than most people realize, and it's not really about time.

What You'll Learn

• How to tell the difference between an inbox rule and an actual fix for inbox overload
• Why trimming a meeting's invite list changes the quality of the decision, not just the length of the meeting
• The difference between an auto-blocked calendar hold and a real Design Day
• What changed, concretely, when I moved from managing my social media to leaving almost all of it

The Filter

If you caught episode 127, you know the relentless prioritization filter. Three questions:

• Does this reduce or eliminate a bottleneck or conflict?
• Does this eliminate a decision?
• Does this protect capacity or energy?

You don't need the exact wording. Asking yourself even one of these before you reach for an optimization is usually enough to catch it.

Download the free graphic.

Inbox

Building an inbox rule that routes anything you're CC'd on into its own folder, checked once a day, is a good move. Build it.

But prioritize first. Train your team on how "to" and "cc" actually work, because most people never learned. If you're in the "to" line, you have an action. If you're in "cc," you need access, not action. It’s FYI.

The optimization is the folder rule. Prioritization is asking whether you're still being copied on things you don't need to see, and whether requiring people to loop you in on every client email quietly tells them you don't trust them to send it alone.

Meetings

Shortening a meeting is optimization, and it's fine up to a point. Prioritization means looking at the invite list and asking why six people are on it when two of them talk for a combined five minutes.

There's real research behind this. Bain & Company found that every person added past seven in a decision-making meeting drops decision effectiveness by about 10 percent. That's not a time problem. It's a decision-quality problem.

Focus Time

Letting Outlook or Google automatically block two hours a week for "focus time" is an optimization. Your calendar tool doesn't know your best hours. It just finds open space and drops a block there, and you end up scheduling right over it anyway.

Prioritization is a Design Day: one full day, one or two projects that keep getting pushed, no meetings, no calls, out of the inbox entirely. I covered this in full back in episode 69.

Sleep

I'm actively working on my sleep this quarter. Downloading an app that creates friction on my phone after 8 or 9 PM is an optimization (because most apps have bypasses). It doesn't address the real problem: scrolling fitness apps to plan tomorrow's workout, then picking a meditation to fall asleep to.

Prioritizing meant keeping my phone completely out of the bedroom. I haven't taken it inside for months. I also found a clock with zero ambient light. You touch it, it blinks on for a second, and that's it.

Relationships

Scrolling Facebook to "catch up" is optimization. It's efficient. You don't have to call anyone or have them over. Prioritizing is admitting that watching someone's updates isn't the same as connecting with them.

This connects to Dunbar's number, the idea that we can only sustain relationships at a handful of tiers: about 5 close loved ones, 15 good friends, 50 regular friends, 150 meaningful contacts, and around 500 acquaintances. My version took two steps. About 15 years ago, I optimized by trimming my Facebook friends list to 25 people. About 10 years ago, I prioritized by deleting Facebook and every social platform except LinkedIn, which I only use during business hours.

Shopping

Using grocery delivery apps is an optimization, and it's genuinely useful. What wasn't useful was the time I spent scrolling meal options across multiple apps. Prioritizing meant narrowing it down to a rotation, one app per week, and I'm cutting that down further to three.

The Close

Each of these comes down to the same catch: reaching for the faster version of something before asking whether it needs to exist in its current form at all. Optimize after you prioritize, never before.

FAQ

What's the difference between optimization and prioritization? Optimization makes something you're already doing faster or smoother. Prioritization asks whether you should be doing it at all. Saving ten minutes in a meeting is optimization. Asking whether the meeting needs to happen is prioritization.

What is the relentless prioritization filter? Three questions to run a decision through: Does this reduce or eliminate a bottleneck or conflict? Does this eliminate a decision? Does this protect capacity or energy? You don't need all three to apply. One is often enough to catch an optimization masquerading as a fix.

Where can I learn more about relentless prioritization? The Right Things First: A Pocket Guide to Relentless Prioritization covers the filter in more depth, along with additional examples like the ones in this episode.

Resources

• Episode 127: The Relentless Prioritization Filter
• Episode 69: Design Days for Deep Work
• Design Days blog post - www.helloraderco.com/design-days
• Bain & Company, "Effective decision making and the rule of 7"
• Forbes, "Why You Should Never Invite More Than 7 People To Your Meeting"
• Dunbar's number: BBC article link
• My TEDx, The Relentless Pursuit of More
• The Right Things First: A Pocket Guide to Relentless Prioritization

The post What’s the Difference Between Optimization and Prioritization? appeared first on RaderCo.

You know what it is. You've probably known for months. And you still can't get to it half the time.

Sometimes that's because we call something a priority just because we think it's supposed to be one, when the honest answer is that we aren't that interested. Sometimes it's a discipline problem, and there's a straightforward fix for that: write it down, and tell someone. I share my quarterly priorities with three friends and my husband, and I keep them on a whiteboard, in my Powered Path Playbook, and in ClickUp.

But when you genuinely do want to prioritize something and it still doesn't happen, the problem is sometimes one of three things. They look identical from the outside and they need completely different fixes.

levels of prioritization

Before you can fix a stalled priority, you need to know your baseline. There are three levels, and most people can place themselves in about ten seconds.

Essential. You don't really have a system, or the one you have is reactive. You respond to what shows up. You remember the email blast the day you launch the product. You remember the birthday because Facebook told you. You handle what's in front of you and hope the important things don't fall through the cracks. Sometimes they do. There's nothing wrong with you for being here. Plenty of people are.

Relentless. You've named your priorities. You work from a top three, professionally and personally. You're more intentional than reactive. You don't always get it right, but you know what right looks like for you. You've built guardrails rather than barriers. When I'm driving the Blue Ridge Parkway, I want a guardrail. A barrier blocks the view. A guardrail lets me see the path forward and still feel safe.

Radical. You've redesigned your life around your priorities. Quarterly review partners. A family that sets priorities every January. Prioritization is how you operate.

Radical isn't the goal. Knowing where you are is important because the fix for a stalled priority depends on the level you're operating at and on which of the three problems you actually have.

A note on the phrase underneath all of this: relentless prioritization beats endless optimization. Most of us are optimizing, and optimization can quietly make the wrong things faster and leaner without anyone asking whether they deserve to exist. I'll go deeper on that distinction in an upcoming episode.

Ability, capacity, agency

Ability is the skill to prioritize, and it doesn't transfer just because you got promoted or reached a certain age.

One of my clients spent ten happy years as a bench scientist with a pipette in her hand. One experiment, one question, one data set at a time. Then she got a team of four, one-on-ones on her calendar, a budget with her name on it, and a board meeting twice a quarter where she had to explain a slipped timeline to people who didn't know a western blot from a whiteboard.

She knew how to prioritize research. Prioritizing for a team had never been modeled or taught. We should never assume people already know how.

Capacity is room. Brad got a pre-diabetes diagnosis and clear instructions from his doctor. He had the ability; he knew exactly what to do. He had agency; he was making conscious choices about his time every week. The problem was that those choices already had somewhere to go. Two kids, eight and ten, and he was coaching their baseball team. That was a real priority and he was living it. What it left for his health was nothing. Coaching kept him out late, and stopping at Chick-fil-A on the way home was easier (and he wasn't ordering the kale salad).

He wasn't failing. He was succeeding at one priority and paying the price in another. The fix wasn't trying harder. It was looking at the rest of the stack and finding something else that could move.

Capacity is also where neurodivergence often shows up. When the structure, environment, or support isn't right, what looks like an inability to prioritize is usually a conditions problem, and the right setup changes everything.

Agency is whether the decision is yours to make. Another client broke her foot. Boot, crutches, six weeks, couldn't drive. She suddenly had more capacity than she'd had in years, because half her obligations became physically impossible. What she didn't have was agency. She needed someone to get her groceries and drive her to PT, and she waited on whoever had room in their week. Someone else was running her schedule.

You may recognize this if you manage a project or a team and can't get resources. You know exactly what you need. You just don't have the authority to hire.

The three questions

Ask yourself right now:

• Do I know how to do it?
• Do I have the room to do it?
• Am I actually the one deciding?

Wherever you get stuck, that's where you begin.

The test

Suppose a journalist were following you for three days. What would they actually see?

Would they write down that you're living your stated priorities? Would they see you protecting the time you said you'd protect? Or would your actions tell a different story?

It's your calendar that shows up in that story, and what you decide when something else tries to take the slot.

Three problems, three fixes

Ability is a learning problem. Find someone who does this well and get close to them. That skill can be built.

Capacity is a trade. The priority doesn't rise unless something else in the stack comes down.

Agency is escalation or negotiation. You can't outwork your way to a decision that isn't yours to make yet, but you can name who's holding it and start there.

And you can't fix any of them by trying harder.

Go back to the priority you had in mind at the start. Name which one is stopping you. Out loud. That's the first step, and it's the one most people skip.

The Right Things First: A Pocket Guide to Relentless Prioritization is the pocket version of this framework. Learn more here.

The post The Three Levels of Prioritization: Essential, Relentless, Radical appeared first on RaderCo.

Are You Solving the Real Problem or the Visible One?

A few months ago, I was in Atlanta going through TSA. Long line. Really long. The checkpoint was short-staffed, and anyone could see it.

What I also noticed: they'd brought in ICE agents to manage the line. Agents who are not trained in TSA responsibilities. Not authorized to do the actual screening. And here's the part that bugged me - TSA agents weren't at home playing Fortnite. They were working second jobs because they hadn't been paid in weeks.

So the line didn't move. It couldn't. The problem wasn't the line. The problem was an upstream government bottleneck resulting in staffing and pay decisions that nobody in that airport had the authority to fix.

I walked away (slowly) thinking, "I see this everywhere."

We add bodies to a problem. We create more Slack channels. We schedule another weekly check-in. We call it a solution. Meanwhile, the actual source of the problem is sitting upstream, untouched, because addressing it is harder, slower, or politically uncomfortable.

That's the difference between optimizing what's visible and prioritizing what's real.

Optimization and Prioritization Are Not the Same Thing

Optimization is making something faster, leaner, or smoother.

Prioritization is deciding what deserves to exist at all.

I teach a lot of optimization. I love a good system. But I've watched people spend enormous energy making something more efficient that never should have been there in the first place. It's like researching which door to put between two offices when it should really be a wall. No door needed.

Work example: your team's chat channels are out of control. People are getting pinged all day. So you create more specific channels. You color-code, mute, and set up folders. That's optimization. It might help at the margins. But it doesn't touch the real problem: probably that your team has no shared understanding of what channel is for what kind of communication—or they don't have a project management system, so they're using chat for status updates that nobody should be messaging about in the first place.

If you had a project management system, a lot of those messages wouldn't exist. That's the upstream fix.

Same thing happens outside of work. You're overwhelmed by everything that goes on in the household. So you buy a planner. Download an app. Set up reminders. That's optimization. The upstream question is: who actually needs to be involved in each of these decisions, and is there anything on this list that doesn't need to happen at all? Am I cleaning baseboards weekly when quarterly would do? Am I still doing my kid's laundry when that's a life skill they should learn? Those questions are harder. They're also the ones that actually reduce the load.

The Relentless Prioritization Filter

I've been developing and refining this filter for years. It's now the framework at the center of my new book, The Right Things First: A Pocket Guide to Relentless Prioritization.

Three questions. Asked in order. The order matters.

Question One: What Is the Real Bottleneck?

Not the thing people complain about. Not the symptom. The thing causing the problem.

Think about what a bottle looks like. The neck is narrow, and it doesn't matter how much is in the bottle if the flow is restricted at the exit point. You can have incredible talent, real budget, the right intentions — and still be stuck, because nobody has named where the flow is actually breaking down.

And that's the key word: named.

If we don't name it, we can't fix it.

Here's what makes that harder than it sounds: bottleneck identification carries a social risk. Naming a bottleneck might mean naming a person. Maybe a system leadership invested a lot of money in. Maybe a decision that came from the top. So people don't say it. They build elaborate workarounds and call them solutions.

What I've built at RaderCo: for a stretch, every Friday, someone had to come to the table with a bottleneck. We eliminated so many. It's still a standing question in our processes.

The version that works in teams: make it a standing agenda item. "Has anyone found a bottleneck this week?" Ask each person to bring one to share among the group. If you're a leader, go further: ask them to share one that involves you. That's the move that actually changes the culture. When people hear their leader say, "If I’m the bottleneck here, I want to know about it," it opens the door for everyone else to do the same.

You can also use brainwriting before the discussion - people write their observations independently before anyone talks. It surfaces the real answers before anyone can self-censor.

Quarterly recognition for the team or person who finds and solves the most bottlenecks is worth considering, too. Reward what you want to see.

For a deeper look at how to build this culture, read: Celebrating Bottlenecks: Why Replacing Obstacles Can Supercharge Business Growth

Question Two: What Would Remove It Entirely - Not Just Improve It a Little?

Most people skip this question. We go straight to "how do we make this better?" We don't ask whether we could make it not exist.

Some things can't be removed entirely. I get that. But you'd be surprised how many can, once you ask directly.

If the bottleneck is decision approval, you might improve it with a faster escalation path. But you might eliminate it by creating a decision rights document — so people know which decisions they already have the authority to make without asking. Parameters like: if it costs less than $X, you can fix it. Over $X, escalate.

If the bottleneck is status meetings, you might improve them by shortening them. Or you might eliminate them by moving to a project management system, so everyone can see the current status without a meeting. Nobody needs a meeting to answer "where are we?" if the answer is already visible.

If the bottleneck is approval on routine client communications, you might improve it by batching your approvals. Or you might eliminate it by building approved language templates — so the approval step is no longer required for standard messages.

If the bottleneck is the onboarding questions a manager gets every time someone new joins, you might improve it by adding office hours. Or you might eliminate it by building a real onboarding guide with FAQs and a few short screen-capture videos, so the question doesn't need to be asked.

The question to keep asking yourself: am I still involved in this because I need to be, or because we haven't decided I don't need to be?

That distinction alone is worth a lot of hours back.

Here's the honest counterpart: there's a reason we don't ask this question enough. Sometimes the bottleneck is a conversation nobody wants to have. Sometimes it's a budget decision. Sometimes the answer requires asking someone senior to step out of a process they like being in. As one director put it in a training: "I just realized I'm inserting myself into too many meetings and people are either afraid to speak up or just waiting for me to make the decision."

Optimization is easier. You can optimize without ruffling feathers. Which is exactly why we default to it.

Question Three: Why Are We Solving Around It Instead?

This question is about honesty.

Are we optimizing because the bottleneck is the boss, and nobody's going to say that in a meeting?

Are we optimizing because we paid $50,000 for a system and don't think we can also afford the $7,000 in training to actually use it — so we're patching it with YouTube tutorials and hoping for the best?

Are we optimizing because it feels like progress even when it isn't?

I've seen all three. I've probably done all three.

The goal of this question isn't to assign blame. It's to get honest about whether the solution you're considering is real or whether it's just within your comfort zone. We tend to solve the problems that are safe to name - not the ones causing the actual damage.

Once You Have a Proposed Solution: The Three-Part Check

Before you commit to any fix, run it through this:

Does this reduce or eliminate the bottleneck or conflict? If the answer is "reduces," fine. Keep going. But if there's another path that eliminates it entirely, ask whether you're choosing "reduces" because it's genuinely the right call or because it's easier.

Does this eliminate downstream decisions? Every time you add a process, a system, or a policy, ask: Does this create fewer decisions or more? Moving to a project management system doesn't just give you visibility into status. It removes the need for status messages, status follow-ups, and the decision of whether to follow up. You've eliminated a whole category of small decisions. That's the right direction.

(Slack and Teams are not project management systems. I say this a lot. You cannot project-manage in a chat tool. Episode 41: Why Companies Will Never Get Out of Email Hell covers exactly why.)

Does this protect capacity or energy? Energy counts as a resource. Your team's attention is finite. Your focus is finite. If the solution technically works but requires your people to spend cognitive energy tracking, managing, or checking in on it, that cost matters. Account for it.

If any of the three answers isn't "yes," it may not be a solution. It might be an improvement. Improvements are worth something. But they're not the same thing, and stopping at improvement and calling it solved is how the real problem survives another quarter.

One more thing: pilot everything. Call it a pilot. Run it for 30, 60, 90 days and ask whether it worked. The word "pilot" removes the anxiety of having to succeed. It's just what you're testing right now. After the pilot period, ask the question: Did this work, and if not, why?

Not every action is progress. The pilot framing gives you permission to evaluate and adjust without it becoming a failure of character.

This Works Everywhere

The filter isn't just for work.

Health: if driving to the gym is your bottleneck, you can optimize it — find a slightly closer gym, pack your bag the night before. Or ask: what would remove this bottleneck entirely? If a 35-minute drive is the issue, a home gym eliminates the excuse. You transfer the membership cost to equipment, lose the commute, and remove the friction entirely. You roll out of bed and go.

Meal planning, sleep, recovery — same questions. Where's the real bottleneck? What removes it entirely? Are you solving around it because the real answer requires a bigger change?

You can apply this to commuting, to how you run your household, to how you manage your own calendar. The questions are the same. The order is the same. What's the real bottleneck? What removes it entirely, and why are you working around it?

The Book

The Relentless Prioritization Filter is the framework at the center of The Right Things First: A Pocket Guide to Relentless Prioritization.

"Pocket guide" is literal. It fits in your pocket. This isn't a 300-page business book you read once and shelve. It's a tool. It's meant to sit on your desk, get handed to a teammate, get included in a manager's onboarding kit. Designed to be used repeatedly, in real situations, by real teams.

It's available in packs of ten or more, priced for organizations, teams, conference attendees, and groups who want to work from the same page.

If you're planning a leadership retreat, a conference, or a team offsite this fall, this is worth ordering ahead.

Order The Right Things First at helloraderco.com/therighthingsfirst →

Frequently Asked Questions

What is the Relentless Prioritization Filter? The Relentless Prioritization Filter is a three-question prioritization framework for teams to identify the root cause of what's slowing them down, rather than optimizing the visible symptoms. The three questions are: What is the real bottleneck? What would remove it entirely? Why are we solving around it instead?

What is the difference between optimization and prioritization? Optimization makes something faster, leaner, or smoother. Prioritization decides whether something deserves to exist at all. Teams that optimize without prioritizing first often spend significant effort improving processes that should be eliminated entirely.

How do you identify the real bottleneck on a team? Separate the symptom from the source. The thing people complain about is rarely the actual problem — it's usually downstream of a decision, system, or assumption that hasn't been named. A standing agenda item asking "what's the real bottleneck this week?" with each person writing their answer independently before discussion surfaces more honest answers than open group conversation.

How do I know if a proposed solution is actually a solution? Run it through the three-part solution check: Does it reduce or eliminate the bottleneck? Does it eliminate downstream decisions rather than create more? Does it protect your team's capacity and energy? If any answer is no, you have an improvement — not a solution.

What is The Right Things First? The Right Things First: A Pocket Guide to Relentless Prioritization is a pocket-sized book by Marcey Rader built around the Relentless Prioritization Filter. It's designed to be used repeatedly by real teams, not read once and shelved. Available in packs of ten or more at helloraderco.com/therighthingsfirst.

Related Resources

• Celebrating Bottlenecks: Why Replacing Obstacles Can Supercharge Business Growth
• Embrace the Bottlenecks
• Episode 123: Don't Improve the Symptom Before You Address the Source
• Episode 41: Why Companies Will Never Get Out of Email Hell
• Why Companies Will Never Get Out of Email Hell
• The Right Things First: A Pocket Guide to Relentless Prioritization — available in packs of 10 or more. Official launch September 8, 2026.

Marcey Rader is a Certified Speaking Professional®, TEDx speaker, and five-time author. She helps teams do better through relentless prioritization, attention management, and sustainable performance habits. Learn more at helloraderco.com.

The post Find the Real Bottleneck: A Prioritization Framework for Teams appeared first on RaderCo.

You know what your priorities are. You've probably said them out loud, maybe even written them down. Maybe they're on a whiteboard, in your planner, in your project management system.

You still can't get to them half the time.

That may not be a discipline problem. It could be an ACA problem: ability, capacity, or agency. Knowing which one you're actually missing changes everything about how you fix it.

Ability: the skill to prioritize

Ability is the skill to prioritize. We should never assume people already know what a priority is.

I see this all the time with people who get promoted and never get any training on how to manage priorities now that they're a manager, including managing other people's priorities too.

Here's what it can look like. A bench scientist spends ten happy years with a pipette in her hand, one experiment, one question, one dataset at a time. Then she gets a team of four. Now there are one-on-ones on her calendar for the first time in her career. There's a budget with her name on it. There's a board meeting twice a quarter where she has to explain to a room that doesn't know a Western blot from a whiteboard why the timeline slipped. She knows how to prioritize research. Nobody ever taught her how to decide whether finishing the budget submission or ensuring her postdoc's data reaches the right partner matters more this week.

Capacity: the space to prioritize

Capacity is whether you have the space to prioritize. Time, energy, margin. You can have the skill and still not have the room to use it.

I see this a lot with business owners who have a small team, or who are their own team, wearing multiple hats.

Picture someone running solo ops for a ten-person company. She knows exactly what her top three should be. Built the list in twenty minutes, no problem. The issue is she's also the one answering the phone, chasing the invoice, and covering the front desk when someone calls in sick. The skill's there. The hands aren't.

Agency: the permission to prioritize

Agency is the permission to prioritize. You know what matters. You might even have the time and energy for it. But someone or something else is deciding your week.

You break your foot. Boot, crutches, six weeks. You can't drive. You can't even make yourself a cup of tea. Suddenly you have more capacity to prioritize than you've had in years, because half your normal obligations just got physically impossible. What you don't have is agency. You need someone to pick up groceries. You need a ride to the follow-up appointment. You're waiting on whoever has room in their week to decide when you get help.

This can also be the manager whose senior leadership is deciding whether she gets to add another team member.

Which one is actually stuck

When people don't get to their priorities, they often assume it's a matter of ability. It rarely is.

Ask yourself right now: do I know what to do, or do I lack the ability to do so? Do I have the room to do it, or do I lack the capacity? Am I actually the one deciding, or is someone deciding for me?

Wherever you get stuck, that's where you look for your answer. Each one needs a different fix. You don't fix an agency problem by trying harder. You start by naming it. Only then can you work your way downstream to actually solve it.

If you want to go deeper on this, it's in the pocket guide, The Right Things First. It's 74 pages, or about a 65-minute listen, because I prioritized leaving out any fluff and got straight to the point. I relentlessly prioritized my words.

Or if you want to talk through which one's actually got you stuck, book a call with me and let's figure it out.

FAQ

What's the difference between ability, capacity, and agency? Ability is the skill to prioritize. Capacity is having the time or energy to act on it. Agency is having the actual permission or control to act on it. You can be missing one, two, or all three at once.

How do I know which one is actually blocking me? Ask yourself three questions. Do I know what to do, or do I lack the ability? Do I have the room to do it, or do I lack the capacity? Am I actually deciding, or is someone deciding for me? Whichever one stops you, that's your answer.

Can I have the ability and the capacity but still not have agency? Yes, and it's one of the harder ones to sit with. You know exactly what to do, and you have the time and energy for it, but someone else is making the call. That's not a try-harder problem. It's a name-it-and-escalate or negotiate problem.

Is this the same as work-life balance? No. ACA is about why a specific priority doesn't get done. It's not about how you divide time between work and everything else.

What if I have all three and still can't get to my priorities? Then ACA isn't your bottleneck. Go back to the list itself. 

Resources

• Episode 118: Stop Calendar Decorating and Prioritize First with the Altitude Method
• Prioritize First With the Altitude Method
• The Right Things First (pocket guide)

The post Why can’t you get to your priorities? appeared first on RaderCo.

Why It Matters to Stay Connected Remotely

Remote workers tend to work more hours than in-office peers, not because they're more productive but because the transition doesn't exist. No commute, no walk to the bathroom down the hall, no lunch out. And longer hours disguised as engagement eventually show up as burnout. You can optimize all you want, but you need to relentlessly prioritize first. The guardrails that protect your focus and your team's connection don't happen by default. They have to be built.

What You'll Learn

• Why remote workers feel compelled to prove they're working through constant availability and what that pattern costs in microstress, cortisol, and decision-making quality
• What it means to sleep with your company and why checking work email in bed is a guardrail worth building now
• How async video tools like Loom replace meetings, reduce rework, and communicate tone in ways that text never can
• How to use a pre-meeting video review to arrive at decisions faster and sometimes skip the meeting entirely
• How short personal video messages build team connection and client relationships in ways that email alone cannot

FAQ

Why do remote workers tend to work longer hours than in-office employees? Because the transition doesn't exist. No commute signals the start or end of the workday. The bathroom is four steps away. Lunch often doesn't happen away from the desk. Without deliberate guardrails, work expands into every available hour. Longer hours reduce recovery, and reduced recovery eventually shows up as burnout, sometimes disguised as engagement until it isn't anymore.

What does it mean to sleep with your company? If you check work email in bed, you're bringing your team, your inbox, and your stress response into the one place your brain needs to associate with rest. It affects sleep quality, cortisol levels, and next-day decision-making. It's one of the highest-leverage guardrails you can build: the phone stays out of the bedroom.

What is async video and when should I use it? Async video is a pre-recorded video of a screen or face sent in place of a meeting or a long written message. Tools like Loom let you record, share, and caption a video in seconds. Use it when tone matters, when visuals need explanation, or when typing everything out would take longer than just showing it. A 47-second video can replace a paragraph of text and three follow-up questions.

How does a pre-meeting video review save time? Send a short video walking through the material before the meeting. Attendees arrive informed; questions are already answered, and the meeting becomes decision time rather than catch-up time. In some cases, the meeting doesn't need to happen at all.

How can I use video to maintain a connection with my team and clients? Short face-to-camera videos sent without an agenda build relationships faster than email. Twenty seconds saying you were thinking of someone, or a quick Loom walking through a proposal, signals care and effort that text doesn't convey. It's also a differentiator: most people don't do it, so those who do are remembered.

What is a communication matrix and how does it reduce ambiguity? A communication matrix defines which channel to use for each message type and the appropriate response time for each. Confusion about where to reach someone and how quickly they'll respond creates microstress and rework. Clear expectations reduce both. The full framework is in Reclaim Your Workday, and a sample is in the free Go-To Guide.

Resources

• Watch the full clip: How to Stay Connected and Productive Working Remotely
• Book: Reclaim Your Workday
• Free Go-To Guide including a sample communication matrix: Reclaim Your Workday Go-To Guide
• Loom Videos Replace Meetings: The 5-Min Habit That Gives 30
• Designing Meetings for Neurodivergent Brains
• Zoom Zombies to Async Advocates: Burn Down Your Meeting Culture and Rebuild It
• Health-Powered Productivity Podcast: available wherever you listen to podcasts
• Twice-monthly Tipsletter: Weekender Snapshot

The post How to Stay Connected and Productive Working Remotely appeared first on RaderCo.

Why It Matters

Most one-on-ones default to status updates. What are you working on....any blockers...see you next week.

That format does not build the kind of relationship that keeps remote employees visible, recognized, and retained. And yes, having regular one-on-ones is an important baseline. But the questions you ask inside that meeting determine whether it's a check-in or a real conversation. When a team feels disconnected, they often resort to overwork. Overwork reduces recovery, not just physical recovery but cognitive recovery. That pattern doesn't show up tomorrow. It shows up a year or two from now, and it doesn't just go away.

What You'll Learn

• Why fully remote employees are less likely to get promoted and what a structured one-on-one template does to counteract that
• How asking "what was your smartest decision this month" creates a consistent space for wins that women, especially, are less likely to volunteer without being asked
• Why "biggest lesson earned" is more useful language than "biggest failure" and what that distinction does for psychological safety
• Asking about energy drains surfaces what's actually affecting performance, including things happening at home that remote employees would never think to raise
• Why team-level sharing of wins and lessons compounds the individual benefit and builds collective learning

FAQ

Why are remote employees less likely to get promoted? Research puts the gap at 30 to 37 percent, depending on the study. The most common reason is visibility. If decision-makers don't have a strong relationship with someone, it's easier to overlook them when opportunities come up. Structured one-on-ones are one of the most direct ways to close that gap.

What questions should I be asking in a remote one-on-one? At minimum, three: what was your smartest decision or biggest win this month, what was your biggest lesson earned, and what's your biggest energy drain right now? These can be used in any combination and work equally well for weekly check-ins or quarterly reviews.

Why "lesson earned" instead of "lesson learned"? Because earned implies you got something out of it. It reframes struggle as investment rather than failure. That language shift changes how people engage with the question and what they're willing to share.

What if someone's energy drain has nothing to do with work? That's the point. Remote employees are less likely to surface personal stressors because there's no natural moment to do so. A sick dog, a kitchen renovation, a kid who's been home for a week. These things affect performance whether or not anyone names them. Asking the question creates permission to name them.

How does disconnection lead to overwork? When people feel unseen or uncertain about their standing, they compensate by working more. More hours, more output, more visible effort. That pattern reduces cognitive recovery over time. It doesn't show up immediately. It shows up as burnout, disengagement, or turnover a year or two later.

Can these questions work at the team level too? Yes. One person shares their smartest decision at a team meeting. Another shares their lesson earned. The format scales and the learning compounds. Teams that do this regularly build shared knowledge faster and feel more connected to each other's work.

Resources

• Watch the full clip: Better Remote 1:1s: Questions Every Team Leader Should Ask
• Book: Reclaim Your Workday
• Health-Powered Productivity Podcast: available wherever you listen to podcasts
• Powered Path Program goal-achievement course
• Weekly tips: Weekender Snapshot

The post Better Remote One-On-One Questions Every Leader Should Ask appeared first on RaderCo.

Why It Matters

Most focus advice stops at removing distractions. That's necessary but not sufficient. And yes, clearing notifications and going offline are optimization steps worth taking. But getting into genuine deep work requires three distinct anchors working together: your environment, your mind, and your energy. Miss one and the other two carry more weight than they should. This is the practical side of what the science behind distraction and decision fatigue actually demands.

What You'll Learn

• How to set up your physical environment for deep work, including the cathedral effect and why the room you choose changes the kind of thinking you can do
• Why writing down the one thing you are working on by hand, not typing it, signals to your brain that the task is important
• How to use timed focus blocks effectively, including why 50 minutes is the ceiling and what a real break actually looks like
• How two minutes of high-intensity movement before a focus block can improve concentration, especially for anyone with ADHD or on the neurodivergent spectrum
• Why the exhale, not the inhale, is the breath that actually calms your nervous system and prepares your brain for focused work

FAQ

What is the cathedral effect? The cathedral effect is a research-backed phenomenon in which your physical environment shapes the type of thinking you can do. High ceilings and open outdoor spaces make you more likely to think creatively and solve problems. Low ceilings and enclosed spaces help you buckle down and execute. Choosing the right room for the right kind of work is not a preference. It's a performance variable.

Why write down my focus intention by hand instead of typing it? Writing activates a different cognitive process than typing. When you write something down by hand, your brain registers it as more significant. A sticky note with the one thing you are working on isn't a productivity ritual. It's a signal to your brain about what matters right now.

How long should a deep work block be? No more than 50 minutes. Research puts peak productivity time at around 52 minutes, but 50 is a clean number. After that, take a real 10-minute break. Not email. Not Slack. Something that lets your brain recover so the next block is as productive as the first.

What counts as a real break? Anything that isn't screen-based and not work-adjacent. Move, go outside, get water, breathe. Checking email during a break is not a break. It's the start of a new decision fatigue cycle.

How does movement help with focus? Two minutes of high-intensity movement before a focus block can meaningfully improve concentration. This is especially well-documented for people with ADHD, but the benefits extend to people who are not on the neurodivergent spectrum as well. Movement is not a reward for finishing work. It's a tool for doing it better.

Why does the exhale matter more than the inhale? When you tell someone who is anxious to take a deep breath, they tense up. Inhaling activates the nervous system. The exhale releases it. You can't fully tense while exhaling. Three or four slow, complete exhales before a focus block help lower your physiological stress response and prepare your brain for sustained attention.

Resources

• Watch the full clip: Three Attention Anchors That Get You Into Deep Focus
• Book: Reclaim Your Workday
• Health-Powered Productivity Podcast: available wherever you listen to podcasts
• Weekly tips: Weekender Snapshot

Does your team need help learning how to get into deep focus at work? Contact us today!

The post How to Get Into Deep Focus at Work appeared first on RaderCo.

Why It Matters

The pressure to respond immediately is especially acute for remote workers. There's a name for it: the productivity paradox. When you can't be seen at your desk, you prove you're working by staying visibly available. And yes, being responsive and setting clear communication expectations are things worth doing. But the reflex of reactivity is different from intentional responsiveness, and the gap between them has measurable consequences for your health, your team's growth, and the quality of your decisions.

What You'll Learn

• What the productivity paradox is and why remote workers feel compelled to respond instantly, even when it works against them
• Why instant replies can actually disempower your team and steal opportunities for their professional growth
• How micro stress accumulates under constant urgency and what it does to your blood pressure, sleep, cortisol levels, and decision-making over time
• Why cognitive recovery between tasks isn't optional and when your best thinking actually happens
• How a communication matrix can help your team reach you in the right way for the right kind of question

FAQ

What is the productivity paradox? It's the pressure remote workers feel to respond immediately to prove they're working. In an office, nobody thinks twice about a ten-minute bathroom break or a lunch out. Remotely, the same gap feels like a liability. That pressure drives reactive behavior, increasing stress and reducing the quality of your work.

What's the difference between being reactive and being responsive? Reactive means you answer the moment something arrives, regardless of what you're in the middle of. Responsive means you answer within a defined, reasonable window. Siri responds immediately. High performers don't need to.

How does instant replying disempower my team? When you step in to solve a problem the moment someone raises it, you're signaling that you don't trust them to handle it. If you tell someone you're unavailable and then respond anyway, you've undermined the delegation. Sometimes waiting to respond is the most developmental thing you can do.

What is micro stress and why does it matter? Micro stress is the accumulation of small, constant signals of urgency throughout the day. Individually, they feel manageable. Collectively, they raise cortisol levels, disrupt sleep, affect blood pressure, and compromise decision-making. It doesn't show up as a single breakdown. It shows up as chronic, low-grade depletion.

What is cognitive recovery and when does it happen? Cognitive recovery is the mental rest your brain needs between tasks to make better decisions. It doesn't happen between emails. It happens on a walk, in the shower, at breakfast. Building space for it is not a luxury. It's a performance requirement.

What is a communication matrix and where can I learn more? A communication matrix is a framework that defines which channel to use for which type of message, and what response time is appropriate for each. It reduces the pressure to be everywhere at once and gives your team clear expectations. The full framework is in Reclaim Your Workday and a sample copy is linked to in the free Go-To Guide.

Resources

• Watch the full clip: Stop Being Reactive at Work: Why Instant Replies Are Costing You More Than You Think
• Book: Reclaim Your Workday
• Free Go-To Guide including a sample communication matrix: Reclaim Your Workday Go-To Guide
• Health-Powered Productivity Podcast: available wherever you listen to podcasts
• Weekly tips: Weekender Snapshot

The post stop being reactive at work appeared first on RaderCo.

Why It Matters

Most people keep notifications on because they've always been on. That is not a strategy; it's a default. And yes, turning them off is one of the practical steps I recommend (optimization), alongside batching email and creating focus zones. But none of those tactics stick until you understand what the notifications are actually doing to your brain. Reactivity feels like responsiveness. It's not. There's a measurable difference between the two, and your clients, your team, and your own performance feel it.

What You'll Learn

• Why notifications exist to increase your usage of a tool, not your productivity, and what that means for every default setting on your devices
• The difference between being reactive and being responsive, and why immediately replying to every message can actually signal to clients that you're not focused
• How badges, those red number bubbles on your apps, are designed to compel you to tap them, and how to decide which ones you actually need
• How to audit notifications across every device, phone, watch, laptop, and tablet, and where to start if turning them all off feels overwhelming
• How to set up focus zones on both iPhone and Android so distraction guardrails run automatically without requiring willpower

FAQ

Won't I miss something important if I turn off my email notifications? In 16 years of teaching this, not one person has ever turned off their email notifications and forgotten to check their email. Nobody forgets. You will check it. You'll just check it on your terms, not the tool's.

What's the difference between being reactive and being responsive? Reactive means you answer the moment something arrives. Responsive means you answer within a reasonable window you define. Clients and colleagues adapt to responsiveness. What they actually lose trust in is someone who replies instantly to everything except what matters most.

Where should I start if turning off all notifications feels like too much? Start with your watch. Then your phone. Then your laptop. Or start with the obvious ones: Target sales, weather alerts, sports scores. There are notifications on your phone right now that have nothing to do with your work. Remove those first and build from there.

What are badges and why do they matter? Badges are the red number bubbles on your app icons. They're on by default because the companies that make these tools know most people can't resist tapping them. You don't need badges on every app. Decide which ones genuinely require your attention and turn the rest off. You're not going to forget to check.

What is a focus zone and how does it work? Focus zones are built into both iPhone and Android. They let you define which notifications and contacts get through during specific hours, and you can automate them so they turn on and off without you having to think about it. The goal is to make distraction guardrails the default, not something you have to remember to activate.

How many devices are too many for email? If your email is coming in on more than three devices, that's worth auditing. Every device is another surface that can pull you out of focused work.

Resources

• Watch the full clip: Turn Off Notifications to Take Back Your Focus
• Book: Reclaim Your Workday
• Health-Powered Productivity Podcast: available wherever you listen to podcasts
• Weekly tips: Weekender Snapshot

The post turn off notifications to take back your focus appeared first on RaderCo.

Why It Matters

Most focus advice skips the biology. It suggests trying harder, batching your email, or putting your phone in another room. And yes, I talk about doing these things as optimization strategies. None of that sticks if you don't understand what you are working against. Decision fatigue, anticipatory stress, and switchtasking are not productivity buzzwords. They are measurable drains on your performance, your willpower, and your ability to do your best work by the end of the day.

What You'll Learn

• Why every notification is a micro decision, even when you think you're ignoring it, and how 150 emails and chat messages a day add up to serious decision fatigue
• What anticipatory stress is, why your brain starts craving the dopamine hit before the notification even arrives, and how it affects the people around you
• The difference between background tasking, hypertasking, and switchtasking, and why switchtasking is the one most of us are doing most of the time
• Why multitasking is a myth and what the research actually says about how much time you lose in every task switch
• How decision fatigue follows you home and affects everything from your client work to what you eat for dinner

FAQ

Why do smart, high-performing people still struggle with focus? Because focus is not a character trait. It is a biological system being worked against by tools designed to trigger your involuntary attention. Willpower alone does not override a dopamine loop.

What is decision fatigue and why does it matter at work? Decision fatigue is the cumulative drain that comes from the volume and complexity of decisions you make throughout the day. The more decisions you make, the worse your brain gets at making them. It affects your judgment, your willpower, and your ability to prioritize what actually matters.

What is the difference between multitasking and switchtasking? Multitasking is an umbrella term. Switchtasking is what most of us are actually doing: moving back and forth between email, Slack, Teams, and other tools fast enough that it feels like progress. It is not. The brain loses time in every switch and nothing ever feels finished.

What is anticipatory stress? Anticipatory stress is the stress of waiting for a notification, not just receiving one. Your brain starts producing a dopamine response in anticipation of the ping. Over time, it wants more of it. Your family experiences anticipatory stress, too, every time they wonder whether your phone is about to pull you away.

Are these attention and focus problems my fault? No. These tools are designed to make you want to use them more. The compulsions are built in. Knowing that does not fix the problem, but it is the right starting point for building guardrails that actually work.

What is one thing I can do today to protect my focus? Audit your notifications. Identify one alert you could turn off permanently that you would not actually miss. Start there. Focus is not rebuilt all at once.

Resources

• Watch the full clip: Why Smart People Still Struggle to Focus at Work
• Book: Reclaim Your Workday
• Health-Powered Productivity Podcast: available wherever you listen to podcasts
• Weekly tips: Weekender Snapshot

The post Why Smart People Still Struggle to Focus appeared first on RaderCo.