In the Indian ecosystem, the standard hiring drill is intimately familiar. An open position emerges, perhaps a senior role, and the immediate reaction is to source a candidate profile from competitors or create a generic job description created with a certain GPT.
The requirement list looks predictably ambitious: 8 – 10 years of experience, MBA preferred, exceptional communication skills, proactive leader, multi-tasker, expert in client management.
Two months later, after rounds of polite conversations, resume scanning, and negotiation over fixed versus variable compensation, a candidate is hired. On paper, they fit the mold. In practice, six months in, operational friction persists, delivery slips, cross departmental coordination is still ineffective, and leadership finds themselves stepping back into hands on execution.
The reality is, the organisation did not hire a bad employee, It executed a flawed selection process.
Standard job descriptions are one dimensional and do not test for execution capabilities, nor do they measure the operational reality of the business.
1. The Trap of “CV Theatre” and Wish List Hiring
Most job descriptions are not operational role definitions; they are often wish lists. They often combine high level strategic buzzwords with an overwhelming laundry list of daily tasks with conflicting behaviours.
When a role description demands that a single person manage growth, sales and operations, it creates two distinct problems:
- It penalises focused executors: Real operational talent often excels at managing specific systems, enforcing processes, and eliminating execution delays. When presented with a vague, all encompassing JD, high performing operators often recognize an under structured system and opt out.
- It rewards articulate generalists: Candidates who excel at interviewing know exactly how to speak to every point on a broad wish list. They speak the language of management, present well in panel interviews, and articulate past achievements with confidence, regardless of whether those achievements were driven by their individual effort or by the systemic tailwinds of their previous employer.
In an ecosystem where professional polish is often conflated with operational competence, low effort JDs evaluate how well someone can talk about work, not how effectively they can build and run a system.
2. Adaptability / Transferability Failure
A frequent misstep in hiring is assuming that success at a larger, well funded firm or a prominent enterprise automatically translates to success in a lean enterprise.
When a candidate comes from an enterprise with structured SOPs, deep administrative support, and specialised software tools, their primary role was navigating an existing infrastructure. In an SME, however, the infrastructure is often incomplete or entirely missing. The new hire is not just required to operate the process; they have to design, document, and enforce it from scratch.
A generic job description fails to test for this context. It asks for “10 years of experience managing teams,” but neglects to ask: Can this individual build an operating workflow when there are no pre existing templates, no specialised support staff, and limited budget?
Without testing for context adaptability, companies end up hiring people who know how to delegate within a mature system, but freeze when faced with the raw operational ambiguity of an SME.
3. The Solution: Transitioning from Job Descriptions to Functional Hiring Canvases
To stop selecting for interview polish and start hiring for execution ability, organisations must invest time upstream to build an internal Hiring Canvas and the right job description circulated on external channels. This cannot be GPT’d.
A Hiring Canvas should shift the evaluation criteria from subjective qualifications to objective execution requirements across four clear dimensions:
A. Define Non-Negotiable Outputs (Not Just Tasks)
Instead of listing generic tasks like “Manage team operations and drive efficiency,” define the explicit, measurable operational outcomes required within the first 90, 120, 180 days.
- Example: “Establish a daily dispatch tracking mechanism that reduces customer delivery delays from 18% to under 5% without increasing headcount.”
B. Document System Constraints
Be transparent about organisational maturity during the hiring process. If the role requires working with incomplete data, managing informal vendor communication, or working with a lean team, document these constraints directly. Candidates who thrive on structured enterprise support will opt out naturally, while pragmatic problem solvers will engage.
C. Test via Work Sample Simulations
Replace open ended interview questions like “How do you handle conflict?” with practical, operational simulations based on data.
- The Old Approach: “Tell us about a time you handled a project failure.”
- The Hiring Canvas Approach: Provide the candidate with an example snippet of data. Ask them: “Identify three operational bottlenecks in this data, and draft a 5 step protocol on how you would address them using basic tools (like Excel or WhatsApp workflows).”
This instantly strips away presentation driven interviews and reveals their actual problem solving framework, diagnostic ability, and practical tool proficiency.
Moving Beyond CV Theatre
Hiring friction in growing Indian organisations is rarely a scarcity problem; it is mostly an evaluation problem. India has the highest educated population in the world.
When a narrative heavy job description is augmented with structured Hiring Canvases, the organisation stops paying a premium for candidate presentation and starts building a team based on verified operational capability. Execution improves not because the organisation found “better people,” but because they finally built a system that accurately identifies who can actually do the work for their operational reality.