Hiring well is the easier half. Most remote arrangements that disappoint were good hires managed badly, and the failure mode is remarkably consistent: things go quiet, nobody wants to raise it, and six weeks later the conclusion is "remote does not work for us".
Four habits prevent nearly all of it.
1. Set a reporting rhythm in week one
Not when something goes wrong. Week one, while there is nothing to report.
- End-of-day note. Three lines: what is done, what is in progress, what needs you. Two minutes to write, two minutes to read. It removes almost every status-chasing message and it makes drift visible within days instead of weeks.
- Weekly call, fifteen minutes. Priorities for the week, anything stuck, anything to hand over next. Short and regular beats long and occasional.
- Monthly review, thirty minutes. What is working, what should change, what the next seat or next skill should be.
If you take one thing from this article, take the end-of-day note. It is the highest-leverage habit in remote work and it costs almost nothing.
2. Ask better questions than "any blockers?"
"Any blockers?" reliably returns "no, all good", from everyone, everywhere. It is a closed question wearing an open question's clothes, and in a culture that leans towards politeness it will almost never surface a problem.
Replace it with questions that are hard to answer with reassurance:
- "Which task took longest this week, and why?"
- "What did you have to guess at?"
- "What is one thing that would have been faster with a better process?"
- "Where did you wait on someone?"
Then respond well the first time someone raises a real problem. That single response decides whether they raise the next one. If the first honest answer is met with irritation, you have just trained the person into silence and you will not find out for a month.
3. Document into your business, not into a person
Every recurring task should end up as a written procedure in your own drive, written by the person doing it, kept current by them.
The mechanics take ten minutes: record your screen doing the task once, have them write the procedure from the recording, then check it while they run it. Their version is usually clearer than yours would have been, because they write down the context you forgot you had.
Do this and turnover stops being a crisis. The next person starts from a written process rather than from your memory of a process. It is also the single thing that makes leaving an agency painless, which is exactly why you should insist the documentation lives in your drive rather than theirs.
4. Measure output, not presence
Resist time-tracking screenshots and keystroke monitoring. They correlate with worse outcomes, not better ones: they signal distrust, they push people towards looking busy, and they select for the candidates least able to say no to them.
Agree what the week should produce instead. Inboxes cleared by a given hour, listings live within a day of photos, tickets moved to review, calls made and meetings booked. If output holds, hours are not your problem. If output slips, you have a concrete thing to discuss rather than a dashboard to argue about.
Where the work genuinely is hourly, invoiced time plus a daily report of what that time produced is enough.
What "output" means changes by seat, and that is worth setting explicitly. For an administrative assistant it is usually a state: inbox at zero, calendar confirmed, CRM current. For a software developer it is tickets moved to review with tests attached. For an automation specialist it is workflows live and documented, not hours spent mapping. Write the definition down in week one and you will never have the hours conversation.
The access practices that go with it
- A password manager with role-scoped permissions. Never credentials in chat, email or a spreadsheet.
- Delegated access where the tool supports it, so you grant and revoke without sharing your own login.
- Two-factor authentication on everything, with recovery codes held by you.
- A written offboarding checklist, created on day one and run the same day a seat ends.
If you would rather not do any of this
That is a legitimate position, and it is the reason managed teams exist. With us the account manager runs the reporting rhythm, the quality checks and the escalations, and you get one rolled-up summary instead of four separate conversations. Read how every seat runs day to day, or book a discovery call and describe the seat you have in mind.
