LEADERSHIPWeeks to result

FedEx Days and 20% Time

Dedicate structured autonomous time for creative exploration to unlock innovation and engagement

Problem it solves

ineffective leadership

Best for

Organizations seeking to boost innovation and engagement, leaders who want to give teams creative autonomy within a structured framework

Not ideal for

Organizations where baseline trust is broken or where leadership cannot genuinely relinquish control over what people work on

Overview

Why this framework exists

FedEx Days are 24-hour bursts of autonomy where employees work on any problem they want, then present results to the company the next day -- named because you have to deliver something overnight. 20% Time extends this principle, allowing employees to spend one-fifth of their work time on self-directed projects. Both practices institutionalize autonomy over task -- one of the four T's of Type I motivation. The concept traces from 3M's 15% bootlegging policy (which produced Post-it Notes) through Google's 20% time (which birthed Gmail, Google News, and Google Translate) to Atlassian's FedEx Days and formal 20% time program. These initiatives aren't pay-for-performance plans grounded in Motivation 2.0 -- they're autonomy plans tuned to Motivation 3.0.

Core principles

6 total
  1. Autonomy over task -- choosing what you work on -- is essential for creative, nonroutine work
  2. The four T's of autonomy: Task, Time, Technique, and Team
  3. Money is only something you can lose on -- beyond adequate pay, autonomy and creative freedom matter more
  4. Constraints can enhance creativity -- the 24-hour FedEx Day deadline forces focus and delivery
  5. People are far more efficient with autonomous time than regular work time because they choose meaningful problems
  6. Trust is essential -- tracking and monitoring autonomous time undermines its motivational power

Steps

4 steps
  1. Start with a FedEx Day pilot
    Set aside 24 hours where team members can work on any problem they want, with anyone they want, using any approach they want. The only rule: they must deliver something -- a prototype, fix, hack, or concept -- at the end and present it to the group.
    Pro tipAtlassian fuels their FedEx Days with cold beer and chocolate cake at the 4 PM Friday presentations. Make the sharing session celebratory and low-pressure.
    WarningThe project must be something outside people's regular job to break them out of day-to-day patterns and unlock novel thinking.
  2. Evaluate results and build the case
    Document the innovations, fixes, and ideas that emerge from the first FedEx Day. Use these concrete outcomes to justify expanding the practice and to address skeptics who question the investment.
    Pro tipCannon-Brookes responds to CFO objections by showing a long list of delivered innovations, zero engineering turnover, and highly motivated engineers constantly improving the product.
  3. Consider expanding to 20% time
    If FedEx Days prove productive, consider giving people ongoing autonomous time -- typically 20% of their work week -- to pursue self-directed projects. This allows sustained development of ideas that can't be completed in 24 hours.
    Pro tipAt Google, more than half of new offerings in a typical year are birthed during 20% time, including Gmail, Google News, and Google Translate.
    WarningDon't track or micromanage how people spend their 20% time. When Atlassian managers wanted to monitor usage, Cannon-Brookes refused -- that level of control defeats the purpose.
  4. Institutionalize and protect the practice
    Make autonomous creative time a permanent part of the culture, not a one-off experiment. Protect it from encroachment by regular project demands and management pressure to reclaim the time.
    Pro tipAtlassian found that most employees used substantially less than 20% because they didn't want to let down current teammates -- the constraint is voluntary conscientiousness, not laziness.
    WarningWithout institutional protection, 20% time will be the first thing cut during busy periods, destroying trust and signaling that autonomy was never genuinely valued.

Checklist

Saved in your browser

Examples

3 cases
Atlassian's FedEx Days

Atlassian's engineers work through the night on self-chosen problems every quarter, presenting results over beer and cake the next afternoon. The practice produced an array of software fixes and features that might otherwise never have emerged.

OutcomeThe practice became permanent. When expanded to 20% time over a yearlong trial, developers launched 48 new projects, leading to zero engineering turnover and a continuously improving product.
3M's 15% bootlegging policy and Post-it Notes

William McKnight established a policy in the 1930s-40s letting technical staff spend 15% of their time on personal projects. Scientist Art Fry used this bootlegging time to develop Post-it Notes.

OutcomePost-its became a monumental global business with over 600 products sold in more than 100 countries. Most of 3M's major inventions emerged from bootlegging and experimental doodling periods.
Google's 20% time innovations

Google engineers spend one day per week on side projects of their choosing. Krishna Bharat created Google News during 20% time. Paul Bucheit created Gmail as his 20% project.

OutcomeMore than half of Google's new offerings in a typical year are birthed during 20% time, including Gmail, Google News, Google Talk, Google Sky, and Google Translate.

Common mistakes

3 traps
Micromanaging autonomous time
Tracking how people spend their FedEx Days or 20% time sends the message that management doesn't trust them. This converts an autonomy plan back into a control plan, destroying the intrinsic motivation the practice is designed to unlock.
Failing to protect autonomous time from regular work demands
Without institutional protection, autonomous creative time will be consumed by deadlines, client demands, and management pressure. If it disappears when things get busy, people learn that the organization doesn't genuinely value autonomy.
Expecting immediate ROI from creative autonomy
The value of FedEx Days and 20% time compounds over time through innovations, reduced turnover, and sustained engagement. Judging them by immediate short-term returns applies Motivation 2.0 metrics to a Motivation 3.0 practice.

Origin story

How this framework came to be

Australian software company Atlassian, cofounded by Mike Cannon-Brookes and Scott Farquhar, created FedEx Days to spark greater creativity. Engineers could work on anything they wanted for 24 hours, then present results over beer and chocolate cake. The concept proved so productive that Atlassian expanded to formal 20% time. The deeper roots trace to 3M's William McKnight, who in the 1930s-40s encouraged experimental doodling and let technical staff spend 15% of time on personal projects -- leading to Post-it Notes and most of 3M's breakthrough innovations.

Source

Traced to primary
Source · BOOK
Drive: The Surprising Truth About What Motivates Us
Daniel H. Pink · 2009
Open source →

Related frameworks

Browse all Leadership →