You send a message at 9 AM your time.
Your VA reads it eight hours later. They have questions. You’re asleep.
They wait. You wake up. The cycle repeats.
Most people think this is just how async work is. It’s not.
The problem is you’re giving tasks instead of outcomes.
What RPM Actually Is
Tony Robbins created something called the Rapid Planning Method. It’s not a time management system. It’s a way of thinking about work.
Instead of tasks, you define three things:
The result you want. Not “respond to emails” but “inbox at zero with all client questions answered by end of day.”
Why it matters. “So I can focus on product work without switching contexts.”
The action plan. The specific steps to get there.
Robbins designed this for personal productivity. But it solves the exact problem that breaks async work.
Setting Up Your RPM System
You need structure for this to work. Everything must live somewhere your VA can check without asking.
Use Notion, ClickUp, Trello, whatever. The tool doesn’t matter. The structure does.
Each outcome needs:
- Result (what you want)
- Purpose (why it matters)
- Action steps
- Owner
- Due date
- Status
- Notes
Define response times by channel:
Email: 4 hours during your VA’s work hours Slack: 2 hours Project management: 24 hours Urgent (actually urgent): WhatsApp with phone backup
Document these. Your VA shouldn’t have to guess.
Use structured messages:
Every message should have:
- Context (“Following up on the Jones contract”)
- What you need (“Draft the revised pricing section”)
- Deadline (“By Thursday end of day for Friday review”)
- Decision rights (“Use the Smith template, flag anything over $50k”)
This eliminates most questions.
Schedule weekly reviews:
One hour per week. Can be async (Loom video) or a quick call.
Cover: what got done, what blocked progress, what’s coming next.
This regular check-in catches small problems before they become big ones.
The Real Issues Nobody Talks About
Online threads about Filipino VAs mention power outages, internet problems, VAs juggling multiple jobs.
These are real. But they’re planning problems, not VA problems.
Handle infrastructure upfront:
What’s the backup plan for power outages? (Cafe, mobile hotspot, coworking space)
What about internet failures? (Second ISP, immediate notification)
How do you handle disruptions?
Many VAs work from areas with occasional power issues. That’s fine. What’s not fine is finding out after a deadline passes.
Set capacity expectations:
Some VAs work for multiple clients. Some employers want dedicated focus. Both are fine.
What’s not fine is assuming one when you agreed to the other.
Document:
- Hours per week
- Maximum concurrent clients
- Primary working hours
- Response expectations
- Process for schedule changes
If you need this to be their main job, say so upfront.
Use earned autonomy:
Start tight. As your VA consistently delivers early and communicates problems, give them more authority.
Month 1: Draft all client emails for approval
Month 2: Answer routine questions directly, escalate edge cases
Month 3: Handle full inbox except VIP clients
Trust through results, not hope.
Weekly Reviews Make Everything Work
RPM dies without regular reviews.
Set one hour per week. Can be async or a quick call.
Cover:
- What got done
- What blocked progress
- What’s coming next
- System improvements
- Any compliance issues
Monthly, go deeper:
- Results trends
- What decisions can we delegate next
- Training needs
- Infrastructure and tools
Quarterly, step back:
- Are these outcomes still the right priorities?
- Do we need to restructure?
- How’s the relationship?
This creates accountability without micromanagement. Your VA knows when results will be reviewed. You know when you’ll get updates.
Common Mistakes
Outcomes that are just tasks:
“Update the CRM” isn’t an outcome. “All new leads entered with complete information and qualification notes within 24 hours” is.
Purpose that doesn’t explain why:
“Because I said so” isn’t a purpose. “So sales can follow up while leads are warm” helps your VA prioritize.
Action plans with no decision authority:
If every action needs approval, you haven’t enabled async work. Include decisions they can make: “Approve under $50, flag above.”
No adjustment process:
Your first version will have gaps. Build adjustment into weekly reviews.
Async in name only:
Some employers give outcomes then micromanage the methods. If you’re using RPM, judge results, not methods.
Start Small
Don’t convert everything at once.
Week 1: Pick one recurring task. Write it as an RPM outcome. Share with your VA. Ask for improvements.
Week 2: Run it for a week. Track what works and what breaks.
Week 3: Review and adjust. Rewrite based on what you learned.
Week 4: Add a second outcome.
Over three months, you can convert your entire relationship. But trying everything at once usually fails.
Why Outcome-Based Management Creates Sustainable Remote Work
The real value isn’t efficiency. It’s sustainability.
Task-based work makes you the bottleneck. Every question stops progress. You can’t take vacation without things backing up.
Outcome-based work creates a system that runs without you. Your VA makes decisions because they understand the result and why it matters.
This takes time. Trust builds slowly. Documentation takes effort.
But the alternative is staying stuck. Eight-hour delays. Endless messages. Work that only moves when you’re awake.
RPM shifts the foundation from tasks (dependency) to outcomes (autonomy).
For async work across time zones, that’s the difference between constant frustration and actually getting things done.