If you're an IC on a team that demands real-time response — Slack pings at all hours, meeting-heavy days, expectation of instant availability — you have less leverage than your manager and more than you think. The trick is to demonstrate async value in writing, not argue for it in meetings.
Why real-time culture is hard to fight
Real-time culture isn't usually deliberate. It's accumulated — a series of small expectations that nobody set explicitly. "Quick Slack question?" becomes the default; meeting invites with no agenda become routine; the engineer who is always online becomes the model.
You can't argue this away in one conversation. You can change it by demonstrating, in writing, that async produces better outcomes.
Step 1: own one async surface
Pick one place where you can do async work that visibly outperforms the real-time alternative. Examples: a weekly written status that replaces a status meeting. A design doc that gets reviewed async instead of in a 60-minute call. A decision record that captures a debate that would otherwise sprawl across Slack.
Ship it. Make it good. The async artifact will speak for itself if it's actually better.
Step 2: build the receipts
Track, for two weeks: how much time you spend in unscheduled Slack interruptions, how much in meetings without a written outcome, how much in deep work. Most ICs are surprised by the ratio — frequently 60% interrupt, 25% meeting, 15% deep work.
You'll need this data. Anecdotes lose arguments; numbers win them.
Step 3: set focus blocks and defend them
Block 2-3 hours daily on your calendar labeled "focus." Set Slack to do-not-disturb during those blocks. Respond to non-urgent messages at the end of the block. Hold the line for two weeks.
Some teammates will be annoyed. Most will adjust. The ones who escalate to your manager are the data point that tells you whether your team is fixable.
Build the Async Receipts You Need
StandIn gives ICs a structured, queryable record of work and decisions — so the case for async is built into the workflow.
See the Workflow →Step 4: write the manager note
After two weeks of data and one async win, have one conversation with your manager. The structure: "Here's what I tried, here's what worked, here's the data, here's what I'd like to do more of." Not a complaint, not a manifesto — a proposal.
Most managers will engage with this. The ones who don't are giving you a different kind of information about whether to stay.
Step 5: change what you can, accept what you can't
You can change your own response cadence, your meeting acceptance criteria, your defaults on focus blocks. You can demonstrate value through written artifacts. You can decline meetings without agendas.
You can't change a team-wide culture alone. If your manager and team don't move after a quarter of evidence, the lever isn't in your control. That's a job-search signal, not a personal failure.
Common failure modes
Failure: arguing for async in meetings. Meeting-bound arguments don't change meeting culture. Write a doc. Share it. Let people read it on their own time.
Failure: going dark without warning. If you've been online constantly for six months and suddenly aren't, the team panics. Communicate the change: "I'm setting focus blocks 10-12 daily; I'll respond to non-urgent things after."
Failure: framing it as work-life balance only. The case is partly that — but the harder argument is that async produces better engineering outcomes. Lead with the outcomes argument.
What to do tomorrow
Block one 2-hour focus window on your calendar this week. Set DND during that window. Note what you got done. That single block, repeated four times, will produce more visible output than a week of being constantly online. The output is the argument.
Frequently asked questions
What if my team is small and everyone needs me online?
Probably less than you think. Track for two weeks how many "urgent" pings were actually urgent. The number is usually under 15%. The rest can wait an hour without consequence.
Won't I look uncommitted if I go async?
Only if your output drops. If your output goes up while you're online less, you look more committed, not less. Async is leverage, not slack.
What if my manager pushes back?
Bring data. "Here's what I shipped during focus blocks vs. interrupt time." If the data is real and the manager still pushes back, you're not having a productivity disagreement — you're having a control disagreement. That's a different conversation.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.