A previous article talked about conducting Fit Checks to ensure you have the right people on your team.
Now we tackle the next critical question:
"How do I make sure my people know exactly what success looks like in their role?"
After 30+ years of working with teams, I've discovered something that might surprise you:
People usually want to do well. They want to contribute. They want to succeed. But if they're not clear on what "success" means in their specific role, they'll spend their energy on the wrong things, miss important priorities, and leave you wondering why they're not performing better.
Most jobs come with a title and some kind of a job description. That’s usually a good start, but it isn’t uncommon for an employee to still have questions about the specifics of the job and how they can succeed in that role.
The solution isn't lengthy policies or micromanagement.
It's crystal-clear Roles, Accountabilities, and Responsibilities (RARs).
Traditional job descriptions are often mildly useful documents that check a box for hiring requirements, but don't really do much to help a new employee succeed.
They're filled with generic language like:
Job descriptions often focus more on qualifications than on the results that a person in the role should generate in order to be considered successful at that role.
RARs are different. They're living documents that clearly define:
When someone has clear RARs, they can make better decisions, prioritize effectively, and take ownership of outcomes that matter.
The Role defines why this position exists and how it connects to the company's success. It answers the question: "What is this person here to accomplish?"
A good Role statement:
Example Role (Sales Manager): "Lead and develop our sales team to consistently achieve revenue targets while building strong customer relationships that drive long-term business growth. Serve as the bridge between company strategy and front-line execution, ensuring our sales approach aligns with our values and delivers exceptional customer experiences."
A good Role statement can be summarized in a simple list of core elements. For example, the above Sales Manager role could be summarized very simply as:
Accountabilities are the 3-5 key results this person is responsible for delivering.
These are the outcomes that, if achieved consistently, will make this role successful.
Good Accountabilities are:
Here's some example Accountabilities for the Sales Manager role above:
Each of these should be discussed with the employee and broken down further into specific goals and KPIs that will be tracked and reviewed regularly with the employee.
Responsibilities are the key activities, tasks, and behaviors that support the Accountabilities.
They can be thought of as “the How actions that will lead to the What outcomes”.
Good Responsibilities:
Here's some example Responsibilities for the Sales Manager role above:
The specifics of Responsibilities will often change and evolve as the business changes, but the high level elements in the Role will usually stay the same. For example, the Sales Manager will always need to Drive Growth, Lead the Sales Team, and Build strong Customer Relationships, no matter how the business changes.
Don't let RARs just live in your head or in verbal conversations.
Write them down. Share them. Review them regularly.
A clear RARs document becomes a powerful tool for:
Here's how to develop effective RARs for your team:
Before writing anything, be clear about what you need this role to accomplish for your business. What problems does it solve? What opportunities does it create? How does it support your company's goals?
Don't write RARs in isolation. Have conversations with the person in the role (if it's an existing position) or with others who understand the work. The best RARs come from dialogue, not dictation.
Resist the temptation to list every possible task. Instead, focus on the outcomes that matter most. What results will make this role genuinely successful?
Vague Accountabilities lead to vague performance. Instead of "improve customer satisfaction," try "maintain customer satisfaction scores above 8.5/10 and resolve customer issues within 24 hours." Use AI here to help you come up with SMART goals for the Accountabilities.
RARs should evolve as your business grows and changes. Review them at least annually, and update them when roles significantly change.
The key to successful RARs isn't just creating them. You've got to use them consistently:
When you implement clear RARs across your team, you'll notice several changes:
Pick one role on your team that would benefit most from clearer expectations. Set aside some time this week to draft RARs for that position. If someone is currently in the role, involve them in the conversation.
Don't aim for perfection. Aim for clarity that's better than what you have today.
Remember: Your people want to succeed. Your job is to make it crystal clear what success looks like.
Our Foundations workshop has an entire section on RARs, and we have tools and templates to help you with this process.
I'd be glad to help you think through how to create expectations that drive results.