It’s tempting to blame the interview stage when hiring doesn’t work out. But more often than not, the cracks appear earlier, in the process that leads to it and in the reasoning behind the role itself.
A role gets approved. A recruiter is looped in. The process begins moving.
But pause for a moment; what actually triggered that process?
Was it a clearly defined business need?
Or was it pressure, urgency, or a gap that suddenly became visible, especially in critical systems like Workday, where delivery timelines and system dependencies create immediate pressure?
Most hiring processes are designed to move efficiently once a role is open. But process efficiency cannot compensate for a lack of intent. When the “why” behind a hire isn’t clear, the entire process becomes reactive, focused on filling rather than solving.
This is where hiring quietly starts to fail.
And in Workday environments, this becomes even more visible. Teams are often built around immediate system requirements, such as implementations, integrations, and reporting, without fully defining long-term capabilities or ownership. But if the intent isn’t anchored in outcomes, the process simply moves faster in the wrong direction.
Intent defines:
- What success in the role actually looks like?
- What capabilities are truly needed?
- How this hire connects to business priorities?
Without that, hiring becomes a cycle of activity without precision. And lack of process and strategy turns into intent gaps, a common hiring mistake when building Workday teams without clear ownership of system outcomes.
A strong hiring approach brings both together, with a clear intent guiding a structured process.
That’s why fixing hiring isn’t just about improving steps within the process.
It’s about strengthening the thinking that comes before it.
Because hiring works best when process and intent are aligned from the very beginning.
Recruitment Is Execution. Formation Is Strategy
Recruitment is often expected to solve problems it didn’t create.
A role is approved. A job description is drafted. A recruiter is briefed. And the expectation is clear: find the right person.
- But what if the role itself isn’t clearly defined?
- What if the expectations are misaligned?
- What if the real business need hasn’t been fully understood?
This is where formation comes in.
Formation, in practical terms, is the work that happens before hiring begins:
- Defining what success looks like in the role
- Mapping the capabilities required to achieve it
- Aligning stakeholders on expectations
- Connecting the role to broader business goals
Without formation, hiring becomes guesswork.
As per a recent Workday research, over half of organisations (55%) have already adopted skills-based approaches to drive greater adaptability and resilience.
When hiring Workday talent, availability for the right skills at the right time is crucial for any project.
Instead of asking:
- “Who can fill this role?”
The better question is:
- “What problem are we solving, and what does success look like?”
This is the shift from reactive hiring to intentional formation.
It’s the difference between:
- Filling a position vs solving a business need
- Hiring roles vs designing outcomes
Where Most Hiring Goes Wrong
When hiring struggles, the instinct is to fix the process. But the real breakdown usually happens upstream.
Here’s where things begin to unravel:
-
Vague Job Requirements
“We need a senior profile.”
That sounds unclear, since the title does not define the role.
Seniority without defined outcomes creates confusion, both internally and for candidates. Especially in Workday hiring, where “senior” could mean anything from configuration support to solution design.
-
Misaligned Stakeholders
Hiring Managers, HR, and leadership often operate with different expectations.
One wants speed.
Another wants precision.
Another wants transformation.
Without alignment, hiring becomes inconsistent and unpredictable. A common issue in Workday Projects, where multiple stakeholders expect outcomes from a single hire without defining clear ownership. Each role has a distinct focus, but confusion arises when one hire is expected to cover multiple areas without defined priorities.
-
Title-Driven Hiring
Job titles are treated as shortcuts for capability.
But titles don’t guarantee skills, context, or impact.
They rarely reflect what the business actually needs. Job titles may vary from company to company, but what matters most is defining their skills and responsibilities.
-
Poor Intake Conversations
Recruiters are often briefed on roles, but they also need to understand the requirements.
Instead of discussing:
- Business goals
- Team gaps
- Success metrics
The focus remains on responsibilities and experience ranges.
That disconnect shows up quickly in candidate quality and may lead to mismatches in specialised Workday roles.
The reality is simple:
A strong hiring strategy is built around clear business requirements and defined expectations.
And the best candidates respond to opportunities that move their careers forward, especially when these opportunities clearly define ownership and impact within the Workday ecosystem.
The Hidden Cost of Poor Formation
When formation is weak, the impact isn’t always immediate, but it compounds over time.
You start to see:
- Longer time-to-hire as clarity issues slow down decisions
- Higher reliance on agencies to compensate for internal gaps
- Offer drop-offs when candidates sense misalignment
- Early attrition because expectations don’t match reality
- Recruiter fatigue from repeated resets and unclear direction
When building a Workday team, what looks like a hiring problem is often a planning problem in disguise; it causes delays in the system and affects stabilisation and optimisation efforts.
And the cost affects daily operations, team momentum, business timelines, and overall confidence in hiring outcomes.
What “Fixing Formation” Actually Looks Like
Improving hiring outcomes doesn’t start with new tools or more interviews. It starts with better thinking before the search begins.
A simple formation-first approach can reshape how hiring works:
Step 1: Start with Outcomes
Before defining a role, define success.
- What needs to be achieved in 3, 6, or 12 months?
- What impact should this role create?
For Workday teams, this means moving beyond generic asks like “senior consultant” and instead defining outcomes, such as owning payroll configuration stability, improving reporting accuracy, or reducing manual HR processes through Workday.
Clarity here reduces ambiguity everywhere else. It ensures that the roles are clearly defined with ownership and measurable impact.
Step 2: Map Capabilities, Not Titles
Focus on skills and contributions, not labels.
- What capabilities are required?
- What problems should this person be able to solve?
This opens up stronger, more relevant talent pools. In a Workday environment, hiring often means aligning different modules to work seamlessly.
Define hiring strategies for:
- Core technical capability (modules, integrations, reporting)
- Functional understanding (HR, Finance, Data)
- Stakeholder interaction (business-facing vs backend)
Step 3: Align Hiring to Project Phases
Different phases of Workday projects require different capabilities. It is important to clarify which phase of the project you are in, and this step starts with asking:
Where are we in the Workday Project lifecycle, and what does success look like in this phase?
What capabilities are needed at this stage?
What should this role be responsible for right now?
The answers depend on the phase of the project:
- Pre-Signature: (Strategy & Alignment):
Aligning on goals, scope, and what the transformation needs to achieve. - Plan, Design & Architect: (Future-state design)
Defining processes, requirements, and how the system should work. - Configuration: (Building systems)
Building the system, setting up modules, and enabling integrations. - Testing & Deployment:(Validation & go-live readiness)
Building the system, setting up modules, and enabling integrations. - Business As Usual: (Optimisation & adoption)
Improving performance, driving adoption, and continuously optimising the system.
Hiring should reflect clear business needs and opportunities that result in a measurable impact.
Step 4: Build for Flexibility
Avoid rigid team structures.
Instead, structure intake discussions around clarity:
- What business problems are we solving?
- Where is the current gap between the Workday team?
- How will this role interact with existing team members?
Businesses evolve, and so do the roles they need to grow and scale.
A flexible approach ensures hiring stays relevant over time.
Conclusion: Fix the Beginning, Fix the Outcome
Hiring failures are rarely just hiring failures.
They often result from unclear thinking, misaligned expectations, and rushed decisions made before recruitment even begins. It is a pattern frequently seen in hiring for Workday teams, where urgency may overtake structure due to the high stakes of a project.
Better hiring doesn’t start with sourcing strategies or interview frameworks. It starts earlier in the process with clarity, structure, and intent for the business requirements and expectations.
Contact us for a practical guide to help you move from reactive hiring to structured, outcome-driven workforce planning and build stronger, more effective Workday teams.
