Stop Applying First: Start Mapping the Work You Want to Do
Stop Applying First: Start Mapping the Work You Want to Do
By John Crager, CMRP, SHRM-SCP | Next Shift Blog at WorkReady.works Published October 21, 2026 | ~1,500 words | 6 min read
Part 3 of a 10-part series.
Every job search starts in the same little white box.
You open a job board, click into the search field, and type a title. Probably the one on your last business card. Then you hit enter and start scrolling through whatever comes back.
It feels like the obvious first step. It's also where most searches go wrong, before a single application gets sent.
Why? Because you just handed the direction of your career to a label. And job titles are some of the least reliable labels in the working world.
Titles Lie in Both Directions
Take "project manager." At one company, that person runs a nine-figure construction program with forty direct and indirect reports. At another, the same two words describe somebody who schedules meetings and chases status updates. Identical title. Entirely different jobs, different pay, and different skills.
Now flip it. The work you do best might be called operations manager here, business process lead there, continuous improvement specialist at a third employer, and chief of staff at a startup that hasn't settled on an org chart. Four titles, one job. Search for any single one of them and you've hidden the other three from yourself.
So a title search fails twice. It shows you roles that share your label but not your work, and it hides roles that share your work but not your label. You spend your evenings tailoring resumes for the first group and never see the second.
Start With the Work
Forget the title for a minute. What do you actually do when you're at your best?
Not your duties. The problem you solve. For most experienced people it comes down to a short phrase:
- Improving the reliability of an operation that keeps breaking down
- Launching a program from nothing: a training pipeline, a new service line, a second location
- Managing a change that people are resisting
- Bringing cost and schedule discipline to projects that have neither
- Rebuilding a customer relationship that's gone sour
- Taking a team from confusion to execution
Yours may not be on that list, and it doesn't need to be. What matters is that you can say it in one line without mentioning a job title.
Three questions will get you there faster than staring at a blank page. What do people keep bringing to you, even when it isn't your job? Which piece of work would you gladly do again tomorrow? And when you look through your "Why You?" file from the last post, which results show up more than once?
That third question is the honest one. Patterns in your own evidence beat any personality quiz.
Qualified and Motivated. Both.
Here's a trap experienced people fall into. They map the work they're qualified to do and skip the second half of the sentence.
Being good at something and wanting to do it are separate facts. Plenty of professionals are superb at cleaning up other people's messes and are thoroughly sick of doing it. If you build your search around that skill alone, you'll succeed, and then you'll be back in the same search in eighteen months.
So run a simple sort. Work you're good at and want more of goes at the center of the map. Work you're good at and done with becomes a credential, not a target. And work you want but can't yet prove is a development goal, which belongs in a different plan than your job search.
Be blunt with yourself here. Nobody else is reading this list.
Now Find Who Needs It
Once you can name the work, a much better question opens up. Not "who's hiring?" but "who has this problem right now?"
Organizations announce their problems constantly. They just don't call them that. You're reading for signals:
- A growth plan or expansion announcement
- A new executive, or a leadership seat that just changed hands
- A new facility, office, or territory
- An acquisition or merger
- Public service trouble: complaints, recalls, missed deliveries, bad press
- A workforce shortage they keep talking about
- A major capital project
- A reorganization or systems overhaul
Each one creates work. Growth strains every process that was built for a smaller company. A new leader wants her own read on what's broken, usually within the first ninety days. An acquisition means two of everything and nobody sure which version survives. None of those needs will appear on a job board for weeks or months, and some never will.
Where do you find the signals? The sources are free and mostly unglamorous: company press releases, the local business journal, trade publications, earnings call summaries for public companies, and LinkedIn announcements from people who just changed jobs. Twenty minutes, twice a week. That's the whole research budget.
Keep the map simple. Three columns will do: the work you want, the signal you spotted, and the person who owns the outcome. One row per organization.
Change the Question You Ask
Mapping changes what you say when you reach out, and that's where the real payoff sits.
The standard message goes something like, "I'm exploring new opportunities and wondered if you have any openings." It asks a busy stranger to do your research for you, and the easy answer is no.
Compare it with this:
"I saw that your organization is opening a second distribution center next spring. I've spent the last eight years building scheduling and readiness plans for operations going through that kind of growth. If the ramp-up is creating planning challenges, I'd welcome a short conversation about what I've seen work."
Look at what moved. The note opens with their situation, not yours. It names specific work. It asks for a conversation and not a job. And it gives the reader something to react to even if there's no opening today, because a person who understands your problem is worth twenty minutes whether or not there's a requisition.
"Are you hiring?" has two possible answers, and one of them ends the exchange. "Here's how I may be able to help" starts a discussion.
Applications Still Have a Place
None of this means you never apply for a posted job. Postings are real signals too, and some of them are exactly the right fit.
The order is what changes. Map first, apply second. When a posting shows up at an organization already on your map, you know why they need the role, who it likely reports to, and which of your results to lead with. That application is a different document than the one you'd have sent cold at 11 PM.
And when a posting appears somewhere that isn't on your map, with a title that sounds close enough? You've got a quick test now. Does it involve the work at the center of your list? If not, let it go.
Your Move This Week
Four pieces of work, in order.
Write your one-line work statement with no job title in it. Sort your skills into the three piles: want more, done with, and still building. Pick ten organizations and spend twenty minutes looking for signals at each. Then send two outreach notes that open with the other person's situation.
Ten organizations sounds small. It's supposed to. You'll learn more from ten you understand than from two hundred you clicked on.
The Bottom Line
A title is somebody else's shorthand for a job. The work is what you're actually offering, and it's what an employer is actually buying.
Start from the title and you'll compete with everyone who typed the same words into the same box. Start from the work, find who needs it, and you'll often be the only person in the conversation.
Know the work. Then go find where it's needed.
John Crager, CMRP, SHRM-SCP, is a heavy industry operations and planning professional with decades of experience in refinery and petrochemical environments. He is the author of Blue Collar Resume Mastery and Beyond Thank You for Your Service, available on Amazon, and writes about career navigation, credentials, and the future of the industrial workforce.
Follow the data. Trust the signal. Skip the noise.
→ Next in this series: Networking Is Not Asking for a Job. It Is Staying Useful and Visible.
← Previously: The "Why You?" File: Build Evidence Before You Need It