Skip to content
Published on

Working Hard Matters, But Working Well Matters More — Balancing Effort and Leverage

🇰🇷KO🇺🇸EN🇯🇵JA
Split View필사 모드
Authors

Opening — The Person Who Stayed Latest

I want to start with the most diligent colleague I met at my first job. Let me call him J. J arrived first every morning and left last every evening. If the office lights were on over the weekend, it was almost always J. Nobody ever doubted his effort.

Yet a year later, the person who got promoted was not J. It was another colleague, K, who left on time and even seemed to have spare time. At first I thought it was unfair. Only later did I understand the difference between them.

J handled incoming work in order, quickly and accurately. K looked at the same incoming work and always asked one question: "Will I have to do this again next time? If so, is there a way to do it just once and be done?" K turned repetitive manual tasks into scripts, wrote down answers to frequently asked questions, and handed off work that did not require him specifically to the right people.

This essay is not about telling you to stop working hard. Quite the opposite. Effort is still the starting point of everything. But effort alone hits a wall at some point, and the key to going beyond that wall is leverage. We will also look, with a balanced eye, at the common trap of falling back into overwork in the name of "working well."

Why Effort Alone Falls Short — The Limit of Linearity

The defining feature of effort is that it is linear. Work one hour and you get one hour's worth of output. Work twice as much and you get twice the result. The problem is that our time is fixed at 24 hours a day.

Let's do some simple arithmetic. Someone who works 8 hours a day and stretches to 12 is working 50% more. Push to 16 and that's double. But beyond that is physically impossible. In other words, there is a clear ceiling on the output you can produce through pure effort.

The ceiling of effort-based output

Output
  ▲
  │                    ┌─── physical ceiling (24h/day)
  │              ┌─────┘
  │         ┌────┘
  │      ┌──┘
  │   ┌──┘   ← grows in proportion to effort (linear)
  │ ┌─┘
  └─┴────────────────────────────► hours invested

Leverage, by contrast, is nonlinear. Code written once costs no additional effort even if it runs ten thousand times. An article written once is the same whether 100 or 100,000 people read it. A colleague taught once goes on to do the work alone. One input, ever-growing output — that is the essence of leverage.

Let me address a common misunderstanding here. "So is effort meaningless?" Not at all. To build leverage, you first need the experience of doing the work by hand. You can only spot a repeating pattern after doing the task several times, and you can only write something good after understanding a field deeply. Effort is the raw material of leverage. Leverage without effort is an empty shell; effort without leverage is a hamster wheel.

Four Forms of Leverage

Naval Ravikant divides the leverage that creates wealth and influence into labor, capital, and "things with near-zero cost of replication." That last category is exactly code and content. Adding delegation through people and automation through tools, let me lay out four forms you can use in daily life.

1) Code — Write Once, Run Infinitely

The most powerful leverage. Turn a 30-minute daily manual deployment chore into a script, and that script works the same while you sleep and while you're on vacation.

# Capture a deploy check you used to do by hand into code once,
# and from then on a single command stands in for 30 minutes of a person's time
./deploy-check.sh staging
# - confirm tests pass
# - confirm no unapplied migrations
# - confirm no missing environment variables
# - confirm the health-check endpoint responds

The key is to treat "I'm repeating this task three or more times" as a signal to consider automation.

2) Content — Explain Once, Everyone Reads

Have you ever spent an hour answering the same question to three people separately? Write that answer down once, and from then on the same question is settled with a single link. Articles, videos, courses, and internal wikis all follow the same principle.

CategoryEffort-based responseContent leverage
Helping 1 person10 min0 min (link)
Helping 100 people1000 min30 min upfront, then 0
When you're awayImpossibleWorks fine
Quality consistencyVaries each timeAlways identical

3) Delegation — Focus on What Only You Can Do

Delegation is not simply offloading work. It is asking, "Is there someone who can do this better than me, or at least well enough?" The inner voice of people who can't delegate usually says two things: "It's faster if I do it" and "I'm anxious handing it to someone else." Both are true in the short term but make you a bottleneck in the long term.

4) Automation — Hand Machines the Work People Shouldn't Do

Similar to code but broader. Scheduled sends, alert automation, recurring report generation, and workflow connections built with no-code tools all belong here. The key skill is the eye to identify "repetitive work that requires no human judgment."

Leverage selection guide

Does this work repeat?
   │
   ├─ Yes → Does it need human judgment?
   │          ├─ No  → Automation / code
   │          └─ Yes → Is the answer the same each time?
   │                     ├─ Yes → Content (documentation)
   │                     └─ No  → Consider delegation
   │
   └─ No → Just do it once and be done

Priorities and Impact — What You Do Comes First

There is a question that must come before leverage: "Is this work worth doing at all?" No matter how efficiently you do it, nothing is more hollow than doing well something that didn't need doing.

Here the concept of impact matters. Impact can be roughly broken down like this.

Impact ≈ (importance of the work) × (the difference you make) × (number of people affected)

The same hour can yield results 10x or 100x apart depending on where you spend it. Let me organize it with the familiar Eisenhower matrix.

UrgentNot urgent
ImportantDo it now, yourselfPlan and invest (the leverage zone)
Not importantDelegate or automateDrop it decisively

Most people live trapped in the top-left (urgent + important). What actually changes a life is the top-right (important but not urgent). Building automation scripts, organizing documentation, mentoring juniors — all get postponed because they aren't urgent, yet these are exactly the investments that buy your future time.

Efficiency vs Effectiveness — Going Fast vs Going the Right Way

Peter Drucker drew a famous distinction. Efficiency is "doing things right," and effectiveness is "doing the right things."

Driving a fast car down the wrong road is efficient but not effective. The faster you go, the farther you get from your destination. This is exactly the trap the effort-driven person falls into: sharpening tools, raising speed, increasing throughput — while never asking, "Is this direction right?"

Let me show the difference with a real dialogue.

[Efficiency-centered thinking]
Member: It took 3 days to automate this report, and now it takes 5 minutes!
Lead:   That report — who looked at it last quarter?
Member: ... Honestly, nobody did.

[Effectiveness-centered thinking]
Member: Nobody seems to read this report, so I propose retiring it.
        Instead, what if we build a dashboard with the 3 metrics people actually ask about?
Lead:   Now that's something worth automating.

Order matters. First ask "is it the right thing" (effectiveness), then ask "how do we do it well" (efficiency). Flip that order and you get the tragedy of doing the wrong thing flawlessly.

The Busyness Trap — Confusing Motion with Progress

The most dangerous illusion is "busy = doing well." Busyness is often a form of laziness. Too lazy to think about what truly matters, you hide inside busyness, knocking out whatever is in front of you.

You have to distinguish motion from progress. Attending meetings, replying to email, answering Slack — these are motion. Hectic, but not necessarily tied to results. Progress, by contrast, is the act of actually getting closer to a goal.

Try these self-check questions.

  • What did I spend the most time on today?
  • Was that work motion, or progress?
  • If I could finish exactly one thing today, what would I have chosen?
  • Did I actually spend time on that one thing?

I once measured satisfaction by the "count" of tasks finished in a day. Crossing off 30 small items felt great. But looking back, only 2 or 3 of those 30 truly mattered; the rest could have gone undone. From that day, I built the habit of deciding the day's "One Thing" each morning and starting there.

Habits of People Who Work Well

Here is what I've found in common among people praised as "good at their work," from long observation. It's reassuring that this looks more like habit than innate talent.

  1. They pause before starting. Instead of diving straight in, they spend even 10 minutes picturing "the purpose of this work and what done looks like."
  2. They treat repetition as an enemy. The moment they do the same thing a third time, they feel discomfort and think of automation or documentation.
  3. They ask good questions. Before "how do I do this," they confirm "do I even need to do this, who should do it, and what's the real deadline?"
  4. They know how to stop at 80%. They don't pour 100% into everything; they ration effort by importance.
  5. They protect their own time. They deliberately carve out uninterrupted focus (deep work).
  6. They help others grow. They know teaching ultimately grows their own leverage.

If you can start even one of these today, that is the real beginning of change.

A Practical Checklist

Concrete action beats abstract resolve. These are items you can apply next week.

  • Find one task you repeated three or more times this week, and automate or document it.
  • Each morning, write down "the most important One Thing today," and touch it before anything else.
  • Decisively delete one "not important, not urgent" item from your to-do list.
  • Pick one task you can hand off, and actually delegate it.
  • Document one frequently asked question, and answer it with a link from now on.
  • Block one hour of uninterrupted focus time on your calendar in advance.
  • Once a week, reflect on "what I did this week that didn't need doing."

Guarding Against Overwork — Don't Break Yourself to Work Well

If you've read this far and resolved to "be more efficient and get more done," please pause. The real purpose of this essay is not to make you work more, but to find the path to bigger results with less work.

The ultimate purpose of leverage is to buy back time. If you refill the 30 minutes saved by automation and the two hours freed by delegation with yet more work, you've put the cart before the horse. That time should go to resting, thinking, and being with people you love.

Christina Maslach, an authority on burnout research, describes burnout along three axes: emotional exhaustion, cynicism, and reduced sense of efficacy. The striking part is that the most diligent, responsible people are the most vulnerable to burnout, because they believe they can grind themselves down without limit.

Please remember: results that aren't sustainable aren't real results. If you sprint for a month and lie sick for two, you will never beat the person who leaves on time and keeps going steadily. The last piece of "working hard matters, but working well matters more" is exactly this: taking good care of yourself is part of "working well."

Coming back to J and K, the real reason K shone was not that he had free time, but that he knew how to convert effort into leverage — and could run a long time on the energy he saved.

Closing

Effort is the starting point, leverage is the lever that sends that effort far, and self-care is the fuel that sustains the journey. Drop any one of the three and the balance collapses.

You don't need to change everything today. Pick just one item from the checklist above — the most approachable one — and start. The breathing room created by one small lever will gift you the time to build the next one. Slowly but solidly, may you move from someone who works hard to someone who works well.

References

Discuss on Twitter • View on GitHub