Impact Driver: finding work that actually matters

Daniel spent four years at an ad tech firm optimizing bid auctions. He was good at it. He got promoted twice. On a Tuesday in March, during a routine standup, someone joked that their team's best quarter ever had helped a detergent brand sell more detergent. Daniel laughed, went back to his desk, and cried for twenty minutes in a phone booth.

He quit six weeks later. He's now a product manager at a company that builds case management software for refugee resettlement agencies. He makes 30% less. He is, by every measure he now uses, happier.

Daniel is an Impact Driver. And his story is common enough that if you recognize it, you already know the ending.

What drives them

The three values: impact, purpose, and community.

Impact in the sense of wanting your work to produce a visible, measurable improvement in someone's life. Purpose in the sense of needing to understand why the thing you're building exists at all. Community in the sense of wanting colleagues who care about the same mission, not just the same paycheck.

Impact Drivers can do high-performance work in almost any domain. The trap is that doing the work well is not the same as the work being meaningful to them. They'll burn out twice as fast in a role they find pointless than in one they find hard.

Where they thrive

The honest answer is: wherever the outcome is a person whose life got better, and the person is specific.

Specific roles:

• Program manager at a health system, foundation, or government agency
• Operations or product roles at mission-driven companies (climate tech, health tech with real outcomes, education, financial inclusion)
• Senior staff at nonprofits with operating budgets above $5M (under that, the role usually becomes fundraising, which is a different archetype's job)
• Public sector product and policy roles
• Chief of staff at a mission-first founder's company
• B-corp leadership where the mission isn't decorative

Company types:

• Mission-driven startups where the ICP is an underserved user, not a B2B buyer
• Hospital systems, universities, government agencies with real modernization budgets
• Foundations and funders that fund operating work, not just programs
• Social enterprises where the revenue model is aligned with the mission, not in tension with it

The "aligned with the mission" piece matters. A company whose profit grows when the world gets better is sustainable for an Impact Driver. A company whose profit requires the mission to be slightly compromised will eat them alive.

Where they get stuck

The first trap is "impact-washing" employers. Every company now has a mission statement. Some of them even have a slide. Very few have a business model that rewards the mission when it conflicts with revenue.

Interview for this directly. Ask: in the last year, has the team made a decision that hurt short-term revenue because it was better for the end user? If the answer is a long pause followed by a story about a feature being delayed, keep looking.

The second trap is martyrdom. Impact Drivers often accept bad compensation, bad management, and bad hours because the mission "makes up for it." It doesn't. A burned-out Impact Driver delivers less mission than a healthy one. Being underpaid is not a proof of virtue. It's a recruiting failure on the employer's side.

The third trap is the wrong scale. Some Impact Drivers need to see the person they helped. Others need to see the policy change that helped a million people they'll never meet. These are both valid, but they're different jobs. Direct service burns out the systems thinkers. Systems roles feel hollow to the direct-service people. Know which one you are before you take the role.

How to frame their CV

Impact Drivers have the hardest CV problem in the archetype set, because their natural instinct is to describe process ("ran a program that served 2,000 families") and employers want outcomes ("cut placement times from 14 to 4 months for 2,000 families, reducing emergency shelter spend by $1.8M").

Translate everything into before-and-after, for a specific population. "We helped people" is not a CV line. "We reduced the time to first appointment for Medicaid-eligible mothers in three counties from 28 to 9 days" is.

If you're moving from corporate to mission-driven work, do not apologize for the corporate years. Translate them. The ad tech person who rebuilt an ops process can use the same language at a nonprofit, and the nonprofit hiring manager will be relieved to find someone who can actually ship.

If you're moving in the other direction — from mission to corporate — lead with the scale of ambiguity you operated under. Mission-driven work almost always involves more stakeholders, less budget, and worse tools than equivalent corporate roles. That's a portable skill. Say so.

The takeaway

Impact Drivers are not trying to save the world in a grand sense. They're trying to avoid spending their working life on something they privately find meaningless. That's a much smaller and more reasonable ask than it sounds like.

If you've had a version of Daniel's phone-booth moment — or you're due for one — the question isn't whether you should switch. It's whether you can describe, in one sentence and without hedging, what problem you want to spend the next decade on.

Most people can't, and that's fine. The Values Assessment is a reasonable place to start figuring it out. The answers tend to arrive when you stop treating the question as a luxury.