LLenny's Podcast
← All frameworks
Peak PerformanceFarhan Thawar (VP and Head of Eng)

Calories Per Hour: Intensity Over Hours

Get more done per minute instead of working more minutes, then go home.

Difficulty
Moderate
Time to result
~weeks to results
Steps
3
Confidence
85%

A productivity philosophy that reframes intensity as output-per-unit-time rather than total hours worked. Since an hour is a fixed quantity, the lever is how many 'calories' you expend within it. Compressing work into a focused window lets you achieve extraordinary output without expanding into 12-hour days, freeing the rest of your life.

Origin

Thawar's personal belief, contrasted against a company where he worked 12-hour days that were padded with foosball and coffee breaks. He invokes Parkinson's Law ('work expands to fill the time allotted') as the underlying mechanism.

Core principles

  • 01One hour is one hour; the only variable you control is how much you get done inside it.
  • 02Whatever time you allot to a task is the time it will take (Parkinson's Law), so allot less.
  • 03Truly excellent people produce high-quality output in a fraction of the time a merely-good person needs, so speed need not cost quality.
  • 04Compressing work into the workday buys back life outside it, rather than expanding work to consume the evening.

How to run it

  1. 1

    Reframe the goal from hours to output-per-hour

    Stop measuring effort by time spent. If two people both work 9-to-5, the one who expends more calories in that window simply gets more done in the same elapsed time. Make 'more per minute' the explicit target.

    Pro tip The payoff is life outside work: get more done in the day so you can take your kid to soccer instead of extending the day to 12 hours.

  2. 2

    Deliberately shrink the time box

    Apply Parkinson's Law in reverse. For a task a good person would stretch over a long period, give a great person one hour and expect a high-quality result. Compress deadlines to 2-3x faster without materially dropping quality.

    Pro tip A reorg that takes six months at most companies is done in a week or two at Shopify by sitting down, sketching the bones, and launching before it can leak.

    Watch out Don't confuse this with the false economy of padding the day; foosball and coffee breaks are how a compressible 8-hour day balloons into 12.

  3. 3

    Use forced focus to raise the calorie count

    Structure work so multitasking is impossible (see pair programming). Removing internet and Slack distraction is what lets two focused people out-produce more distracted individuals.

In the wild

The one-to-two-week reorg

Where most companies run a six-month change-management roadmap for something like a reorg, Shopify sketches the bones, brings in a few people, then launches it in a week or two and communicates it after the fact ('this is a volatile company, this is what's happening').

Change lands fast; the company avoids the speed penalty of drawn-out change management and keeps delivering value to merchants.

Common mistakes

Letting work expand to fill available time

Parkinson's Law means whatever time you allot to a task is the time it takes. Padding the day with breaks and long meetings turns a compressible 8-hour day into a bloated 12-hour one with the same output.

Assuming more hours equals more results

The common advice is 'work more hours when you're young.' Thawar's counter is 'what if you just did more per minute?' Total hours is the wrong metric; intensity within the hour is the lever.

Is it for you?

Best for

Teams and individuals whose culture equates long hours with commitment and who want higher output without burnout.

Not ideal for

Genuinely exploratory, pathfinding work where the answer is unknown and forced compression could push a premature, wrong solution.

From the transcript

what if you just did more per minute

00:00

if I just expend more calories in that hour

20:00

whatever time you allot to something will be the time it takes

31:00

From the episode

How Shopify builds a high-intensity culture

Farhan Thawar (VP and Head of Eng)