You Build Purpose at Work, You Don't Find It

Most "find your purpose at work" advice ends in the same place — a thought exercise about your core values. That exercise is real, but it's the first 10% of the work, not the whole job.

In the previous post I unpacked what purpose at work even is — three orientations, three measurable facets, eight sources. This post is the action half. Once you accept that purpose is a portfolio rather than a destiny, one question lands hardest: who actually builds the portfolio — the individual, the team, or the organization?

The thesis I want to defend: purpose at work gets built, not found, and the building happens at three layers — what you do for yourself, what your team does together, and what the organization makes structurally possible. Most popular advice stays stuck at layer one, but the strongest evidence I came across — Wrzesniewski's hospital cleaners, Twitter's Purpose Statement Workshop, and Imperative's 2022 Workforce Purpose Index — points to layer two doing the heaviest lifting.

That mirrors the three-levels structure from the four-pillar overview — but the "where the leverage is" answer is more specific for purpose than for the other pillars.

Three layers, in order — because skipping one tends to break the others.

Layer 1: the personal moves — reflect, align, remind

Dacher Keltner, in his Berkeley lecture on cultivating purpose, gives three personal moves the literature converges on. They're simple. They're also where most "find your purpose" articles stop.

Reflect on your core values. Take time, on a real cadence — not just at quarterly review season — to write or talk about what you actually value. The reflection isn't useful as performance; it's useful because most people have never had to pin their values down in concrete sentences, and the act of pinning surfaces the gaps.

Align your work with those values. When you have choice over which projects to take on, which roles to volunteer for, or how to frame the work you already have, choose the path closest to your core values. If you value advancing knowledge, gravitate toward projects with a learning curve. If you value serving others, pick the work where the contribution is concrete and visible.

Remind yourself — and others. Talk explicitly about the meaning of your work. To your team. To collaborators. The reminding isn't bragging; it's the maintenance work that keeps the values-to-action arrow alive across the inevitable bad weeks.

These three are real. They're also famously the things people don't sustain on their own, which brings us to the layer where most of the action actually lives.

Layer 2: job crafting — the hospital cleaner who said "it's not part of my job, but that's part of me"

The cleanest evidence that purpose can be built inside an unchanged job description is Wrzesniewski and Dutton's hospital cleaner study with Gelaye Debebe. They went into a university hospital expecting to find a low-meaning, low-skill job, and found a puzzle instead.

Roughly half the cleaners they interviewed described the work the way an outsider would — low-skill, replaceable, "exactly the same as the cleaning you do at home, you could come in and do my job tomorrow." The other half described the work as highly skilled, requiring years of training. Same role. Same shifts. Same units. Same management.

The puzzle resolved when Wrzesniewski and Dutton looked at what each group was actually doing.

The first group performed the job as written — cleaning patient rooms and public areas, following the rule that they shouldn't engage with patients or visitors unless asked.

The second group was doing a different job entirely. They tracked which patients hadn't had visitors and doubled back to spend extra time in those rooms. They walked the elderly parents of patients all the way through the labyrinthine hospital back to their cars so the patient wouldn't worry about their family getting lost. One cleaner on a long-term rehab floor — a unit where many patients arrived comatose — quietly rotated the artwork on the walls every few days. When the researchers asked her if this was part of her job, she said:

It's not part of my job. But that's part of me.

When asked what her role was, she answered: "I'm a healer." Her job, as she described it, was to create sterile spaces where patients could heal, and to do whatever else she could to help that healing along.

What Wrzesniewski and Dutton called this is job crafting — the active redesign of tasks, relationships, and interactions inside an existing job description, in ways that change the meaning of the work for the person doing it. Job crafting shows up across health care, education, for-profit, nonprofit, and at every level of an organization. It isn't reserved for jobs that already feel meaningful.

The reason this lands at layer 2 and not layer 1: job crafting is hard to do alone. It needs at least the implicit permission of teammates and the explicit non-blocking of management. The cleaners weren't operating against their managers — they were operating quietly outside what their managers had specified. That requires a team where the act of crafting doesn't get reported as "not following procedure."

Layer 2 again: Twitter's 140-minute Purpose Statement Workshop

Team-level purpose work doesn't have to stay theoretical — Twitter built a workshop with three hard-coded constraints, and the constraints are what made it ship. Brad Wolfe's Greater Good profile of Niki Lustig — who led Twitter's Learning and Organizational Development team — walks through it end-to-end.

The setup mirrors Twitter's own product constraint. Tweets were 140 characters, so:

• The pre-work survey takes each person exactly 10 minutes.
• The workshop runs exactly 140 minutes.
• The final team purpose statement comes in at 140 characters or fewer.

The pre-work is a 9-question survey at three levels:

Before the workshop, every team member reads every other team member's answers. Lustig's reported observation is that this single step — reading why your colleagues took the job in the first place — generates more shared purpose than the workshop itself.

Even though we encounter challenges and frustrations, remembering why we came here and what we set out to do, and hearing it from peers and colleagues, is so inspiring. — Niki Lustig

In the 140 minutes, the team consolidates their answers into a single 140-character statement. Lustig's own team's distillation:

Setting Twitter up for Success, Setting Tweeps up for Life: Designing opportunities to grow + learn everyday. here. and in the world.

The workshop had been run with over 120 employees at Twitter at the time of Wolfe's reporting. The piece I want to underline isn't the statement itself — most teams could write something similar in an afternoon. The piece is that the workshop is engineered at the team level rather than the company level, and the engineering choices (140-minute hard cap, 140-character cap, peer-to-peer pre-reading) are what make it ship.

Why team-level beats company-level

Most organizations stop at a single, monolithic company-wide purpose statement. The research suggests that's the wrong unit of observation.

Olivia Kiriakidou and Lynne Millward, at the University of Surrey, studied organizational identification and found that members of separate divisions or functional departments hold distinct sub-organizational identity beliefs, internalized at different levels and in different degrees. The "we" that resonates inside the engineering org isn't the same "we" that resonates inside customer support. Their conclusion is that managers should not try to bolster commitment by presenting employees with monolithic, top-down identity solutions. Instead, the work has to happen closer to where employees actually are — bolstering identity around their own teams and divisions.

That's the structural reason Lustig's workshop runs at the team level. Each team writes its own statement. They don't all write the same one.

The risk most companies take by stopping at the corporate-poster level is investing in something that signals values without doing the per-team work that makes those values operational.

Layer 3: the relational infrastructure most companies haven't built

87% of workers want to invest more time in workplace relationships, and only 13% don't — which means the gap at layer 3 is supply-met but infrastructure-missing. Imperative's 2022 Workforce Purpose Index, conducted in collaboration with NYU, PwC, LinkedIn, and the University of Michigan, surveyed 517 full-time US employees at companies with 1,000+ employees, and the headline finding is that the largest gap in workplace relationships is in supportive and purpose-generating connections.

Read the right column from top to bottom. As you move from task-related to purpose-related to personal-support relationships, the unmet share grows. Companies are best at the relationship type closest to the immediate work, and worst at the one furthest from it.

The barriers from the same survey:

• 73% — not feeling comfortable initiating a relationship
• 65% — lack of space for meaningful interactions
• 64% — not knowing who I should meet
• 60% — not having the skills to develop deeper relationships

Most of these are structural. Knowing who to meet is an org-design problem. Lack of space is a calendar and policy problem. Comfort initiating relationships is partly individual but mostly about whether the culture has rituals that bridge the first awkward conversation. Skills can be taught.

The manager gap reads even sharper. 53% of employees say their manager does not help them build a sense of purpose at work, 51% say their manager doesn't provide personal support, and 57% say their manager doesn't help them build their internal network at all.

Joseph Coughlin makes the longer historical version of this argument in The Longevity Economy: the institutions that once let workers "simply be in society" — religious organizations, fraternal orders, single-job careers, defined-benefit pensions, the extended-family Sunday dinner — have weakened steadily since midcentury, and nothing has been built to replace them at the layer where purpose-generating relationships actually form. The Imperative gap isn't a 2022 anomaly; it's the current shape of a 70-year structural arc. Layer 3's job, in that arc, is to rebuild the infrastructure those institutions used to provide — at the unit where it actually forms, which means around teams, not around the whole org.

The other Imperative number worth holding: those workers want, on average, 2.5 additional hours per week of relationship time at work. Supply is real. Infrastructure is what's missing.

That, more than the personal moves at layer 1, is where layer 3 has work to do — not designing inspirational posters, but designing the rituals, calendars, and matchmaking that let the relationships at the bottom of the table actually form.

"But isn't this just engineered enthusiasm?"

Before pulling the layers together, the strongest counter is worth taking seriously. Stanford's Jeffrey Pfeffer, in Dying for a Paycheck, argues that purpose programs and culture initiatives often act as cover for unfixed structural problems — long hours, unsafe demands, inequitable pay. Workshops on team purpose, on Pfeffer's reading, can dress up an exploitative workplace as a meaningful one.

That's a real concession, and the answer is not to choose between them: investing in purpose layers is not a substitute for fixing the conditions, and the right move is to do both.

There's a sharper version of the objection, though. Can purpose actually be engineered at the team level, or does the very act of engineering hollow it out?

Two pieces of evidence push back on the strong form.

Wrzesniewski and Dutton's hospital cleaners weren't engineered. Half the cleaners crafted the job toward meaning without management's knowledge. The crafting was bottom-up. What the team layer adds is the implicit permission and the explicit non-punishment when crafting departs from the formal job description. That's not engineering meaning into existence — it's removing the structural blockers that prevent meaning from being crafted.

Twitter's workshop also doesn't manufacture meaning out of nothing. It surfaces the meaning each person already brings, makes it visible to teammates, and consolidates the overlap into something the team can act on. Reading colleagues' answers to "what gets you out of bed every day to come to work?" doesn't manufacture intrinsic motivation. It just surfaces what was already there.

The honest version: layer 2 is not a substitute for fair pay, sane hours, or safe conditions, and treating it as one is precisely the failure Pfeffer names. Layer 2 is a complement — it lets meaning that's already in the room actually circulate.

Three layers, where the leverage is

A clean way to read the three layers: layer 1 is necessary but rarely sufficient, layer 2 is where the most movement happens, and layer 3 is what makes layer 2 possible. Most popular content lives at layer 1. Most actual-leverage work lives at layer 2. Most missing infrastructure lives at layer 3.

If I'm honest, my own version of "purpose at work" used to sit almost entirely at layer 1. Reading these studies redistributed it. The next time I find myself doing the values-reflection exercise alone in a notebook, the question I want to be asking is: whose else's notebook am I reading, and which structural blocker is keeping it the case that none of us has read each other's?

A few things I'm taking away

• Purpose at work is built, not found — and the building happens at three layers: you, your team, and your organization
• Keltner's three personal moves (reflect on values, align work with them, remind yourself and others) are real but rarely sufficient on their own
• Wrzesniewski and Dutton's hospital cleaner study showed that half the cleaners had quietly job-crafted their roles — including the woman who said "it's not part of my job, but that's part of me"
• Job crafting depends on team-level permission as much as on individual initiative — without it, crafting reads as deviation from procedure
• Twitter's 140-minute Purpose Statement Workshop does most of its work in the pre-reading step, where teammates see why each other came to the company in the first place
• Kiriakidou and Millward's research argues that monolithic, top-down purpose statements miss the point — sub-organizational identities are real, and resonance lives at the team level
• Imperative's 2022 Workforce Purpose Index shows the unmet share of relationships grows as you move from task-related to purpose-related to personal-support — companies are worst at the relationships closest to meaning
• The strongest counter — Pfeffer's "engineered enthusiasm covers for unfixed conditions" — is right that purpose work isn't a substitute for fair pay and sane hours, but the team-layer evidence shows it surfaces existing meaning rather than manufacturing it
• Layer 2 is where the leverage is, but layer 3 is what makes layer 2 possible — without permission and infrastructure, even motivated teams can't sustain crafting

The line that stays with me is the cleaner's: it's not part of my job, but that's part of me. Most of the conversations I've had about purpose at work were a loop of layer 1 — me asking myself what I value. The shift she points to is that the meaning of the work isn't a fact about the job description. It's a fact about who you decide to be inside it, and whether the people next to you make it possible to keep deciding that.

If you're a manager and you take only one thing off this post: run the Twitter pre-reading step on your own team this quarter. Nine questions, ten minutes per person, and everyone reads everyone's answers. The workshop is optional. The pre-reading is where the move actually happens.

Sources

• Keltner, D. — Lecture: "Cultivating Purpose at Work," Science of Happiness at Work, BerkeleyX. Used for: the three personal cultivation moves (reflect, align, remind)
• Wrzesniewski, A., & Dutton, J. E. — Crafting a Job: Revisioning Employees as Active Crafters of Their Work, Academy of Management Review 26(2), 179–201 (2001). Used for: the job-crafting concept and the structural framing
• Wrzesniewski, A., Dutton, J. E., & Debebe, G. — University hospital cleaner case study (Yale / Michigan / Vanderbilt collaboration). Used for: the "I'm a healer" cleaner anecdote and the bottom-up crafting finding
• Wrzesniewski, A. — Yale School of Management lecture, "On Job Crafting." Used for: the broader claim that job crafting shows up across occupations and at every level
• Wolfe, B. — Can Higher Purpose Help Your Team Survive and Thrive?, Greater Good Magazine. Used for: the Niki Lustig / Twitter Purpose Statement Workshop walkthrough and quoted statement
• Lustig, N. — Twitter Learning and Organizational Development. Used for: the 140-minute / 140-character / 9-question workshop design and the team statement quoted
• Kiriakidou, O., & Millward, L. J. — Research on sub-organizational identity at the University of Surrey. Used for: the argument against monolithic top-down purpose statements and the case for team-level identity work
• Imperative — 2022 Workforce Purpose Index: The Relationship Imperative, in collaboration with NYU, PwC, LinkedIn, and the University of Michigan. Used for: the relationship-gap table, the barrier list, the manager gap, and the willingness-to-invest finding
• Pfeffer, J. — Dying for a Paycheck (Stanford GSB). Used for: the steelman that purpose programs can mask unfixed structural problems
• Coughlin, J. F. — The Longevity Economy: Unlocking the World's Fastest-Growing, Most Misunderstood Market (Hachette, 2017), ch. 8. Used for: the institutional-collapse arc that frames Layer 3 as the current shape of a longer structural decline
• Steger, M. F., Dik, B. J., & Duffy, R. D. — Measuring Meaningful Work: The Work and Meaning Inventory (WAMI), Journal of Career Assessment 20(3), 322–337 (2012). Referenced for: the previous post's measurement model that the layer-2 evidence here builds on
• Greater Good Science Center, UC Berkeley. Used for: the editorial framing of purpose as a structurally cultivable construct