Kendal Framework: Core defention

[MrHinsh]

Here is a clear, concise core definition of the Kendall Framework, distilled directly from the workshop content and expressed in a practical way you can use to teach others. I need to add this to my Kendall guide, and weave any changes to the content as needed.

---

Core Definition of the Kendall Framework

The Kendall Framework is a practical, operations-first approach to enterprise AI that helps organisations build reliable AI capability by mastering three foundations before creating solutions: AI Literacy, User Needs, and AI Operations.

It teaches teams to

1. understand how AI works and how language drives quality (AI Literacy),
2. identify real problems grounded in user needs rather than ideas or technology hype (User Needs / Problem Curation),
3. and build predictable, low-variation AI systems through structured context, clear rules, and modular components (AI Operations).

The framework is built on proven disciplines including TQM, Lean, Agile, Scrum, Lean Startup, Design Thinking, and Problem Curation. It applies their principles to AI so organisations can solve the problems they actually have, not chase theoretical opportunities.

At its core, Kendall is about reducing variation, increasing clarity, and building AI that works in the real world, using structured context, defined roles, and continuous improvement.

---

One-Sentence Version

The Kendall Framework gives organisations a disciplined way to succeed with AI by building literacy, clarifying real problems, and operating AI with structured context, rules, and modular components before attempting AI solutions or agents.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

✅ Successfully generated implementation plan.

💡 Use @coderabbitai <feedback> to replan

Examples

• Example 1
• Example 2

🔗 Similar Issues

Possible Duplicates

• nkdAgility/NKDAgility.com#699

Related Issues

• nkdAgility/NKDAgility.com#701
• nkdAgility/NKDAgility.com#696
• nkdAgility/NKDAgility.com#568

👤 Suggested Assignees

• MrHinsh

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[coderabbitai]

Implementation Plan

Approach

Add a new core definition emphasizing three foundations (AI Literacy, User Needs, AI Operations) to the Kendall Framework guide, and weave changes throughout the existing content to prominently feature proven disciplines (TQM, Lean, Agile, Scrum, Lean Startup, Design Thinking, Problem Curation) while maintaining the guide's established structure.

Observations

The site is built with Hugo static site generator, with content organized in site/content/ directories by type. The Kendall guide lives at site/content/resources/guides/kendall-guide/index.md and follows the standard framework guide pattern (Definition → Principles → Accountabilities → Artifacts) seen in other guides like Scrum and Kanban. The guide is self-contained markdown with Hugo front matter, currently spans 8 main sections, and is referenced by the AI Opportunity Discovery capability page. Currently, the guide mentions "Lean" three times but lacks explicit references to other proven disciplines.

Assumptions

Assumption 1: How to present the three foundations (AI Literacy, User Needs, AI Operations)

Options Considered:

• Create dedicated top-level sections for each foundation and reorganize all content under them
• Add a single "Three Foundations" section that explains the concept, then map existing sections to these foundations through cross-references and enhancements

Chosen Option: Add a single "Three Foundations" section that explains the concept, then map existing sections to these foundations through cross-references and enhancements

Rationale: Add a dedicated "Three Foundations" section after the core definition that clearly explains each foundation, then enhance existing sections (First Principles, Accountabilities, Artifacts) to show how they support the foundations. This preserves the established guide structure pattern (consistent with Scrum/Kanban guides), avoids breaking existing references, and feels like a natural evolution rather than a complete restructure. Developers working with the codebase will find this approach more predictable.

Assumption 2: How prominently to weave proven disciplines throughout the guide

Options Considered:

• Add a dedicated "Proven Disciplines" section explaining each discipline
• Weave discipline references organically throughout existing sections where they naturally apply

Chosen Option: Weave discipline references organically throughout existing sections where they naturally apply

Rationale: Weave discipline references organically throughout existing sections rather than creating a separate disciplines section. This approach creates a more cohesive reading experience where disciplines are introduced in context (e.g., mentioning TQM when discussing variation reduction, Scrum when discussing accountabilities, Design Thinking when discussing problem curation). This feels more natural to readers and avoids making the guide feel like a catalog of methodologies.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Plan

Phase 1: Core Definition & Three Foundations

Establish the new core definition and introduce the three-foundation structure that will organize the rest of the guide's enhancements.

Task 1: Replace Purpose & Definition Section

Update the opening definition of the Kendall Framework to emphasize the operations-first approach and three foundations.

• Replace the existing "Purpose & Definition" section (lines 51-55) in site/content/resources/guides/kendall-guide/index.md with the new core definition provided in the ticket
• Position this as the primary "## Kendall Framework Purpose & Definition" section
• Include both the full paragraph and the one-sentence version as a TL;DR at the end of the section
• Ensure the tone remains consistent with the rest of the guide (practical, direct, actionable)

Task 2: Add Three Foundations Section

Create a new section immediately after the core definition that explains each foundation in detail.

• Insert new "## The Three Foundations" section after the core definition in site/content/resources/guides/kendall-guide/index.md
• Create three subsections (### AI Literacy, ### User Needs, ### AI Operations) that expand on what each foundation means and why it's essential
• For AI Literacy: Explain how understanding AI mechanics and language quality prevents failed implementations
• For User Needs: Describe problem curation practices and how to identify real problems versus technology-driven ideas
• For AI Operations: Detail how structured context, clear rules, and modular components create predictable systems
• Link each foundation to the disciplines that inform it (e.g., Design Thinking and Problem Curation for User Needs, Lean and TQM for AI Operations)

Task 3: Update Application Section

Revise the Application section to reference the three foundations as prerequisites.

• Modify the "## Kendall Application" section (lines 56-60) in site/content/resources/guides/kendall-guide/index.md
• Add language explaining that organizations benefit most when they commit to mastering the three foundations sequentially
• Emphasize that the framework is particularly valuable for organizations seeking to move beyond experimental AI to production-grade systems
• Maintain the existing applicability statements (organisations, teams, entrepreneurs, governments) while adding foundation-focused context

🤖 Prompt for AI agents

This phase establishes the new core definition and introduces the
three-foundation structure (AI Literacy, User Needs, AI Operations) that will
organize the guide's enhancements.

In `site/content/resources/guides/kendall-guide/index.md`:
- Replace the existing "Purpose & Definition" section with the new core
definition emphasizing the operations-first approach and three foundations
(include both full paragraph and one-sentence TL;DR)
- Insert a new "## The Three Foundations" section after the core definition with
three subsections (### AI Literacy, ### User Needs, ### AI Operations)
explaining what each foundation means and why it's essential, linking each to
relevant disciplines
- Update the "## Kendall Application" section to reference the three foundations
as prerequisites for mastering the framework, emphasizing value for
production-grade AI systems while maintaining existing applicability statements

Phase 2: Map Existing Content to Foundations

Connect the guide's existing First Principles and operational mechanics to the three foundations, showing how proven disciplines are applied.

Task 1: Enhance First Principles with Foundation Mapping

Show how each of the nine existing First Principles supports one or more of the three foundations.

• Update the "## First Principles" section (lines 61-73) in site/content/resources/guides/kendall-guide/index.md
• Add a brief introductory paragraph explaining that these principles draw from proven disciplines (TQM, Lean, Agile) and operationalize the three foundations
• For each principle, add a parenthetical or brief note indicating which foundation(s) it primarily supports:
  • Problem Before Solution → User Needs
  • Context Creates Meaning → AI Literacy + AI Operations
  • Pull Context at the Rate of Demand → AI Operations (Lean)
  • Clarity of Language → AI Literacy (TQM/variation reduction)
  • Accountability Anchored in Stakeholders → User Needs (Scrum/Agile)
  • Boundaries Enable Trust → AI Operations
  • Structure Builds Reliability → AI Operations (TQM)
  • Collaboration Sustains Value → User Needs (Agile)
  • Continuous Improvement → AI Operations (Lean, Scrum)
• Add brief discipline references in the principle descriptions where they naturally fit

Task 2: Revise How It Works Section

Update the operational mechanics description to show how the framework operationalizes the three foundations.

• Modify the "## How It Works" section (lines 75-84) in site/content/resources/guides/kendall-guide/index.md
• Restructure to explicitly connect the six operational mechanics to the three foundations
• Add references to Lean Startup (Build-Measure-Learn cycles), Scrum (sprint-like discovery cadence), and Lean (pull-based flow)
• Emphasize how the mechanics reduce variation and increase clarity (TQM principles)
• Maintain the existing six mechanics (Problem-First, Role of Context, Pull-Based Flow, Collaboration, Iteration, Discovery Cadence) while showing their foundation alignments

🤖 Prompt for AI agents

This phase connects the guide's existing First Principles and operational
mechanics to the three foundations, showing how proven disciplines are applied.

In `site/content/resources/guides/kendall-guide/index.md`:
- Enhance the "## First Principles" section with an introductory paragraph
explaining these principles draw from proven disciplines (TQM, Lean, Agile) and
operationalize the three foundations
- Add foundation mappings to each of the nine principles (e.g., Problem Before
Solution → User Needs, Context Creates Meaning → AI Literacy + AI Operations)
with discipline references where applicable
- Revise the "## How It Works" section to explicitly connect the six operational
mechanics to the three foundations, add references to Lean Startup, Scrum, and
Lean, and emphasize variation reduction and clarity (TQM principles) while
maintaining existing mechanics

Phase 3: Accountability & Artifact Alignment

Connect the framework's roles and artifacts to the three foundations, showing how each accountability contributes to building capabilities.

Task 1: Update Accountabilities with Foundation Contributions

Enhance each accountability role description to show how it contributes to one or more foundations.

• Modify the "## Kendall Accountabilities" section (lines 86-179) in site/content/resources/guides/kendall-guide/index.md
• Add a brief section introduction explaining that the accountability structure draws from Scrum and Agile practices adapted for AI contexts
• For each of the six accountabilities, add a "Contributes to:" statement showing which foundation(s) the role primarily serves:
  • Kendall Coach → All three foundations (through mentorship and framework consistency)
  • Context Curator → AI Operations (context governance across domains)
  • Problem Owner → User Needs + AI Operations (domain-specific problem curation and solution deployment)
  • AI Lead → User Needs (opportunity backlog discipline, similar to Product Owner in Scrum)
  • Context Controller → AI Operations (context assembly and versioning)
  • Context Owner(s) → AI Operations (lean context management per instance)
• Enhance role descriptions with references to Scrum roles (where applicable) and Lean practices (pull-based thinking, waste reduction)

Task 2: Enhance Artifacts with Foundation Support

Show how each artifact supports specific foundations and embeds proven disciplines.

• Update the "## Artifacts" section (lines 198-210) in site/content/resources/guides/kendall-guide/index.md
• Add a section introduction noting that these artifacts apply Lean, Scrum, and Lean Startup practices to AI contexts
• For each of the three artifacts, enhance descriptions to show foundation alignment:
  • Opportunity Backlog → User Needs (problem prioritization inspired by Scrum Product Backlog and Lean Startup validation)
  • Context Repository → AI Operations + AI Literacy (structured context management using Lean principles and TQM variation reduction)
  • Roadmap → User Needs + AI Operations (strategic planning integrating Design Thinking outcomes)
• Add brief notes about how each artifact reduces variation, increases transparency, or enables pull-based flow

🤖 Prompt for AI agents

This phase connects the framework's roles and artifacts to the three
foundations, showing how each accountability contributes to building
capabilities.

In `site/content/resources/guides/kendall-guide/index.md`:
- Update the "## Kendall Accountabilities" section with an introduction
explaining the structure draws from Scrum and Agile practices adapted for AI
contexts
- Add "Contributes to:" statements to each of the six accountabilities showing
their foundation alignment (e.g., Kendall Coach → All three foundations, Context
Curator → AI Operations) with references to Scrum roles and Lean practices
- Enhance the "## Artifacts" section with an introduction about applying Lean,
Scrum, and Lean Startup practices to AI contexts
- Add foundation alignments to each of the three artifacts (Opportunity Backlog
→ User Needs, Context Repository → AI Operations + AI Literacy, Roadmap → User
Needs + AI Operations) with notes about variation reduction, transparency, and
pull-based flow

Phase 4: Events & Summary Integration

Update the Events and Summary sections to reinforce the three-foundation structure and proven disciplines.

Task 1: Update Events Section

Revise the Opportunity & Context Sourcing event description to show how it reinforces the foundations.

• Modify the "## Events" section (lines 180-197) in site/content/resources/guides/kendall-guide/index.md
• Add language explaining how the event embodies Scrum's inspect-and-adapt cycles and Lean Startup's Build-Measure-Learn approach
• Show how the event serves all three foundations: reviewing opportunities (User Needs), inspecting context quality (AI Literacy + AI Operations), and improving flow (AI Operations)
• Maintain the existing event structure while adding foundation-focused outcomes
• Reference how the quarterly/half-yearly cadence aligns with Agile planning cycles

Task 2: Rewrite Summary Section

Create a new summary that emphasizes the three foundations and proven disciplines as the guide's organizing concepts.

• Replace the existing "## Summary" section (lines 212-225) in site/content/resources/guides/kendall-guide/index.md
• Restructure to explicitly state that the framework helps organizations master the three foundations
• Emphasize how the framework applies proven disciplines (TQM, Lean, Agile, Scrum, Lean Startup, Design Thinking, Problem Curation) to AI
• Conclude with the core message: reducing variation, increasing clarity, and building AI that works in the real world
• Include a closing statement about mastering foundations before attempting AI solutions

Task 3: Update Front Matter

Revise the Hugo front matter to reflect the updated emphasis on three foundations and proven disciplines.

• Update the description field in the front matter of site/content/resources/guides/kendall-guide/index.md to mention the three foundations
• Update the tldr field to incorporate the one-sentence version from the new core definition
• Consider adding relevant tags if they don't already exist: "Problem Curation", "AI Literacy", "TQM", "Lean Startup"
• Verify that the weight field (430) maintains appropriate ordering relative to other guides
• Update lastmod date to reflect the revision

🤖 Prompt for AI agents

This phase updates the Events and Summary sections to reinforce the
three-foundation structure and proven disciplines, completing the guide
enhancements.

In `site/content/resources/guides/kendall-guide/index.md`:
- Update the "## Events" section to show how the Opportunity & Context Sourcing
event embodies Scrum's inspect-and-adapt cycles and Lean Startup's
Build-Measure-Learn approach, serving all three foundations (User Needs, AI
Literacy, AI Operations) while maintaining existing structure
- Replace the "## Summary" section with a new summary explicitly stating the
framework helps organizations master the three foundations by applying proven
disciplines (TQM, Lean, Agile, Scrum, Lean Startup, Design Thinking, Problem
Curation), concluding with reducing variation, increasing clarity, and building
real-world AI
- Update the Hugo front matter: modify `description` to mention three
foundations, update `tldr` with the one-sentence core definition, add relevant
tags (Problem Curation, AI Literacy, TQM, Lean Startup), verify `weight` field
(430), and update `lastmod` date

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

This phase establishes the new core definition and introduces the
three-foundation structure (AI Literacy, User Needs, AI Operations) that will
organize the guide's enhancements.

In `site/content/resources/guides/kendall-guide/index.md`:
- Replace the existing "Purpose & Definition" section with the new core
definition emphasizing the operations-first approach and three foundations
(include both full paragraph and one-sentence TL;DR)
- Insert a new "## The Three Foundations" section after the core definition with
three subsections (### AI Literacy, ### User Needs, ### AI Operations)
explaining what each foundation means and why it's essential, linking each to
relevant disciplines
- Update the "## Kendall Application" section to reference the three foundations
as prerequisites for mastering the framework, emphasizing value for
production-grade AI systems while maintaining existing applicability statements
===============================================================================

Task: 2

This phase connects the guide's existing First Principles and operational
mechanics to the three foundations, showing how proven disciplines are applied.

In `site/content/resources/guides/kendall-guide/index.md`:
- Enhance the "## First Principles" section with an introductory paragraph
explaining these principles draw from proven disciplines (TQM, Lean, Agile) and
operationalize the three foundations
- Add foundation mappings to each of the nine principles (e.g., Problem Before
Solution → User Needs, Context Creates Meaning → AI Literacy + AI Operations)
with discipline references where applicable
- Revise the "## How It Works" section to explicitly connect the six operational
mechanics to the three foundations, add references to Lean Startup, Scrum, and
Lean, and emphasize variation reduction and clarity (TQM principles) while
maintaining existing mechanics
===============================================================================

Task: 3

This phase connects the framework's roles and artifacts to the three
foundations, showing how each accountability contributes to building
capabilities.

In `site/content/resources/guides/kendall-guide/index.md`:
- Update the "## Kendall Accountabilities" section with an introduction
explaining the structure draws from Scrum and Agile practices adapted for AI
contexts
- Add "Contributes to:" statements to each of the six accountabilities showing
their foundation alignment (e.g., Kendall Coach → All three foundations, Context
Curator → AI Operations) with references to Scrum roles and Lean practices
- Enhance the "## Artifacts" section with an introduction about applying Lean,
Scrum, and Lean Startup practices to AI contexts
- Add foundation alignments to each of the three artifacts (Opportunity Backlog
→ User Needs, Context Repository → AI Operations + AI Literacy, Roadmap → User
Needs + AI Operations) with notes about variation reduction, transparency, and
pull-based flow
===============================================================================

Task: 4

This phase updates the Events and Summary sections to reinforce the
three-foundation structure and proven disciplines, completing the guide
enhancements.

In `site/content/resources/guides/kendall-guide/index.md`:
- Update the "## Events" section to show how the Opportunity & Context Sourcing
event embodies Scrum's inspect-and-adapt cycles and Lean Startup's
Build-Measure-Learn approach, serving all three foundations (User Needs, AI
Literacy, AI Operations) while maintaining existing structure
- Replace the "## Summary" section with a new summary explicitly stating the
framework helps organizations master the three foundations by applying proven
disciplines (TQM, Lean, Agile, Scrum, Lean Startup, Design Thinking, Problem
Curation), concluding with reducing variation, increasing clarity, and building
real-world AI
- Update the Hugo front matter: modify `description` to mention three
foundations, update `tldr` with the one-sentence core definition, add relevant
tags (Problem Curation, AI Literacy, TQM, Lean Startup), verify `weight` field
(430), and update `lastmod` date

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.