A professional services firm had no shared definition of "good." Managers hired against one standard, evaluated performance against another, and had no common language for coaching or promotion. I replaced siloed job descriptions with one competency framework that fed six connected systems: hiring, performance reviews, development, manager coaching, compensation, and internal mobility. Within six months, project escalations dropped 26%. By end of year one, they were cut in half.
Roles existed. Standards didn't.
At a professional services firm I worked with, no one agreed on what "good" looked like. Managers interpreted expectations differently. Employees didn't know how to grow. HR hired against one definition; the business evaluated performance against another.
Job descriptions described the role. They didn't define success. That gap showed up everywhere.
One framework. Six systems. No interpretation required.
I replaced job descriptions with a competency framework built to connect every system to the same source of truth. Every role broken down into specific, observable behaviors. A manager and an employee could read the same criteria and know exactly what good looked like.
Most competency models get referenced once a year during review season. This one fed hiring, performance, development, compensation, and coaching from the same source.
Hiring
Interview questions pulled directly from competency criteria. Evaluators assessed real behaviors from documented evidence.
Performance management
Reviews built around the same language. No invented expectations. Ratings consistent because the standard was shared.
Training and development
Performance gaps mapped to a specific competency. Training had a clear target. Development conversations had a starting point.
Manager coaching
Managers coached against defined criteria, with something concrete to point to. One-on-ones became more direct and more useful.
Compensation
Contribution measured against defined criteria. Pay decisions became easier to defend and harder to dispute.
Career and internal mobility
Employees saw exactly what each level required. Growth had a roadmap. Movement across roles had clear criteria.
What a competency form actually looks like.
Every role had a form like this one. Each competency written as a specific, observable behavior — no interpretation needed in a review or a coaching conversation.
This example is from a professional services firm, for consultants leading technical implementations. The structure works for any role in any organization. The criteria change. The approach doesn't.
- Prepares a written agenda before every client meeting and sends documented next steps within 24 hours.
- Flags scope changes in writing before acting on them — never assumes verbal agreement is enough.
- Adjusts detail level for the audience: summary for sponsors, specifics for day-to-day users.
- Surfaces risks to their workstream before they affect the project timeline — and brings a proposed path forward.
- Completes handoffs so cleanly that the next person can pick up the work without a walkthrough.
- Owns the quality of their output — doesn't rely on a senior team member to catch errors.
- Gives a clear recommendation when a client is weighing options — doesn't present choices without a point of view.
- Flags downstream consequences of a client decision before it's made, not after.
- Backs recommendations with reasoning the client can evaluate, not just assertions.
- Tells a client clearly what is configurable, what requires a workaround, and what is out of scope.
- Demonstrates core platform functionality without relying on a scripted walkthrough.
- Flags when a product update affects an active project before it becomes a problem.
- Writes test cases against real client workflows — not just technical functionality.
- Documents defects specifically enough that another person can reproduce and fix them without follow-up.
- Distinguishes between a defect, a config gap, and a scope change — and routes each appropriately.
- Validates source data against target requirements before migration begins — not during.
- Documents mapping decisions so that errors can be traced to their source after the fact.
- Runs reconciliation checks after migration and resolves discrepancies before sign-off.
The framework defines the path forward.
Every form was built with movement in mind. Advancement, lateral shifts, and track changes all had defined criteria. Employees knew what the next step required. Managers had something concrete to coach toward.
Switching tracks meant identifying what carried forward and what needed to be built. That conversation was grounded in documented criteria rather than guesswork.
When escalations spiked, the framework showed exactly where to look.
Project quality issues were traced back to inconsistent documentation and QA practices. The framework pinpointed the competency gaps. We worked with frontline managers, updated the criteria, built targeted training, and pushed it out through the same system already in place.
Clear criteria made the diagnosis fast. A flexible system made the fix straightforward.
What guided the build.
One language. Every decision.
Hiring, performance, development, and compensation all ran off the same foundation. Managers coached with better tools. Employees had clearer expectations. Hard conversations became practical ones — because the criteria were already defined and shared.