Position Descriptions That Actually Guide Performance
Why CEOs, executive directors, and board leaders must replace activity-based job descriptions with outcome-based leadership architecture
By Hugh Ballou
Most executives can name every title on the organization chart. Fewer can clearly name the measurable contribution each role must produce this quarter. That gap is where performance problems begin. It is also where leaders unknowingly create bottlenecks, confusion, and under-functioning teams.
A job title can locate a person in the structure. It can indicate rank, department, or reporting line. But a title does not define performance. “Development Director” does not tell the executive team what revenue streams must be built, what donor stewardship rhythm must be sustained, what authority the role carries, or how success will be measured. “Chief Operating Officer” does not automatically clarify which systems must be strengthened, which decisions belong to the role, or what measurable outcomes should appear on the dashboard.
A job title tells people where they sit. A position description tells them what contribution they are responsible for producing.
For CEOs, executive directors, and board leaders, this distinction matters. Organizations do not scale because they add titles. They scale when leaders convert strategy into outcomes, outcomes into ownership, and ownership into a review rhythm. That is the work of a position description that actually guides performance.
The title trap
Many organizations still treat position documentation as human resources paperwork. A traditional job description often lists duties, qualifications, reporting relationships, and generic responsibilities. It may be useful for recruiting, compliance, or salary benchmarking. But once the person is in the role, that document often disappears into a file while performance expectations drift back into verbal assumptions.
The executive problem is not that people lack commitment. In mission-driven organizations, commitment is often abundant. The deeper problem is that the leadership system has not defined what performance means. Leaders then evaluate people against expectations that were never fully written, shared, measured, or reviewed.
From duties to deliverables
Activity language sounds productive but can hide ambiguity. Words such as manages, coordinates, oversees, supports, and assists describe motion. They do not always define value. Outcome language is different. It uses verbs such as completes, produces, builds, launches, sustains, measures, and improves. It names what the role must contribute to the organization.
Consider the difference between “oversees donor communications” and “sustains a monthly donor communication rhythm that increases retention, deepens engagement, and supports eight recurring revenue streams.” The first describes an activity. The second describes contribution. One gives a person something to stay busy with. The other gives the leader and team a measurable expectation.
A position description is leadership architecture
An effective position description is an operating agreement between strategy and performance. It translates the strategic plan into human contribution. It clarifies why the role exists, what it must produce, what authority it carries, what support relationships it requires, and how performance will be reviewed.
This is especially important in nonprofit and purpose-driven organizations, where paid staff, board members, committees, advisors, and volunteer or servant-leader roles all contribute to mission results. If these roles are described only by title and tradition, the organization becomes dependent on personality, memory, and executive rescue. If they are described by outcomes and ownership, the organization gains repeatable capacity.
The seven elements of a performance-guiding position description
The first element is position definition: why the role exists and which strategic outcome it advances. If the role cannot be connected to strategy, it may need to be redesigned. The second is roles and responsibilities, written in outcome language wherever possible. Responsibilities should point toward deliverables, not simply categories of activity.
The third element is specific competencies. These should not be generic traits copied from another document. Competencies must be tied to the outcomes the role is expected to produce. The fourth is term of service, including duration, renewal, transition, and succession clarity. This applies not only to board and committee roles, but also to key leadership assignments that should be reviewed as strategy evolves.
The fifth element is performance expectations. Every significant role should include 90-day and one-year outcomes that can be reviewed quarterly. The sixth is support roles and collaborations: the internal and external relationships needed for success. The seventh is authority limits and culture fit: what the person can decide, where input is required, and how the role embodies the organization’s values and guiding principles.
Write the role from strategy backwards
Too many organizations begin with an old job title and revise the bullet points. Executives should begin with the strategic priority. What outcome must be produced for this strategy to move forward? Which role owns that outcome? What authority, resources, and collaboration are required? What will be visible in 90 days if the role is working?
This approach changes the leadership conversation. Instead of saying, “We need a marketing person,” leaders ask, “What measurable visibility, engagement, and conversion outcomes does our strategy require?” Instead of saying, “We need a board development committee,” leaders ask, “What board capacity, referral, stewardship, and governance outcomes must be produced this year?”
Make expectations a living data field
Annual performance reviews are too slow for fast-moving mission work. By the time a leader waits twelve months to address unclear expectations, the organization has already paid the cost in delays, frustration, turnover, or missed opportunity. Performance expectations should be living data fields, reviewed and adjusted as strategy, capacity, and market conditions change.
Quarterly review rhythms make performance more objective. The leader is no longer forced into vague personality conversations. The team can ask: What outcomes were agreed upon? What progress is visible? What support is missing? What has changed? What needs to be adjusted for the next 90 days?
The executive payoff
Clear position descriptions reduce executive over-functioning. When people do not know the outcomes they own, work flows back to the senior leader. The executive answers every question, fills every gap, and becomes the organization’s performance system. That is not leadership scalability. It is heroic exhaustion.
Clear authority limits also prevent two common problems: hesitation and free-range decision chaos. When authority is undefined, capable people either ask permission for everything or make decisions that should have been aligned with others. A good position description gives people freedom within boundaries.
The leader’s role is to conduct performance, not rescue it. Like a conductor, the executive clarifies the score, sets the tempo, listens across the whole system, and helps each player contribute to the larger result. The instrument is not the title. The music is the measurable contribution.
The leadership challenge
Choose one critical role this week. Rewrite it from strategy backwards. Replace five activity verbs with measurable deliverables. Clarify what the person can decide without further approval. Then review the description with the person in the role and ask, “Is this the contribution the mission actually needs from this seat?”
Performance improves when expectations are written before disappointment arrives. Leaders do not scale organizations by assigning titles. They scale organizations by clarifying outcomes, authority, ownership, and rhythm. A position description is not paperwork. Done well, it is performance architecture.
More resources from Hugh Ballou at http://AboutHugh.com
