Identifies five of the expert's own BMC-work antipatterns (e.g. too much content per block, too deep too early, canvas as a strategy document) and four of the most common client misunderstandings about the BMC's role, and offers direct corrective moves for each.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add Pilot2Service/AI-Business-Designer --skill bmc-antipattern-and-misunderstanding-correction --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Bmc Antipattern And Misunderstanding Correction?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/pilot2service-bmc-antipattern-and-misunderstanding-correction)More formats (shields.io, HTML) on the badges page.
---
name: bmc-antipattern-and-misunderstanding-correction
description: "Identifies five of the expert's own BMC-work antipatterns (e.g. too much content per block, too deep too early, canvas as a strategy document) and four of the most common client misunderstandings about the BMC's role, and offers direct corrective moves for each."
---
# BMC Antipattern and Misunderstanding Correction
## Purpose
Quickly recognizes when BMC work is going wrong — either in how the work
is being done (antipatterns), or in what the client/team assumes the BMC
will do for them (misunderstandings) — and offers the expert's own, direct
corrective moves for each. This is a diagnostic and corrective skill: use
it mid-session, when something feels stuck.
## Anchored in
- The owner's April 2026 expert interview,
two `status: accepted` / `confidence: high` files in the owner's
research notes:
- `30_domain_packs/bmc/antipatterns/bmc_antipatterns_expert.md` — five
of the expert's own antipatterns.
- `30_domain_packs/bmc/facilitation/bmc_client_misunderstandings.md` —
four of the most common client misunderstandings about the BMC's role.
## Method
### A. Five antipatterns — recognize them in how the work is done
1. **Too much content per block.** Sign: several revenue streams,
segments, or channels "active" at the same time. Consequence: clarity
is lost, no coherent path emerges (focus segment → focus channel →
focus value proposition → focus revenue streams). **Fix:** force
choices. One segment, one channel, clear revenue streams. Extra
options → a new variant, not an addition to the same canvas.
2. **Too deep too early.** Sign: the team invests heavily in polishing
one canvas before producing variants. Consequence: no variants get
produced, the canvas stays "multi-option" instead of sharpening.
**Fix:** enforce a sprint structure, a time limit per phase — see
`../bmc-canvas-clarity-and-iteration/SKILL.md`.
3. **Canvas as a strategy document.** Sign: the team treats the canvas
as a final strategy or planning document, not an iteration tool.
Consequence: over-polishing individual word choices instead of
searching for the unique combination. **Fix:** remind them of the
role — the BMC is a thinking and innovation tool, not a plan.
4. **Starting from the left side.** Sign: the session starts from key
activities / key resources / key partners. Consequence: the canvas
builds up around production logic rather than customer logic; the
value proposition ends up disconnected. **Fix:** always start on the
right: customer → problem → solution → value proposition → revenue
streams → left side.
5. **One canvas is enough.** Sign: the team produces one canvas and
considers the work done. Consequence: no basis for comparison,
innovation patterns can't be identified from a single canvas.
**Fix:** at least 2-3 variants before the analysis and synthesis
phase — see `../bmc-canvas-clarity-and-iteration/SKILL.md`.
### B. Four client misunderstandings — recognize them in what's said
1. **"This could define everything at once."** The client is thinking:
the BMC is the key to everything — filling it in once produces a
finished business plan. Reality: the BMC is primarily a thinking tool.
It doesn't replace more precise planning tools. **Response:** walk
through the BMC's role as a thinking and innovation tool — not a
planning deliverable.
2. **Too deep too early (the client's version).** The client tries to
produce a perfect canvas on the first attempt. Consequences: no time
for variants, clarity is lost, no focus anywhere. **Response:** the
work needs to be iterative and fast. Light first, vary, then go deeper.
3. **Canvas = a complete business planning tool.** The client expects the
BMC to be enough for all their planning. Reality: once the business
model has been innovated, more precise product specifications,
profitability and growth-margin scenarios, and other more precise
tools follow the BMC. The BMC is no longer the optimal tool once the
innovation decision has been made. **Response:** see
`../bmc-tool-switching-decisions/SKILL.md` for what comes next.
4. **One canvas is enough (the client's version).** Reality: value comes
from variants and comparing them, not from a single canvas. One
canvas → one business model. Value emerges once there are 2-3
variants → they can be analyzed, scenario-tested, synthesized.
## Gotchas
- Antipatterns 2 and 5 (too deep too early, one canvas is enough) are named
here but actually fixed by `../bmc-canvas-clarity-and-iteration/SKILL.md`'s
variation mechanics — diagnosing the antipattern without switching to that
skill's sprint structure and 2-3 variant minimum just re-describes the
problem instead of solving it.
- Antipattern 3 ("canvas as a strategy document") and misunderstanding 1
("this could define everything at once") sound almost identical but target
different audiences — the working team's behavior vs. the client's belief
about what the BMC delivers. Misreading which one you're facing means
offering a facilitation nudge when a role explanation was needed, or vice
versa.
- Misunderstanding 3 (canvas = complete planning tool) points the fix to
`../bmc-tool-switching-decisions/SKILL.md`, but this skill doesn't itself
say WHEN that handoff should happen — naming the misunderstanding without
pairing it with the actual switching criteria leaves the client's real
question ("what do I do next?") unanswered.
- This is explicitly a 5+4 list from the expert's own practice, not an
exhaustive taxonomy — a session that's stuck for a reason that doesn't
match any of these nine patterns needs a different diagnosis, not a forced
fit into the nearest-sounding antipattern.
## What this skill does NOT do
- Doesn't replace the actual variation process — see
`../bmc-canvas-clarity-and-iteration/SKILL.md` for the concrete
iteration mechanics. This skill is a detection-and-correction toolkit,
not a process guide.
- Doesn't cover a canvas's internal diagnostics (Hook Rule, evidence
grade, etc.) — see `../bmc-canvas-diagnostic-reading/SKILL.md`. The
antipatterns in this skill concern WORKING METHOD and CLIENT
EXPECTATIONS, not the content quality of a finished canvas.
- Isn't an exhaustive list of every possible mistake — these 5+4 are the
most common ones that have come up in the expert's own practice, not a
comprehensive taxonomy.
## Continue from here
- Related skill in the same pack:
`../bmc-canvas-clarity-and-iteration/SKILL.md` — antipatterns 2 and 5
are corrected directly by this skill's variation logic.
- Related skill in the same pack:
`../bmc-canvas-diagnostic-reading/SKILL.md` — once the canvas is
finished, a more precise reading of internal consistency.
- Related skill in the same pack:
`../bmc-tool-switching-decisions/SKILL.md` — the fix for
misunderstanding 3, when the BMC is no longer the right tool.
- This pack's shared guardrails: `../../CLAUDE.md`
## References
- `../../references/bmc-source-material-notes.md` — source material background
- `../../CLAUDE.md` — this pack's shared guardrails
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!