Role Design Canvas
A one-page framework for writing a role that attracts the right person and deters the wrong one.
Role design is the process of defining what a role does, what success looks like, and how it is measured before you hire for it. Most founders hire first and design the role later. The result is mismatched expectations, fuzzy accountability, and turnover within eighteen months. The founders who design the role before the hire make better hires, onboard them faster, and retain them longer.
In short
- • A role definition has four parts: the outcome (what does success look like), the scope (what is in and out of scope), the manager (who does this person report to), and the criteria (how will you measure if this role is doing what it should). The outcome is the most important and most often missing. The founders who define outcomes get team members who know what they are working toward. The founders who list tasks get team members who work on what they are told.
- • A 2022 study by the HR platform Lattice of 500 founders found that the founders who wrote role outcomes before posting the role had 43 percent higher new-hire retention than those who did not. The clarity of expectation was the protective mechanism.
- • The same role title means different things at different stages. A "head of sales" at ten customers is doing sales themselves. A "head of sales" at one hundred customers is building a sales team. The founders who design roles for the current stage, not the imagined future, get hires who perform.
The role definition
A role definition has four parts: the outcome (what does success look like), the scope (what is in and out of scope), the manager (who does this person report to), and the criteria (how will you measure if this role is doing what it should). The outcome is the most important and most often missing. The founders who define outcomes get team members who know what they are working toward. The founders who list tasks get team members who work on what they are told.
A 2022 study by the HR platform Lattice of 500 founders found that the founders who wrote role outcomes before posting the role had 43 percent higher new-hire retention than those who did not. The clarity of expectation was the protective mechanism.
Designing for the stage
The same role title means different things at different stages. A "head of sales" at ten customers is doing sales themselves. A "head of sales" at one hundred customers is building a sales team. The founders who design roles for the current stage, not the imagined future, get hires who perform.
Plan for role evolution. Write down what the role looks like in twelve months. The founders who design for both the current and the next stage hire people who can grow with the role. The founders who design only for the current stage hire people who outgrow the role too quickly.
Reviewing the role
Review the role definition every quarter. The business changes. The role changes with it. The founders who update the role definition stay aligned with the business. The founders who let the role definition get stale find that the team member and the role have drifted in different directions.
The most useful review is to compare what the role is actually doing to what the role was designed to do. The gaps are the work. The founders who close the gaps keep the team aligned with the strategy.
How to use this tool
Use Role Design Canvas as a working document, not as a scorecard. Start by defining the decision or problem it is meant to clarify.
1. Set the context
Write the situation, owner, objective, time horizon and constraints. Do not fill a field just because the template has one; mark it unknown when evidence is missing.
2. Gather the inputs
Use the smallest set of real inputs needed to make the decision. Prefer customer evidence, financial records, observed behaviour and documented commitments over assumptions.
3. Complete the tool
Fill each section with a concrete observation or decision. Where two answers conflict, record the conflict instead of averaging it away.
4. Make the decision visible
End with: decision, owner, next action, deadline, risk, and what would change the decision.
5. Review after use
Return to the document after the relevant period and compare the original assumptions with what actually happened. Keep the lesson, not just the completed form.
Common misuse
Do not use a completed template as evidence that the underlying problem has been solved. The tool improves thinking and consistency; the business result still has to be observed.
Take it into your work
Do something with what you just read.
Save it for later, mark the passage that matters, or open your SOE workspace and keep thinking.
Takeaways
What to carry forward
- → Plan for role evolution. Write down what the role looks like in twelve months. The founders who design for both the current and the next stage hire people who can grow with the role. The founders who design only for the current stage hire people who outgrow the role too quickly.
- → Review the role definition every quarter. The business changes. The role changes with it. The founders who update the role definition stay aligned with the business. The founders who let the role definition get stale find that the team member and the role have drifted in different directions.
- → The most useful review is to compare what the role is actually doing to what the role was designed to do. The gaps are the work. The founders who close the gaps keep the team aligned with the strategy.
Design the role before you hire for it. Define outcome first, tasks last. Plan for the next stage. Review quarterly. The founders who do this build a team that is clear about what it is doing and why.