Insights · Hiring guidance · 5 minute read

Before You Hire a Consultant, Get the Question Right

A contractor can deliver exactly what the brief calls for and still leave the client’s problem unsolved. Agree on the decision the work must support, who owns it and what evidence will count before anyone starts building.

By Vitaver Staffing ·

This article draws on The Method in the Vitaver Playbook. Before committing people or money, identify the question that will decide whether the work advances the mission. Write it where the sponsor, staff and contractor can all see it.

Ask what the person will be able to do

Imagine a county asks a consultant to build a dashboard showing how many permit renewals miss their target date. The consultant delivers a working dashboard. At the demonstration, the operations director asks why renewals are late and what staff should change on Monday. The project answered the question in the brief. The director had a different decision in mind.

The sponsor could have asked: “Which step accounts for the longest avoidable wait in complete renewal applications, and what change should we test next month?” That question changes the evidence the consultant needs. A count of late renewals tells the team how often the target was missed. To locate the delay, someone needs timestamps for handoffs, a definition of a complete application and a way to distinguish time waiting for the applicant from time waiting for internal review. If those records are missing, observe a sample of cases before promising a diagnosis.

Write enough for someone else to test the request

For a technical job, use the same discipline. Define the recurring decisions the new hire will own, where approval stays with someone else and what good work looks like at the first review. For example, an analyst might reconcile a weekly queue and flag conflicting records, while the service manager decides priorities. Assess applicants for the same role against the same job-related task and evidence.

The federal acquisition rules offer a useful reference for project briefs. FAR 37.602 on performance work statements emphasizes required results and measurable standards, and lists purpose and operating constraints among the elements of a statement of objectives. The companion section on performance standards connects the standard to how the work will be assessed.

Review the question before judging the answer

At kickoff, ask the contractor to restate the question, show a sample deliverable and name the assumption most likely to change the result. Give staff a deadline to confirm the evidence and correct the brief. If the contractor spots a mismatch between the stated output and the stated mission, raise it while there is still time to change course. Record any new scope and its effect on schedule and cost through the agreed approval path.

If a delivery disappoints, put the approved question, the evidence and the deliverable side by side. If the dashboard did what staff commissioned but the director needed a diagnosis, the sponsor owns the correction to the brief. If the brief clearly called for the diagnosis and the contractor supplied counts alone, the contractor owns that delivery gap. If both sides agreed to report late renewals but never defined a late renewal, check when each side recognized the ambiguity and had enough information to raise it. Assign the next action to the person able to correct that specific problem.

Before the next request goes out, hand it to someone who was outside the discussion. Ask them what decision the work serves, who will make it and what would count as done. Compare their answers with the sponsor’s. Resolve any material difference before setting the work in motion.

← All Insights