How to Write an Effective Job Description: Start With the Role, Not the Document

Aug 26

3 min read

A job description is not a list of everything someone could possibly do.

Too many job descriptions begin with an old document, a list of tasks someone is already carrying, or a collection of responsibilities that no one else wants.

Start somewhere else: What does the organization need this role to accomplish?

A strong job description should help a candidate understand not only what they will do, but why the role exists, what they will own, where they sit in the organization, and what should be different because they are there.

Before You Write the Job Description

Why does this role exist?

What organizational need, growth, gap, risk, or opportunity created the position?

“Because the Executive Director has too much to do” is a capacity problem. It is not yet a role.

Get more specific. What work needs an owner? What decisions need to move away from another position? What function needs greater capacity, expertise, or accountability?

If you cannot explain why the role exists without describing the person who currently has too much work, keep going.

What should this person own?

Separate ownership from participation.

A job filled with phrases like “assist with,” “support,” and “help manage” may signal that the organization has not actually decided who owns the work.

Ask:

· What is this person responsible for producing?

· What can they decide?

· What requires approval?

· What relationships or processes do they own?

· Where does responsibility sit when work crosses departments?

Someone can collaborate on a function without owning it. The job description should make the distinction clear.

What are the essential responsibilities?

Do not turn the posting into an inventory of every task the employee might touch. Group work into meaningful areas of responsibility.

A useful test: If this responsibility disappeared, would the reason for having the position materially change?

If not, it may not belong among the role’s core responsibilities.

What level of responsibility does the work require?

Title should follow scope.

Consider:

· Complexity of decisions

· Independent judgment

· Budget or revenue responsibility

· People management

· Organizational influence

· External representation

· Technical expertise

· Accountability for outcomes

A manager without management responsibility may not be a manager. A director responsible primarily for executing someone else’s plans may not be designed at the director level.

Titles that do not match the work eventually create problems with compensation, authority, career progression, and organizational structure.

Define Success Before You Hire

One of the most useful questions in role design is also one of the least frequently answered:

What should be different because this person is here?

Think beyond activities. Instead of “Manage organizational partnerships,” ask what successful partnership management should produce. Instead of “Maintain organizational data,” ask what should become more accurate, timely, useful, or actionable.

Consider three horizons:

· First 90 days: What should they understand, stabilize, establish, or begin?

· Six months: What should they independently own or have meaningfully improved?

· One year: What organizational result should be visible?

If you cannot describe success before someone starts, evaluating performance later becomes considerably harder.

Are You Hiring for Today Only?

Organizations often create positions in response to immediate pressure. That may solve today’s problem while creating tomorrow’s structure.

Consider what happens if the organization grows, adds programs or locations, receives substantially more funding, loses a revenue source, or adds several employees.

You do not need to predict the future perfectly. You do need to know whether the role is a temporary response to pressure or part of the organization you are intentionally building.

The Workroom Standard

Before a job description is ready to post, you should be able to explain:

· Why the role exists.

· What the person owns.

· How the role fits into the larger organization.

· What level of authority comes with it.

· What success looks like.

If those answers are unclear, the problem may not be the job description.

The role itself may need more work.

The Opportunity Board asks employers to make these decisions before a position is published. That is intentional. Candidates should not have to figure out what the job is after they apply.