The Four Worketypes

Thinking in Worketypes

These are archetypes. Over the years, when I've asked team members to choose which column best describes their strengths, many choose one — plus a little bit of another "on the side". This is real life. I've never had a team member self-describe into more than two. Most are at home in "one + a couple from the next column over" which validates my thesis that most team members thrive in only 1-2.

No Worketype is "better" than another. This grid doesn't represent career progression. A Coordinator is not an "under-performing" Optimizer, and an Implementor doesn't mature into a Coordinator once they learn the ropes. Also, team members do not become more valuable towards the right or the left.

You can have all four types in your org chart — but you don't necessarily need all four. There's no templated recipe for this. It's a combination of what you make and sell, who you already have on your team, your budget, what strengths you-as-business-owner bring to the table — and what's left over.

Make room for each type to work in their strengths. This means acknowledging the kind of guidance they work best under, supplying it — and matching job duties to strengths. Without wishful thinking, finger-pointing, or delusion.

Here's what it actually looks like when each Worketype gets the same challenge.

Seeing the Worketypes in Action

This scenario illustrates what both agreement and pushback would sound like from the four types — in a realistic scenario.

Scenario: you're planning a launch. Goal is 50 units and the cart opens at the end of October. Here's how each Worketype responds to the same brief:

Pathfinder (as FB Ads expert)

Agreement sounds like: Great, let me run an audit of your assets, give me access to your ads manager, and I'll come back with a plan. OK, here's the plan: I've been noticing that webinars don't convert as strongly as they used to and so I propose this new type of funnel to get the numbers you want to see. The ads budget will need to be $x to make those goals. Here's my scope of work, and my fee.

Pushback sounds like: If you really want to stick with a webinar, your ad spend will be 2x to produce the same results, or we'll need to adjust the unit goal down.

Optimizer (as Launch Manager)

Agreement sounds like: Great, let me pull the metrics of our previous launches and set up a doc with what we've done before and what it produced. Once we've digested that, let's call a meeting to sift through the options, and you can make the decisions of what's in and out. Once you've nailed down the moving parts, I'll get everyone organized.

Pushback sounds like (at the kick-off meeting): I don't think there's enough runway for that. It's more complex than it sounds, and to really pull it off we'll need either more people or more time. Here's an alternative.

Coordinator (as Tech Specialist)

Agreement sounds like: Great, remember I'll need 10 days to create the automations, load, link, and test all the emails. So I'll need the copy finalized and to me by mid-October.

Pushback sounds like: Remember last time I didn't get enough runway and was still building as we were launching? That meant we couldn't implement anything creative in response to what we were seeing. Let's not do that again.

Implementor (as Tech Specialist)

Agreement sounds like: Great, I've blocked off a lot of October to work on this. Let me know what you need.

Pushback sounds like: There's too much work all due at the same time, and when I'm this rushed errors can creep in, despite my high standards for quality. The rushing is because others didn't make up their minds in time — and I'm expected to pick up the slack. Give me adequate time so you'll see my very best work.

Similar brief. Four different responses. All have their place in the well-run team.

Common Mistakes I see Founders Make

These are the patterns I see week after week.

Asking Implementors to think like strategists. You hand an Implementor a problem and ask them to suggest improvements, or "take more ownership" by anticipating what the business needs next. What comes back: silence, surface-level suggestions, or the same Implementor questions you've always gotten.

The Implementor's value lives in dialed-in execution. Asking them to operate two columns over from where they thrive is asking them to be a different person. They either nod uncomfortably and don't deliver, or they try, fail, and start doubting their own competence at the work they were hired to do.

The Department-of-One. On a small team, roles are tiny enough that combining several together to create one seat is common, asking one person to do Pathfinder thinking, Optimizer planning, Coordinator project running, and Implementor task execution, all in a single seat.

That team member either burns out trying to deliver across all four archetypes, or quietly specializes in the one or two they can actually carry and the rest of the role goes unfulfilled. It looks like a performance or a motivation problem — it's a "that unicorn person doesn't exist in real life" problem.

Implementor-question fatigue. Pathfinder founders feel drained by Implementor questions and read it as "they're not taking ownership."

The Implementor is asking for the goalposts they need to do their work. If the goalposts aren't there, asking is the only behavior available. You may read it as a personality flaw, but the problem is you're asking two roles to work against type (yours and theirs).

Not screening for worketype when hiring or assigning roles. Job descriptions almost never specify the size and kind of decisions a role will own. There's no screening for it in interviews.

Hiring "well" becomes guesswork, and "performance problems" downstream are almost always hiring mismatches nobody had a vocabulary to spot.

Mini Case Study: What a mismatch looks like in real life

One of my clients was a founder-led services firm with a GM, a small core team, and a wider bench of contractors. Despite earnest attempts at delegation, the founder was still in the daily work.

The dominant issue wasn't effort or skill. It was a leadership seat operating at the wrong worketype. The GM role was running like a project coordinator working a task list of meetings, updates, and reports. What the business needed was outcome ownership: a GM who would make the decisions, make the tradeoffs, and drive results without the founder constantly re-engaging.

Here's the moment the mismatch became obvious. The GM had been tasked with improving sales conversions, so they arranged training and mentoring to make it happen. However, the next month, conversion percentage actually dropped. They investigated and came back with the explanation that the lead source mix had changed month over month.

That was technically true, but it's not the kind of answer you want from the #2 person in a business. That answer was passive-voice analysis that focused on lead-source and ignored the high-priority training initiative that hadn't yielded any results yet. The GM was explaining the number, not managing the number.

An outcome-focused answer sounds like: here's what's working, here's what's not, here's what I'm trying next, here's what we should expect to see by when.

Once we understood the issue, we were able to collaborate to make the fix. In this case, you either redesign the seat to match the person, or you find the person who actually wants that level of ownership.

Mismatches run both ways

That's one version of a mismatch. But they run in every direction.

Delegate outcome-level responsibility into a seat that's functioning at task or analyst level, and you won't get true delegation. You'll get updates, and you'll stay the bottleneck. Go the other direction — put an Optimizer or Pathfinder into a seat of high-volume, repetitive execution with no room for judgment — and you'll get someone who looks sloppy and disengaged. They're likely not. They're just in the wrong seat.

And if your team has roles that span multiple columns, realize that at least one or two roles are getting short-shrift. That's not a performance issue — that's an impossible job.

Now you know

The Four Worketypes give you a lens for understanding how roles and responsibilities are, and should be, distributed among your team. With it, you can see clearly who is well-matched to their work — and understand exactly what's happening when the match isn't so clean.

You already know which seat to look at first.