Marcey Rader

Ask any leader on your team what matters most and they'll answer without blinking. That was never the gap.

The gap shows up in the meeting that runs long anyway. In the request nobody had the nerve to say no to. In the project everyone keeps funding because stopping it feels harder than continuing it. Your team isn't confused about priorities. They're losing the moment when priorities are actually chosen.

The Right Things First gives leaders one idea and one guardrail, a rule you set for yourself before you need it. Nobody hands it to you; you build it live in the room. The idea: relentless prioritization beats endless optimization. It's why that project nobody's willing to kill keeps eating the calendar anyway. The guardrail: leaders leave having named their own, specific to whatever's actually costing them right now, not a generic rule everyone gets the same version of. One idea, delivered hard enough that a room sees it in their own choices before the keynote ends.

How long could your team run before things fell apart? A day? A week? A month? Most people don't actually know the answer.

Most teams run fine until someone's out. A vacation, a leave, a two-week notice, and the cracks show up fast. Coverage nobody planned for. Knowledge that lived in one person's head and left with them. A system that was never actually a system, just a group of people improvising in sync.

Reclaim Your Workday builds the real thing first: a repeatable way to choose what gets done, using tools built for it (Task Batching, Theme Days, the Altitude Method). If your team has already moved past treating coverage as an afterthought, this goes further: it stress-tests the system you've built against the moment it's actually tested.

Attendees leave with a plan that protects the organization when someone's out: real coverage, a documented bottleneck process, and a gatekeeper who isn't guessing. And their own part in making that plan hold: clean handoffs, the right people alerted, a genuine disconnect, because the plan only works if the person who built it actually follows it.

Takeaways:

• A repeatable way to choose the right work first, using tools built for exactly this.
• The real stress test: how long could your team run before coverage gaps and lost institutional knowledge start costing you, and do you actually know the answer?
• A documented bottleneck process and a real gatekeeper, not guesswork, for when someone's out.
• Your own part in making the system hold: clean handoffs, the right people alerted, a genuine disconnect, because the plan only works if you follow it.
• A live action plan built in the room, not a handout.

Sixty-seven percent of people attending meetings call them unproductive (State of Meeting Note-Taking, Laxis).

The Meeting Reset gives leaders a three-way decision framework: kill it, shrink it, or keep it, and starts with the question that should come before the invite goes out: Does this need to be a meeting at all? Three questions decide it, along with a real weekly meeting budget, meeting-free days, and a clear-eyed look at what AI notetakers change and what they still can't replace.

For the meetings that do happen: right-sized length, real accountability for action items, and facilitation tools that keep discussion moving without shutting anyone down. The guardrail here isn't a device ban; it's staying genuinely present, whatever that looks like for the person in the room.

Attendees leave having run one of their own recurring meetings through kill it, shrink it, or keep it, live, and decided on the spot.

Takeaways:

• A clear filter for deciding whether a meeting needs to happen at all, updated for what AI notetakers genuinely change and what they don't.
• The real cost of meetings, and a system for right-sizing who's in the room and how long it runs.
• Facilitation tools that keep the discussion moving without shutting anyone down.
• A guardrail that protects real presence without a blanket ban on devices, since some people focus better when typing, doodling, or mapping out ideas.
• Kill it, shrink it, or keep it: a live decision on one of their own recurring meetings, made in the room.

The keynote makes the case that attention is finite. This is where that case turns into a system.

Attendees learn OHIO, Only Handle It Once, a principle Marcey's taught for over a decade, originally built for paper mail and deliberately adapted for the inbox: delete, delegate, reply, archive, or task; nothing sits undecided. From there, the session builds the norms that keep it that way, a reply-all policy decided on purpose instead of left to instinct, subject lines that route work without anyone opening the email first, and a communications matrix, an if-this-then-that across five things: the type of communication, the right channel, its purpose, how fast a response is actually expected, and who needs to be in it. A quick question goes in chat. A project task goes into the project management system. Response windows are clear. No more guessing which channel a message belongs in.

Attendees leave having built one real piece of their new system in the room: a filter, a template, or a categorized inbox. Not a list of good intentions.

Takeaways:

• OHIO, Only Handle It Once: a simple rule for never touching the same email twice without making a decision.
• A five-way sort, delete, delegate, reply, archive, or task, so nothing sits undecided.
• A communications matrix across five axes, communication type, channel, purpose, response time, and participants, so nobody's guessing which tool a message belongs in.
• Team norms, decided on purpose: reply-all, aliases, tone, instead of left to instinct.
• One real piece of the system, built in the room: a filter, a template, or a categorized inbox.

Sixty-seven percent of people attending meetings call them unproductive (State of Meeting Note-Taking, Laxis).

The Meeting Reset gives leaders a three-way decision framework: kill it, shrink it, or keep it, and starts with the question that should come before the invite goes out: Does this need to be a meeting at all? Three questions decide it, along with a real weekly meeting budget, meeting-free days, and a clear-eyed look at what AI notetakers change and what they still can't replace.

For the meetings that do happen: right-sized length, real accountability for action items, and facilitation tools that keep discussion moving without shutting anyone down. The guardrail here isn't a device ban; it's staying genuinely present, whatever that looks like for the person in the room.

Attendees leave having run one of their own recurring meetings through kill it, shrink it, or keep it, live, and decided on the spot.

Takeaways:

• A clear filter for deciding whether a meeting needs to happen at all, updated for what AI notetakers genuinely change and what they don't.
• The real cost of meetings, and a system for right-sizing who's in the room and how long it runs.
• Facilitation tools that keep the discussion moving without shutting anyone down.
• A guardrail that protects real presence without a blanket ban on devices, since some people focus better when typing, doodling, or mapping out ideas.
• Kill it, shrink it, or keep it: a live decision on one of their own recurring meetings, made in the room.

The core session decides which meetings deserve to exist and runs them well. This add-on goes deeper into two things that only show up once a team goes hybrid or remote.

Does everyone actually get heard, whether they're in the room or not? Meeting equity and neurodivergent inclusion turn out to be the same underlying question: does someone get a fair shot at contributing, regardless of why they're quieter or less visible, a bad connection, a camera that's off, or a different way of processing a live conversation. Attendees build this with a Camera Norms Conversation: a non-recurring discussion where each person states when cameras on works for them, when off is fine, and what the team should assume when a camera's off, so it never gets silently read as checked out. Documented once, revisited only if the team's makeup changes.

The same logic that sorts meetings by purpose and urgency extends to a third option: async video or a written update, judged by whether the situation needs real-time reaction or just clear information, delivered with a named owner, a clear response window, and a length cap, so it gets read and answered instead of becoming a new inbox to manage.

Attendees leave having made one real decision on their own calendar: keep a meeting synchronous, or move it async.

Takeaways:

• Meeting equity and neuro-inclusive practice solve the same underlying problem: does someone get a fair shot at contributing, regardless of why they're quieter or less visible, a bad connection, a camera that's off, or a different way of processing a live conversation.
• A Camera Norms Conversation: a brief, one-time discussion that documents what "on" and "off" actually mean for this specific team.
• When to skip the meeting entirely: a named owner, a clear response time the team sets themselves, and a length cap turn async video or written updates into something that actually gets read and answered, not a new inbox to manage.
• A practical standard for making sure remote, in-room, and neurodivergent participants all get an equal shot, not three separate rulebooks.
• One meeting on the calendar, decided live: keep it synchronous, or move it async.

Remote work creates two problems that an office never had. No one sees you work, only whether you look like you're working. Nothing tells you when the day ends.

This session names both directly. Half of remote workers worry visibility gaps will hurt their career progression (Microsoft Work Trend Index). Proximity bias is measurable, not imagined, and looking active isn't the same as being effective. Proactive updates and intentional check-ins make the work visible. No green dot required.

Disconnecting gets the same treatment. Isolation-driven and boundary-erosion burnout are different problems with different causes: one comes from under-stimulation; the other from norms that were never set. This session builds guardrails for both transition rituals and a DND signal that's actually respected, and for honest availability with the people around you.

Attendees leave having chosen one guardrail, tested the next day. This is a personal commitment, not a tracked deliverable, built to hold on its own.

Takeaways:

• Proximity bias is measurable, not imagined, and looking active isn't the same as being effective.
• Two distinct burnout risks in remote work, isolation and boundary erosion, and why they need different fixes.
• Real guardrails for disconnecting: transition rituals, screen-free time blocks, and honest availability with the people around you.
• A DND signal that's respected, not just displayed.
• One guardrail, chosen live, tested the next day.

Managers carry every visibility and burnout risk their team does, plus one more: they decide who gets seen, advocated for, and protected.

This add-on builds directly on The Remote Reset's foundation, with what's specific to leading people you can't see in the room. Proximity bias isn't just something remote workers feel; it's something a manager actively produces or prevents in who gets picked, praised, and promoted. The instinct to counter that by monitoring more closely tends to backfire; trust erodes faster than oversight can catch up. Real delegation does the opposite: name the decision, watch it back once, and set the check-in date. It gives time back instead of adding a layer nobody asked for.

Managers leave having built one weekly habit for staying genuinely connected to their team, not a tracking system, and committed to one guardrail of their own to model, starting this week.

Takeaways:

• Proximity bias isn't just something remote workers feel; it's something managers actively produce or prevent in how people get seen, picked, and promoted.
• Why monitoring harder tends to backfire: trust erodes faster than oversight ever catches up.
• Delegation that actually gives a manager real time back: name the decision, watch it back once, and set the check-in date. Not just moving work around.
• How to model the guardrails you want your team to trust, not just announce them.
• One weekly habit for staying connected to the team, plus one guardrail of their own, modeled starting this week.