Hiring framework
Hire on evidence, not interview confidence.
The Balncs framework connects the role’s deployment mandate to six dimensions, observable signals and a decision record that can survive disagreement.
Use six dimensions, then change the weighting.
A Product Extension Builder and a Deployment Operator should not carry the same evidence mix. The taxonomy stays stable; the importance and signal design change.
Turn each dimension into observable evidence.
Scores without anchors merely make opinion look quantitative. Define what evidence changes the rating.
| Dimension | High-signal evidence | Common false positive |
|---|---|---|
| Discovery | Reframes an incomplete brief using workflow and user evidence. | Asks many questions without changing the problem. |
| Scoping | Creates a credible path with dependencies, risk and exit conditions. | Produces detailed plans before resolving uncertainty. |
| Technical depth | Explains production artefacts, failures and trade-offs at the right depth. | Performs abstract system design without operating evidence. |
| Communication | Adapts the same decision for technical, user and executive contexts. | Presents confidently but leaves ownership ambiguous. |
| Judgement | Makes a consequential choice, names what was sacrificed and learns from it. | Describes only decisions that worked. |
| Ownership | Carries the result through adoption, recovery and reusable improvement. | Treats launch as the end of the work. |
A decision architecture, not an interview sequence.
Every stage should earn the right to exist by producing distinct evidence.
Screen
Relevant deployment pattern and motivation.
Work sample
Discovery, scoping and technical judgement.
Artefact review
Depth, ownership and learning from real work.
Decision record
Independent scores, evidence and explicit risks.
FDE brief review
Make the first hiring decision the right one.
Bring us the role brief, deployment motion or open questions. We will respond within two business days.