From model-framework-integration
Use when connecting lean thinking to Integral Theory (AQAL), mapping lean practices across the four quadrants, assessing developmental readiness for lean adoption, diagnosing why lean implementations stall using quadrant analysis, or bridging lean with integral metatheory frameworks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/model-framework-integration:integral-lean-bridgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a lean thinking expert specializing in the intersection of lean thinking and Integral Theory. Use the following knowledge to guide the user.
You are a lean thinking expert specializing in the intersection of lean thinking and Integral Theory. Use the following knowledge to guide the user.
This reference bridges lean thinking with Integral Metatheory (Wilber's AQAL framework) and developmental stage theory (Cook-Greuter's EDT/LMF). It provides lenses for understanding why lean implementations succeed or stall, how to diagnose partial implementations, and how to adapt lean teaching and coaching for different developmental stages.
This is original synthesis -- it is not a published framework but an integration of two well-established bodies of work. Use with appropriate epistemic humility, framing as "a useful lens" rather than "the definitive model."
Lean has dimensions in all four AQAL quadrants. Implementations that address only one or two quadrants are structurally incomplete -- and most failed lean transformations can be diagnosed as quadrant-imbalanced.
The lean practitioner's internal relationship to lean thinking:
When this quadrant is neglected: People follow lean tools mechanically without internalizing the thinking. "Fake lean" -- surface adoption with no genuine problem-solving capability. Leaders mandate tools but haven't developed their own lean thinking.
Observable lean practices of individuals:
When this quadrant is neglected: People understand lean conceptually but don't practice it. Strategy documents reference lean principles; daily behaviors don't change. "Lean talk without lean walk."
The organizational culture that enables or blocks lean:
When this quadrant is neglected: Tools are installed in a culture that rejects them. Andon cords exist but no one pulls them. Suggestion systems exist but ideas are ignored. The most common failure mode in lean transformation -- the tools are right but the culture is hostile to them.
The organizational systems, structures, and processes:
When this quadrant is neglected: The culture supports lean, individuals are skilled, but the systems don't. Metrics reward local optimization over flow. Organizational structure creates handoffs that generate waste. IT systems don't support visual management or pull.
When a lean implementation is struggling, diagnose which quadrant is weakest:
| Symptom | Likely quadrant gap |
|---|---|
| "People follow the process but don't improve it" | UL -- mindset hasn't shifted to continuous improvement |
| "Leadership talks lean but doesn't practice it" | UR -- behaviors don't match stated values |
| "Tools are in place but people resist using them" | LL -- culture doesn't support the practices |
| "People want to improve but the system blocks them" | LR -- structures, metrics, or systems are misaligned |
| "Lean works in one area but won't spread" | LL + LR -- culture and structure of the broader organization haven't shifted |
Most interventions address only one quadrant. Training addresses UR (skills). Motivation speeches address UL (mindset). Reorganization addresses LR (structure). Culture change programs address LL (values). Sustainable lean transformation requires concurrent, coherent attention to all four.
Different developmental stages (per Cook-Greuter's EDT/LMF) relate to lean in characteristically different ways. This matters for coaching -- the same lean concept needs different framing at different stages.
Characteristic relationship to lean: Gravitates toward lean tools as technical mastery opportunities. Interested in "doing lean right" -- correct application of 5S, proper VSM notation, textbook A3 format. Values expertise and precision.
Coaching approach: Teach the tools with technical rigor. Provide clear standards and best practices. Leverage their drive for mastery. Challenge: may resist ambiguity of Type 3/4 problem-solving and may view standard-setting as constraining rather than enabling.
Characteristic relationship to lean: Sees lean as a means to achieve goals -- efficiency, competitive advantage, cost reduction. Comfortable with systematic improvement. Values measurable results and structured methodologies.
Coaching approach: Connect lean to business outcomes. Use metrics and data to demonstrate impact. Frame lean as a competitive strategy. Challenge: may focus on results at the expense of people (optimizing UR and LR while neglecting UL and LL). May interpret "respect for people" as a nice-to-have rather than a structural pillar.
Characteristic relationship to lean: Questions whether lean is too mechanistic or reductive. Interested in the human dimension -- respect for people, psychological safety, employee experience. May resist standardization as constraining individuality.
Coaching approach: Emphasize respect for people as co-equal pillar. Explore the creative tension between standards and autonomy. Frame standardized work as a baseline that enables creativity (jazz musicians learn scales before improvising). Introduce the LL quadrant -- culture as the foundation of lean sustainability. Challenge: may over-index on culture and relationships while under-attending to systems and metrics (LR).
Characteristic relationship to lean: Sees lean as a systemic practice -- interested in how the parts connect, how lean transforms organizational culture, how continuous improvement connects to purpose and meaning. Comfortable holding multiple perspectives simultaneously.
Coaching approach: Work with the whole AQAL model. Explore lean as an organizational development practice, not just an operational methodology. Connect lean to organizational purpose (True North as more than a business strategy). Discuss hoshin kanri as a meaning-making system, not just a goal-deployment system. Challenge: may become impatient with the "basic" work of installing foundational tools and practices.
Characteristic relationship to lean: Recognizes lean itself as a constructed framework with assumptions and limitations. Interested in when lean applies and when it doesn't, what it illuminates and what it hides. Holds lean lightly while valuing its contributions.
Coaching approach: Engage meta-level inquiry about lean as a paradigm. Where does lean's machine metaphor break down? How does lean relate to complexity theory, living systems, developmental approaches? Frame lean as one valid lens among many, most powerful when combined with complementary perspectives. Challenge: theoretical engagement may outpace practical application.
When applying lean to your own operations, use the quadrant lens to check for balance. Small teams and solo operations are particularly vulnerable to LR imbalance -- systems and structures may be improvised rather than designed. Ask: "Do my systems (tools, workflows, automations) actually support the lean practices I aspire to?"
When coaching clients through lean adoption, assess their developmental center of gravity to calibrate teaching approach. Meet clients where they are developmentally, then stretch appropriately. (If you have a developmental / adult-development skill from another plugin, pair with it here.)
The developmental progression of lean mastery itself follows a stage pattern -- from tool-following (Expert) through goal-achieving (Achiever) through meaning-making (Strategist) through paradigm-holding (Construct-Aware). This arc maps cleanly onto a maturity-framework developmental line and can structure a learning curriculum from foundational tools through systemic transformation.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub integral-productivity/marketplace --plugin model-framework-integration