Hourglass Remote-Work Approach
Prove remote productivity in a long trial, then expand from one reversible day
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 98%
The Hourglass Remote-Work Approach earns mobility through evidence and reversibility. The employee first tests communication systems and personal discipline, then works remotely for a relatively large block of time. During that period, the employee records concrete outputs such as billable hours, clients contacted, and projects completed. After returning to the office, the employee presents the productivity comparison and proposes only one remote day per week as a reversible experiment. A midweek day reduces the impression that the request is merely for a long weekend. The shape resembles an hourglass: begin with a large remote period, narrow back to a small recurring allowance, and then expand again as remote productivity becomes demonstrably stronger.
Origin
Ferriss developed the approach from a case study of a lifetime employee who wanted enough mobility to spend time with his fiancée in China.
Core principles
- 01Test the technical and personal requirements before making the request
- 02Gather objective evidence during a substantial remote period
- 03Propose a small reversible arrangement rather than a permanent change
- 04Use productivity data to reduce the manager's perceived risk
- 05Expand mobility only after the initial arrangement works
How to run it
- 1
Prove the setup
Test remote communications, routing, access, and personal discipline before leaving the office. Resolve failures without risking ordinary work.
Pro tip The case-study employee worked Saturdays for about three weeks to test the arrangement.
Watch out Do not ask for mobility before proving that the work can continue.
- 2
Run a long trial
Complete a substantial period outside the office while continuing to work. Treat it as an experiment rather than unmeasured time away.
Pro tip Frame a necessary absence around how the work will continue, not merely whether absence is permitted.
Watch out Ferriss's case-study excuse should not be read as permission to make deceptive claims.
- 3
Collect the evidence
Track comparable outputs throughout the remote period. Use measures the manager already recognizes, such as completed projects or billable work.
Pro tip Prepare the comparison before returning to the office.
Watch out A claim of feeling more productive is weaker than measured work.
- 4
Narrow the request
After returning, request one remote day each week as a reversible test. Choose a day in the middle of the week and explicitly preserve the manager's ability to change course.
Pro tip Use the puppy-dog close: let the manager try the arrangement without accepting permanence.
Watch out A permanent all-at-once request makes refusal easier.
- 5
Expand through results
Continue producing stronger measurable results remotely and use that evidence to seek additional mobility over time.
Watch out Expansion without sustained results undermines the original proof.
In the wild
A lifetime employee tested his remote setup over several Saturdays, then worked for two weeks from China while routing support calls to his fiancée's phone. He returned with data showing more billable hours, client contacts, and completed projects, and asked to try one remote day per week.
→ A long remote proof period supported a low-risk recurring mobility request.
Common mistakes
Requesting permanence first
Ferriss says a permanent change invites refusal, while a one-day reversible test lowers perceived risk.
Relying on subjective productivity
The case study used billable hours, client contacts, and completed projects to support the proposal.
Choosing a long-weekend day
A midweek starting day is less likely to look like an attempt to create a three-day weekend.
Is it for you?
Best for
Employees whose work can be measured and performed remotely but whose organizations are reluctant to grant broad flexibility upfront.
Not ideal for
Roles that require physical presence or employees who cannot demonstrate reliable remote performance.
From the transcript
“So, he used what I call the hourglass approach to to earning his mobility.”
“It's called the hourglass approach because you start with a large period outside the office, you come back in and then you you balloon back…”
“If you propose a permanent change, your boss is going to say no. Just one day per week, let's try it out.”
From the episode
#548: The Lost Presentation That Launched The 4-Hour Workweek — “Secrets of Doing More with Less in a Digital World” from SXSW 2007