How to test a workforce decision, set an evidence standard, and judge whether the process can work in another part of the business.
At our November 11 Skills Roundtable, a talent leader described a pilot her organization was planning. The team wanted to help proposal leads find people whose skills met the technical and client requirements for a bid. A central function could assemble the information. The proposal lead would still decide who to staff.
That division of responsibility gives the pilot a clear test. Can the proposal lead use skills evidence to put together a qualified team faster or with fewer unresolved gaps? The group discussed possible outcome measures, including how many proposals get staffed or submitted. The team was still planning the pilot and had yet to set targets. That made it a good time to agree on a baseline and decide what improvement would justify further investment.
Define the decision before collecting data
Start with one use case, one workforce segment, and one recurring decision. Identify who has authority to act, when the decision occurs, and how exceptions will be resolved. In proposal staffing, the review might happen whenever a bid reaches a defined stage. The lead assesses who meets the requirements, what evidence supports that assessment, and who is available.
Choose a measure the owner can observe in that workflow. Time to assemble a qualified team or the proportion of proposals staffed by the deadline could show whether the process improved. Win rate may be worth following over time, with the recognition that pricing, competition, and other factors also affect it. Profile completion can help diagnose participation along the way.
Set an evidence standard for the action
The staffing discussion surfaced a common sequence. A team may start with employee self-assessments, add manager validation, and use role-based inference where reported data is sparse. Each source has limitations. Self-ratings vary in accuracy, managers see different slices of someone’s work, and inference from a job title inherits the limitations of that title. Recent, relevant work evidence can help resolve a disagreement.
The consequences of the decision determine how much confidence you need. A self-assessment may support a learning recommendation. A shortlist for a client assignment may call for recent work samples or a manager’s validation against the requirements. Decide who reviews conflicting evidence and how the team records the rationale.
Ask what the pilot evidence supports
We tested this distinction with a fictional mobility case. In 12 weeks, 84% of 120 employees completed profiles and the platform surfaced 18 possible matches. It relied largely on job titles and profile histories. Work evidence and manager validation were incomplete, receiving managers lacked a shared definition of readiness, and disputed matches had no review owner. The sponsor wanted to add three divisions before any moves or post-move results were available.
One participant favored testing readiness reviews with the current population. That would give the team a chance to define what “ready” means, see whether reviewers apply the criteria consistently, and learn how much effort each review takes. A bounded expansion of exploratory matching could also be considered if the sponsor defines what people can do with the matches and who will monitor the results.
Review the workflow and cost of expansion
Another participant described the practical challenge of getting agreed job skills into a separate recruiting system. The hiring manager needs those skills at the point of review, alongside the requirements for the particular role. That is a concrete test of integration. Map the information to the point where the manager uses it, and decide which system or role owns it when records disagree.
Our Skills Pilot-to-Scale Scorecard examines decision clarity, skills signal fit, trust and confidence, workflow integration, governance and ownership, outcome evidence, and scalability. Use it to find the condition that could block the next step. If a pilot worked because a coordinator manually reconciled records each week, estimate the review effort in the next division and establish who will own that work.
Set the next test with your sponsor
Use the Skills Pilot Design Canvas to document the decision, evidence standard, workflow, measures, and what you expect to carry into the next setting. Before the next sponsor review, pick one assumption to test. Name the owner, the evidence they will review, and the date. Then decide whether to expand under explicit conditions, continue testing, redesign, or defer.
If your team has a priority use case and needs a pilot plan for sponsor review, our three-week Skills Pilot Design Sprint covers one use case and one employee population. It produces a pilot charter and measurement plan. Contact Brian at brian@richardsonconsultinggroup.com to discuss your use case.