General Manager Competency Map: Strategy, Finance, Operations and People
An integrated competency map showing how general managers connect strategy, finance, customers, operations, technology, people and governance through evidence.
Advanced Executive Program in Management & Business Administration develops connected capability across strategy, finance, customers, operations, technology and people. This practical competency map can be used before enrollment, during executive study or inside an authorized workplace exercise.
Competency lists often mix personality labels, activities and outcomes. This map defines capabilities through observable work products and decisions, making development more concrete and avoiding the claim that one course completion proves executive readiness.
Capability-map standard
Which integrated competencies should a general manager develop, and what observable evidence demonstrates them? Use the tool on this page to produce a competency map with proficiency levels and an evidence portfolio. Start with a bounded decision, retain the evidence behind every material claim, and distinguish what is known from what is assumed. The tool is designed to improve management preparation and review; it does not replace the authority, specialist judgement or procedures required by an employer.
Turning broad traits into observable evidence
The competency map creates a compact common language for those connections. It does not force every organization into the same answer. Instead, it makes local definitions, evidence, constraints and accountability visible. That is useful when a management team agrees on the goal but disagrees about the route, or when confident recommendations rely on incompatible assumptions.
Domains, levels and evidence
| Element | Management purpose | Minimum evidence |
|---|---|---|
| Strategy | Frame choices, test assumptions and translate direction into priorities. | Evidence includes option memos, scenario choices and resource implications. |
| Finance | Interpret economics, cash, investment and performance trade-offs. | Evidence includes reconciled models, sensitivity tests and decision commentary. |
| Customer and commercial | Connect customer value, market evidence, pricing and growth choices. | Evidence includes segment decisions, proposition tests and commercial reviews. |
| Operations | Design flow, ownership, quality, capacity and resilience. | Evidence includes operating maps, service measures and exception decisions. |
| Technology and data | Use data and technology responsibly to improve decisions and work. | Evidence includes requirement choices, data definitions and governed experiments. |
| People and governance | Build capability, clarify authority, communicate change and manage risk. | Evidence includes decision-right maps, talent plans, communications and control responses. |
1. Strategy
Frame choices, test assumptions and translate direction into priorities. Evidence includes option memos, scenario choices and resource implications.
Review question: What observable evidence would confirm that strategy is working in the selected scope, and who has authority to respond when it is not?
2. Finance
Interpret economics, cash, investment and performance trade-offs. Evidence includes reconciled models, sensitivity tests and decision commentary.
Review question: What observable evidence would confirm that finance is working in the selected scope, and who has authority to respond when it is not?
3. Customer and commercial
Connect customer value, market evidence, pricing and growth choices. Evidence includes segment decisions, proposition tests and commercial reviews.
Review question: What observable evidence would confirm that customer and commercial is working in the selected scope, and who has authority to respond when it is not?
4. Operations
Design flow, ownership, quality, capacity and resilience. Evidence includes operating maps, service measures and exception decisions.
Review question: What observable evidence would confirm that operations is working in the selected scope, and who has authority to respond when it is not?
5. Technology and data
Use data and technology responsibly to improve decisions and work. Evidence includes requirement choices, data definitions and governed experiments.
Review question: What observable evidence would confirm that technology and data is working in the selected scope, and who has authority to respond when it is not?
6. People and governance
Build capability, clarify authority, communicate change and manage risk. Evidence includes decision-right maps, talent plans, communications and control responses.
Review question: What observable evidence would confirm that people and governance is working in the selected scope, and who has authority to respond when it is not?
Build, assess and calibrate the map
Step 1: Choose the target role
Define the scope, scale, industry and decisions expected. The immediate output is a role-specific benchmark.
Step 2: Collect evidence
Gather recent work products, outcomes and feedback. The immediate output is an evidence portfolio.
Step 3: Map demonstrations
Connect each artifact to the competency it genuinely shows. The immediate output is a traceable evidence map.
Step 4: Rate proficiency
Use levels based on complexity, independence and integration. The immediate output is a calibrated profile.
Step 5: Identify gaps
Distinguish missing experience, knowledge, authority and evidence. The immediate output is a precise development need.
Step 6: Select practice
Choose assignments that produce observable work under appropriate supervision. The immediate output is a development plan.
Step 7: Seek review
Ask qualified reviewers to challenge reasoning and outputs. The immediate output is evidence of feedback and revision.
Step 8: Reassess
Update the map after meaningful practice or role change. The immediate output is a current capability record.
Calibration example: regional GM
A commercial director preparing for a general manager role has strong customer and revenue evidence but limited ownership of cash, operating capacity and enterprise risk. The map prevents broad leadership experience from being mistaken for integrated business responsibility.
| Evidence or choice | Current entry | Interpretation | Management response |
|---|---|---|---|
| Customer and commercial | Advanced | Pricing review and segment strategy | Maintain through larger scope |
| Strategy | Applied | Market-entry options memo | Add resource-allocation decision |
| Finance | Developing | Interprets P&L; no cash forecast ownership | Build cash and investment case |
| Operations | Developing | Participates in service review | Own one cross-functional flow |
| People and governance | Applied | Team plan and risk committee contribution | Practice decision-right design |
Assessment distortions
- Rating confidence instead of evidence.
- Using course completion as proof of mastery.
- Treating years of experience as a competency level.
- Ignoring role context and scale.
- Collecting artifacts without outcomes or decisions.
- Creating a development plan with no opportunity to practice.
Development-review questions
Is this a personality assessment?
No. It maps observable management work and judgement, not fixed personal traits.
Can one artifact demonstrate several competencies?
Yes, when the evidence shows each contribution. An integrated business case may demonstrate strategy, finance and operations without proving every competency.
Who should rate the map?
Self-assessment is useful for reflection, but manager, peer or assessor challenge improves calibration.
What does advanced mean?
Advanced performance integrates several functions under uncertainty and produces defensible decisions and outcomes within the persons actual authority.
Competency evidence, calibration and fairness
The U.S. Office of Personnel Management’s Executive Core Qualifications illustrate how executive requirements can be expressed as interdependent qualifications used across selection, performance and development. OPM’s framework is specific to the U.S. federal Senior Executive Service. This article does not reproduce or replace it; it uses the broader lesson that executive performance combines results, people, stewardship and coalition-building rather than treating competencies as isolated adjectives.
The map defines observable proficiency and evidence because abstract competency statements are difficult to rate consistently. The development use case is primary. If an organization uses the map for employment decisions, it must conduct job analysis, validate relevance, train assessors, provide reasonable accommodation, protect personal data and obtain qualified local guidance. A course completion, job title or self-rating is not itself proof of workplace proficiency.
Calibration study design
Select a small group of assessors familiar with the role but not all from the same function. Train them using two fictional evidence portfolios: one strong in operations but weak in customer and people evidence, and one commercially strong with limited governance. Each assessor rates independently, cites evidence and marks uncertainty before discussion.
Compare exact agreement and differences greater than one level. Resolve differences by examining the behavioural anchor, context and evidence—not by averaging immediately. If an anchor permits contradictory interpretations, rewrite it and retest. If evidence opportunity differs, add an equivalent work sample instead of lowering the standard invisibly.
For any real use, monitor rating patterns, development opportunity and outcomes under qualified people and legal review. A correlation between level and later performance would not by itself prove causality or fairness. Record appeals or evidence corrections and maintain the standard in force at the rating date.
The map is ready for a development pilot when assessors can explain ratings, managers understand what evidence can change a level, sensitive information stays in approved systems and every development action names a real task, support, boundary and review. Selection use requires separate job-related validation.
Do not convert the six domains into a single average “GM score.” A role can require a threshold in governance or people leadership that strength in another domain cannot compensate for, and development priorities depend on the actual work context. Present a profile with confidence and evidence gaps. When a target level changes, explain the strategic or operating reason. This prevents the framework from becoming a status label detached from the work it was designed to support.
Evidence-portfolio rules
For each domain, use an evidence portfolio that includes the work produced, the context, the manager’s reasoning and a source of challenge or outcome information. One artifact can support several domains, but the reviewer must state what behaviour it demonstrates in each.
| Evidence type | Strong use | Weak use |
|---|---|---|
| Decision record | Shows frame, alternatives, trade-offs and authority | Names only the selected option |
| Operating review | Connects measures, diagnosis, action and learning | Contains attractive charts without decisions |
| Stakeholder feedback | Describes observed behaviour in a defined situation | Provides general praise or popularity |
| Outcome evidence | Compares baseline, result, contribution and uncertainty | Attributes every favourable change to the manager |
| Retrospective | Shows adaptation after an assumption failed | Rewrites the original expectation after the fact |
Use recent evidence where the operating context changes quickly, but do not discard an older example solely because it is inconvenient. Ask what was within the manager’s authority and which result depended on others. A development rating should recognize effective escalation, stopping and learning—not only visible expansion or financial upside.
If evidence is confidential, the assessor can verify it in an approved location and store a de-identified description in the development record. Absence of permission to copy a document should not be interpreted as absence of capability. Provide a fictional work sample where access to comparable workplace assignments is unequal.
For each portfolio item, record the manager’s contribution separately from the team outcome. Ask what the manager decided, enabled, challenged or changed, and which actions belonged to others. This avoids both crediting one leader for collective work and ignoring the capability to build a system in which others perform effectively.
Conflicting evidence and confidence
Evidence portfolios rarely point in one direction. Record confidence separately from proficiency when sources conflict.
Example: a manager provides a strong operating-review record showing level-three integration, but two stakeholders report that decisions are repeatedly reopened because affected teams were not consulted. Do not average the documents and feedback into a vague score. Examine whether the evidence concerns different contexts, dates or behaviours. The manager may integrate financial and operational evidence while remaining level two in stakeholder implementation.
Use three confidence labels. High means several relevant sources converge and the behaviour has repeated. Medium means the evidence is relevant but limited in setting, recency or independence. Low means the rating relies on one narrative, an ambiguous artifact or an opportunity the manager has not yet had. Low confidence is a reason to gather evidence, not automatically to assign a low proficiency level.
Development-plan conversion
Turn each gap into a work-based experiment:
Capability and target level:
Current evidence and confidence:
Real work assignment:
Behaviour to demonstrate:
Support, mentor or training:
Authority and risk boundary:
Artifact or observation required:
Affected stakeholder feedback:
Review date and assessor:
Continue, adapt or close rule:
For a finance-integration gap, the assignment might be to lead a pricing decision that reconciles customer cohort, contribution, capacity and downside scenarios. For a people-change gap, it might be to design and run one adoption review with workload and feedback evidence. The task should matter to the organization without exposing it to an unsupported stretch.
At review, assess the new behaviour against the agreed anchor. Course attendance and effort can be recorded as support, but the proficiency decision rests on applied evidence. If the organization did not provide the promised opportunity or support, revise the plan rather than interpreting the missing artifact as failure.
Evidence-based general manager competency map
This map is for development and calibration, not automatic employment decisions. Adapt it through role analysis and authorized people processes. A competency is useful only when it links a work demand to observable behaviour, evidence and a proficiency standard. Personality labels, seniority and confident presentation are not substitutes.
Proficiency scale
| Level | Scope and evidence |
|---|---|
| 1 — Understands | Explains the concept and applies it to a bounded case with guidance |
| 2 — Applies | Produces a reliable output in a defined unit and escalates beyond authority |
| 3 — Integrates | Reconciles several functions, makes trade-offs and achieves repeatable outcomes |
| 4 — Shapes | Designs the management system, builds capability in others and adapts it under uncertainty |
Rate behaviour demonstrated in context. A level is not permanent: a manager can integrate operations in a familiar service but need support in a regulated manufacturing setting. Record context, date and evidence strength.
Domain 1 — strategy and external orientation
Work demand: translate external change and organizational purpose into choices and an executable portfolio.
At level 1, the manager distinguishes diagnosis, choice and plan. At level 2, they frame a unit strategy with evidence, alternatives and measures. At level 3, they resolve trade-offs across markets, capabilities, investment and timing and explicitly stop lower-value work. At level 4, they build a repeatable strategy process, challenge assumptions and help other leaders make coherent choices.
Evidence may include a market diagnosis, strategy table, portfolio decision record, scenario analysis and retrospective comparing assumptions with outcomes. Weak proxies include the number of initiatives, the visual quality of a strategy deck or unverified claims of “strategic thinking.”
Domain 2 — finance and commercial value
Work demand: connect operating decisions with value, cash, risk and customer economics.
Level 1 reads core statements and distinguishes revenue, margin, cash and investment. Level 2 builds a traceable business case and explains sensitivity. Level 3 integrates price, mix, volume, capacity, quality and risk into a decision. Level 4 improves capital-allocation and performance routines and raises financial fluency across the team.
Evidence may include a reconciled variance bridge, risk-adjusted investment memo, unit-economics model, forecast review and benefits register. A favourable outcome alone is insufficient if the underlying reasoning cannot be traced.
Domain 3 — customer and stakeholder value
Work demand: define whose problem matters, use credible customer evidence and manage commitments across stakeholders.
Progression moves from interpreting segment evidence, to designing a bounded response, to resolving customer/financial/operational trade-offs, to building a system that connects insight, promise, delivery and learning. Evidence can include cohort analysis, interview synthesis with limitations, service promise, stakeholder map and an adaptation made because customer evidence contradicted the initial view.
Domain 4 — operations and execution
Work demand: convert demand into reliable flow, quality and outcomes through explicit ownership and capacity.
Level 1 maps a process and identifies a measure. Level 2 diagnoses a constraint and runs a controlled improvement. Level 3 manages cross-functional dependencies, variability and portfolio capacity. Level 4 designs the operating cadence, decision rights and continuous-learning system. Evidence can include process and capacity maps, KPI dictionary, operating-review record, root-cause test and benefits transition plan.
Domain 5 — people, organization and change
Work demand: create conditions in which people can understand, adopt and sustain the required work.
Progression runs from fair delegation and feedback, through team capability planning, to organization-wide alignment of roles, incentives, capacity and change, and finally to building leaders who can sustain the system. Evidence includes role clarity, capability assessment, change-impact plan, stakeholder feedback, workload correction and an example where the manager changed their approach after challenge. Sensitive employee records remain in approved systems and are not copied into a learning portfolio.
Domain 6 — governance, technology and responsible judgment
Work demand: use authority, data and technology within control boundaries while preserving accountability.
Level 1 recognizes limits and escalates. Level 2 keeps evidence and decision records, follows approved controls and verifies technology outputs. Level 3 integrates risk, data quality, security, legal, AI and operational consequences into choices. Level 4 designs proportionate governance and independent challenge without making the organization unable to act. Evidence includes a decision-quality audit, data-quality control, AI verification record, risk acceptance and an incident or near-miss learning review.
Calibration worksheet
| Domain | Target level for role | Evidence observed | Context / date | Assessor rating | Manager rating | Gap and risk | Development action | Recheck |
|---|---|---|---|---|---|---|---|---|
| Strategy | ||||||||
| Finance / commercial | ||||||||
| Customer / stakeholder | ||||||||
| Operations / execution | ||||||||
| People / change | ||||||||
| Governance / technology |
Require at least two evidence types for a high-stakes rating and include one source other than the manager’s own narrative. Calibrators should discuss the evidence and standard before discussing the person. Where ratings differ, record the reason: different evidence, different context, ambiguous anchor or genuine judgment.
Worked calibration: regional GM
The role target is level 3 in all domains and level 4 in operations because the unit is scaling a complex service. The manager submits a successful revenue plan as evidence of strategy and finance. Reviewers rate strategy 2 because alternatives and stopped work are not visible; finance 3 because the model links price, mix, capacity and downside scenarios; customer 2 because evidence is mostly aggregate satisfaction; operations 4 because the manager designed a cadence that reduced rework across three units; people 2 because capability plans depend on informal knowledge; governance 3 because decision and risk records are consistent.
The development plan does not say “be more strategic.” It requires the manager to lead the next portfolio review using explicit alternatives, capacity constraints and a decision log, with an independent reviewer observing. For customer capability, the manager must compare two cohorts and change one operating choice based on evidence. For people capability, they will create role and coverage maps with the HR partner. Evidence is reviewed in 90 days.
Development experiment design
Write each action as stretch task + support + evidence + boundary + review. Example: “Lead a €300,000 service redesign business case; receive two finance coaching sessions; submit the model, options and challenge log; do not commit supplier spend; review with CFO and sponsor on 30 November.” Courses, mentoring and reading can support the task but are not evidence that behaviour changed.
Fairness and maintenance controls
Check whether examples privilege access to large budgets, international assignments or charismatic presentation. Offer comparable work samples where opportunity differs. Train assessors, pilot anchors, compare rating patterns and review for adverse impact under qualified local guidance. Do not average away a critical role requirement, and do not convert the map into an undisclosed automated selection score.
Review the map when strategy, role scope, technology, risk or operating model changes. Retire competencies that no longer predict work, and preserve version history so past assessments are interpreted against the standard used at the time.
The Advanced Executive Program in Management & Business Administration can support development across the integrated domains represented in this map.