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:

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 — the strategic thinking framework that underpins this skill.