Systems Thinking Iceberg

Apply the systems-thinking iceberg — events, patterns, systemic structures, mental models (and Daniel Kim's fifth level, vision) — to explain why a problem keeps happening and where to intervene. Draws on Peter Senge's The Fifth Discipline (levels of explanation, archetypes), Daniel Kim's Vision Deployment Matrix and archetype work, Donella Meadows' Thinking in Systems and twelve leverage points, Peter Stroh's Systems Thinking for Social Change, and Deming/Ackoff on the system producing the behaviour. Covers the questions and response mode at each level, causal loops and delays, the archetypes

5 stars 2 forksDevOps & Cloud Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill systems-thinking-iceberg
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/systems-thinking-iceberg ~/.claude/skills/systems-thinking-iceberg

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Systems Thinking Iceberg

Apply this skill when someone is about to fix a visible problem — an outage, a missed date, a process breach, a team "not following the process" — or is proposing a process, policy or reorganisation meant to stop one. The iceberg asks *which level the problem lives at* and *which level the proposed fix acts on*. Most fixes act on events; most problems live in structure and mental models.

## Core Philosophy

**The system produces the behaviour.** Senge: "structure influences behaviour". Deming: most variation in outcome comes from the system, not the worker. Put different people into the same structure and you get much the same results (the beer game). Blaming people for a recurring event is a sign the analysis stopped at the waterline.

**Leverage rises with depth.** Responding to an event changes one event. Changing a structure changes every future event it would have produced. Shifting a mental model changes which structures people build in the first place. Depth also costs more and takes longer — so the skill is choosing the right level, not always the deepest.

**Structure means more than the org chart.** In systems thinking, structure is what generates a pattern: feedback loops, delays, stocks and flows, incentives, rules, information flows, physical and digital layout, who decides what. A form, a metric, an approval step, a budget cycle and a dashboard are all structure.
Read the full skill on GitHub

Details

Skill name
systems-thinking-iceberg
Path
plugins/engineering-practices/skills/systems-thinking-iceberg/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Systems Thinking Iceberg skill do?

Apply the systems-thinking iceberg — events, patterns, systemic structures, mental models (and Daniel Kim's fifth level, vision) — to explain why a problem keeps happening and where to intervene. Draws on Peter Senge's The Fifth Discipline (levels of explanation, archetypes), Daniel Kim's Vision Deployment Matrix and archetype work, Donella Meadows' Thinking in Systems and twelve leverage points, Peter Stroh's Systems Thinking for Social Change, and Deming/Ackoff on the system producing the behaviour. Covers the questions and response mode at each level, causal loops and delays, the archetypes

How do I install the Systems Thinking Iceberg skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Systems Thinking Iceberg popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Tailscale Manager

8

Freddy-CHEN-ux/00_claude_skills

Manage Tailscale funnels across different ct project instances. Start/stop funnels and route traffic to different docker containers.

DevOps & Cloud

Ops Devops Platform

8

Freddy-CHEN-ux/00_claude_skills

Production-grade DevOps and platform engineering patterns: Kubernetes, Terraform, containers, GitOps, CI/CD, observability, incident response, security hardening, and cloud-native operations (AWS, GCP, Azure, Kafka).

DevOps & Cloud

Tech Readiness Review

5

eshmith7/claude-skills-library

Review a service against blast radius, observability, failure handling, rollback and ownership, and separate real blockers from debt. Use for production or launch readiness.

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.