Free Competency Framework Template | Role-Based Examples & Proficiency Levels
Free Competency Framework Template | Role-Based Examples & Proficiency Levels
An AI skills matrix for finance leaders creates a shared, testable definition of “good” AI use in planning and reporting. It helps you make promotion and hiring decisions that feel fair because they rely on observable outcomes, not confidence or buzzwords. It also gives your finance team a practical development path: what to learn next, what evidence to collect, and what “safe” looks like in EU/DACH contexts.
| Skill area | Finance Manager / Controller | Senior Finance Manager / Head of Controlling | Head of Finance | CFO |
|---|---|---|---|---|
| 1) AI foundations, ethics & guardrails in finance | Uses approved tools and follows the team’s “do-not-enter” rules; documents AI use in workpapers. Flags hallucination risk when outputs influence numbers or narratives. | Defines team guardrails for typical finance workflows (forecast drafts, variance analysis, board narrative) and trains others to apply them. Escalates high-risk use cases early (e.g., HR data, customer pricing, M&A). | Aligns finance AI practices with GDPR, internal audit expectations, and any Betriebsrat/Dienstvereinbarung requirements. Ensures human accountability for plan sign-off and external reporting narratives. | Sets the tone: AI supports judgement, never replaces accountability for financial decisions. Sponsors cross-functional governance for AI model risk, vendor risk, and decision traceability. |
| 2) Data quality, governance & controls | Checks data lineage, mapping logic, and period consistency before using AI outputs. Never uploads raw GL exports into unmanaged tools; uses data minimisation by default. | Builds control points for AI-assisted workflows (input checks, reconciliation steps, versioning, review/approval). Defines “minimum data quality” thresholds for forecasts and management reporting. | Owns finance data governance across ERP, BI, and planning tools; sets responsibilities for master data and chart-of-accounts discipline. Ensures audit-ready documentation for AI-assisted analyses. | Funds and enforces enterprise-grade controls: access rights, audit logs, retention rules, and vendor DPAs. Balances speed with controls so finance can scale AI use safely. |
| 3) AI in planning, forecasting & scenario modelling | Uses AI to generate scenario options and driver hypotheses, then validates them with business owners. Detects outliers and explains adjustments in plain language. | Runs structured scenario planning (base/upside/downside) with driver trees and sensitivity analysis. Improves forecast accuracy by tightening assumptions, not by “letting the model decide.” | Integrates AI-assisted forecasting into the planning calendar and decision forums (budget reviews, QBRs). Ensures forecast changes are traceable and comparable across cycles. | Uses AI insights to steer strategic choices (investment, capacity, pricing) while requiring explicit confidence ranges and risks. Challenges teams to show “what changed” and “why now.” |
| 4) AI in reporting & management information (MI) | Drafts first-pass reporting narratives with AI, then fact-checks against source reports and reconciliations. Keeps a clear separation between numbers, interpretations, and recommendations. | Standardises board-pack narratives and variance commentary templates; reduces rework by improving prompt and data inputs. Spots inconsistencies across dashboards and resolves root causes. | Owns a consistent “single version of truth” across management reporting and performance metrics. Ensures stakeholders trust reports because errors are caught early and corrected transparently. | Uses AI-supported MI to improve board decision speed while maintaining credibility. Sets expectations for traceability: which data, which assumptions, which human reviewer. |
| 5) AI in cost management & efficiency | Uses AI to spot cost anomalies and recurring drivers; confirms findings with procurement and budget owners. Proposes automation candidates with control implications clearly stated. | Builds business cases for automation and process redesign, including risk, controls, and change impact. Measures realised savings versus “paper savings” and adjusts the approach. | Runs a cost governance cadence where AI insights translate into owned actions (policy changes, renegotiations, process fixes). Protects compliance, ethics, and employee trust while driving efficiency. | Balances efficiency with resilience: avoids cost cuts that create audit, fraud, or delivery risk. Ensures AI-driven cost programs have clear accountability and do not undermine culture. |
| 6) Workflow & prompt design for finance | Uses role-approved prompt templates for recurring tasks (variance commentary, forecast risks, investment memo drafts). Stores prompts with examples and “red flags” for review. | Maintains a prompt library with version control and quality checks; trains the team on prompt patterns and verification. Improves output quality by tightening context, constraints, and evidence requests. | Standardises finance workflows where AI adds speed without losing control (draft → check → reconcile → approve). Ensures prompts and templates align with finance terminology and policies. | Promotes a culture of disciplined use: prompts are assets, not personal hacks. Sponsors tooling and enablement that reduce shadow AI and improve auditability. |
| 7) Cross-functional collaboration (HR, RevOps, IT, Legal, Data) | Coordinates inputs and definitions (headcount, payroll accruals, ARR metrics) so AI analysis does not mix inconsistent sources. Shares assumptions early to avoid late-stage reporting disputes. | Leads cross-functional metric alignment (unit economics, productivity, pipeline coverage) and resolves definition conflicts. Partners with IT/Data on secure access and approved toolchains. | Creates operating rhythms with HR/RevOps/Legal to govern AI-enabled metrics and sensitive data. Ensures conflicts are resolved with clear owners and documented definitions. | Represents finance AI risks and opportunities at executive level; aligns incentives across functions. Ensures strategic KPIs remain consistent, explainable, and trusted enterprise-wide. |
| 8) Change management & team enablement | Uses AI in a way that supports psychological safety: shares drafts, asks for peer review, and admits uncertainty. Helps colleagues adopt safe habits through simple how-to support. | Runs hands-on enablement (office hours, templates, review checklists) and addresses failure modes (over-reliance, weak verification). Tracks adoption and quality issues without blame. | Builds an enablement plan for finance: training, guardrails, measurable outcomes, and support channels. Integrates AI skills into performance and development conversations. | Sponsors change at scale: budget, time, governance, and role modelling. Prevents “AI theatre” by tying adoption to measurable improvements and risk controls. |
Key takeaways
- Use the matrix to define promotion evidence before the next review cycle starts.
- Calibrate “safe AI use” expectations across finance, audit, IT, and Legal.
- Turn recurring finance work into prompt templates with built-in verification steps.
- Rate skills with evidence, not self-assessed confidence or tool familiarity.
- Spot readiness by scope growth: ownership, cross-functional influence, and risk handling.
Definition of this framework
This AI skills matrix for finance leaders is a role-based competency framework with observable behaviours across four leadership levels. You use it to hire and interview consistently, assess performance with shared anchors, build promotion cases with evidence, and design development plans that balance speed, governance, and EU/DACH compliance expectations.
Skill levels & scope in an AI skills matrix for finance leaders
Levels are defined by decision scope, risk ownership, and how strongly you shape cross-functional behaviour. In finance, “seniority” also means tighter control discipline: traceability, audit readiness, and responsible handling of sensitive data. Use this section to align titles across Finance, Controlling, and FP&A before you start rating people.
| Level | Scope & decision rights | Typical contribution |
|---|---|---|
| Finance Manager / Controller | Owns defined processes (monthly close tasks, cost centre reporting, variance commentary) with limited policy-setting authority. Uses approved AI tools within guardrails; escalates unclear cases early. | Delivers accurate analyses faster while keeping reconciliations and documentation clean. Improves team reliability by catching errors and documenting assumptions. |
| Senior Finance Manager / Head of Controlling | Owns end-to-end workflows across a domain (forecasting cadence, board pack preparation, cost governance) and can redesign processes. Sets team-level standards for AI usage and verification. | Reduces rework and surprises by standardising templates, controls, and definitions. Improves forecast quality by aligning assumptions across business owners. |
| Head of Finance | Owns finance operating model across planning, reporting, and controls; influences policies and tooling choices. Partners with audit, IT, Legal, and Betriebsrat-facing stakeholders on governance. | Builds trust in management information through consistency, traceability, and strong review routines. Turns AI adoption into measurable cycle-time and quality improvements. |
| CFO | Owns enterprise-level accountability for financial decisions, external-facing narratives, and risk posture. Sponsors governance and investment decisions; sets non-negotiables for safe AI use. | Uses AI to improve strategic decision speed while protecting credibility and compliance. Aligns executives on what AI can support—and where humans must override. |
Hypothetical example: A Controller uses AI to draft variance commentary, but a Senior Finance Manager changes the workflow: the commentary cannot be final unless the driver tie-out is attached and reviewed.
- Write a one-page “scope statement” per level: decisions owned, budgets influenced, risks carried.
- Define which AI outputs can be used as drafts, and which require formal review.
- Agree who signs off AI-assisted plan changes and how that is documented.
- Map each level to your skill framework and career ladder language.
- Run a 45-minute alignment workshop with Finance, Internal Audit, and IT.
Skill areas in an AI skills matrix for finance leaders
Skill areas should mirror real finance outcomes: plan quality, reporting credibility, cost control, and risk management. Keep them stable across business units so calibration stays possible. If you already maintain a finance skills catalogue, treat this as the AI overlay, not a full replacement.
| Skill area | Goal | Typical outputs you can observe |
|---|---|---|
| AI foundations, ethics & guardrails | Ensure AI is used responsibly and predictably in finance decisions. Reduce the chance that AI output becomes an unreviewed “authority.” | Documented AI usage notes, clear “do-not-enter” rules, escalation paths, and training artefacts. |
| Data quality, governance & controls | Prevent “garbage in, garbage out” and protect sensitive data through data minimisation. Keep AI-assisted work audit-ready and reproducible. | Data lineage checks, control points, approval steps, reconciliations, access logs, and retention rules. |
| AI in planning, forecasting & scenario modelling | Use AI to explore scenarios and drivers while keeping humans accountable for assumptions. Improve learning speed without hiding uncertainty. | Scenario packs, driver trees, sensitivity analysis, documented assumptions, and post-mortems on forecast deltas. |
| AI in reporting & management information | Produce accurate, consistent narratives and dashboards that leaders trust. Separate facts from interpretation and clearly flag uncertainty. | Board pack drafts with fact checks, consistent metric definitions, and tracked corrections when issues are found. |
| AI in cost management & efficiency | Identify cost levers and automation opportunities without weakening controls or fairness. Convert insights into owned actions and measurable results. | Cost anomaly reviews, automation business cases, savings tracking, and risk assessments for process changes. |
| Workflow & prompt design for finance | Turn repeatable finance work into high-quality, verifiable AI-assisted workflows. Reduce individual “prompt hacks” that create inconsistency. | Prompt libraries, templates, verification checklists, version history, and onboarding materials. |
| Cross-functional collaboration | Align definitions and data across Finance, HR, RevOps, IT, Legal, and Data. Prevent metric drift and conflicts late in the cycle. | Signed-off metric dictionaries, meeting notes with decisions, shared dashboards, and resolved definition disputes. |
| Change management & team enablement | Make adoption safe and sustained, not tool-driven. Protect psychological safety while raising skill levels and output quality. | Training plans, office hours, adoption metrics, incident learnings, and team-wide templates. |
Practical example: Your Head of Controlling creates a “forecast driver dictionary” with RevOps and Sales Ops, so AI-generated scenarios don’t mix incompatible pipeline stages.
- Keep 6–8 skill areas; add depth through evidence, not more categories.
- Define “observable outputs” per area so ratings stay grounded in work products.
- Align areas with your existing finance skill inventory (for a starting point, see a finance skills matrix template and extend it with AI behaviours).
- Assign one owner per area to maintain anchors and examples over time.
- Agree which areas are required for each level versus “nice to have.”
Rating & evidence for an AI skills matrix for finance leaders
Ratings only work when they are tied to evidence that peers can review. In finance, evidence should show both outcome quality and control quality: accuracy, traceability, and safe handling of data. Keep the scale small so managers can use it consistently during busy cycles.
| Rating | Label | Finance-specific definition (evidence-based) |
|---|---|---|
| 1 | Awareness | Can explain basic risks (hallucinations, confidentiality) and follows “do-not-enter” rules when reminded. Evidence: completed training, uses approved tools, asks for review. |
| 2 | Basic | Uses AI for drafts in low-risk tasks and performs basic verification (spot checks, ties to source reports). Evidence: annotated workpapers, corrected AI errors before sharing. |
| 3 | Skilled | Delivers measurable workflow improvements (cycle time, fewer iterations) while maintaining controls and documentation. Evidence: templates, checklists, reconciliations, peer-reviewed outputs. |
| 4 | Advanced | Designs scalable AI-assisted processes with governance: versioning, approvals, audit-ready documentation, and training. Evidence: adopted team standards, reduced error rates, clear ownership. |
| 5 | Expert | Shapes policy and cross-functional governance; anticipates regulatory, audit, and model-risk needs. Evidence: governance artefacts, risk assessments, leadership decisions with traceable AI use. |
Good evidence types for finance leaders include: board-pack change logs, forecast assumption registers, reconciliation files, internal control documentation, prompt libraries with version history, post-mortems after forecast misses, and stakeholder feedback (e.g., “finance narrative matched numbers and answered risks”). If you use a talent system like Sprad Growth, capture evidence links directly in review notes so calibration relies less on memory and recency.
Mini example (Fall A vs. Fall B): Both people “used AI to speed up variance analysis.” Fall A gets a lower rating because they shared AI commentary without tying to reconciled numbers. Fall B is rated higher because they built a repeatable template, included tie-outs, and reduced rework for the whole team.
- Require 2–3 evidence items per rating discussion, with at least one control-related artefact.
- Separate “output quality” from “process safety” so fast work does not get rewarded blindly.
- Use the same evidence standard in performance management conversations and promotion cases.
- Run a simple bias check: would you rate this the same with names removed?
- Store prompt templates with versioning, owners, and examples of acceptable outputs.
Growth signals & warning signs
Readiness for the next level shows up as scope expansion and reliability over time, not one impressive dashboard. In an AI skills matrix for finance leaders, growth means you reduce risk while increasing leverage: others can reuse your work safely. Warning signs often look like speed, but with missing controls, weak documentation, or poor collaboration.
Growth signals (ready for the next level)
- Consistently ships AI-assisted outputs that survive scrutiny from audit-minded reviewers.
- Creates reusable templates that reduce team cycle time without lowering control quality.
- Expands stakeholder trust: business owners adopt finance definitions and assumptions faster.
- Flags edge cases early (GDPR, Betriebsrat sensitivity, vendor risk) and proposes mitigations.
- Shows stable performance across at least two cycles (planning + reporting), not a one-off.
Warning signs (promotion blockers)
- Uses unapproved tools or copies sensitive data into unmanaged prompts (“shadow AI”).
- Cannot reproduce results: missing inputs, missing prompts, or unclear assumption changes.
- Over-trusts AI outputs; explains decisions with “the model said so.”
- Creates metric confusion across teams by mixing definitions without alignment.
- Resists peer review, treats verification as bureaucracy, or dismisses control concerns.
Hypothetical example: A Senior Finance Manager is fast with AI-generated board narratives, but the text sometimes contradicts dashboards. That is a warning sign until they introduce a verification checklist and reduce contradictions over multiple cycles.
- Define “promotion-ready” as sustained scope handling plus risk discipline, not tool usage.
- Track recurring failure modes (wrong numbers, missing tie-outs) and coach with specific fixes.
- Use a shared bias language from performance review biases to keep discussions evidence-led.
- Reward people who prevent incidents (data leaks, wrong narratives), not only those who automate.
- Agree escalation rules for sensitive data: payroll, customer pricing, M&A, and litigation topics.
Check-ins & review sessions
You get consistent ratings when managers compare examples together, not when they fill forms alone. Keep sessions short and concrete: real artefacts, recent work, and clear anchors from the AI skills matrix for finance leaders. The goal is shared understanding, not perfect calibration.
| Format | Cadence | What you review | Output |
|---|---|---|---|
| Monthly “AI-assisted finance work” review | 30 minutes | One planning artefact and one reporting artefact; verify tie-outs and narratives. | Small fixes to templates, updated checklists, and named owners. |
| Quarterly calibration (Finance leadership) | 60–90 minutes | Borderline level cases and “what good looks like” examples for two skill areas. | Aligned ratings guidance and a short decision log for future reference. |
| Post-cycle retrospective (planning/reporting) | 45 minutes after each cycle | Where AI helped, where it caused rework, and where controls failed. | 3–5 process changes with dates and owners for the next cycle. |
| Office hours / peer clinics | Bi-weekly | Prompt patterns, verification steps, and sensitive-data scenarios. | Shared prompt library improvements and faster onboarding for new users. |
Practical example: In a quarterly session, two managers rate the same behaviour differently (“AI-based scenario analysis”). The group resolves it by requiring a driver-tree attachment and a short assumption register for a “Skilled” rating.
- Use the same pre-read template: role scope, 2–3 evidence items, and one risk/control example.
- Timebox each person: 5 minutes evidence, 5 minutes discussion, then decide or park.
- Add a quick fairness prompt: “What would change your mind?” before debating opinions.
- Rotate a neutral facilitator; use a simple guide like a talent calibration workflow.
- Keep decision logs short; focus on future consistency, not defending the past.
Interview questions
Interviewing for finance AI capability works best with behavioural questions tied to real artefacts: forecasts, board packs, reconciliations, and controls. Ask for what they did, what evidence exists, and what they changed after errors. Use the same question set for hiring and internal promotion panels to keep standards aligned.
1) AI foundations, ethics & guardrails
- Tell me about a time you rejected an AI output. What was the risk and outcome?
- Describe a situation where AI use created a confidentiality concern. What did you do?
- When do you refuse to use AI in finance work, even if it saves time?
- How do you document AI assistance so others can reproduce and review your work?
2) Data quality, governance & controls
- Walk me through how you verify data lineage before using AI for analysis.
- Tell me about a time bad mappings or master data broke your reporting. What changed?
- How do you apply data minimisation when using AI tools with finance exports?
- Describe a control you added to an AI-assisted workflow. What failure did it prevent?
3) AI in planning, forecasting & scenario modelling
- Tell me about a forecast scenario you generated with AI. How did you validate drivers?
- Describe an outlier you found in an AI-supported forecast. What was the root cause?
- How do you communicate uncertainty ranges to business owners or executives?
- What is one time AI made you faster but less accurate, and how did you fix it?
4) AI in reporting & management information
- Tell me about a board narrative you drafted with AI. How did you fact-check it?
- Describe a time narratives and dashboards disagreed. How did you resolve it?
- How do you prevent AI from “smoothing over” bad news or missing risks?
- What’s your method to separate facts, interpretation, and recommendation in reporting?
5) AI in cost management & efficiency
- Tell me about a cost anomaly AI surfaced. How did you verify and act on it?
- Describe an automation idea you rejected due to control or compliance concerns.
- How do you measure realised savings versus assumed or allocated savings?
- Tell me about a cost initiative that affected teams. How did you manage trust?
6) Workflow & prompt design for finance
- Show how you structure a prompt for variance analysis. What constraints do you add?
- Tell me about a prompt template you improved over time. What changed and why?
- How do you build verification steps into prompts rather than relying on memory?
- Describe how you share prompts so the team can reuse them safely.
7) Cross-functional collaboration
- Tell me about a metric definition conflict (Finance vs Sales/RevOps/HR). How did you resolve it?
- Describe a time you needed IT/Data/Legal to approve an AI use case. What was the outcome?
- How do you align stakeholders on assumptions before planning cycles start?
- Tell me about feedback you received that improved your reporting credibility.
8) Change management & team enablement
- Tell me about a time you introduced a new AI workflow. How did adoption go?
- Describe a situation where someone over-relied on AI. How did you coach them?
- How do you create psychological safety so people admit uncertainty in AI-assisted work?
- What enablement artefact did you create (training, checklist, office hours) and what changed?
Practical example: For a Head of Finance candidate, ask them to bring one anonymised board-pack excerpt and explain how they verified AI-assisted narrative against the numbers.
- Require candidates to answer with one artefact: a template, checklist, or decision log.
- Use follow-ups: “What did you verify?” and “Who reviewed it?” for every AI story.
- Score answers using the same four levels as your AI skills matrix for finance leaders.
- Train interviewers to probe for controls, not just speed or “prompt cleverness.”
- Include one question on GDPR/Betriebsrat sensitivity, framed as non-legal, practical handling.
Implementation & updates
Implementing an AI skills matrix for finance leaders works best as a pilot with tight scope and clear governance. Start with planning and reporting workflows where finance already has artefacts, reviewers, and a cadence. Keep it non-legal and practical: who can use what tools, with which data, and what evidence is required.
- Kickoff (Week 1): CFO/Head of Finance frames goals, non-negotiables, and accountability; name an owner.
- Leader training (Weeks 2–3): Run a 90-minute session on levels, evidence standards, and bias checks.
- Pilot (Weeks 4–10): Choose one area (e.g., forecasting + board reporting) and rate 10–20 leaders.
- Review (Week 11–12): Collect feedback, adjust anchors, and publish a short “what changed” note.
- Scale (Next cycle): Expand to all finance leaders; integrate into hiring loops and performance reviews.
| Governance element | Owner | Simple rule that prevents drift |
|---|---|---|
| Framework content (levels, anchors) | Head of Finance (or delegated FP&A/Controlling leader) | No change without two reviewers from different finance sub-teams. |
| Tooling & data access | Finance Ops + IT/Security | Approved tools list reviewed quarterly; access is role-based. |
| Compliance touchpoints (high-level) | DPO/Legal partner + Betriebsrat liaison where applicable | Sensitive data use cases must have documented guardrails and escalation path. |
| Enablement (training, prompt library) | Senior Finance Manager / Enablement lead | Every template includes verification steps and an example of a “bad output.” |
Benchmarks / trends (EU/DACH lens): Expect more internal scrutiny on traceability and decision accountability as the EU AI Act becomes operational. Treat this matrix as an internal “proof of discipline” tool: it helps you show that AI-assisted finance work is reviewed, documented, and owned by humans. Assumption: you operate in an environment with formal controls and potential Betriebsrat involvement.
Practical example: A finance function pilots the matrix in Controlling first, then reuses the same evidence templates for FP&A and business partnering.
- Choose one “high-frequency” workflow for the pilot so you get evidence fast (variance + forecast).
- Set a change log and a quarterly review cadence; keep updates small and explainable.
- Connect rollout to your AI enablement and training plans so behaviours improve, not just ratings.
- Offer role-based training (managers vs ICs); reuse a practical AI training for managers structure for coaching and reviews.
- Store prompts, evidence, and review notes in one place to reduce recency bias (your HR/talent system or a controlled repository).
Conclusion
An AI skills matrix for finance leaders is useful when it creates clarity on expectations, fairness in decisions, and development paths that people can follow without guessing. The core idea is simple: reward outcomes and control discipline, not tool enthusiasm. When you define levels by scope and evidence, you also reduce the risk of shadow AI and inconsistent reporting narratives.
To start, pick one pilot domain (forecasting and board reporting works well) and name a framework owner this week. Within the next 4–6 weeks, run one calibration session using real artefacts and the rating scale, then capture the two or three changes that will make the matrix easier to use next cycle. If you have a Betriebsrat context, align early on transparency, data minimisation, and how AI assistance will be documented—high-level, practical, and human-accountable.
FAQ
How do we use an AI skills matrix for finance leaders without encouraging people to “game” AI usage?
Rate outcomes and controls, not tool frequency. Require evidence like tie-outs, assumption registers, and review notes that show verification happened. If someone uses AI daily but can’t reproduce results or explain adjustments, they should not score high. Also include “do-not-enter” rules (sensitive data, unmanaged tools) so safe behaviour matters more than speed.
How do we align this matrix with our existing finance competency model?
Treat this as an overlay, not a replacement. Keep your existing finance competencies (IFRS/local GAAP, internal controls, stakeholder management) and add AI behaviours where they change how work is done. For example, “communication” becomes “AI-assisted narrative with fact-checking and traceability.” Keep skill areas stable and update anchors and evidence examples as tools and workflows evolve.
How do we avoid bias in ratings when some leaders are more vocal about AI than others?
Use evidence thresholds and calibration. Ask each manager to bring 2–3 concrete artefacts per person, then compare borderline cases together. Add a simple bias script: “What evidence would change your rating?” and “Would we rate this the same if anonymised?” If you need a consistent process, borrow facilitation patterns from structured performance calibration and keep decision logs short and factual.
What’s the minimum governance we need in EU/DACH to use AI safely in finance?
Keep it practical and non-legal: approved tools list, data classification rules, and a clear escalation path for sensitive cases (payroll, customer pricing, M&A). Build in data minimisation habits and require documentation when AI assistance influences decisions or narratives. If a Dienstvereinbarung with the Betriebsrat is relevant, align early on transparency, retention, and who can access what evidence.
How often should we update the AI skills matrix for finance leaders?
Plan two cadences: quarterly for examples, templates, and prompt libraries; annually for the structure (levels and skill areas). Quarterly updates should be small: add one new “good example,” one common failure mode, and one improved checklist step. Annual updates should reflect major tool or governance changes, and you should keep a simple change log so managers understand what shifted and why.
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
