Management Work Products in 100 Vacancies from Eight Fortune 100 Employers
Executive answer
Management candidates should prepare evidence of making work visible, not only evidence of possessing skills. In a frozen purposive sample of 100 US management vacancies from eight 2026 Fortune 100 employers, 62 vacancies explicitly asked managers to create, develop, maintain, review or deliver a plan, roadmap or strategy. Thirty-three named a process, workflow, template or operating model; 24 named metrics, dashboards or KPIs; 24 named analyses, assessments or recommendations; and 14 named budgets, forecasts, financial models or business cases.
The practical implication is not that every candidate needs the same portfolio. It is that a portfolio should contain work products matched to the target role family. A finance-oriented candidate should show how a forecast or model changed a decision. A technology manager should show a roadmap connected to metrics and operating controls. A people or operations manager should show a plan and a redesigned process. The artifact must be redacted, contextualized and honest about what the candidate personally owned.
This report is a dated content analysis, not a ranking of employers and not a representative estimate of all Fortune 100 hiring. The sample contains 100 distinct vacancies from eight employers captured on 10 August 2026. The September report re-analyzes the frozen source text under a stricter work-product question and publishes vacancy-level coding and a role-family cross-tab.
Research question
Which concrete work products are managers explicitly asked to create, maintain, review or deliver in a frozen sample of 100 US management vacancies from eight Fortune 100 employers, and how does the mix vary by role family?
The decision behind the question is practical: if a candidate or student can build only three portfolio artifacts, which types are most defensible for the roles being targeted?
Why work products are more useful than another skills list
A skill label such as “strategic thinking” can mean many things. A work product creates a testable conversation. A roadmap can reveal how priorities were chosen. A dashboard can show whether measures connect to decisions. A budget can expose assumptions. A process map can show handoffs and controls. An executive brief can demonstrate whether a manager distinguishes evidence from recommendation.
This does not mean that documents are the whole job. Managers also coach, negotiate, decide, communicate and respond in real time. Nor does a portfolio prove performance by itself. However, an artifact plus a concise explanation gives a reviewer something concrete to question:
- What problem did it address?
- What information did you use?
- Which decision did it support?
- What trade-off did you make?
- What changed afterward?
- What was your personal contribution?
- What information had to be removed or protected?
Those questions are more informative than asking whether someone “has leadership.”
Scope and sample
The source corpus contains 100 unique public management vacancies captured on 10 August 2026 from eight employers appearing in the 2026 Fortune 100 universe. Roles span general management, technology and data, people and operations, finance and strategy, risk/legal/compliance, and commercial/customer functions.
The role-family distribution used in this analysis is:
| Role family | Vacancies |
|---|---|
| General management | 46 |
| Technology and data | 25 |
| People and operations | 10 |
| Finance and strategy | 8 |
| Risk, legal and compliance | 6 |
| Commercial and customer | 5 |
| Total | 100 |
The employer distribution is not presented as a league table. Availability, corporate career-site structure and the original purposive sampling method shaped the corpus. Eight employers cannot represent the full diversity of the Fortune 100. Results should be treated as signals for portfolio design and future testing, not population prevalence.
Inclusion and exclusion criteria
An observation qualified when it was a distinct US vacancy, available in the frozen archive, and managerial in title or responsibilities under the original sample protocol. Duplicate URLs and non-management roles were excluded before this re-analysis.
A work-product category was coded only when the vacancy connected an action verb—such as create, develop, build, prepare, produce, deliver, maintain, manage, draft, implement, define, document, present, analyze, track, review or update—to a named artifact within the same local text segment. This conservative rule reduces false positives from generic phrases.
For example, “develop a product roadmap” qualifies. “Strategic mindset” does not. “Create and implement productivity plans through forecast reviews” qualifies for plans and for forecasts when both are explicit. A site-wide privacy policy in footer text does not qualify because boilerplate was removed before coding.
Coding framework
Ten non-exclusive categories were used:
- plans, roadmaps and strategies;
- reports, briefs and presentations;
- metrics, dashboards and KPIs;
- budgets, forecasts, financial models and business cases;
- policies, procedures, SOPs and playbooks;
- contracts, proposals, RFPs, statements of work and project scopes;
- risk registers, risk assessments, control matrices, evidence and remediation plans;
- processes, workflows, templates and operating models;
- analyses, evaluations, assessments and recommendations;
- schedules, backlogs, project charters, milestones and deliverables.
Categories can overlap because a vacancy may ask for several products. Counts therefore do not sum to 100. The public supporting file contains the binary category fields and the first qualifying evidence excerpt for auditability.
Overall findings
| Work-product category | Vacancies | Share of sample |
|---|---|---|
| Plans, roadmaps and strategies | 62 | 62% |
| Processes, workflows, templates and operating models | 33 | 33% |
| Metrics, dashboards and KPIs | 24 | 24% |
| Analyses, evaluations, assessments and recommendations | 24 | 24% |
| Budgets, forecasts, financial models and business cases | 14 | 14% |
| Policies, procedures, SOPs and playbooks | 14 | 14% |
| Schedules, backlogs, charters, milestones and deliverables | 12 | 12% |
| Reports, briefs and presentations | 10 | 10% |
| Contracts, proposals, RFPs, SOWs and project scopes | 9 | 9% |
| Explicit risk/control evidence artifacts | 1 | 1% |
The final category should not be interpreted as evidence that risk work is unimportant. The coding required a narrow explicit artifact such as a risk register, risk assessment, control matrix or remediation plan. Vacancies can describe risk responsibility without naming one of those products. The result is a reminder that this study measures explicit work-product language, not the full task content of each job.
Twenty-one vacancies did not contain any of the ten action-linked artifact categories under the conservative screen. That does not mean they produce nothing. They may emphasize people leadership, operational execution, negotiation, service delivery or responsibilities described without a named artifact.
Finding 1: plans and roadmaps are the most portable portfolio artifact
Plans, roadmaps or strategies appeared in 62 vacancies. They were visible across every role family: 80% of technology/data roles, 80% of people/operations roles, 62.5% of finance/strategy roles, 54.3% of general management roles, 40% of commercial/customer roles and 33.3% of risk/legal/compliance roles.
This breadth makes a decision roadmap a strong default portfolio artifact. But a useful roadmap is not a timeline of activities. It should connect an outcome, decision criteria, dependencies, resources, measures, risks and review cadence.
A candidate should be able to explain why one item appears before another and what evidence would change the sequence. Without that logic, a roadmap demonstrates formatting rather than management.
Finding 2: operating design is a major part of management work
Processes, workflows, templates or operating models appeared in 33 vacancies. The category reached 50% among risk/legal/compliance roles, 40% among people/operations roles, 37.5% among finance/strategy roles, 34.8% among general management roles and 28% among technology/data roles.
This pattern supports a second portfolio artifact: a before-and-after workflow or operating-model design. The artifact should identify inputs, outputs, owners, decision rights, handoffs, failure signals and controls. A manager can then show what was simplified, automated, standardized or reassigned and why.
The practical distinction is between “I improved a process” and an evidence chain showing the original bottleneck, proposed design, implementation choice and measured effect.
Finding 3: measurement requirements vary by role family
Metrics, dashboards or KPIs appeared in 24 vacancies overall. The share was 50% in finance/strategy, 30% in people/operations, 24% in technology/data and 23.9% in general management. None of the five commercial/customer or six risk/legal/compliance roles met the conservative action-linked rule for this category.
The small subgroup sizes mean those zeros should not be generalized. They do, however, demonstrate why a single portfolio formula is weak. A finance candidate should expect questions about measurement logic and economic assumptions. A legal or contracts candidate may need a stronger evidence artifact around terms, workflow or negotiation rather than a dashboard.
A dashboard portfolio item should include a metric dictionary, data source, owner, update frequency, decision threshold and example of a decision that changed. Screenshots without definitions can hide rather than demonstrate understanding.
Finding 4: financial artifacts are concentrated but decision-rich
Budgets, forecasts, financial models or business cases appeared in 14 vacancies. They appeared in 50% of the small commercial/customer group, 30% of people/operations, 25% of finance/strategy, 12% of technology/data and 8.7% of general management roles.
The surprising spread beyond finance reflects the economic dimension of management. Operations leaders forecast capacity. Commercial leaders evaluate opportunities. Technology managers justify investment. A simple business case can therefore be a useful cross-functional artifact if it shows assumptions, scenarios, non-financial constraints and a review rule.
Candidates should avoid presenting a model as proof that the chosen initiative will succeed. A model is a conditional representation. The stronger interview discussion is which assumption mattered most, how uncertainty was handled and what evidence would trigger a different decision.
Finding 5: work products appear in combinations
The categories are non-exclusive. Nineteen vacancies named one category, 18 named two, 16 named three, 11 named four, seven named five, one named six and one named nine. Twenty-one had none under the strict rule.
The combination matters because managerial work often forms a chain. Analysis informs a plan. A plan establishes metrics. A workflow implements the plan. A report communicates performance. A portfolio with three connected artifacts is therefore more persuasive than three unrelated examples.
For instance:
- an assessment identifies a bottleneck;
- a roadmap sequences changes;
- a dashboard monitors outcome and guardrails.
The candidate can then show how evidence moved through the system.
Role-family cross-tab
Selected percentages illustrate the different portfolio emphasis:
| Role family | n | Plans / roadmaps | Processes / workflows | Metrics / dashboards | Budgets / models | Policies / procedures |
|---|---|---|---|---|---|---|
| Technology and data | 25 | 80.0% | 28.0% | 24.0% | 12.0% | 0.0% |
| People and operations | 10 | 80.0% | 40.0% | 30.0% | 30.0% | 30.0% |
| Finance and strategy | 8 | 62.5% | 37.5% | 50.0% | 25.0% | 37.5% |
| General management | 46 | 54.3% | 34.8% | 23.9% | 8.7% | 15.2% |
| Risk, legal and compliance | 6 | 33.3% | 50.0% | 0.0% | 0.0% | 16.7% |
| Commercial and customer | 5 | 40.0% | 0.0% | 0.0% | 40.0% | 0.0% |
The commercial and risk groups are too small for stable prevalence comparisons. Use them as observed examples within this sample, not forecasts for the labor market.
The Portfolio Evidence Matrix
Choose three artifacts for a target role. Complete this matrix before building them:
| Field | Question |
|---|---|
| Target decision | What decision will the artifact support? |
| Artifact | What will the reviewer see? |
| Source inputs | What evidence and assumptions feed it? |
| Personal ownership | What did you decide or produce? |
| Stakeholders | Who reviewed, challenged or used it? |
| Acceptance test | What makes the artifact complete and useful? |
| Outcome evidence | What changed, or what did the analysis reveal? |
| Limitation | What cannot be concluded? |
| Redaction rule | What must be removed, aggregated or recreated? |
Suggested three-artifact sets
Technology/data manager: product or capability roadmap; metric dictionary and decision dashboard; before-and-after operating workflow.
People/operations manager: staffing or productivity plan; process redesign; forecast or capacity business case.
Finance/strategy manager: driver-based model; strategic option assessment; KPI dashboard with decision thresholds.
Risk/legal/compliance manager: scoped workflow; policy or playbook; redacted contract/proposal or control-evidence case suited to the role.
General manager: strategy-on-a-page; cross-functional operating process; monthly performance review pack.
These are starting points, not claims about every vacancy. Read the target descriptions and replace the set when the employer names different outputs.
Worked example: a technology manager portfolio
Ana targets technology program manager roles. She selects three artifacts.
First, a six-month capability roadmap for a fictional internal service. It states the user problem, options, dependencies, resource assumptions, success measures and stop conditions. Second, a metric dictionary and dashboard mock-up covering cycle time, failure rate, adoption and a safety guardrail. Third, a redesigned incident-escalation workflow showing decision rights and handoffs.
Ana does not upload employer-confidential files. She reconstructs the scenario with synthetic data and labels it. In her explanation, she distinguishes what is based on a real pattern from what is invented for demonstration. Her acceptance tests are:
- roadmap priorities trace to stated criteria;
- every metric has a source, owner and decision threshold;
- every workflow escalation has an accountable role and response time;
- no confidential client, employee or system details remain;
- limitations are visible.
The portfolio now answers a practical question: can Ana translate ambiguity into a plan, measurement system and operating mechanism? It does not prove she will perform in a new employer, but it gives the reviewer evidence to challenge.
Implications for educators
Courses should assess connected work, not only recall. A management module can require learners to move from problem framing to analysis, roadmap, measurement and executive communication. Rubrics should test traceability, assumptions, decision relevance, clarity and limitations.
Educators should also teach redaction. Learners often cannot publish genuine work products. They need a method for converting experience into a safe case without implying that fictional numbers are real results.
Finally, feedback should ask whether the artifact changed a decision. A beautiful dashboard with no decision threshold is incomplete. A plan with no constraint is not executable. A report with no distinction between evidence and recommendation is difficult to trust.
Limitations
This study has important limits:
- The sample covers 100 vacancies from only eight Fortune 100 employers.
- It is purposive and availability-dependent, not statistically representative.
- Vacancies were captured on one date and may later change or disappear.
- Role families were assigned from titles using a transparent rule and simplify hybrid jobs.
- Automated pattern screening can miss synonyms or unusual sentence structure.
- Conservative action-to-artifact rules undercount responsibilities described without a named product.
- A vacancy may expect an artifact even when it is not stated.
- Frequency does not indicate importance, time spent or hiring weight.
- This report studies wording, not actual on-the-job behavior or candidate success.
The supporting CSV preserves source URLs, capture dates, category flags and evidence excerpts so readers can audit the classifications. Future waves should include more employers, manually adjudicate edge cases with multiple coders and compare changes over time.
What candidates should do next
- Collect ten target vacancies and highlight explicit work products.
- Count categories for that personal target set rather than copying this report’s totals.
- Select three connected artifacts.
- Build or reconstruct them with a clear decision, inputs and acceptance test.
- Remove confidential and personal information.
- Write a 150-word explanation of ownership, trade-off, outcome and limitation.
- Ask a practitioner to challenge one artifact.
- Revise the portfolio and prepare to explain what the artifact does not prove.
This sequence converts a market signal into an individual learning plan.
Learning pathway
The General Management & Strategic Leadership programme is the relevant MTF pathway for learners who want to deepen decision framing, strategy execution, operating design and evidence-based management. Use the report’s Portfolio Evidence Matrix to connect learning to three role-relevant outputs.
Reproducibility and data availability
The archival package includes the vacancy-level coded dataset, category summary, role-family cross-tab and a searchable PDF of this report. Source URLs and capture dates are provided for verification. The original vacancy text was used for analysis but is not redistributed in full because career-site content can be copyrighted and change over time. Evidence excerpts are limited to what is necessary to audit coding.
Citation
MTF Institute Editorial Team. Management Work Products in 100 Vacancies from Eight Fortune 100 Employers. MTF Institute Research Report MTF-RR-2026-09-16-01. 16 September 2026.
Sources
- MTF Institute frozen 100-vacancy source inventory, captured 10 August 2026.
- NIST NICE Workforce Framework for Cybersecurity, used as an example of work-role and task-oriented capability description.
- O*NET Resource Center, consulted for occupational-information context.
Research date: 16 September 2026. This report is an educational market snapshot and does not provide employment, legal or investment advice.