I wrote a job description for an operations manager three years ago that I was proud of. Clean scope, clear reporting line, a list of responsibilities I'd sanded down until every sentence pulled its weight. I hired against it twice, eighteen months apart, for the same role at the same company. The two people who took that job did two different jobs. Not similar jobs with different personalities layered on top. Different jobs, wearing the same title, at the same desk.
That took me longer to understand than I'd like to admit, because it runs against everything a tidy org chart wants to promise you. The chart says a box is a box. Draw the lines, fill the boxes, and the machine runs the way the diagram says it will. Six businesses in, I don't believe that anymore, and I don't think anyone who's actually built something believes it either. They just don't always say so out loud, because it sounds like you didn't plan well enough. I've come to think it's the opposite. Planning well means knowing which parts of the plan were never going to hold.
The Job Description Is a Forecast, Not a Fact
A job description is the best guess you can make on the day you write it. It describes a role in the abstract, stripped of the three things that actually determine what the job becomes: who's standing next to it, how big and how strained the business is that quarter, and what's currently broken. Write the description in January and hire in March, and you've already hired into a slightly different company than the one you described.
This isn't a failure of the hiring process. It's a category error about what a hiring process can promise. You can write the cleanest job description in Sheridan County and still end up with an outcome nobody in the room predicted, because a job description describes a task. It doesn't describe a relationship, and every hire is a relationship before it's a function.
Organizational psychologists have a name for the piece that actually predicts how well someone performs and how long they stay: person-environment fit, first laid out formally by researchers studying occupational stress in the 1970s and built on for decades since. The idea, stripped of the academic language, is straightforward and a little humbling. The research consistently finds that fit between a person and their actual working environment predicts outcomes independent of, and often more than, the person's raw skill for the task on paper. A great candidate in the wrong environment underperforms a good candidate in the right one, reliably enough that decades of research keeps landing on the same conclusion. Your org chart doesn't have a column for "environment." It should.
The Three Variables: Personalities, Portfolio, Problems
I've started calling the three things that actually write the job PPP, mostly because I needed a way to explain it to myself before I could explain it to anyone else. Personalities, portfolio, problems. None of them show up on the org chart. All three of them decide what the org chart actually means once a real person steps into it.
Personalities is who else is already in the room. The same role sits differently next to a detail-obsessed operations lead than it does next to one who thinks in big swings and delegates the details down. I've watched a hire who would have been a strong second-in-command to one manager get quietly sidelined under another, not because either person did anything wrong, but because the chemistry between two specific humans changes what "support" even means day to day.
Portfolio is the size and shape of the business the day the person actually starts, not the day you posted the listing. A maintenance coordinator role at three properties is a different job than the same title at forty. Not harder, necessarily — different. Fewer relationships to track but more urgency per relationship. More systems and less improvisation. I've hired the same role at different points in Wyo Stays' growth and effectively hired for different jobs each time, even though the job posting barely changed a word.
Problems is whatever's actually on fire that season. You can design a role around steady-state operations, and then a well freezes, or a platform changes its algorithm overnight, or a key vendor goes dark, and the person you hired to manage a calm system is suddenly managing a crisis they were never scoped for. The role survives. The job doesn't. Whoever's in the seat absorbs the difference, whether or not it was in the description.
You can design the role. You can't design the season it lands in.
The Same Title, Two Different Businesses
I run enough different ventures now that I get to watch this play out sideways, not just over time. Take something as simple as "front-facing host." At Wyo Stays, that's a guest coordinator answering messages across a portfolio of properties, mostly text, mostly asynchronous, judged on response time and review scores. At The Living Room Sheridan, a role with almost the same description — greet people, make them feel welcome, keep the space running — turns into something closer to community stewardship. People don't want a fast reply. They want to be remembered, to have someone notice they haven't been in for a couple weeks, to feel like the room knows them. Same instinct, same warmth required, completely different rhythm and completely different definition of doing the job well.
Hire the STR-minded host for the community space and you'll get someone efficient who quietly starves the room of the thing that makes it work. Hire the community-minded host for the rental portfolio and you'll get someone warm who can't keep up with volume. Neither person did anything wrong. The job description could have been identical on paper, and it still would have been the wrong match, because the portfolio wasn't a detail. It was the whole difference.
Why This Isn't an Argument Against Structure
None of this is an argument for winging it. I still write the job description. I still build the org chart. Structure is what keeps six businesses from becoming six fires, and I'd never tell anyone to skip it. What I've stopped doing is mistaking the structure for the whole truth. The chart tells you the shape of the role you're hoping for. It doesn't tell you the shape of the role you're going to get, and treating those as the same thing is where the friction starts.
The cost of getting this wrong isn't abstract, either. The U.S. Department of Labor's baseline estimate puts the cost of a bad hire at roughly thirty percent of that person's first-year earnings once you count the recruiting time, the training, the lost output, and the disruption to whoever's already on the team. For a business running lean, that's not a line item you shrug off — it's a number that can eat a whole quarter's training budget in one mis-hire. Most of those mis-hires aren't skill mismatches. They're fit mismatches, dressed up as skill mismatches because that's the easier story to tell afterward.
What Happens When You Hire for the Chart Instead of the Season
I've made this mistake enough times to describe it precisely. You post the role you need in theory. You interview for competence against that theory. You hire the most competent person who fits the theory. Then the theory meets the actual business — the actual personalities already in the room, the actual size of the operation that month, the actual fire that's currently burning — and the person you hired has to reconcile the job they were promised with the job that's actually sitting in front of them.
Some people do that reconciliation well. They read the room, adjust, and grow into whatever the role turns out to actually be. Some people can't, not because they're bad at their jobs, but because the job they were hired for and the job they're doing have drifted too far apart, and nobody ever renegotiated the terms out loud. That second group doesn't usually quit loudly. They quietly shrink to fit whatever part of the original job description still matches reality, and you lose most of what you hired them for without ever officially losing them.
I ran a maintenance hire through exactly this. Brought someone on to manage a calm, systemized queue of routine work orders across a stable portfolio. Within two months we'd added a dozen new units and lost a longtime handyman on short notice. The role on paper hadn't changed. The actual job had become triage under pressure, which is a completely different skill set from steady-state coordination. I hadn't hired for triage. I'd hired for coordination and then handed someone triage without ever saying so.
I've seen the same pattern on the consulting side, where the mismatch is quieter but just as real. Bring someone in to help build out a client's brand and content system, and the job you scoped is strategy and structure. Then the client's real problem turns out to be that nobody on their end trusts each other enough to execute anything you hand them, and the actual job becomes translation and reassurance between two people who won't talk to each other directly. That's not in any consulting contract I've ever written. It's still the job, the moment you're standing in the room.
The pattern holds because none of these are hiring failures in the traditional sense. Nobody screened poorly. Nobody lied on a resume. The mismatch lives entirely in the space between what a role was designed to be and what it became once it met an actual season of an actual business, and that space is invisible from a job posting no matter how carefully it's written.
Once you start looking for it, the pattern shows up everywhere teams get built, not just in mine. A restaurant hires a line cook for a steady dinner service and then adds a lunch rush six months later without ever renaming the role. A nonprofit brings on a coordinator for one grant cycle and then triples its caseload the following year with the same job title still on the door. The title survives. The job underneath it rarely does, and the gap between the two is where good people quietly start failing at jobs they were never actually hired for.
Reading the Room Before You Write the Role
What I do differently now is treat the job description as a draft, not a contract, and I say that plainly to whoever I'm hiring. Before I post anything, I ask three questions I used to skip. Who's this person actually going to work alongside every day, and what does that relationship need to look like for both of them to succeed. What size and shape is the business likely to be in ninety days, not today, because most hires outlast the current snapshot fast. And what's the most likely fire this role will get pulled into, even if it's not officially part of the job.
None of those questions have clean answers. That's the point. You're not trying to eliminate the uncertainty. You're trying to name it out loud, before it becomes an unspoken source of friction between what someone thought they signed up for and what they're actually doing by month three.
I also do something now that felt uncomfortable the first few times: I revisit the role explicitly at thirty, sixty, and ninety days, and I say plainly what's changed. Not a performance review. A fit review. Has the portfolio shifted. Has a new personality entered the picture. Has a new problem taken over the actual day-to-day. If the answer is yes to any of those, the job has changed, whether or not the title has, and pretending otherwise is how good hires quietly become mismatched ones without either side noticing until it's expensive.
The Part Nobody Tells You About Building a Team
Here's what surprised me most, once I stopped expecting the org chart to be load-bearing on its own. The teams that ended up working best weren't the ones where I'd predicted the fit correctly in advance. They were the ones where I stayed honest about the mismatch early enough to fix it before it calcified into resentment on either side. Sometimes that meant reshaping the role around the person instead of the other way around, because the person turned out to be stronger in a direction I hadn't scoped for. Sometimes it meant admitting the portfolio had outgrown the role faster than either of us expected, and building a second position instead of asking one person to silently absorb two jobs.
I used to think a well-run business meant the org chart and the lived reality matched closely. I think now it means you've built a habit of noticing when they've drifted apart, and you close the gap before someone quietly starts doing a different job than the one they agreed to, for the same pay, without either of you saying so.
What I'd Tell Myself Before the First Hire
If I could hand my younger self one sentence before that first operations manager posting three years ago, it wouldn't be about interview questions or compensation bands. It would be this: you are not hiring for the role you wrote. You're hiring for the role that exists at the intersection of who's already there, how big the business actually is the week they start, and whatever's currently on fire — and none of those three things will hold still long enough to write down permanently.
That's not a reason to skip the job description. It's a reason to hold it loosely, revisit it often, and stop being surprised when the same title produces two different jobs eighteen months apart. It isn't a flaw in your hiring process. It's just what building something real, with real people, in a place and a season that keep changing, actually looks like.
Out here, a fence line gets built to a plan too — post spacing, wire tension, gate placement, all worked out ahead of time. And then the winter does what the winter does, the ground heaves, an elk herd comes through where nobody expected them, and the fence that holds is the one somebody kept walking and fixing, not the one drawn up once and left alone. Teams work the same way. The chart gets you started. Walking the line all season is what actually keeps it standing.
If you're building a team right now and the org chart isn't matching what you're actually living day to day, that gap isn't a sign you did it wrong. It's a sign it's time to look at the personalities, the portfolio, and the problems again, and rewrite the role around what's actually true instead of what you guessed months ago. If you operate short-term rentals in the Mountain West and want to talk through how a team should actually be built around a growing portfolio, Wyo Stays is where I've run every version of this experiment for real. And if the delegation side of this resonates, I wrote through the mechanics of that in an earlier piece on why owners end up being the bottleneck in their own businesses — this one's companion, really, on the hiring side of the same problem.
