Skip to main content
Productivity4 min read

Top 10 work from home productivity tips (that also reduce typing strain)

Ten practical remote-work habits, what the Bloom randomised experiment and a 2022 systematic review actually found, and how to cut keystrokes on writing-heavy days.

Key takeaways

answer-first
  • The strongest evidence for remote work productivity is usually “it depends”: role, autonomy, coordination costs, and home setup matter.
  • A randomised experiment at a Chinese travel agency found a performance increase for home workers, alongside tradeoffs in communication and promotion (Bloom et al., NBER working paper 18871).
  • If your job is writing-heavy (docs, PR descriptions, tickets, long emails), one of the biggest levers is simply reducing keystrokes by using speech-to-text for first drafts.

Remote-work advice is mostly willpower advice, and willpower is the input you have least control over. The habits below change the environment instead: what has to be decided, what has to be written down, and how much of the day is spent typing.

Ten of them, plus a drafting workflow for people who spend the day in docs, tickets, and messages.

TL;DR

  • The strongest evidence for remote work productivity is usually “it depends”: role, autonomy, coordination costs, and home setup matter.
  • A randomised experiment at a Chinese travel agency found a performance increase for home workers, alongside tradeoffs in communication and promotion (Bloom et al., NBER working paper 18871).
  • If your job is writing-heavy (docs, PR descriptions, tickets, long emails), one of the biggest levers is simply reducing keystrokes by using speech-to-text for first drafts.

Not medical advice. If you have persistent pain, numbness, or weakness, seek clinical advice. This article is about productivity and workflow.

Tip #1: Treat “where you work” as a production decision

Remote work isn’t a personality test. It’s an operations problem:

  • Where do you get deep work done?
  • Where do you do coordination work?
  • Where do you do meetings?

Even if you’re “fully remote,” it’s okay to use multiple environments (home desk + occasional quiet place) if it reduces friction.

Tip #2: Create a daily “start ritual” you can repeat

The goal is to remove decision-making at 9:00am.

Examples:

  • laptop open → calendar review → 1 sentence: “Today I will finish X”
  • 5 minutes of inbox triage, then one deep-work block

The ritual is boring on purpose. A boring ritual survives a bad morning.

Tip #3: Reduce coordination overhead (and write it down)

Remote work fails when every decision requires a meeting.

A simple rule that helps teams: if it can be decided asynchronously, write it down first (a short doc, a proposal, or a comment in the ticket) before asking for a meeting.

Tip #4: Use “one doc per decision”

If decisions are scattered across Slack, email, and meetings, you re-litigate them forever.

Pick a single source of truth per decision:

  • Notion page
  • Google Doc
  • GitHub issue
  • Jira ticket description

Tip #5: Make meetings smaller and more structured

Two practical habits:

  • Add an agenda (even 3 bullets).
  • End with explicit owners and next steps.

If you can’t write an agenda, the meeting probably isn’t ready.

Tip #6: Use speech-to-text for drafts (docs, tickets, long messages)

Remote work converts conversations into writing. The meeting that would have settled something becomes a doc, and the doc has to be typed.

Drafting by voice works well for:

  • weekly updates
  • project summaries
  • meeting notes
  • PR descriptions / design docs

Then you edit with the keyboard.

Start with built-in macOS Dictation: /speech-to-text-mac

If you dictate daily, a dedicated hotkey helps you actually stick with it: /voice-typing-mac

Tip #7: Batch notifications instead of receiving them

The cost is not the interruption, it is the reload afterwards:

  • disable non-essential notifications during deep work
  • batch check-ins for Slack/email

Tip #8: Add microbreaks (so you don’t pay later)

Remote work often removes natural breaks (walking to a meeting room, commuting, etc.).

Be careful with what you read about microbreaks, including on this site. One 2001 study reported reduced discomfort without obvious productivity loss in a controlled task (McLean et al., 2001). But the Cochrane review that pooled the randomised trials found no significant effect on musculoskeletal pain, and its October 2025 update concludes the evidence is very uncertain (Luger et al., Cochrane 2025). Take breaks because they are free and carry no known risk, not because the trials proved a benefit. We cover this in full at /blog/microbreaks-for-typing.

Practical starting point:

  • 30 to 60 seconds every 20 minutes
  • 3 to 5 minutes once per hour

Tip #9: Make “end of day” real

If you never stop, you never recover.

A small, repeatable shutdown ritual helps:

  • write tomorrow’s first task
  • close tabs
  • set calendar boundaries

Tip #10: Review weekly outcomes, not daily emotions

Daily mood is noisy. Weekly outcomes are signal:

  • what shipped?
  • what got blocked?
  • what created churn?

What research says about WFH and productivity (a quick reality check)

There’s a large literature, but it’s uneven: lots of surveys, fewer clean experiments.

Two sources worth reading:

Neither implies “WFH is always better.” They do support a practical takeaway: setup and process matter.

Keep going

Sources (research + primary references)

Related articles

Productivity
How to be more productive in Linear (without writing more tickets)

Linear productivity is mostly about clarity: fewer meetings, fewer follow-ups, and issues that are easy to execute. Here’s a practical workflow (with templates) that makes teams faster.

Privacy
Three pairs of Wispr Flow documents, read side by side

A reading of one dictation vendor's published pages against each other, checked on 2026-08-29: the certification wording, the analytics wording, and the training default.