Skip to content
English
Sign in
Contact us
  • There are no suggestions because the search field is empty.

Lens based report prompt overview

The Lens-based (Match) prompt turns a role lens (your selected set of competencies) into a job-fit narrative. It explains the person’s likely contribution against the role, using your performance levels — UNDER / JUST_RIGHT / OVER — instead of numbers. The output links each competency to its domain impact (Driving, Enabling, Strategic, Operative) and finishes with practical, role-relevant suggestions.

What you provide

  • Lens match level (Lower / Average / Strong / Very strong).

  • 4–9 competencies from the lens, each with its performance level (UNDER / JUST_RIGHT / OVER).

  • Locale (language/market) so the text reads like a native consultant’s draft for that country. 

How the prompt writes (rules it follows)

  • Reports never show numeric scores; only the three performance levels appear.

  • It writes like a local organizational psychologist (native tone, idiomatic phrasing).

  • Each competency is referenced inline with a custom tag, e.g.
    … excels at <Competency id="NETWORKING">building and maintaining professional relationships</Competency> …

  • Every competency paragraph weaves 3–5 behaviors, a brief workplace example, domain outcomes (e.g., Driving → ambition & accountability), risks if not developed, and 1–2 concrete suggestions.

Domains & typical effects (used throughout the text)

  • Driving → ambition, goal clarity, accountability, customer focus.

  • Enabling → cohesion, psychological safety, inclusion, team focus.

  • Strategic → innovation, adaptability, long-term thinking, change.

  • Operative → structure, predictability, compliance, process discipline.

How levels are interpreted (plain English)

  • UNDER → behavior shows less consistently; expect caution/hesitation; clarify expectations and add scaffolding.

  • JUST_RIGHT → balanced, reliable intensity; behavior supports outcomes without unintended side-effects.

  • OVER → strength used too much; risk of dominance, rigidity, over-networking, or over-servicing at the expense of results.
    (The narrative uses your domain- and competency-specific descriptors for each level.)

Competency coverage (examples the prompt knows)

The prompt includes detailed behavior libraries and level descriptors for the core competencies across all four domains, e.g.:

  • Driving: Influencing & Inspiring, Networking, Initiating Action, Drives Progress – Ambitious, Driving Leadership.

  • Enabling: Self-Awareness & Humility, Collaborates with Others, Fosters Transparency, Service-Oriented, Enabling Leadership.

  • Strategic: Problem Solving, Entrepreneurial & Commercial, Embraces Change, Stays Adaptive, Strategic Leadership.

  • Operative: Demonstrates Integrity, Results-Oriented, Plans & Structures, Stays Resilient, Operative Leadership.
    Each has UNDER / JUST_RIGHT / OVER narratives baked in (e.g., overuse of Initiating Action → too many parallel starts; Fosters Transparency overuse → bluntness).

Sections the prompt produces

1) Profile Match

Interprets overall lens match (e.g., “Strong match”) and what that likely means day-to-day. Always reminds that potential ≠ performance without context and growth.

2) Key Takeaways

2–3 evident strengths and at least 2 development areas, each introduced with an inline <Competency …> tag, a short workplace example, a domain outcome (e.g., impact on cohesion or throughput), and one “keep/start” suggestion. Ends with a bridge to the next section.

3) Detailed Competency Insights

One paragraph per competency (highest → lowest). Each 5–6 sentences: behaviors in practice, a brief scenario, domain effect, risk if unaddressed, and a practical development action. Tone is objective, supportive, and future-focused.

4) Summary

Pulls the pattern together: match level + likely contribution + where to focus. Closes with a balanced message (strengths and risks) and reinforces that addressing development needs is essential for long-term success.

Practical tips for users

  • Confirm the lens first. The lens defines the behaviors the prompt will talk about.

  • Sense-check levels before generating; they drive the entire narrative.

  • Pick the right locale (SE/NO/NL/DE/DK/EN). The prompt “thinks” and writes natively for that market.

  • Use with Report Studio templates where job-fit is central: Match, Match with Core Talents, Match with Extremes, or Match with Agility.

  • Document decisions in the report’s Notes; keep numbers for internal analysis views, not for stakeholder prose.

FAQ

Can I add numbers back into the text?
Avoid it. The prompt and templates are designed to suppress numeric scores in narrative to keep focus on observable behavior and fairness. Use Analyze for numeric comparisons.

What if all competencies are low?
The prompt still surfaces relative strengths and clear, non-punitive development advice, keeping tone constructive.

How are examples chosen?
From a curated behavior library per competency and level (e.g., Networking → relationship-building across teams; Plans & Structures → breaking work into steps, anticipating risks). The narrative adapts examples to the selected domain outcomes