Lewin Leadership Styles logo

Lewin Leadership Styles

Community
fatihguner
lewin-leadership-styles

Assesses leadership approach using Lewin's three styles: autocratic, democratic, and laissez-faire. Evaluates the fit between a leader's dominant style and their organizational context. Use when diagnosing team dysfunction caused by management style, transitioning from founder-led to distributed decision-making, navigating a crisis requiring temporary style shifts, or auditing the founding team's leadership dynamics.

Overview

Publisherfatihguner
Repositoryforeman
Skill namelewin-leadership-styles
Stars
63
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by fatihguner on GitHub. Read the source before you install it.

Installation

Install the Lewin Leadership Styles AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/lewin-leadership-styles
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/fatihguner/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/plugins/foreman/skills/lewin-leadership-styles .claude/skills/lewin-leadership-styles
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Lewin Leadership Styles in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Lewin Leadership Styles on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Lewin Leadership Styles is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Lewin's Leadership Styles

Imagine three identical teams of ten people, each given the same project, the same deadline, and the same resources. The only variable is the leader. Team A's leader makes every decision, assigns every task, and monitors every output. Team B's leader sets the vision, then asks the team how they want to get there. Team C's leader says "figure it out" and retreats to their office. Kurt Lewin ran essentially this experiment in 1939 with groups of children -- and the results mapped with uncomfortable precision onto dynamics that play out in every startup, corporation, and nonprofit today. The autocratic group produced more output but lower quality and collapsed when the leader left. The democratic group produced slightly less volume but far higher quality and sustained performance independently. The laissez-faire group produced the least, with the most frustration and the worst interpersonal dynamics.

Three styles. Three radically different organizational outcomes. Lewin's framework remains the foundation upon which all subsequent leadership theory was built.


The Framework

Lewin identified three primary leadership styles along a spectrum of control. The framework is descriptive (leaders tend toward one style) and prescriptive (certain contexts reward certain styles).

The Three Styles Compared

DimensionAutocraticDemocraticLaissez-Faire
Decision authorityLeader decides aloneLeader facilitates group input, then decides or delegatesLeader abdicates decision-making
Communication flowTop-down, directiveBidirectional, consultativeMinimal, reactive
Team autonomyLow; tasks are assigned with specific instructionsModerate; team participates in planning and execution choicesHigh in theory, chaotic in practice
Speed of decisionsFastModerateSlow or absent
InnovationLow; risk-aversion dominatesHigh; diverse perspectives surfaceVariable; depends entirely on team capability
Team moraleLow long-term; resentment buildsHigh; ownership breeds engagementLow; absence of guidance feels like abandonment
Quality of outputVariable; depends on leader's expertiseConsistently high; collective intelligence corrects errorsTypically low; no quality standards enforced
ScalabilityPoor; bottleneck at the leaderStrong; distributed decision-making scalesUnpredictable; works only with exceptional self-managing teams
Leader absence impactSevere; work stops or quality collapsesMinimal; team continues autonomouslyNone; the leader was already functionally absent

Autocratic Leadership

The autocratic style concentrates authority in the leader. Decisions are made without consultation. Execution follows prescribed instructions. This style produces rapid decision-making and clear accountability -- valuable during crises, turnarounds, or situations requiring strict compliance. The cost is suppressed initiative, hidden information (team members withhold bad news from directive leaders), and a single point of failure.

Founders default to this style more frequently than they realize. The founding period demands rapid, intuitive decision-making, and the habit persists long after the team has grown beyond the point where one brain can hold all relevant context.

Democratic Leadership

The democratic style distributes authority while retaining ultimate responsibility. The leader sets direction, solicits input, facilitates deliberation, and either makes the final call or delegates it to the most capable team member. This is the style most consistently associated with high performance, innovation, and retention in Lewin's research and in subsequent decades of organizational studies.

The cost is speed. Democratic processes take longer than autocratic ones. For startups racing against runway, this tradeoff is real. The art lies in knowing which decisions warrant democratic process and which do not.

Laissez-Faire Leadership

The laissez-faire style delegates almost all authority and provides minimal guidance. Lewin's research consistently showed this style producing the worst outcomes -- not because autonomy is bad, but because laissez-faire as Lewin defined it implies abdication rather than intentional empowerment.

The distinction matters enormously. A leader who deliberately builds systems, hires exceptional people, and then steps back is not practicing laissez-faire -- they are practicing high-trust democratic leadership. Lewin's laissez-faire leader provides neither structure nor support. The team is not liberated; it is abandoned.


Prompts

Prompt 1 -- Leadership Style Self-Assessment:

Based on the following description of how I typically lead my team, assess which of Lewin's three leadership styles I default to and how that style is affecting our performance. Here's how I operate: [describe your decision-making process, communication patterns, how you handle disagreements, how much autonomy you give team members, how you respond when things go wrong]. Identify the strengths of my current style, the costs I may not be seeing, and specific situations where I should consciously shift to a different style.

Prompt 2 -- Situational Style Selection:

I'm facing the following leadership challenge: [describe situation -- e.g., "We need to pivot our product in 4 weeks with a team of 8" or "We're scaling from 15 to 50 people and decisions are getting slower"]. Using Lewin's framework, which leadership style should I adopt for this specific situation and why? What would the autocratic, democratic, and laissez-faire approaches each look like here, and what are the risks of each?

Prompt 3 -- Team Dynamics Diagnosis:

My team is exhibiting these behaviors: [describe -- e.g., "People wait for me to make every decision," "Nobody takes initiative," "There's a lot of resentment about micromanagement," "We have great ideas but can't execute"]. Using Lewin's leadership styles framework, diagnose which leadership style is likely producing these symptoms, and recommend a transition plan to a more effective style for our context.

Prompt 4 -- Leadership Style Audit for the Founding Team:

Our founding team consists of [number] co-founders with these roles: [describe]. Each of us leads differently. Map each co-founder's style to Lewin's framework based on these descriptions: [describe each person's approach]. Analyze where our styles complement each other, where they conflict, and how we should allocate leadership responsibilities based on which style each situation demands.


Use Cases

Founder Transition from Autocratic to Democratic

A validation-stage fintech founder built the first version of the product through sheer force of will -- making every product decision, writing much of the code, dictating design choices. The company survived. Now at 20 employees, the same autocratic instincts are causing the best engineers to leave. Exit interviews reveal a consistent theme: "I felt like a pair of hands, not a brain." Applying Lewin's framework, the founder recognizes that the style appropriate for a three-person garage operation is toxic at the current scale. The transition plan involves categorizing decisions into three tiers: strategic (founder decides after consultation), tactical (team leads decide with founder input), and operational (team members decide autonomously). The shift is uncomfortable. Decisions take longer. But within six months, retention stabilizes and product velocity actually increases because the founder is no longer the bottleneck.

Crisis Requiring Temporary Autocratic Shift

A growth-stage e-commerce company with a normally democratic culture discovers a critical security breach exposing customer payment data. The CEO, who typically runs collaborative decision-making processes, recognizes that this moment demands autocratic leadership: clear commands, no debate, immediate execution. She assigns specific tasks to specific people, sets 30-minute check-in cycles, and makes every escalation decision herself for 72 hours. Once the crisis is contained, she deliberately shifts back to democratic mode for the post-mortem and remediation planning. Lewin's framework provides the vocabulary for this conscious style-switching -- and the team understands the shift because the CEO names it explicitly.


Anti-Patterns

  • Permanent Autocracy Disguised as Startup Necessity. The belief that startups require autocratic leadership indefinitely. Early-stage founding demands fast, centralized decisions -- but failing to evolve toward democratic leadership as the team grows is a primary driver of co-founder conflict and early-employee exodus. The startup excuse has an expiration date.

  • Laissez-Faire as Flatness Ideology. Adopting a leaderless or flat organizational structure and believing it represents enlightened management. Without deliberate structure, clear accountability, and active facilitation, "flat" organizations devolve into laissez-faire dysfunction: invisible hierarchies, diffused responsibility, and decision paralysis. Valve, GitHub, and other companies that experimented with radical flatness have documented the resulting pathologies extensively.

  • Style Rigidity Across Contexts. Applying the same style to every situation regardless of circumstances. A democratic process for deciding whether to evacuate a burning building is as dysfunctional as an autocratic process for designing a creative campaign. Lewin's framework is descriptive of tendencies but prescriptive of flexibility.

  • Confusing Democratic with Consensus. Believing democratic leadership means everyone must agree. Democratic leadership means everyone's input is heard and considered. The leader still decides. Consensus-seeking produces the worst of both worlds: the slowness of democracy without the decisiveness of autocracy.


By Stage

StageRecommended Dominant StyleKey Difference
IdeaAutocratic with democratic elementsThe founder's vision drives direction; small team size makes full democracy unnecessary, but co-founder input is essential
ValidationDemocratic-leaningRapid experimentation benefits from diverse perspectives; the team must feel ownership of pivots
Early TractionDemocraticDecision-making must distribute as the team grows beyond the founder's cognitive bandwidth
GrowthDemocratic with role-based authorityFunctional leaders adopt their own styles within their domains; founder sets culture and strategy
ScaleInstitutional democraticFormal processes, clear decision rights, and cultural norms replace the founder's personal style as the organizing principle

Output Template

markdown
# Leadership Style Assessment: [Leader/Team Name]

**Date:** [Date]
**Team Size:** [Number]
**Company Stage:** [Stage]

## Current Style Profile

| Leader/Role | Dominant Style | Secondary Style | Context Appropriateness |
|-------------|---------------|-----------------|------------------------|
| [Name] | [Autocratic/Democratic/Laissez-Faire] | [Style] | [High/Medium/Low] |

## Situational Analysis

### Decisions That Should Be Autocratic
- [Decision type]: [Why speed/clarity outweighs input]

### Decisions That Should Be Democratic
- [Decision type]: [Why diverse input improves outcomes]

### Decisions That Can Be Fully Delegated
- [Decision type]: [Why the team member is best positioned]

## Transition Recommendations
1. [Specific behavior change]
2. [Specific process change]
3. [Specific communication change]

## Risks of Current Style at Current Stage
- [Risk 1]
- [Risk 2]

## Success Metrics
- [How you'll know the style shift is working]

Related Skills

  • Situational Leadership -- Hersey and Blanchard's framework extends Lewin by matching leadership style to follower maturity, providing a more granular decision model for style-switching.
  • Tuckman's Team Stages -- The stage of team development influences which leadership style is most effective; forming teams need more direction, performing teams need less.
  • Hackman's Enabling Conditions -- Hackman's research shows that the leader's primary job is creating conditions for team success, which aligns with democratic rather than autocratic leadership.
  • Leadership Style Adaptation -- Provides practical guidance for shifting between leadership styles in response to context, extending Lewin's theoretical taxonomy into daily practice.
  • Decision Making Under Pressure -- Crisis situations often demand a temporary shift to autocratic leadership; this skill addresses how to make that shift deliberately and return to democratic mode afterward.

Frequently asked questions

What does the Lewin Leadership Styles AI skill do?

Assesses leadership approach using Lewin's three styles: autocratic, democratic, and laissez-faire. Evaluates the fit between a leader's dominant style and their organizational context. Use when diagnosing team dysfunction caused by management style, transitioning from founder-led to distributed decision-making, navigating a crisis requiring temporary style shifts, or auditing the founding team's leadership dynamics.

Why use Lewin Leadership Styles on TypingMind?

Because you install it once and use it with any model. Lewin Leadership Styles is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Lewin Leadership Styles in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/lewin-leadership-styles. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Lewin Leadership Styles?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Lewin Leadership Styles?

As many as you like. As long as a model supports skills, you can use Lewin Leadership Styles with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Lewin Leadership Styles AI skill free?

Yes. It is published on GitHub by fatihguner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇