Week 48 Day 7: Assignment: Build a Hiring Scorecard for Your Next Open Role

Build a scorecard with three sections: key behaviors (3-5 role-specific behaviors with interview questions and scoring rubrics for each), technical skills (4-6 skills with three levels -- minimum acceptable, strong, exceptional), and culture add (2-3 things the team currently lacks that this hire should bring). Before building the scorecard, review your team's Working Genius profile from Week 2 to identify the gaps the hire should fill.

Here is the step-by-step process. Step one -- define the role's purpose in one sentence. Not the job title, not the responsibilities list -- the purpose. 'This role exists to...' For example: 'This role exists to own the reliability and performance of our production infrastructure, enabling the product engineering team to ship features without worrying about scalability.' The purpose sentence guides every subsequent decision on the scorecard because it defines what success looks like for this hire. Step two -- identify key behaviors. Ask yourself: 'Think of the best person who has ever held this role (or a similar role). What specific behaviors made them exceptional? What did they do that average performers did not?' Write 3-5 behaviors. Then, for each behavior, write a behavioral interview question. Not 'tell me about a time you showed leadership' but 'describe a specific situation where you identified a significant technical risk that others had not recognized. What was the risk, how did you identify it, what action did you take, and what was the outcome?' The question should require a specific story, not a hypothetical answer. Then define what a strong response includes (specific context, clear individual contribution, measurable outcome, evidence of learning) and what a weak response includes (vague generalities, team outcomes without individual role clarity, hypothetical plans rather than actual experience). Step three -- define technical skills with three levels. For each skill, the minimum acceptable level defines the hiring bar -- below this, the candidate cannot do the job. The strong level represents full independent capability. The exceptional level identifies candidates who will elevate the team. Make the levels concrete. 'System design -- minimum: can design a standard CRUD application with appropriate database selection and basic caching. Strong: can design a distributed system handling millions of daily active users with appropriate trade-offs between consistency, availability, and partition tolerance. Exceptional: can design system architecture that anticipates 2-3 years of growth trajectory and incorporates observability, graceful degradation, and cost efficiency from the initial design.' Step four -- define culture add. Review your team's current profile. What are the team's blind spots? What perspectives are missing? If the team is culturally homogeneous (everyone has similar backgrounds, communication styles, or problem-solving approaches), what diversity of perspective would strengthen the team's output? The culture add section should be specific: not 'brings diversity' but 'brings experience working in regulated industries, which will strengthen our approach to compliance as we move into healthcare partnerships.' Step five -- test the scorecard. Before using it in a real interview, have a colleague review the scorecard and provide feedback: are the behaviors observable and evaluable? Are the skill levels well-defined? Are the culture add factors genuinely additive rather than veiled versions of culture fit? Step six -- document the scorecard in your Leadership Operating Manual so it serves as a template for future hiring.

The role purpose statement implements what job design researchers call 'job significance' (Hackman and Oldham, 1976) -- one of the five core dimensions in the Job Characteristics Model that predicts motivation, satisfaction, and performance. Their research found that roles defined in terms of purpose and impact produced 30% higher motivation than roles defined in terms of tasks and responsibilities, because purpose-framing connects the work to an outcome that matters beyond the task itself. This insight applies to the hiring process because candidates evaluated against a purpose-defined scorecard are being assessed on their potential contribution to the team's mission rather than their ability to perform isolated tasks. The behavioral interview question design follows the STAR framework (Situation, Task, Action, Result) -- validated by Janz (1982) as the most reliable behavioral interview structure, producing inter-rater reliability coefficients of 0.73 compared to 0.42 for unstructured interviews, because the framework constrains the response to observable and verifiable elements. The three-level technical skill assessment maps to what Dreyfus and Dreyfus (1986) call the 'skill acquisition model' -- their research identified five levels of skill development (novice, advanced beginner, competent, proficient, expert), and the three-level scorecard simplifies this to three hiring-relevant levels: competent (minimum acceptable), proficient (strong), and expert (exceptional). The culture add approach is supported by research on 'cognitive diversity' (Reynolds and Lewis, 2017) -- their study of 1,000 teams found that teams with higher cognitive diversity (different thinking styles, perspectives, and problem-solving approaches) solved complex problems faster and more accurately than cognitively homogeneous teams, because diversity of perspective produced a wider search of the solution space.