facilit8
๐Ÿ”’
Protected Playbook

This document is confidential.
Enter your access code to continue.

Incorrect code โ€” please try again.
facilit8 ยท Capability-Lens for Open Roles ยท Commercial Edition

Look Before You Backfill:
The Capability-Lens Playbook
for Open Commercial Roles

For HR and commercial leaders. Run every open sales, marketing or service role through the lens before you repost it. Let AI do the AI-able work. Free your people for the work only people can do โ€” the accountabilities and the soft skills โ€” and put the right person on it. A role-design tool, not a layoff tool.

Owner guide: HR / People Commercial Both Facilitator
v2 โ€” facilit8 ยท Capability-Lens Series ยท 2026
Step 0
Integrity Check โ€” Run This Before You Use the Lens
5 questions ยท 2 minutes ยท tells you whether this is safe to use yet
โ–พ

The same tool that redesigns a role well can be misused to justify never filling it. These five questions tell you which one you're about to build. Answer honestly โ€” the result is for you, not your board.

Q1
Is this role genuinely open โ€” no incumbent, and nobody being quietly managed out behind it?
Q2
Do both an HR lead and the commercial manager own this review and the decision together?
Q3
Do you have a real picture of what the team actually does โ€” not just the job description?
Q4
Is there real permission to reshape the role and develop people โ€” not only to fill it or freeze it?
Q5
Have you agreed in writing that the lens informs the decision but never makes it?
๐Ÿงญ
One truth before you start: same engine, two outcomes. Framing decides which.
Used well, the lens hands the AI-able work to AI. That frees people for the accountabilities and soft skills only they can do โ€” and puts the right person on that work. Used badly, it becomes a way to justify not hiring. Open roles only. Output questions, never verdicts. A person owns every decision.
โšก
๐Ÿ“
The rule: the lens asks questions; it never says "don't hire." Every run gives four outputs โ€” what AI can carry, the human work that's left, who's the right person for it, and a bridge with a decision date. People decide.
๐Ÿšง
Prerequisite โ€” The Scope Fence
Open roles only โ€” never a role with a person attached
Open means no incumbent: no displacement, no consultation trigger. If someone is behind the vacancy โ€” retiring, resigning under pressure, being restructured โ€” stop. That is a different, governed conversation, and the wrong job for this lens. In Switzerland it can trigger consultation and mass-dismissal duties (Code of Obligations Art. 335d ff. and the Participation Act). Keep open-role and filled-role work as separate engagements.
Record this before you begin
"This covers an open role with no incumbent. It informs โ€” it does not make โ€” the decision, which [HR lead] and [commercial manager] own jointly."
1
Zero cost ยท sets the integrity of everything after it Both
Confirm the fence and name two owners
Confirm in writing the role is open. Name both owners: HR and the commercial manager. One owner drifts โ€” commercial toward cost, HR toward process; the pair holds the line. Treat the Integrity Check above as a hard gate: red means stop, amber means fix the foundation first. Target: Day 2.
โšก Smaller Mittelstand: Day 1โ€“2 ๐Ÿข Works-council context: Week 1, loop in HR
Success looks like: Every open role has two named owners and a recorded scope-fence confirmation before recruiting spend starts.
2
The step everyone skips ยท highest leverage in the sequence Commercial
Read the job description assuming it lies
The JD is a recruiting artefact, not the truth. It's stale and it misses the glue work that holds a team together. Spend 30 minutes with the people who sat next to the role: "What did this person actually do that isn't written down?" That answer is the real job. Target: Day 8.
Watch for: Analysis built on the JD alone inherits its flaws. No lived picture of the role means a confident, wrong output.
3
Where the four outputs are produced Both
Run the role through the capability lens
Take the real role through the lens (next tab). It gives four outputs, never a verdict: (1) what AI can carry; (2) the human work that's left โ€” the accountabilities and soft skills; (3) who's the right person for that work; (4) a bridge with a decision date. The caveat travels with every output. Target: Day 18.
Success looks like: Each role leaves the lens with four written outputs and a confidence note โ€” and none of them reads "don't hire."
4
The decision ยท owned by people, with a date HR Commercial
Decide together and set the sunset
The two owners pick a path and write down why. Every bridge gets a sunset date; on expiry the default is hire, not keep automating. Aim for a better team in six months โ€” not a smaller one this quarter. Target: Day 25.
โšก Smaller Mittelstand: Week 3โ€“4 ๐Ÿข Works-council context: Week 4โ€“6, HR sign-off
Reversibility warning: Not-hiring is cheap to decide and expensive to undo. When the lens is ambiguous, hire and keep reshaping โ€” don't freeze.
๐Ÿ”
A job is accountability, not a task list
Step 1High impactBoth
Don't read a role as tasks and tick off what AI could do. A job is a bundle of accountability. AI drafts, summarises, updates โ€” but it can't be on the hook when the forecast is wrong or the customer's furious. Start with what the role is accountable for. Tasks come second.
Ask: "What breaks, and who carries it, if this had no human owner for three months?" That's usually more than the JD admits.
Hunt for the glue work the JD never mentions
Step 2High impactCommercial
The best commercial work is the least documented: sensing a renewal is wobbling, killing a tempting-but-wrong campaign, being the person everyone routes the angry customer to. That's glue work โ€” judgment, trust, memory. It's invisible to a JD. Map it before you ask what AI can take, or the lens will quietly cut the most valuable part.
Success looks like: The team can point to the role's glue work and agree it stays human โ€” named before any automation question.
Ask the four questions
Step 3Both
Run the real role against four questions. (1) Carry: what can AI do? (2) Human work: what's left โ€” the accountabilities and soft skills? (3) Right person: who's best placed to own that work? (4) Protect: what must never be automated? Four answers โ€” never a recommendation not to hire.
Capacity check: A proper run takes a few focused hours across the owners and the team. Twenty minutes gets you the JD's answer, not the real one.
Make the caveat travel with the number
Step 4High impactHR
The master risk: a conclusion outlives its caveats. The tidy line gets screenshotted into a board deck; the "this JD is unreliable" footnote drops off. Build the caveat in so it can't be separated โ€” confidence band plus the top two reasons it's wrong, in the same box. If it can be quoted without the caveat, the format failed.
Why it matters: A confident output on a bad input produces industrialised error โ€” one stale JD becoming an org-wide pattern of wrong, certain-looking calls.

Same Engine, Opposite Outcomes
The misuseThe good versionWhy the difference holds
Declares the role mostly automatable; recommends no backfillGives four options; a person choosesOutput is questions, never a verdict
A single score that travels to the board aloneEvery output carries its confidence and top two flawsThe caveat can't be stripped off
Quietly applied to filled roles and peopleOpen roles only โ€” filled roles are a separate trackThe scope fence is structural
A bridge that silently becomes permanentEvery bridge has a sunset; default on expiry is hireDrift has a forced stop date
Automates away the work where people build skillProtects the work where capability is grownCapability outlasts this year's saving
Priced on headcount savedPriced on the quality of the decisionThe model removes the incentive to cut

The One-Page Lens Worksheet
๐Ÿ“
Run this for each open role
Four questions, one caveat โ€” and deliberately no score
Fill this in with both owners, from the real role โ€” not the JD. There's nothing to total and no box that reads "don't hire," by design. If you start inventing a score, stop: that's the misuse version returning.

1 ยท Carry โ€” What routine, codifiable work can AI take on?

2 ยท Human work โ€” What's left that only a person can own โ€” accountability, judgment, relationships, the soft skills?

3 ยท Right person โ€” Who's best placed for that work, and what support and bridge (with a decision date) gets them there?

4 ยท Protect โ€” What must never be automated? (Empty list = look harder.)
Mandatory caveat โ€” travels with every output
"Based on a JD we know is imperfect. Confidence: low / medium / high. Top two reasons it's wrong: [reason], [reason]. Informs a decision a named person owns โ€” it does not make one."
๐Ÿงญ
Sales โ€” let AI do the codifiable work, people do the trust
Per open roleHigh impactCommercial
Give AI the codifiable load: outreach drafts, CRM hygiene, first-draft proposals. What's left is human โ€” qualification, discovery, trust, the negotiation. In Mittelstand B2B, that's where deals are won. Shape the role around that work, and put your strongest relationship people on it.
Success looks like: Reps spend most of their time on relationships and judgment, with the routine handled in the background.
Marketing โ€” automate production, keep the judgment human
Per open roleCommercial
AI drafts and reports fast. The human work is positioning, brand judgment, and knowing what not to publish. Shape the role around that โ€” directing and editing AI, owning the calls that protect a precision brand. The right person is whoever has that judgment.
Nuance: "Faster drafting" is a capability, not a strategy. Automate production but never the judgment, or you ship more that says less.
Service โ€” automate the routine, keep the saves human
Per open roleHigh impactCommercial
Let AI deflect routine tickets and draft standard replies. The human work retains revenue: de-escalation, complex problems, the loyalty moments. In B2B manufacturing, service is where accounts are saved or lost. Shape the role around the hard cases and route them to the person best at them.
Success looks like: The team spends far more of its time on retention and complex saves; routine queries resolve on their own.
Don't let "reshape" lose by default
Every reviewBoth
Cost (cut a salary) and bridge (delay) are easy to measure. "Work matched to the right person" isn't โ€” so it tends to lose. Counter it: state the reshape option first, give it an owner, and put a rough value on the upside. Measure only what's easy and you'll only ever choose what's cheap.
Watch for: "We'll reshape it later" is how reshape dies. No owner, no date โ€” then it's a polite no.
๐ŸŒฑ
๐ŸŒฑ
The point of the lens: an open role is the cheapest moment to develop people. No incumbent, real work to grow into. Ask "who's the right person for the human work, and what would help them?" before "who do we recruit?"
Free people for the work that matters
Per open roleHigh impactHR
AI carries the routine load. That frees people for the accountabilities and soft skills only they can do. So treat the open role as a chance to give that work to the right person โ€” and develop them into it โ€” rather than recruiting on reflex.
Make the growth plan real, not implied
A growth plan that isn't funded, scheduled and visible is just extra work with a compliment attached. Name the person, the capability, the mentor, what AI carries, and the review date. Unfunded "development" becomes overload โ€” and the person leaves.
Use AI to remove the drudgery, not the work
Bridge phaseCommercial
Healthy: AI takes the low-judgment, high-volume tasks so people do the human work. Unhealthy: the team quietly shifts to just checking AI output โ€” a reorg nobody approved. Name which one you're doing, out loud, and check back.
Watch for: A "humans review the machine" drift de-skills the team and removes your redundancy. That's a reorg โ€” treat it as one, with consultation.
Keep the muscle alive
OngoingFacilitator
The trap: automate a skill, stop practising it, lose it โ€” then the next review "proves" you can't do it, so you automate more. Break the loop. Keep people doing the judgment work. AI is a floor under the load, not a replacement for the craft.
Dependency note: Building around a tool creates a quiet dependency on its price and quality. Keep the human skill alive so a vendor change isn't a capability crisis.
Protect the roles where people learn the work
Per roleHigh impactHR
Some roles look the most automatable precisely because they're where people build judgment, relationships and accountability. Automate them away and you lose the place capability is grown. In the Swiss Lehre system it's also part of who you are as an employer. Protect these as capability investments, not costs.
Success looks like: Learning roles are ring-fenced from automation logic and discussed as investment, not overhead.
๐Ÿšซ
โ›”
Hard carve-out: safety-, compliance-, quality- and relationship-critical work gets no score and no automation call โ€” it's marked "human-required, not assessed." Naming what you won't touch is what makes the rest credible.
The relationship and the close (Sales)
Human-requiredCommercial
In Mittelstand B2B, deals run on years of trust and reading the room. The relationship is the asset, not a task. AI can prepare the person; it can't replace them. Over-cut the legible work and under-value the trust, and you make the most expensive mistake the lens allows.
High risk if ignored: Hollow out relationship ownership to save cost and you learn its value only when the account leaves.
Brand judgment and what not to publish (Marketing)
Human-requiredCommercial
A tool will happily produce a clever campaign that's subtly wrong for a conservative brand in a small market. Positioning, tone, and what not to say are human-required โ€” the cost of a misstep is trust, not impressions. Protect brand stewardship; let AI speed up production beneath a person who owns the brand.
Nuance: Producing assets is easy to automate and easy to over-cut. Knowing which asset is right is where the value sits.
De-escalation and the loyalty moment (Service)
Human-requiredCommercial
The angry customer, the high-stakes complaint, the account on the line โ€” human-required. Routine deflection is fine; routing a furious key customer to a bot turns a recoverable problem into a lost contract. Protect these moments and design the tool to hand off to a person early.
Success looks like: Routine queries resolve without a person; high-stakes moments reach a skilled human fast, by design.
Accountability and institutional memory (All)
Human-requiredBoth
Across all three functions, the connective tissue is human-required. Someone has to be on the hook when it goes wrong, hold the context that isn't written down, notice what no dashboard flags. AI does tasks; it can't carry accountability. These are exactly the parts a task-by-task lens makes invisible.
Watch for: No "don't automate this" list means the lens didn't look hard enough. An empty list is a red flag, not a clean bill of health.
๐ŸŽฏ
๐ŸŽฏ
On the scripts below: each is written for direct, low-spin cultures โ€” Swiss, German, Scandinavian norms where brevity reads as respect. In relationship-led cultures, add one sentence of context first. Keep them short either way: a long, over-framed intro to anything touching jobs reads as suspicious.
๐Ÿ›
The CEO / Owner (Mittelstand)
"Will this protect what makes us a good employer โ€” or quietly erode it?"
The owner's identity is bound up in the social contract โ€” apprenticeships, loyalty, looking after people. They'll like the hiring discipline; the risk is liking it for the wrong reason. Frame it as discipline plus people development: AI takes the routine, people get the work that matters. Be clear it never recommends not-hiring. Reputational spillover in a small sector is what they'll feel most.
Invitation script
"[Name], before we repost the next open role, I want to run it through a capability lens โ€” to see what AI could take off the team's plate and which of our people should own the work that's left. It never decides for us. 30 minutes?"
For relationship-led cultures, add first: "This came out of wanting to use AI to help our own people grow, not to do without them."
Watch for: An owner who wants the number as cover for a decision already made. If it's to win an argument, not inform one, pause โ€” that's the bad version arriving.
๐Ÿ’ผ
The Chief Commercial Officer
"I'm under budget pressure โ€” can this just tell me which roles I can skip?"
The CCO is the persona most likely to misuse the lens โ€” to win a budget fight, strip the caveats, push from open to filled roles. Meet the pressure honestly, then hold the line: the lens builds a better team, not a cheaper one. Lead with what they want โ€” the right people on the work that wins deals, and retention defended.
Invitation script
"[Name], the next open role is a chance to get AI doing the routine work and our best people on what wins deals. The lens gives four options and a decision we make together โ€” it won't hand you a 'skip this hire.' 20 minutes?"
For relationship-led cultures: "I know the budget's tight โ€” I think this gives you a stronger argument than a simple cut would."
Relationship prerequisite: If the CCO can't hear "this won't justify a cut" without disengaging, you don't yet have the foundation โ€” build trust on a reshape win first.
๐Ÿ‘ฅ
The HR / People Lead
"Is this a threat to my function and a discrimination risk waiting to happen?"
HR often reads a tool like this as a threat and carries the exposure if recommendations skew. Reposition them as co-owner and guardian of the guardrails โ€” the equal-treatment review, the scope fence, the protection of learning roles are theirs. Done right, it makes HR more central to commercial decisions, not less.
Invitation script
"[Name], I won't run this on open roles without you co-owning it. You'd hold the equal-treatment check and the scope fence. Can I walk you through how it's built to develop people, not cut them? 30 minutes."
This works across cultures โ€” HR responds to being made a co-owner of the safeguards, not a reviewer after the fact.
Success looks like: HR co-owns the lens and runs the equal-treatment gate as routine โ€” the signal it's seen as protection, not threat.
๐Ÿค
The Worried Team Member
"Does 'capability lens' mean you're about to automate my job?"
The people next to the role hear "AI" and fear for themselves. Be direct and early: this runs on open roles only, never on them, and the point is often to take the routine off their plate so they do more of the work that matters. Honesty builds more trust than silence โ€” which they'll fill with the worst version.
Invitation script
"[Name], we're looking at the open role next to you โ€” not your job. Part of the question is whether AI could take some routine load off you, so you take on more of the interesting work. I'd value your honest view on what that role really involves. 20 minutes."
For relationship-led cultures: "I wanted to tell you directly rather than have you hear it second-hand โ€” this is about the open role, and your growth."
Relationship prerequisite: If trust is already low, no script fixes it โ€” be visibly straight about scope and let the first reshape prove intent.
25
Specific actions across 7 tabs
4
Outputs per role โ€” never a "don't hire"
5
Structural guardrails that beat policy
1
Scope fence: open roles only, by design
facilit8 ยท Commercial Transformation enabled by Technology
Decision-support only, and not legal advice โ€” confirm employment-law questions with Swiss counsel. The client owns every hiring decision in writing; the lens is never the sole basis for not backfilling a role. Liability terms live in the engagement letter, not on this page.

An open commercial role? Run it through the lens.

A 30-minute conversation with David can show you how the capability-lens framework applies to your next open role โ€” and how to build a repeatable process around it.

Want this playbook by email?

Leave your email and I'll send you a copy โ€” no spam, unsubscribe anytime.