How to Set Clear Performance Expectations Before Hiring

By Don Georgevich

Phase One of the Scientific Hiring Method: The Blueprint

Performance expectations should not be invented after the person starts. They should be visible before the company interviews them.

Many employees are told what their job includes but not what successful performance looks like. They begin with a list of responsibilities, a few conversations, and an unspoken expectation that they will somehow figure out what matters most.

That ambiguity begins in hiring. If the company cannot explain what it expects the person to accomplish, it cannot gather the right evidence from candidates. It also cannot fairly decide whether the person is succeeding after the hire.

Performance expectations begin with outcomes

A responsibility tells the person what area of work they own. An expectation explains what successful performance in that area should produce.

For example, “manage the sales team” is a responsibility. “Within 45 days, install a weekly sales review that gives the owner a reliable forecast and gives each salesperson clear next actions” is an expectation.

The second statement gives the company something it can discuss with candidates, evaluate during hiring, and review after the person starts.

OPM explains that performance elements identify what employees must do, while performance standards explain how well they must do it. A performance standard is an expression of the threshold, requirement, or expectation that must be met at a particular level of performance. See OPM’s guidance on developing performance standards.

Set expectations before interviews begin

Writing expectations early protects the company from moving the goalposts around a candidate. It also gives interviewers a better question to answer.

Instead of asking whether the candidate seems experienced enough, the team can ask whether the candidate has produced similar results, how they approached the work, what obstacles they faced, and what evidence supports the claim.

The expectations should appear first in Define Success Before You Hire and then in the Job Scorecard. The job description should communicate the most important expectations to candidates, while the internal scorecard can contain more detail.

Include five parts

A clear expectation should identify the result, evidence, timing, standard, and support needed to produce it.

The fifth part is often missed. Expectations are not one-sided. The company must be honest about the authority, resources, information, and cooperation the person will have.

Use 30-, 60-, and 90-day expectations carefully

Early milestones are useful when they reflect what a new employee can realistically understand and influence. They become harmful when they are copied from a template without considering the role, the company, or the condition of the work.

At 30 days, evidence may include learning, diagnosis, relationships, and a clear understanding of the current state. At 60 days, the person may begin installing a process, making decisions, or delivering early work. At 90 days, the company may expect consistent use, visible progress, or proof that the person can operate with less direct support.

Not every role follows this exact pattern. A complex technical role may require more time before results appear. An entry-level role may require clear performance much sooner. The purpose is not to force every hire into the same calendar. It is to make the timing of expectations explicit.

Distinguish activity from performance

Activity is easier to count, but it does not always show whether the work is producing value. A recruiter can send many messages without building a qualified pipeline. A manager can hold many meetings without improving coordination. A salesperson can make many calls without moving important opportunities forward.

Use activity measures when they help explain the work, but connect them to outcomes. Ask what the activity is supposed to change and what evidence would show that the change occurred.

Define acceptable and strong performance

A single target may tell the employee what minimum result is required, but it may not explain what good judgment, quality, reliability, or ownership look like.

OPM recommends that standards be specific, measurable, attainable, relevant, timely, and written clearly. Its performance-management guidance also emphasizes setting expectations at the beginning of the performance cycle and applying standards consistently. See the OPM performance-management cycle.

For an Operations Manager, acceptable performance may mean the weekly review occurs, priorities are documented, and owners are assigned. Strong performance may mean the review consistently produces decisions, recurring failures decline, and the owner no longer has to rescue the same problems.

Make expectations observable

A good expectation gives the manager and employee something they can both inspect. It should not depend entirely on whether the manager feels satisfied.

Evidence may include work products, customer results, completed decisions, quality measures, project milestones, process adoption, error rates, response times, reliable forecasts, documented follow-through, or examples of improved judgment.

Use qualitative evidence when quality matters, but explain what good quality looks like. “Communicates well” is vague. “Raises risks early, makes decisions clear, and gives the right people enough context to act” is more useful.

Include the conditions of success

An expectation may be reasonable only when the employee has the needed authority, access, support, and cooperation. If the company expects a manager to improve a process but gives them no authority to change ownership, priorities, or meetings, the expectation is incomplete.

Write down major dependencies. Identify decisions the person can make, people they need access to, information they must receive, and support the manager must provide.

This makes the hiring conversation more honest. Candidates can explain whether they have worked under similar conditions, and the company can see whether its expectations are realistic.

Use expectations during interviews

Each major expectation should lead to one or more interview questions. Ask candidates to describe comparable work, the decisions they made, the obstacles they faced, the evidence they used, and the result they produced.

A work sample can then represent a smaller version of the same expectation. If the person must diagnose a broken process, give them a realistic process problem. If they must build a forecast, let them work with a simplified set of relevant information.

The goal is not to make candidates perform unpaid work for the company. It is to give them a fair chance to show how they approach the kind of work the role requires.

Review expectations after the hire

The original expectations should become the starting point for onboarding and early performance conversations. They should not disappear once the offer is accepted.

During the first 30, 60, and 90 days, compare actual progress with the outcomes, evidence, timing, and support written before the search. When the person is behind, ask whether the issue is capability, unclear direction, missing resources, unrealistic timing, or a change in business conditions.

This keeps the company from blaming the employee automatically or quietly changing the standard after the fact. It also gives the hiring process feedback. When the person performs differently than expected, look back at the evidence gathered during hiring and ask what the company missed or misunderstood.

A completed expectation example

Common mistakes

The first mistake is using responsibilities as though they were expectations. “Manage projects,” “support customers,” and “lead the team” describe areas of activity but not successful performance.

The second mistake is setting expectations that depend on results the employee cannot reasonably control. A person should be accountable for their decisions, work, and influence, but not for every outside condition.

The third mistake is setting goals without defining evidence, quality, or timing. A number alone may encourage the wrong behavior if it ignores how the result is produced.

The fourth mistake is withholding the standard until after hire. Candidates should understand the central expectations before accepting the role, and the hiring process should gather evidence connected to those expectations.

The final mistake is changing the standard without acknowledging the change. Business conditions may shift, but new expectations should be discussed clearly rather than treated as though they had always existed.

Review your performance expectations

• Each expectation states a result rather than only an activity.
• The evidence of progress or success is clear enough to review.
• Timing reflects the real complexity and condition of the role.
• Acceptable and strong performance are meaningfully different.
• The employee can reasonably influence the expected result.
• Major dependencies, support, resources, and authority are stated.
• The expectations appear in the job scorecard before interviews begin.
• Interview questions and work samples connect to the expectations.
• The same expectations will guide onboarding and early performance reviews.
• Changes in expectations will be discussed and documented openly.

Legal and fairness note: Performance and conduct standards should be applied consistently. Employees with disabilities generally must be able to perform essential job functions, with or without reasonable accommodation, and qualification standards should be job-related and consistent with business necessity. See the EEOC’s guidance on applying performance and conduct standards. This page is educational and is not legal advice.

Phase One is complete

Clear performance expectations close the loop that began with defining the role. The company now has a reason for the position, outcomes, evidence, entry capabilities, hiring criteria, and an early standard for judging whether the decision worked.

The next phase of the Scientific Hiring Method is Attraction: building a dependable way to attract better candidates before the role becomes urgent.

After the employee starts, compare these expectations with actual performance through Quality of Hire. This closes the loop built into the Scientific Hiring Method.