The Hiring Problem May Begin Before the Job Posting

A team misses a target. Work is falling between functions. A leader is carrying too much. The organization decides it needs another person.

Recruiting begins with a familiar list: responsibilities, preferred experience, competencies, and a title borrowed from another company. The search may produce capable candidates. The role can still fail because the organization has not decided what the person will truly own.

Many hiring problems begin before a recruiter sees the job. They begin when accumulated pressure is mistaken for a coherent role. This is often the same moment described when an operating model has outgrown its ambition: the work has changed shape, but the design underneath it has not.

A job description can hide an unresolved operating problem

Consider a company hiring a vice president to “own growth.” Marketing owns demand. Sales owns revenue. Product owns the offer. Customer success owns expansion. The new leader is expected to improve all four without clear authority over any of them.

The title sounds senior. The mandate is broad. The decisions remain elsewhere.

Once the person starts, ordinary disagreements expose the design. Which team sets the commercial priority? Who can change the offer? What happens when near-term revenue conflicts with retention? The new leader becomes a coordinator, an escalation point, or the person blamed for an outcome no one gave them the means to control.

That is not primarily a selection problem. It is a role-design problem.

Define the outcome before the activity

A useful role starts with the result the organization needs, not the tasks currently without an owner.

Before opening a search, answer five questions:

1. What outcome will exist because this role exists? Name the change the person must create, not the meetings they will attend.
2. Which decisions belong to the role? Authority should be clear enough that the person can act without renegotiating the mandate each week.
3. Where does the role depend on others? Identify the teams, information, and handoffs required to deliver the outcome.
4. How will progress be judged? Use measures the person can influence and that reflect value, not only activity.
5. What work or authority moves from current leaders? A new role is not real if the old owners keep every meaningful decision.

These questions make the job more specific. They also reveal when one proposed role is actually several incompatible jobs.

Separate capability from rescue

Organizations often write roles around the person they hope will save the situation: strategic and tactical, visionary and operational, able to influence everyone, comfortable with ambiguity, and willing to “roll up their sleeves.”

Some roles genuinely require range. But a long list of heroic traits can signal that the system is asking one person to compensate for unclear priorities, missing processes, or unresolved executive ownership.

Hire for the capabilities the strategy requires. Do not use capability language to disguise conditions that would prevent a strong person from succeeding. When the gap is really about judgment and influence at the leadership level, the better answer may be leadership development rather than a new hire.

Test the real work, not interview fluency

Once the role is clear, selection becomes more grounded. Candidates can respond to a representative situation: a decision with competing inputs, a cross-functional handoff, a difficult tradeoff, or the first 90 days of the mandate.

A useful work sample tests how the candidate frames the situation, what evidence they seek, which decision they would make, and how they would bring others through it. It should resemble the work closely enough to reveal judgment without asking candidates to perform unpaid client work.

The same clarity improves reference conversations. Instead of asking whether someone is “strategic,” ask how they handled the kind of authority, ambiguity, pace, and interfaces the role actually contains.

Onboarding is the first test of the design

The role is not finished when the offer is accepted. Onboarding should make the operating contract visible.

The new hire needs to know:

• the outcomes they own;
• the decisions they can make;
• the decisions they influence but do not own;
• the people and teams with whom the work must move;
• the measures that matter;
• the unresolved questions they are expected to help answer.

If leaders cannot explain those elements consistently, the organization has learned something important. The role still needs design.

Better hiring starts with better organizational choices

People matter enormously. So do the conditions in which they are asked to perform.

When a business defines the outcome, authority, interfaces, and measures before it recruits, candidates can judge the opportunity honestly and leaders can select for the work that must be done. The person enters a role instead of a collection of expectations.

That is how hiring supports the business story: the organization builds the capability required to make its strategy real.

If a critical role is difficult to define or repeatedly fails to deliver, explore NWC’s organizational design consulting or start a conversation about the work behind the hire.