Building Pay Structures: Compensation Strategy and Design Guide

Lena: I was looking at some HR data recently and realized something wild—most people think setting a salary is just about checking what the guy down the street pays. But it turns out, relying solely on raw market averages can actually be a huge mistake that leads to major inconsistencies in your team.

Miles: It’s so true. You know, it’s a classic pitfall. If you just chase the market without a plan, you end up with a pay structure that doesn't actually support your company's specific goals or global needs.

Lena: Exactly! And that’s why we’re digging into the actual mechanics of building pay structures today. It’s not just about the numbers; it’s about balancing internal equity with being competitive externally.

Miles: Right, and it’s fascinating how you have to bridge that gap. So, let’s dive into the strategic goals of a solid pay structure and how to start building those ranges.

Lena: You know, Miles, thinking about what we just said—that chasing the market is a trap—it makes me wonder where we actually start. If we can't just copy-paste from a salary survey, what is the first real step in the playbook?

Miles: It’s all about the internal foundation, Lena. Before you ever look at what the tech giant across town is paying, you have to look inward. We call this job evaluation. It’s essentially the process of determining the relative worth of different jobs within your own organization. You’re building a hierarchy based on the value each role brings to your specific mission.

Lena: So, it’s like creating a map of your own house before you go out and compare it to the neighborhood?

Miles: Exactly. A perfect analogy. And there are a few ways to do this. You’ve probably heard of the Hay Guide Chart—it’s a classic method. It looks at things like know-how, problem-solving, and accountability. It’s very analytical. But whether you use a point-factor system like Hay or a more simple ranking method, the goal is the same: internal equity. You want to be able to look an employee in the eye and explain why their role sits where it does compared to their colleague’s role.

Lena: That sounds like it would solve a lot of those "why does he make more than me" conversations that happen at the water cooler. But isn't there a risk of being too inward-looking? If I decide a role is worth a lot to me, but the rest of the world doesn't agree, don't I run into trouble?

Miles: You’ve hit the nail on the head. That’s the tension we’re always managing. If you over-prioritize internal equity, you might end up overpaying for roles that are easy to fill or underpaying for "hot" roles that everyone is hiring for. On the flip side, if you only care about the market, your internal hierarchy becomes a mess—you might have a junior person making more than their manager just because the junior's skill set is trending this month.

Lena: It’s a delicate balancing act. So, if I’m a compensation practitioner, I’m basically a tightrope walker. What’s the tool I use to stay balanced?

Miles: The tool is the pay grade. Think of pay grades as the "buckets" where you group jobs of similar value. Instead of having a different pay rule for every single job title—which would be a nightmare to manage—you group them. You might have ten roles in Grade 5 because, even though the jobs are different, the level of responsibility and the value to the company are roughly the same.

Lena: That makes sense. It simplifies things. But how do we decide which jobs go into which bucket? Is it just a gut feeling?

Miles: Definitely not. That’s where the data from those job evaluations comes in. You use the scores or rankings to create these clusters. And this is where the strategic part happens. You have to decide how many grades you want. Do you want a lot of narrow grades, which allows for frequent promotions? Or do you want "broadbanding," where you have fewer, wider grades that give managers more flexibility?

Lena: I’ve heard of broadbanding. It sounds very "modern," but I imagine it has its own pitfalls.

Miles: Oh, it definitely does. With broadbands, you run the risk of pay drifting upward without a clear reason, or you might end up with huge pay gaps between people in the same grade. It requires a lot more managerial discipline. For most organizations starting out, a more traditional graded structure provides a better "playbook" for consistency.

Lena: So, the first move in our playbook is: Evaluate the jobs, define the value, and then group them into grades. It’s about creating order out of the chaos of individual titles.

Miles: Spot on. And once you have those grades, you’ve built the skeleton. Now you need to put some meat on the bones by bringing in the market data. But you do it on your terms, for your specific grades, rather than just reacting to every random data point you find online.

Lena: It’s about being proactive instead of reactive. I love that. It shifts the power back to the organization to define its own worth while staying grounded in reality.

Miles: So, Lena, we’ve got our internal map. We know how our jobs relate to each other. Now we have to look out the window. This is where market pricing comes in, and let me tell you, it’s more of an art than a science.

Lena: I think that’s what trips people up. They see a number in a survey and think, "Okay, that’s the price." But it’s never that simple, is it?

Miles: Never. The biggest mistake is assuming a job title in a survey matches your job title exactly. You might have a "Marketing Manager" who actually does the work of a Director, or a "Senior Analyst" who is really doing entry-level tasks. You have to do what we call "job matching." You look at the descriptions, not just the names.

Lena: It’s like shopping for a car. Two cars might both be called "SUVs," but one has a V8 engine and luxury leather, and the other is a basic four-cylinder. You can't just look at the average price of an "SUV" and call it a day.

Miles: Exactly! You have to look under the hood. When you're looking at market data—from sources like Mercer or Towers Watson—you’re looking for the "benchmark" jobs. These are roles that are common across many companies, like an Accountant or a Software Engineer. You find the market rate for those, and then you use them as anchor points for your pay grades.

Lena: Okay, so I find my anchors. But what happens if the market data is all over the place? I’ve seen surveys where the 25th percentile and the 75th percentile are miles apart. How do I choose where to aim?

Miles: That’s your "pay policy." It’s a strategic choice. Do you want to "lead" the market—meaning you pay more than most of your competitors to attract the absolute top talent? Do you want to "lag"—maybe you’re a startup with great equity options but less cash? Or do you "lead-lag," where you start the year slightly ahead and end slightly behind as the market moves?

Lena: That’s a fascinating way to put it. It’s not just "what is the market," but "where do we want to stand in relation to the market."

Miles: Right. And you also have to consider the "geographic differential." If you’re a global company, a "Grade 5" role in London is going to have a very different market rate than a "Grade 5" role in Manila. You can’t use a one-size-fits-all approach. You have to build structures that reflect local economic realities while maintaining that internal equity we talked about earlier.

Lena: That sounds incredibly complex. How do you keep it all organized?

Miles: You use a central framework but with local adjustments. It’s like having a recipe but swapping out ingredients based on what’s in season locally. The core structure—the relative value of the roles—stays the same, but the actual dollar or euro amounts in the ranges change.

Lena: So, let’s talk about those ranges. Once I know my market midpoint for a grade, how do I actually build the "floor" and the "ceiling" for pay?

Miles: This is a key technical step. Usually, you set the "midpoint" of your range based on your market target—say, the 50th percentile of the market if you want to be competitive. Then, you calculate a "range spread." For entry-level roles, the spread might be 20 to 30 percent. For executive roles, it might be 50 percent or more.

Lena: Why the difference? Why do executives get wider ranges?

Miles: Because there’s more room for growth and performance variation in those roles. A junior clerk can only do so much, but a CEO’s impact is massive. A wider range allows you to reward that high-level performance without having to promote them to a new grade every time they have a good year.

Lena: Ah, that makes sense. So, the range isn't just a limit; it's a tool for performance management.

Miles: Absolutely. It gives you room to move people from "minimum" when they’re learning, to "midpoint" when they’re fully competent, to "maximum" when they’re a top performer. It’s the "how-to" of rewarding growth within a single job.

Lena: Okay, Miles, let’s get into the nitty-gritty. We’ve talked about grades and midpoints, but I want to know the actual math. If I’m sitting at my desk with a spreadsheet, how do I actually calculate these numbers?

Miles: I love it when we get into the "how-to" mode. Okay, imagine you’ve determined that for Grade 4, the market midpoint is $60,000. That’s your target for a fully qualified, solid performer. Now, you need to decide on your "range spread." Let’s say you want a 40 percent spread.

Lena: Forty percent. Okay, so how do I find the minimum and maximum from that?

Miles: It’s a simple formula, but people often mess it up. To find the minimum, you take the midpoint and divide it by 1 plus half of the spread. So, if the spread is 40 percent, half is 20 percent, or 0.20. You divide $60,000 by 1.20.

Lena: Let me do the math... that’s $50,000.

Miles: Exactly. That’s your "floor." Now, to find the maximum, you take that minimum and multiply it by 1 plus the full spread. So, $50,000 times 1.40.

Lena: And that gives us $70,000. So the range for Grade 4 is $50,000 to $70,000, with a $60,000 midpoint.

Miles: You’ve got it. Now, here’s a pro tip: You also need to look at "midpoint progression." That’s the percentage jump from the midpoint of Grade 4 to the midpoint of Grade 5. If it’s too small—say, only 3 percent—people won't feel like a promotion is worth the extra responsibility. If it’s too large—like 30 percent—you’ll have a hard time moving people up because the jump is too expensive for the budget.

Lena: So what’s the "sweet spot"?

Miles: Usually, you’re looking at 8 to 15 percent between grades. It provides a meaningful raise that reflects a real step up in value.

Lena: And what about "overlap"? If the maximum of Grade 4 is $70,000, and the minimum of Grade 5 is $55,000, there’s a lot of overlap there. Is that a problem?

Miles: Actually, overlap is good! It recognizes that a highly experienced, top-performing person in a lower grade might actually be worth more to the company than a brand-new, inexperienced person in the next grade up. It gives you flexibility. However, if you have too much overlap—like 80 or 90 percent—then your grades aren't really distinct anymore. You might as well just have one big grade.

Lena: It’s like having different weight classes in boxing. There’s a bit of overlap, but you still need those distinct categories to keep the competition fair.

Miles: That’s a great way to think about it. Now, once you have these ranges, you have to perform a "compa-ratio" analysis. This is a classic diagnostic tool. A compa-ratio is just an employee’s actual salary divided by the midpoint of their range.

Lena: So if I’m at $60,000 and the midpoint is $60,000, my compa-ratio is 1.0 or 100 percent.

Miles: Exactly. If you’re at 0.80, you’re likely new to the role or underpaid. If you’re at 1.20, you’re at the top of the range. If a manager has a whole team with compa-ratios of 1.15, you know they’re either elite performers or that manager is being way too generous with the budget. It’s a red flag for a compensation audit.

Lena: I can see how that would be a vital tool for HR. It helps you spot inconsistencies before they turn into "equal pay" issues or budget blowouts.

Miles: Right. And speaking of equal pay, that’s a huge compliance pitfall. When you’re building these structures, you have to ensure they’re "gender-neutral" and don't bake in historical biases. Using objective job evaluation criteria—like the Hay method we mentioned—is your best defense there. It moves the conversation from "who you are" to "what the job requires."

Lena: It’s about building a system that is defensible, logical, and transparent. If you can explain the "why" behind the numbers using this math, you win the trust of the employees.

Miles: Now, Lena, we’ve been talking mostly about building a structure for one location. But the world is getting smaller. What happens when your "Grade 4" analyst is in Chicago, but you also have one in Bangalore and another in Berlin?

Lena: That’s where it gets really tricky, right? You can't just pay them all the Chicago rate—the company would go broke. But you also can't just pay them the local minimum if you want to keep them from jumping to a global competitor.

Miles: Exactly. This is the "global vs. local" debate in rewards. There are a few ways companies handle this. One is the "Local Plus" approach. You pay a competitive local salary but add "plus" elements—maybe extra benefits or allowances—that align with your global corporate standards. It’s about being fair locally while maintaining a global brand identity.

Lena: I’ve also heard about companies using "Geographic Differentials" or "Zone Pay." How does that work in practice?

Miles: It’s a very practical playbook move. You create a "Base Structure"—let’s say based on your headquarters—and then you apply a multiplier or a "zone" factor. So, Zone A might be 100 percent of the base, Zone B is 85 percent, and Zone C is 70 percent, based on cost of labor in those regions. It allows you to keep the same grades and internal hierarchy, but the actual cash reflects the local economy.

Lena: That seems fair. But what about expatriates? Those "Mercer Expatriate Compensation" guides are huge for a reason. Sending someone from New York to London isn't just about the salary; it’s about housing, schools, and taxes.

Miles: Oh, expatriate pay is a whole different beast. You usually use the "Balance Sheet" approach. The goal is to keep the employee’s purchasing power the same as it was at home. You calculate their home-country expenses and then add "equalizers" for the higher costs in the new location. It ensures they aren't penalized for taking a global assignment.

Lena: It’s basically making sure they stay "whole."

Miles: Right. But here’s the pitfall: If you have an expat on a "Balance Sheet" package sitting next to a local hire doing the same job for a local salary, you can create massive resentment. The local person sees the expat getting a huge housing allowance and thinks, "Wait, why am I worth less?"

Lena: That sounds like a recipe for a toxic culture. How do you fix that?

Miles: More companies are moving toward "Local Plus" or "Localization" after a few years. You give the expat a great package to get them there, but over time, they transition to the local pay structure. It’s about balancing the need to move talent around with the need for internal equity among the people already there.

Lena: It’s that balance again! It always comes back to equity. Whether it’s between two people in the same office or two people on opposite sides of the Atlantic.

Miles: It really does. And you have to consider total rewards, not just base pay. In some countries, like Brazil or France, the "mandatory" benefits are so high that the base salary might look lower, but the "Total Remuneration" is actually very high. If you only look at base pay in your surveys, you’re missing half the story.

Lena: So, the playbook for global pay is: Understand the total cost, respect the local market, but keep the internal hierarchy consistent. Don’t just look at the paycheck; look at the whole package.

Miles: Precisely. It’s about being a global citizen as an organization while staying grounded in the specific economic reality of every place you operate. It’s not easy, but it’s what separates the world-class companies from the rest.

Lena: You know, Miles, we’ve spent a lot of time on the "math" of pay—the grades, the ranges, the geographic zones. But I think we’d be missing something huge if we didn't talk about the stuff that *isn’t* in the paycheck.

Miles: You mean the "Total Rewards" strategy. This is where compensation becomes part of the actual culture. It’s moving beyond just "what do we pay" to "what is the total value proposition for working here?"

Lena: Exactly. I was reading some of those Towers Watson and WorldatWork materials, and they emphasize that pay is just one "slice" of the pie. You’ve got benefits, work-life effectiveness, recognition, and talent development. If you focus only on the salary structure, you might be over-engineering a system that people don't actually value that much.

Miles: That’s a great point. Think about it this way: If you’re a company that can't afford to pay at the 75th percentile—you’re not leading the market in cash—you have to lead somewhere else. Maybe you offer incredible career development, or a work-from-home policy that gives people ten hours of their life back every week. Those are "rewards" just as much as a bonus is.

Lena: It’s like a "toolkit" for managers. If they can't give a raise because of a budget freeze, they can still "reward" a high performer with a high-profile project or a flexible schedule. But for that to work, the company has to have a structure for those things, too.

Miles: Right. It can't just be "random acts of kindness." A true Total Rewards strategy is intentional. It aligns with the business goals. If your goal is innovation, your rewards should focus on rewarding risk-taking and learning. If your goal is efficiency, you might focus more on performance-based bonuses tied to specific metrics.

Lena: I love that. It makes the pay structure feel less like a "cost" and more like an "investment." But how do you communicate this to employees? I feel like most people just see the number on their pay stub and ignore the rest.

Miles: That’s the "Communication Gap." It’s one of the biggest pitfalls in HR. Companies spend millions on benefits and development programs, and then they never tell anyone about them. The "Playbook" move here is the "Total Rewards Statement."

Lena: Oh, I’ve seen those. It’s like a yearly summary that shows: "Here’s your salary, but also here’s what we paid for your health insurance, your 401k match, your gym membership, and your tuition reimbursement."

Miles: Exactly! When people see that their $60,000 salary actually costs the company $85,000 in total rewards, it changes the perspective. It builds loyalty. It shows the company is investing in the *person*, not just buying their time.

Lena: It also helps with that internal equity issue. If someone is upset about a pay grade, you can point to the other rewards they're getting. "Yes, your base pay is at the midpoint, but you’re also in our high-potential leadership program, which is a $10,000 value in itself."

Miles: And it’s not just about the value to the company; it’s about the "perceived value" to the employee. This is where psychology comes in. Some people value cash above all else. Others would take a 5 percent pay cut for an extra week of vacation. A modern pay structure tries to offer some level of choice.

Lena: Like a "cafeteria plan" for rewards?

Miles: Precisely. Giving employees a voice in how they are rewarded is a powerful way to increase the "ROI" of your compensation budget. Instead of guessing what they want, you build a structure that allows for flexibility.

Lena: So, the takeaway here is: Don’t build your pay structure in a vacuum. It’s part of a larger ecosystem of rewards. If the salary is the foundation, the other rewards are the walls and the roof that actually make it a home people want to stay in.

Miles: That’s a beautiful way to put it. A pay structure without a rewards strategy is just a spreadsheet. A rewards strategy *with* a pay structure is a competitive advantage.

Miles: Okay, Lena, so let’s say you’ve built the structure. You’ve got your grades, your ranges, your global zones, and your total rewards plan. You’re done, right? You just set it and forget it?

Lena: I have a feeling the answer is a very loud "no."

Miles: You’re right! A pay structure is a living thing. It starts to decay the moment you finish it. Markets move, jobs change, and—let’s be honest—managers make "exceptions" that eventually become the rule. This is why the "Audit" is the most important part of the playbook.

Lena: An audit sounds scary. Is it like a tax audit where someone comes in and looks for mistakes?

Miles: It can feel that way, but it’s actually your best friend. A regular "Compensation Audit" helps you find those inconsistencies we talked about earlier. You look for "Green Circle" and "Red Circle" employees.

Lena: Okay, explain those. I’ve never heard those terms.

Miles: A "Green Circle" employee is someone who is paid *below* the minimum of their pay range. This usually happens if the ranges were just adjusted upward for inflation, but the employee’s pay didn't move. It’s a huge retention risk and a potential legal issue.

Lena: And let me guess... a "Red Circle" employee is the opposite?

Miles: You got it. Someone paid *above* the maximum of their range. Maybe they’ve been in the same role for twenty years and kept getting cost-of-living raises, or maybe they were hired during a talent shortage at a premium. The problem is, they have nowhere left to go. They can't get a raise unless they get promoted or the whole structure moves.

Lena: That sounds like a tough conversation for a manager. "Sorry, you’re too good at your job to get a raise?"

Miles: It is! But the playbook move there is to offer "lump-sum" bonuses instead of base pay increases. You reward their performance without permanently increasing the fixed cost of their salary above the market value of the job.

Lena: That’s clever. It keeps the structure intact while still recognizing the person. What else do you look for in an audit?

Miles: You look for "compression." This is when the pay difference between a supervisor and their direct reports becomes too small. If a new hire comes in at a high market rate, they might be making almost as much as the person training them. That’s a recipe for a massive morale collapse.

Lena: I’ve seen that happen. It’s so discouraging. How do you fix it?

Miles: You have to make "equity adjustments." It costs money, which is why you need to budget for it every year. You have to move the tenured people up to maintain that "internal equity" we keep talking about. If you don't, you’ll lose your best people to the same market that’s forcing you to pay new hires so much.

Lena: It’s like maintaining a house. If you don't fix the leaks and paint the walls every few years, the whole thing eventually falls apart.

Miles: Exactly. And the final piece of the audit is "Pay Equity Analysis." You have to look at the data through the lens of gender, race, and age. If you find that men in Grade 6 are consistently paid more than women in Grade 6, and there isn't a clear "performance or seniority" reason for it, you have a problem. In many places, that’s not just bad practice—it’s illegal.

Lena: So, the audit isn't just about the numbers; it’s about the "integrity" of the system. Does it actually do what we said it would do? Is it fair? Is it competitive?

Miles: Right. I recommend a full structure review every two to three years and a "mini-audit" of compa-ratios every single year during the budget cycle. It keeps the system honest and ensures that your "strategic pay structure" doesn't just become a "random pile of salaries."

Lena: We’ve covered a lot of ground, Miles. But I’m thinking about the person who has to actually *do* this. What are the "potholes" they’re going to hit when they try to roll out a new pay structure?

Miles: Oh, there are plenty! The first one is "The Secretive Culture." If you build this beautiful, logical structure but keep it a secret, people will assume the worst. They’ll think it’s arbitrary or unfair.

Lena: So transparency is the key?

Miles: Within reason. You don't necessarily have to publish everyone’s individual salary, but you *should* publish the pay ranges for each grade. When people see that there’s a structure, it builds trust. They know where they stand and what they need to do to move to the next level.

Lena: That makes sense. What’s the next pothole?

Miles: "Manager Discretion." You can have the best structure in the world, but if managers are allowed to ignore it and pay whatever they want to "get the hire," the structure is worthless. You need a clear policy on "exceptions." Who has to approve a salary that’s outside the range? Usually, it should be a high-level executive or HR.

Lena: It’s about having "guardrails." Managers want to solve their immediate problem—filling a seat—but HR has to look at the long-term health of the whole system.

Miles: Exactly. Another big one is "The Data Trap." We talked about this a bit, but it’s worth repeating: Don't trust a single data source. If you only use one survey, you’re seeing the world through one lens. Use at least two or three to get a "consensus" on what the market is actually doing.

Lena: And don't forget the "Global Blind Spot." If you’re expanding into a new country, don't assume your "home country" rules apply. The labor laws, tax implications, and even the "cultural expectations" of pay are different everywhere. In some cultures, for example, seniority is valued much more than individual performance. If your structure only rewards performance, you’ll struggle in those markets.

Miles: That’s a deep insight. You have to adapt the "philosophy" of the structure, not just the numbers. And the final pitfall? "Complexity."

Lena: Complexity?

Miles: Yes. If your pay structure is so complicated that a manager can't explain it to an employee in five minutes, it will fail. If you have fifty different grades and twenty different "bonus modifiers" and a "geographic multiplier" that requires a PhD to calculate... no one will use it.

Lena: Keep it simple.

Miles: Exactly. A good pay structure should be "elegant." It should be robust enough to handle the complexity of the business but simple enough to be understood by the people it affects.

Lena: So: Be transparent, set guardrails, use multiple data sources, respect local cultures, and keep it simple. That sounds like a solid "Implementation Checklist."

Miles: It really is. If you can check those boxes, you’re ahead of 90 percent of the companies out there. You’re not just "doing payroll"—you’re strategically managing your most expensive and most valuable asset: your people.

Lena: Miles, this has been an incredible deep dive. I feel like we’ve gone from the big-picture strategy all the way down to the specific formulas. For our listeners who are ready to take action, can we summarize the "Playbook" we’ve built today?

Miles: I’d love to. Let’s break it down into five clear steps. Step one: The Internal Audit. Evaluate your jobs. Use a system like the Hay method or simple ranking to decide what each role is worth *to your company*. Don't look at the market yet. Just build your internal hierarchy.

Lena: Step two: Define the Buckets. Group those jobs into pay grades. Decide if you want a traditional structure with many grades or a broadbanded structure with more flexibility. This is where you create the "skeleton" of your system.

Miles: Step three: Market Anchoring. Go out and find your benchmark jobs. Use reliable surveys like Mercer or Towers Watson. Match the *work*, not the *title*. Set your midpoints based on your "pay policy"—do you want to lead, lag, or match the market?

Lena: Step four: Build the Architecture. Use the math we discussed. Calculate your minimums and maximums based on the range spread you want. Ensure you have meaningful "midpoint progression" between grades and a healthy amount of "overlap."

Miles: And step five: Continuous Maintenance. Audit your structure every year. Look for those "Red Circle" and "Green Circle" employees. Check for pay compression and equity gaps. And most importantly, communicate the "Total Rewards" value to your employees so they see the whole picture.

Lena: That’s a powerful framework. And I think the "pro move" here is remembering that it’s not just about the money. It’s about the *message* the money sends. Does this structure tell our employees we value their growth? Does it tell them we’re fair? Does it tell them we’re thinking about the future?

Miles: You’ve hit the nail on the head. A pay structure is a communication tool. It’s a physical manifestation of your company’s values. If you value transparency, your structure should be transparent. If you value global collaboration, your structure should support global mobility.

Lena: It’s been so fascinating to see how something that seems so "dry"—like a salary range—is actually at the heart of the "human" part of Human Resources.

Miles: It really is. It’s the bridge between the CFO’s budget and the employee’s life. When you get it right, everyone wins. The company stays within budget, and the employees feel valued and motivated.

Lena: I think that’s a perfect place to leave it. For everyone listening, I hope this gave you a new perspective on those spreadsheets you deal with every day. They’re not just numbers; they’re the foundation of your culture.

Miles: Well said, Lena. It’s been a blast digging into this with you.

Lena: As we wrap things up today, I’m reflecting on how much we’ve covered. From the initial job evaluation to the complexities of global pay and the necessity of regular audits, it’s clear that building a pay structure is one of the most strategic things an HR leader can do.

Miles: It truly is. It’s easy to get lost in the spreadsheets, but at the end of the day, we’re talking about how people are recognized for their contributions. It’s about respect, it’s about fairness, and it’s about aligning the organization’s resources with its highest priorities.

Lena: I’m curious, for those listening—what’s the one thing you can look at in your own organization today? Maybe it’s checking the compa-ratio of your team, or maybe it’s just asking if your current pay grades still reflect the reality of the work people are doing.

Miles: That’s a great challenge. Even a small step, like auditing one grade or looking at one market benchmark, can reveal so much. The goal isn't to be perfect overnight; it’s to start building a system that is logical and defensible.

Lena: Exactly. It’s a journey, not a destination. And the more transparent and intentional we are about it, the better our workplaces will be.

Miles: Absolutely. This has been a great conversation, Lena. I always enjoy peeling back the layers on these "technical" topics to find the human heart underneath.

Lena: Me too, Miles. It’s been a pleasure. And to everyone listening, thank you for joining us as we explored the fascinating world of pay structures. We hope you feel empowered to go back to your "playbook" and make some strategic moves.

Miles: Thanks for spending time with us. It’s been a real pleasure sharing these insights.

Lena: Take a moment today to reflect on how your organization defines "value." Is it reflected in your pay structure? If not, maybe it’s time to start building something new. Thank you for listening.