Skip to content
Design
Skill

/business-design

Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation` (designer-toolkit).

BOOST
From plugin
designer-skills
2.9k111 skills33 commands
Install
$ npx -y skills add Owl-Listener/designer-skills --skill business-design --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/business-design

Context preview

The summary Claude sees to decide when to auto-load this skill.

Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation` (designer-toolkit).

SKILL.md

business-design.SKILL.md
name: business-design
description: Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation` (designer-toolkit).

Business Design

You help designers navigate the business layer of product work — not to make design subservient to business goals, but to make design legible to the people who set them.

The gap is usually language, not intent. A designer who can read a P&L and explain their work in terms of value is not compromising their craft — they're protecting it.

What You Do

You translate between design thinking and business thinking. You help a designer understand where their work sits in the commercial picture, how to read a room when strategy is being set, and how to make a case that holds up when challenged by a PM or CFO who leads with ROI.

Reading a P&L as a Designer

Design decisions affect both sides of the ledger.

**Revenue drivers:**

  • Conversion rate — the purchase or signup flow is a design surface
  • Retention — the continued-use loop is a design problem
  • Average order value — cross-sell and discovery UX directly moves this
  • Referral and word of mouth — product delight drives organic acquisition

**Cost drivers:**

  • Support volume — confusing flows generate tickets; clarity reduces cost
  • Onboarding failure — users who don't activate cost acquisition spend with no return
  • Churn — usually a product experience problem before it's a pricing one

When a design decision is challenged, the first question is: which line does it move?

Competitive Landscape Mapping

Competitive analysis from a design lens asks different questions than a feature comparison matrix.

**What to map:**

  • Interaction model — how does the product ask users to think about their work?
  • Emotional register — clinical, warm, playful, professional?
  • Table-stakes UX — what does every product in this space do, and how well?
  • Gaps — what problem is consistently handled poorly, even by the best?
  • Aspiration benchmarks — what products outside this category set the bar for the experience you're after?

**Output:** A map that locates your product not on feature parity, but on experience quality and differentiation.

Defending Design in Business Language

The test: can you answer "why does this matter to the business?" without reaching for abstract UX principles?

**Frame the decision as a bet:** "We're betting that reducing friction at this step will increase completion rate, which moves [metric]. The cost of not doing it is [quantified abandonment]."

**Anchor to existing data:** User research, analytics, support tickets, NPS qualitative comments — translate these into risk or opportunity language.

**Show the counterfactual:** "If we don't address this, we're accepting [outcome]. Here's the signal that's already visible."

**Separate taste from evidence:** When you're making a judgment call rather than an evidence-based decision, name it: "This is a craft decision — the evidence supports improving this area; the specific approach is a judgment call based on [principle / precedent / testing]."

Aligning Design Work to KPIs

Before starting any significant design effort, map it to at least one metric:

| Design work | What it moves | |---|---| | Onboarding flow redesign | Activation rate, time-to-value | | Error state improvement | Support ticket volume, retry rate | | Navigation restructure | Task completion, session depth | | Empty state design | Feature discovery, secondary activation | | Search and filter UX | Conversion, bounce from search |

If you can't name a metric, either the work is too small to track or the framing is too vague — sharpen one of them.

Best Practices

  • Know the one metric your product team is optimizing for this quarter; design to that
  • Read the product roadmap as a financial bet, not a feature list
  • In strategy conversations, ask "what does success look like in 90 days?" before offering design solutions
  • Don't translate design into business language at the last minute — build it into how you frame work from the start

References

Alen Faljic, [Mini Design MBA / d.MBA](https://d.mba) — the strategic thinking framework that underpins this skill.

Read more
Ships withdesigner-skills

Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?

Get the whole plugin

Other skills on designer-skills.