Meaning at Work: When the Company Can't Supply It, How You Make Your Own
Topic: Meaning at Work·4 Principles
"Those who have a 'why' to live can bear with almost any 'how'." — Nietzsche, quoted by Viktor Frankl
This week's thesis: at your level, what wears people down is usually not difficulty but meaninglessness—a reorg that erases your team's mission, six months on a compliance migration nobody reads, being flat-out busy yet unable to say "who did I create something for?" The self-help line is "find your passion," as if meaning were treasure buried somewhere waiting to be dug up. This week rejects that metaphor: meaning is not discovered, it is constructed. Four tools: diagnose with the three sources where meaning is actually missing, handle "bullshit-job" moments without self-deception, rewrite your role through job crafting, and—most fundamentally—stop outsourcing your meaning to the company, a client that can change anytime. Honesty first: some roles are structurally short on meaning; this week won't pretend every job can be reframed into a calling.
PRINCIPLE 01
The Three Sources: Autonomy, Mastery, Purpose—Diagnose Which Is Missing
Autonomy · Mastery · Purpose — Diagnose Which One Is Missing
Three sourcesDiagnosisDrive
The Principle in One Line
"It's meaningless" is a symptom, not a diagnosis. Break it into three sources—autonomy (can I call my own shots), mastery (am I getting stronger), purpose (who is this useful to)—and one question tells you which is missing. The three deficits call for completely different prescriptions.
In Their Words
"Human beings have an innate drive to be autonomous, self-determined, and connected to one another. And when that drive is liberated, people achieve more and live richer lives."— Daniel Pink, Drive, Part Two
Three-Source Diagnostic
Scene
Setup: a senior engineer says in a 1:1, "Lately I'm just hauling bricks, it's meaningless." That sentence tells you nothing.
✗ Straight pep talk
"What you do really matters, it's a huge contribution to the company, hang in there." — You haven't heard what's missing, and you've handed him nothing actionable. He won't level with you next time.
✓ Probe each of the three sources
"I want to figure out which kind of 'meaningless' this is. One—someone else dictates how you do it and you have no room (autonomy)? Two—it's too familiar, you're not getting stronger (mastery)? Or three—you don't know who this work helps (purpose)?"
(He says "mostly the second, I could do it with my eyes closed.") "Then this is a mastery problem, not an attitude problem. Next quarter I'll give you something you haven't touched—mentor a junior to multiply your leverage, or take on that real-time pipeline neither of us knows. You pick."
Diagnostic Checklist (for yourself or a report)
Autonomy: over the past month, how many calls did I make myself vs. were approved/assigned to me?
Mastery: can I name one new skill I learned this year? Or am I living off what I learned three years ago?
Purpose: can I name the specific "who" whose week got better because of my work?
Which of the three scores lowest? That's the one to act on—don't pile more onto the high-scoring ones.
Common Mistakes + A Note for Women
Patching all three at once. A meaning gap is almost always just one or two. Blindly "giving autonomy AND adding challenge AND preaching vision" hits nothing.
Treating purpose as a vision pitch. Purpose isn't a mission slide; it's "my code saved that support agent two hours of overtime"—a touchable connection.
Plugging meaning with money. A raise can briefly mask any of the three, but Pink's core point is exactly this: external rewards can't replace internal drive—once the money's spent, the gap remains.
Female Leader's Note
Women are more often assigned "office housework" (note-taking, coordinating, organizing events)—work high on "purpose" but low on "mastery," which keeps you in place while looking "very engaged." When diagnosing reports (women especially), don't be fooled by high compliance: compliant ≠ growing. Ask the mastery question directly: "Which of these makes you more valuable three years from now?"
This Week's Exercise + Reflection
Action: score your current role 1–5 on autonomy/mastery/purpose. Fix your eyes only on the lowest, and write one concrete change you can make this month. Reflect: last time you felt "it's meaningless," which one was actually missing—and did you patch the wrong one?
PRINCIPLE 02
Bullshit-Job Moments: Tell "Pointless" From "Hard"—No Self-Deception, No Grinding On
Bullshit-Job Moments — Tell Pointless From Hard
Bullshit JobsHonestyMinimum input
The Principle in One Line
Not everything that pains you "carries deep meaning." Some tasks are simply pointless—compliance theater, filling in cells of a report no one reads. Admitting a task is meaningless isn't slacking; it means you honestly give it the minimum necessary input and return the saved energy to what actually has leverage.
In Their Words
"A bullshit job is a form of paid employment that is so completely pointless, unnecessary, or pernicious that even the employee cannot justify its existence."— David Graeber, Bullshit Jobs, Ch.1
Scene
Setup: compliance requires every team to file a monthly "risk self-assessment," and in three years you're certain no one has read one. A report complains it's pure waste.
✗ Pretend it has meaning
"This is actually important, it shows we care about quality, fill it in seriously." — The team knows you're saying something you don't believe; from now on all your "this is important" credit is discounted, including the things that truly are.
✓ Honest tiering + minimum input
"I agree this form probably goes unread—it's a compliance paper-trail ritual, not real risk management. So: 15 minutes, ship it, no gold-plating. I'll build a template; copy it and change three lines."
"Real risk review happens in our monthly incident review—that one I need you to take seriously. Save your energy for there." (Meanwhile I'll ask compliance: can it be quarterly, can it be auto-generated—cut it if we can.)
"Is This a Bullshit Job?"—Four Questions
If this stopped next month, who'd actually be affected? Can't name a specific person = danger sign.
Is it "pointless," or just "hard/dull but useful"? Don't flee the latter; don't glorify the former.
Can I kill it, automate it, or only lower the input? Try the three paths from highest cost to lowest.
Does the team's input on it match its real value? Or are we putting our hearts into a fake thing?
Common Mistakes + A Note for Women
Misjudging "hard" as "bullshit." Lots of high-value work is dull and unrewarding early on (foundations, docs, paying down debt). The opposite of honesty isn't only self-deception—it's also making excuses to avoid things.
Being a megaphone. Forwarding the pointless task from above as-is with "nothing I can do"—you've forfeited the one value a leader adds: absorbing it and reducing the cost.
Real heart into a fake thing. Perfectionism on a task you know is meaningless is the biggest hidden killer of your sense of meaning.
Female Leader's Note
Pointless "maintenance" tasks (ordering lunch, taking minutes, chasing action items) default onto women more, and the social cost of declining is higher for her. The fix isn't shouldering it alone or flatly refusing, but institutionalized rotation: put these tasks on a team-wide rota so "who does the housework" becomes a rule, not something riding each time on someone's goodwill or reluctance to say no.
This Week's Exercise + Reflection
Action: list your team's 3 weekly routine outputs; for each ask "who's affected if it stops." Pick the most bullshit-like one and this week either cut it or drop it to minimum input. Reflect: is there one thing you do to "look diligent" rather than "be useful"? For whose eyes?
PRINCIPLE 03
Meaning Is Made: Rewrite Your Role Through Job Crafting
Meaning Is Crafted — Job Crafting, Not Job Waiting
Job CraftingActive constructionThree rewrites
The Principle in One Line
Meaning isn't handed to you; you reshape it within the boundaries of your role. Three levers: change the tasks (do more of what lights you up, less of what drains you), change the relationships (more contact with people who give you energy), change the cognition (redefine what this job "is really about").
In Their Words
"We define job crafting as the physical and cognitive changes individuals make in the task or relational boundaries of their work."— Wrzesniewski & Dutton, Academy of Management Review, 2001
Scene
Setup: an engineer rotates into the quarter's on-call/platform maintenance—all firefighting and shifts—and feels his career has stalled for six months. The classic "hospital cleaner" study says: same job, some treat it as drudgery, others as part of healing.
✓ Land each of the three levers
Cognition: "Don't see it as 'shift drudgery.' Redefine: this quarter you're the guardian of system reliability—you understand best where things break. That's the most valuable hands-on experience on the SRE track."
Tasks: "Beyond firefighting, keep 20%: distill the incidents you fixed into a runbook + three automated alerts. In six months what you hand over isn't 'I did the shifts' but 'I cut the next person's pain in half.'"
Relationships: "While firefighting you're dealing with every team in the company—a network others can't build in a year. Deliberately get to know each person who comes to you."
Job Crafting Three-Lever Worksheet
Tasks: this quarter, can I add one thing that lights me up and shed/delegate one that drains me?
Relationships: which two people energize me on contact? Can I create more collaboration surface with them?
Cognition: given a bigger definition, what is my work "about"? (gatekeeper / coach / translator)
Boundaries: can these rewrites happen within my current authority? (crafting is reshaping within boundaries, not demanding a transfer)
Common Mistakes + A Note for Women
Treating crafting as job-hopping. Its power is precisely that you reshape within existing boundaries—no new job, no boss's sign-off. Use up the freedom inside your boundaries first.
Only changing cognition, not tasks. Pure "think about it differently" while the actual work is unchanged is self-soothing; it fades in weeks. Cognitive reframing needs a task/relationship anchor.
Only adding, never shedding. Adding the lighting-up work without shedding the draining work just makes you more tired. Crafting must be two-way, or it's just unpaid overtime.
Female Leader's Note
"Changing tasks" has a gender trap: the tasks women add voluntarily are more often high-visibility, low-payoff support work rather than the core projects that raise your professional leverage. When crafting, calibrate deliberately—the thing you add, does it make you more valuable, or just more needed? The two are very different.
This Week's Exercise + Reflection
Action: take your least meaningful current duty and write one rewrite per lever (add/shed a task, connect a person, swap the definition); this week land one cognition and one task change. Reflect: if you redefined your work in one bigger sentence, what would you say it's "about"?
PRINCIPLE 04
Don't Outsource Meaning to the Company: Diversify the Supply
Don't Outsource Your Meaning — Diversify the Supply
Don't outsourceMeaning portfolioAntifragile
The Principle in One Line
Betting 100% of life's meaning on the mission the company hands you is a single point of failure: one reorg, one strategy pivot, and the client writes your meaning off with a stroke. Meaning supply should be a portfolio—craft, the people you grow, outside community, family—multi-sourced, so a single org change doesn't bankrupt you spiritually.
In Their Words
"Ultimately, man should not ask what the meaning of his life is, but rather must recognize that it is he who is asked. Each man is questioned by life; and he can only answer to life by answering for his own life."— Viktor Frankl, Man's Search for Meaning, Part Two
Scene
Setup: a reorg folds the project you nurtured for two years and were proud of into another department and changes its direction. You and an equally invested report both feel hollowed out.
✗ Pin all meaning on the project
"Everything we did was wasted, this company doesn't care at all." — Hidden in this is a dangerous premise: your meaning = this project's survival. Once that premise holds, any company change can destroy you. That's not the company's problem; it's that your meaning structure is too brittle.
✓ Re-anchor meaning to sources a reorg can't delete
"The project got redirected; the two years of work were real, and I'm hurting too. But I want to re-anchor the meaning: projects change, the capability I grew can't be taken from me, the people I mentored can't, and the method we worked out is still used by other teams."
"Orgs change constantly—that's normal, not betrayal. What we control is building meaning on what we can carry with us—craft, people, reputation—not on any one project that can be reorganized away at any time."
Meaning-Portfolio Checklist
What share of my sense of meaning is pinned on "the current project/title"? Over 70% = single point of failure.
List at least three independent sources: craft, mentoring, outside community/writing, family. Is each still alive?
If the project is cut tomorrow, what can't the company take? (capability, relationships, reputation, work) That's the foundation.
Do I have one meaning source that doesn't depend at all on my employer's approval? (open source, community, teaching, family)
Common Mistakes + A Note for Women
Misreading "don't outsource" as "don't invest." It's not telling you to go cold. It's precisely because you're invested that you must diversify sources—so you can throw yourself in fully without fearing loss.
Waiting for the company to hand you a vision. A vision slide is the company's answer; Frankl's core is that meaning is your answer to life, not something to wait for. Passive waiting is itself outsourcing.
Using busyness to cover emptiness. Filling the calendar is the most common way to dodge "why am I doing this." Busy ≠ meaningful—sometimes the opposite.
This Week's Exercise + Reflection
Action: draw a "meaning pie chart," slicing your current sense of meaning by source (current project/craft/mentoring/outside/family). If any slice exceeds half, water a different source this week. Reflect: if your title and project were gone tomorrow, could you still name three things that make you feel "these years weren't wasted"?
Going Deeper
Could "meaning is constructed" become a tool for employees to self-soothe and let bad organizations off the hook?
That's a real risk. "Go craft your own meaning" can degrade into management's excuse-making—structural meaninglessness (bureaucratic bloat, bad incentives, doomed projects) shouldn't be something individuals digest with mindset. So this week's stance is two-layered: for the individual, constructing meaning is agency you can take back—don't hand it all over; for the leader (you), the opposite—your job is to reduce the team's bullshit work at the source and supply real autonomy and purpose, not to toss off "go find meaning yourself." Employees shouldn't wait passively, leaders shouldn't dodge—both must hold for it to be honest.
Do the three sources carry the same weight across cultures and career stages?
No. Early in a career "mastery" weighs heaviest—meaning comes mainly from getting stronger; senior, it shifts to "purpose" and "autonomy," because the skill curve flattens and drive comes from influence and control. Culturally, collectivist environments ignite people more through "purpose/connection," while individualist ones weight "autonomy" more. When diagnosing reports, don't apply your own current weighting—what a newcomer most lacks may be exactly the one you stopped lacking long ago.
Are some roles structurally unable to provide meaning? Is "construction" still useful then?
Honestly: yes. Assembly-line, tightly scripted roles where you never see a beneficiary leave genuinely little crafting room, and pretending every job can be reframed into a calling is another kind of self-help. Two more realistic paths: one, move the center of gravity of meaning clearly outside work (the Card 4 portfolio idea), demoting the job to "a means to buy freedom" rather than "a source of meaning"—that's clarity, not failure; two, acknowledge it's structurally short on meaning and start a planned exit. Recognizing "this really can't be crafted" is its own wisdom.
As a leader, how do you give a team "purpose" without it becoming empty cheerleading?
The difference is specificity and follow-through. Cheerleading is abstract, grand, forever in the future, and never tested ("we're changing the world"); real purpose is specific, touchable, and closes the loop: take an engineer to watch a real user suffer less because of their feature, read a beneficiary customer's own words in review, let the data say "that metric actually moved after launch." A sense of purpose comes from seeing your output land on a real person, not from hearing a vision speech.