Set Expectations, Not To-Do Lists, For Career Growth

You may feel like you have solid job descriptions and career paths - especially if you listed a robust set of skills, detailed all the tasks, and wrote it planning for it to answer all the potential scenarios  for that role (and the next one). 

But you may have found that in 1:1s and performance conversations that well-crafted document has been interpreted by your team as less guidance, and more checklist. And now that your team member feels they have checked all the boxes, they are wondering why they aren’t being promoted. 

So what went wrong? Many companies don’t have any career guiding docs or framework, so you were ahead of the game! Turns out that if you the only way you know how to describe roles and career progression is only through a to-do list, your people will treat it that way. Marking everything off means you get something, right? But in reality, what you were trying to do was set expectations and provide guidance for growth. While the essence might be there the practical application led you astray. 

Why Job Descriptions Become Checklists (And Why That's a Problem)

You start with the right intention when you create leveling and progression docs. Usually it is born out of a want to be clear and to give people something that is tangible to work towards. So you try to capture everything - every task, every tool, every possible situation the role might touch. Thoroughness feels like fairness. 

But here's what happens when those documents hit the hands of the people on your team. Instead of illustrating what the role is, they see a checklist and scorecard. And a reasonable person, looking at those two things, assumes that completing it earns them something. A raise. A title. A promotion.

That's not entitlement in the negative sense, it’s a logical thought process. You built a list, they completed it, they'd like their reward, please.

The problem is the business may not be ready to give it - and now you're negotiating against your own documents and trust erodes. They feel like you moved the goalposts - you feel like they're missing the bigger picture. Nobody's wrong, exactly. The framework set everyone up to fail. 

Expectations Are About Behavior and Standards, Not Just Tasks

So we need to take a step back and truly understand what we want to achieve with documents like job descriptions, career paths, and level. We want people to know what good looks like and what we expect out of them to be successful in the role. A good set of expectations communicates that - the standards, the actions, and the behaviors - not just tasks to be done.

For example, check out two different ways to frame an expectation for a potential mid-level role. 

- Task version: "Builds 10 client decks per quarter."

- Standard version: "Demonstrates polished, client-ready communication under tight deadlines - anticipates the client's questions before they ask them."

The first is specific in output, but not in outcome - someone can hit it while producing decks that make you cringe. The second describes a standard that can apply to any task, any deliverable - decks, emails, client calls, meetings, etc. It isn’t dependent on the what - it focuses on the how. 

Building expectations from this place are incredibly important in a services business, where the actual work changes constantly. Tasks are frozen the moment you write them down and are dependent on the who and the when. Standards have the ability to keep up with (and should spread across) different client and internal situations. 

Fluidity Over Prescription: Building Frameworks That Flex

We know that some of you are silently screaming”I need the HOW or I’ll be fighting for my life in every 1:1”. We get it. But there's a difference between clear and exhaustive, and prescriptive frameworks confuse the two. When you try to write the complete manual for every scenario, you box in the company and the employee. There's no room left for the flexibility that defines client-based work - and that variability isn't an anomaly, it is the core of how services firms run. 

So don't build a manual, find the essence. No, you didn’t jump to some blog about holistic healing. What we mean is that for every role and level, ask: what's the core of what must be true here? What's non-negotiable about how this person shows up, decides, and delivers? Nail that and then stop. Resist the urge to keep going until you've accounted for every "but what if."

It’s not laziness or not caring or not useful if you don’t have 40 different elements listed in every leveling doc. In our world, it's a requirement to understand how to shift, move, and navigate - this doc helps our people understand how to do that within the container of expectations we have created. 

Readiness Isn't Enough - Your Team Needs to Understand 'Need'

We also need to talk about how setting up your leveling and career progression docs with the extra element - company need - is often missed and can cause big headaches.

Readiness is only half the equation. The other half is whether the business needs the role filled — and you can't skip that math. Just because there is a blank square on the org. Chart or someone is truly ready for a jump, you must understand whether the business actually needs that person in that role. 

You can't be a $2 million dollar company with all VPs and no doers. Somebody has to do the client-facing work, and a firm top-heavy with senior titles collapses under its own payroll long before it scales.

So here's the distinction worth figuring out and communicated to your team clearly and often:

> Readiness gets you eligible. Need gets you promoted.

Meeting your expectations should absolutely make someone eligible for more - a stretch assignment, a seat in a senior conversation, expanded scope, inclusion in the conversation when you do need that next leader. Eligibility is a promise you can always keep. What it does not guarantee is a title change or a raise on a specific date, because that depends on business need.

That's the difference between eligibility and entitlement. Eligibility says, "you've earned the right to be considered and to grow into more." Entitlement says, "I finished the list, reward me." One is a partnership - the other feels like a hostage situation to one party and a broken promise to another. 

The move that prevents this: teach the "need" factor from day one - in onboarding, in the first career conversation, not in a tense review when someone's already frustrated. When people understand from the start that advancement requires both their readiness and the firm's need, you've removed the unwelcome surprise. 

Build the Org Chart for Where You're Going, Not Just Where You Are

So here is how you weave together good expectations and  your growth. Your org chart should reflect the roles you'll need in the next 12 to 18 months, not just today's headcount. Building ahead gives your people a visible path and gives you a plan for the growth you're actually chasing.

But - and this is the part that gets skipped - you have to teach your team how to read that chart.

An open box on the org chart doesn't mean an open seat. It means a path.

Some of those boxes will sit empty for months. Some for a year or more, depending on how fast you grow. That's not stagnation, and it's not you dangling a carrot you never intend to hand over. It's planning. It's you being honest that the seat opens when the business can support it — which is exactly the "need" conversation that has to happen. 

Pair a forward-looking chart with a clear "eligible vs. filled" distinction, and something nice happens: ambition has somewhere to point. People can see the future role, understand what readiness looks like for it, and know the seat becomes real when the growth is real. That's motivating. 

Here's what this looks like in practice: mark active roles one way and planned or open roles distinctly - "planned Q3 next year," "opens at $X in revenue." Make the conditions visible, not just the box.

How to Reframe Expectations Starting Today

You don't need to burn your frameworks down. A few concrete moves:

1. Audit one leveling doc for checklist language. Every line that starts with a countable verb ("build 10," "run 5") is a candidate to rewrite as a standard.

2. Rewrite to the essence. For each role, name the non-negotiable core - how they show up, decide, and deliver - and cut the manual.

3. Add the "need" conversation to onboarding. Explain eligibility vs. entitlement before anyone's frustrated. Make it normal, early, unremarkable.

4. Redraw your org chart 12–18 months out and mark planned roles distinctly from active ones.

5. Train your leaders to say it out loud: Readiness gets you eligible, need gets you promoted.

The firms that get this right don't end up with fewer ambitious people. They end up with ambitious people who trust the system - because the system was honest with them from the start. That's what protects your culture as you scale: not vaguer expectations, but clearer, humaner ones.

Ready to rebuild your leveling framework so it drives growth instead of grievances? Talk to prism+spire about designing expectation-based career paths built for the realities of professional services - where the work changes daily and your best people deserve a path they can actually trust.