Week 48 Day 2: The Hiring Scorecard: Behaviors, Skills, and Culture Add

Note the term 'culture add,' not 'culture fit.' Culture fit means 'is this person similar to us?' Culture add means 'does this person bring perspectives, experiences, or capabilities that make the team stronger?' You are not looking for someone who fits into the existing team. You are looking for someone who expands what the team can do.

Here is how to build each section. Section one -- Key Behaviors: identify 3-5 behaviors that distinguish high performers from average performers in this specific role. Not generic behaviors ('good communicator,' 'team player') but role-specific behaviors that you can observe and evaluate. For a senior engineer: 'Breaks ambiguous problems into well-defined technical tasks without needing the problem fully specified upfront,' 'Proactively identifies technical debt that will become a production risk and proposes a specific remediation plan,' 'Adjusts communication style effectively when explaining technical decisions to non-technical stakeholders.' For each key behavior, write a specific interview question that requires the candidate to demonstrate the behavior (not just claim they have it) and define what a strong response looks like (specific example with context, action, and result) versus a weak response looks like (vague claims without examples, or examples that do not demonstrate the behavior). Section two -- Technical Skills: list the 4-6 technical skills required for the role. For each skill, define three levels: minimum acceptable (the candidate can do the job but will need support), strong (the candidate can do the job independently), and exceptional (the candidate can do the job and elevate the team's capability). The levels prevent all-or-nothing evaluation. A candidate might be exceptional in system design but minimum acceptable in testing methodology -- the scorecard makes this visible instead of collapsing it into a single 'technical ability' rating. Section three -- Culture Add: identify 2-3 things the team currently lacks that this hire could bring. This requires knowing your team's current composition -- their strengths, their blind spots, their Working Genius profile from Week 2. If your team is strong on execution but weak on strategic thinking, culture add might be 'brings experience translating business strategy into technical roadmap.' If your team is strong on individual contribution but weak on collaboration, culture add might be 'has a track record of building cross-functional partnerships.' Culture add is the hardest section to define because it requires honest assessment of the team's gaps, which requires honest assessment of your own leadership gaps.

The shift from 'culture fit' to 'culture add' reflects research by Ely and Thomas (2001) on 'cultural diversity at work: the effects of diversity perspectives on work group processes and outcomes.' Their research found that organizations that defined diversity in terms of 'value-in-difference' (culture add) rather than 'assimilation' (culture fit) showed higher team performance, higher innovation, and lower turnover, because the value-in-difference frame motivated teams to integrate diverse perspectives rather than suppress them. The three-level technical skill assessment (minimum, strong, exceptional) implements what competency modeling researchers call 'behavioral anchored rating scales' (BARS) -- developed by Smith and Kendall (1963), BARS define specific behavioral examples at each rating level, which reduces rating errors by 30-40% compared to unanchored scales because evaluators have concrete reference points rather than subjective judgments. The behavior-based interview questions implement what human resources researchers call 'behavioral event interviewing' (BEI) -- developed by McClelland (1973) and refined by Spencer and Spencer (1993), BEI asks candidates to describe specific past situations where they demonstrated the target behavior. Meta-analytic research by Taylor and Small (2002) found that behavioral interview questions (asking about past behavior) predicted job performance significantly better than situational interview questions (asking about hypothetical future behavior), because past behavior is a better predictor of future behavior than stated intentions about future behavior.