Qcd Issue Tree Production Analysis logo

Qcd Issue Tree Production Analysis

Community
MichaelRochonnn
qcd-issue-tree-production-analysis

Use the QCD (Quality, Cost, Delivery) Issue Tree framework to analyze production site issues and evaluate new production technology. Apply when analyzing manufacturing challenges, introducing automation/robots, or identifying operational bottlenecks. This framework helps identify critical blind spots, particularly Delivery Speed, which is often overlooked by HQ experts.

Overview

PublisherMichaelRochonnn
Repositorymckinsey-bcg-consulting
Skill nameqcd-issue-tree-production-analysis
Stars
77
Forks
16
Bundled files
Instructions only
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 MichaelRochonnn on GitHub. Read the source before you install it.

Installation

Install the Qcd Issue Tree Production Analysis 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/MichaelRochonnn/mckinsey-bcg-consulting/tree/main/qcd-issue-tree-production-analysis
  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/MichaelRochonnn/mckinsey-bcg-consulting.git /tmp/mckinsey-bcg-consulting
mkdir -p .claude/skills
cp -r /tmp/mckinsey-bcg-consulting/qcd-issue-tree-production-analysis .claude/skills/qcd-issue-tree-production-analysis
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Qcd Issue Tree Production Analysis 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 Qcd Issue Tree Production Analysis 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 Qcd Issue Tree Production Analysis 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.

QCD Issue Tree for Production Analysis

When to Use This Skill

Use this skill when:

  • Analyzing production site issues or operational challenges
  • Evaluating new production technology or automation (e.g., introducing robots)
  • Identifying bottlenecks in manufacturing processes
  • Balancing competing priorities between HQ and site teams
  • Investigating why production improvements aren't translating to sales

Prerequisites

Before applying this framework, ensure you have:

  • A production site or process to analyze
  • A specific operational challenge or improvement initiative
  • Access to production data and site personnel input
  • Safety measures already established (safety is always the first priority)

The QCD Framework

The QCD framework evaluates production decisions across three interdependent criteria:

  1. Quality (Q): Can quality be maintained or improved?

    • Often the primary focus of site experts
    • Directly impacts customer satisfaction and brand reputation
  2. Cost (C): Will costs decrease?

    • Often the primary focus of HQ experts
    • Includes direct costs and hidden costs (time spent on fixes)
  3. Delivery (D): Can production stabilize quickly?

    • Often the overlooked blind spot
    • Critical for meeting customer demand and cash flow

Execution Steps

Step 1: Establish Safety First

  • Confirm all safety protocols are in place
  • Safety must be ensured before any other consideration
  • Do not proceed if safety is compromised

Step 2: Evaluate the Three Core Criteria

For each production decision or challenge, assess:

Cost Analysis:

  • Will this reduce direct production costs?
  • What are the implementation costs?
  • Consider both short-term and long-term cost implications

Quality Analysis:

  • Can current quality levels be maintained?
  • Will quality improve or degrade?
  • What are the quality risks and mitigation strategies?

Delivery Analysis:

  • How quickly can production stabilize?
  • What is the time-to-stable-production?
  • Will delivery timelines be impacted during transition?

Step 3: Analyze Interdependence

Recognize that QCD criteria are not independent:

  • Quality issues directly cause sales to drop
  • Delivery delays directly cause sales to drop
  • Time spent improving Quality or fixing Delivery delays IS a Cost
  • Cost-cutting that harms Quality or Delivery creates hidden costs

Step 4: Focus on the Blind Spot (Delivery Speed)

Identify which perspective is dominating the analysis:

HQ Expert Bias:

  • Typically focuses primarily on Cost
  • May underestimate time-to-stability
  • May overlook production disruption risks

Site Expert Bias:

  • Typically focuses on Quality and Delivery
  • May resist necessary cost optimizations
  • May have local optimization blind spots

Strategic Insight:

  • Delivery Speed (time to stabilize production) is often the critical bottleneck
  • Example: Tesla's robot production struggles were fundamentally a Delivery Speed issue
  • Stabilization time determines when ROI actually begins

Step 5: Break Down Sub-Issues

For Delivery Speed analysis, decompose into two series:

Human Series (Skills Acquisition):

  • How long does it take workers to master new processes?
  • What training is required?
  • What is the learning curve duration?

Tool Series (Stabilization Frameworks):

  • What frameworks exist to accelerate stabilization?
  • Are there standardized procedures?
  • What tools or automation can reduce variability?

Output

This analysis produces:

  1. Identification of the critical bottleneck (often Delivery Speed)
  2. Understanding of trade-offs between Q, C, and D
  3. A plan to address Human vs. Tool constraints
  4. Strategic focus on the most impactful improvement area

Key Insight

The essence of many production problems is not Cost or Quality, but Delivery Speed—the time required to stabilize new production processes. This is the blind spot that often determines project success or failure.

Frequently asked questions

What does the Qcd Issue Tree Production Analysis AI skill do?

Use the QCD (Quality, Cost, Delivery) Issue Tree framework to analyze production site issues and evaluate new production technology. Apply when analyzing manufacturing challenges, introducing automation/robots, or identifying operational bottlenecks. This framework helps identify critical blind spots, particularly Delivery Speed, which is often overlooked by HQ experts.

Why use Qcd Issue Tree Production Analysis on TypingMind?

Because you install it once and use it with any model. Qcd Issue Tree Production Analysis 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 Qcd Issue Tree Production Analysis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/MichaelRochonnn/mckinsey-bcg-consulting/tree/main/qcd-issue-tree-production-analysis. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Qcd Issue Tree Production Analysis?

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 Qcd Issue Tree Production Analysis?

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

Is the Qcd Issue Tree Production Analysis AI skill free?

It is published on GitHub by MichaelRochonnn. Check the repository for licensing terms. 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 👇