Apply Upper Echelons Theory (Hambrick and Mason, 1984) to analyze how top management team characteristics — demographics, experiences, values — shape strategic choices and organizational outcomes. Use this skill when the user needs to evaluate TMT composition effects on strategy, predict strategic direction from leadership profiles, assess whether managerial discretion enables or constrains executive influence, or when they ask 'does leadership background matter for strategy', 'how does TMT composition affect decisions', or 'why did this management team make that choice'.
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-strat-upper-echelons
Upper Echelons Theory (Hambrick & Mason, 1984) proposes that organizational outcomes — strategic choices and performance — are partially predicted by the characteristics of top management teams (TMTs). Executives face complex, ambiguous situations that they interpret through the filter of their experiences, values, and personalities. Observable demographics serve as proxies for these cognitive bases.
IRON LAW: Managerial characteristics predict strategic outcomes ONLY
when managerial discretion is high. In highly regulated industries
or constrained environments, executive characteristics are muted
by environmental determinism. Always assess discretion before
attributing outcomes to TMT profiles.
Key assumptions:
Objective Situation → Executive Perception (filtered) → Strategic Choice → Performance
↑
TMT Characteristics
(demographics as proxies for cognition)
| Characteristic | Strategic Tendency |
|---------------|-------------------|
| Younger TMT | More risk-taking, innovation, growth strategies |
| Longer tenure | Strategy persistence, less change, commitment to status quo |
| Functional diversity | Broader strategic repertoire, more comprehensive decisions |
| Output-function background (marketing, sales) | Growth, diversification |
| Throughput-function background (operations, accounting) | Efficiency, cost control |
| Higher education | More innovation, tolerance for ambiguity |
| TMT heterogeneity | Better decisions but slower, more conflict |
| Factor | High Discretion | Low Discretion |
|--------|----------------|----------------|
| Industry regulation | Low regulation | Heavy regulation |
| Market growth | High growth | Mature/declining |
| Board vigilance | Passive board | Active, independent board |
| Firm performance | Strong performance (slack) | Crisis (constrained) |
## Upper Echelons Analysis: [Context]
### Managerial Discretion Assessment
- Industry discretion: [high/moderate/low] — ...
- Organizational discretion: [high/moderate/low] — ...
- Overall: [sufficient/insufficient for UE analysis]
### TMT Profile
| Executive | Age | Tenure | Functional Background | Education | Key Experience |
|-----------|-----|--------|----------------------|-----------|----------------|
| [name] | ... | ... | [function] | [degree] | [notable] |
### TMT Composition Summary
- Average tenure: ... | Heterogeneity: [high/moderate/low]
- Dominant functional background: ...
- Predicted strategic tendencies: ...
### Strategy-Profile Alignment
- Predicted direction: ...
- Observed strategy: ...
- Gaps/blind spots: ...
Analyzing a tech firm TMT: young average age (42), short average tenure (3 years), high functional diversity, strong engineering background. Discretion is high (fast-growing, lightly regulated market). Prediction: aggressive innovation strategy with rapid pivoting. Observed: confirms prediction. Blind spot: weak financial/operations representation may lead to scaling problems.
Attributing a utility company's conservative strategy to its older TMT without assessing managerial discretion. The utility industry is heavily regulated with low discretion — any TMT would likely pursue similar strategies regardless of demographics.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take asgard-ai-platform/grad-strat-upper-echelons from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.