Table of Contents
- When business and design team stop fighting and start dating
- Why business and design make perfect partners
- The 10 ways to align business and design teams
- 1. Shared vision
- 💡 Pro tip for crafting killer vision statements:
- 2. Team alignment
- 💡 Pro tips for real alignment:
- 3. Financial literacy
- 💡 Pro tips for financial literacy without the MBA:
- 4. Data inspires design
- 💡 Pro tips for using data without losing your soul:
- 5. People-first approach
- 💡 Pro tips for putting people first while driving business results:
- 6. Get people in the same room
- 💡 Pro tips for productive cross-team gatherings:
- 7. Prioritise viability and experience
- 💡 Pro tips for nailing both viability and experience:
- 8. Define how both teams measure success
- 💡 Pro tips for creating shared success metrics:
- 9. Use creative thinking to solve business problems
- 💡 Pro tips for applying creative thinking to business challenges:
- 10. Create a culture where biz and design learn together
- 💡 Pro tips for creating collaborative learning:
- Your action plan (starting Monday)
- The happy ending (with actual results)
- The real job of design leadership
Do not index
Do not index
Read time: under 15 minutes
When business and design team stop fighting and start dating
Business and design often feel like coworkers from totally different planets.
One lives in spreadsheets and quarterly OKRs. The other lives in Figma files and sticky notes with feelings.
However, here’s what you should understand:
When business and design stop operating in silos and start building together, you don’t just get functional products. You get lovable, scalable, money-making machines that users actually want to use.
Whether you’re a design manager stuck between two feuding teams, or a business leader wondering why your product looks like a modern art piece… this guide will show you how to bring these forces together and create something everyone is proud of.
Let’s go!
Why business and design make perfect partners
Think of business and design like that couple you know who seem completely wrong for each other but somehow make it work.
- Business brings strategy → They know where the company needs to go
- Design brings compassion → They know how to get users to actually want to go there
- Business brings profit → They understand what keeps the lights on
- Design brings satisfaction → They understand what keeps users coming back
- Business brings stats → "Our conversion rate dropped 2.3%"
- Design brings emotion → "Users feel confused and frustrated in this flow"
- Business brings the 'where to' → "We need to capture the mobile market"
- Design brings the 'why now' → "Because users are shopping on their phones during their commute"
When these two forces combine, you don't just get better products. You get products that users love AND that make money. Revolutionary concept, I know 😮💨
Want to learn more about UX Management?
Check out UX Management Playbook — made for first-time managers building healthier and happier design teams.
The 10 ways to align business and design teams
Here's your playbook for turning these star-crossed lovers into a power couple:
1. Shared vision
Stop with the generic mission statements that sound like they were written by a motivational poster generator.
❌ Bad: We want to revolutionize the user experience while driving growth.
✅ Good: Help remote workers feel less isolated while increasing daily active usage by 25%.
Why this works: The good example has a specific user (remote workers), a specific problem (isolation), and a specific metric (25% usage increase). Both teams can rally around this.
💡 Pro tip for crafting killer vision statements:
- The "Mad Lib" method: Fill in the blanks: "Help [specific user] achieve [specific outcome] so they can [emotional benefit] while we [business metric]".
Example: "Help busy parents order healthy meals in under 90 seconds so they can spend dinner time with their kids while we increase average order value by 40%."
- The "Elevator test": Can someone explain your vision to a stranger in 30 seconds and have them actually understand what you're building? If not, simplify.
- The "Grandma test": Would your grandma understand what problem you're solving? If she'd respond with "that's nice, dear" while clearly having no clue, try again.
2. Team alignment
I once worked somewhere where the business team thought we were building for millennials and the design team was optimizing for Gen Z. Six months of mixed signals later, we'd built something that appealed to exactly nobody 😅
Fact: Most "alignment" meetings are just people nodding along while thinking completely different things.
💡 Pro tips for real alignment:
- Create a "Decisions document": Shared Google Doc where you log every major decision with date, reasoning, and who decided. When someone says, "I thought we decided X," you have receipts.
- Use the "5 whys" technique: When teams disagree, don't argue about the surface issue. Dig deeper. "Why do you think we need this feature?" Keep asking "why" until you get to the root assumption.
- The "Bet sizing" exercise: For every decision, have teams literally bet on outcomes. "I bet $50 that changing this button color will increase conversions." "I bet $20 it won't." Suddenly, everyone gets honest about their confidence levels.
- Monthly "Alignment health checks": Send a 3-question survey: 1) What's our top priority this month? 2) Who is our primary user? 3) What does success look like? If answers vary wildly, you have work to do.
3. Financial literacy
Look, I get it. You became a designer because you love creating things, not because you wanted to become an accountant. However, if you don't understand the business model, you can't design for business success.
Learn these acronyms or forever hold your peace:
- ARR (Annual Recurring Revenue): Predictable yearly income
- Churn Rate: Percentage of customers who leave each month
- MRR (Monthly Recurring Revenue): Predictable monthly income
- ARPU (Average Revenue Per User): How much each user brings in
- CAC (Customer Acquisition Cost): How much we spend to get one customer
- LTV (Lifetime Value): How much money one customer brings over their lifetime
Why this matters: When you understand that acquiring a customer costs $50 but they're only worth $30 over their lifetime, suddenly that "friction-free" signup flow makes business sense.
💡 Pro tips for financial literacy without the MBA:
- The "Coffee shop method": Spend 30 minutes monthly with someone from finance. Bring coffee. Ask dumb questions. "If we doubled our signup rate, what would happen to our costs?" They love explaining this stuff to people who actually listen.
- Create a "Business impact calculator": Simple spreadsheet that shows how design changes affect key metrics. "If we improve onboarding completion by 10%, that's X more activated users, which equals $Y in additional revenue."
- The "Unit economics game": Pick three design decisions you made recently. Calculate their impact on customer value and costs. Made signup easier? That might reduce CAC. Improved retention? That increases LTV.
- Shadow a sales call: Nothing teaches you business reality faster than hearing customers explain why they won't pay for your beautiful design.
- Monthly "Numbers and nonsense" sessions: Finance person explains one key metric. Design person explains how their work impacts it. Make it fun. Use analogies. "Think of churn rate like a leaky bucket..."
4. Data inspires design
Data tells you WHAT is happening. Design figures out WHY and HOW to fix it.
Example: Data says users are dropping off at step 3 of onboarding.
❌ Bad response: Move step 3 to step 1
✅ Good response: Understand why step 3 is confusing and redesign it
Think of data as your design detective work, not your design boss.
💡 Pro tips for using data without losing your soul:
- The "Data sandwich" method: Start with qualitative research (user interviews), add quantitative data (analytics), then finish with more qualitative insights (usability testing). Data is the meat, but insights are the bread.
- Ask "What story is the data telling?" Don't just report numbers. "Our bounce rate increased 15%" becomes "Users are arriving with different expectations than we're meeting."
- Create "Data + emotion" reports: For every metric, include a user quote that explains the human behind the number. "Cart abandonment increased 8%" + "I got frustrated because I couldn't figure out shipping costs."
- The "So what?" test: For any data point, ask "So what should we do about this?" If you can't answer, you need more context.
- Use the "Confidence meter": Rate your confidence in any data-driven conclusion from 1-10. Below 7? You need more investigation.
5. People-first approach
Here's where design thinking really shines. Instead of optimizing for abstract metrics, optimize for human outcomes that happen to drive business results.
Business thinking: "Increase session duration"
People-first thinking: "Help users accomplish their goals efficiently" (which might actually decrease session duration but increase satisfaction and retention)
Example: Google's homepage is famously simple because they realized people don't want to hang out on search pages—they want to find answers and get on with their lives.
💡 Pro tips for putting people first while driving business results:
- The "Human translation" exercise: For every business metric, write the human need it represents:
- Retention rate → "Do people find ongoing value?"
- Time on page → "Are people getting what they need?"
- Referral rate → "Are people excited enough to tell friends?"
- Conversion rate → "How quickly can we help people find value?"
- Use "Jobs to be done" thinking: People don't buy products; they hire them to do a job. Ask: "What job is our user trying to get done?" Then design for that job, not for your metrics.
- The "Empathy injection" method: In every business meeting, introduce one user story. "Sarah, our target user, is trying to X because Y, but she's struggling with Z". Make business decisions with real people in mind.
- Create "People-first metrics": Instead of just tracking behavior, track outcomes:
- Traditional: "Page views increased 20%"
- People-first: "Users found relevant content 20% faster"
- The "Grandma's advice" principle: If you can't explain why a business decision is good for users in language your grandma would understand, reconsider the decision.
Want to learn more about UX Management?
Check out UX Management Playbook — made for first-time managers building healthier and happier design teams.
6. Get people in the same room
Slack threads are not a substitute for actual human conversation. I don't care if you're fully remote, hybrid, or working from a coffee shop in Bali.
💡 Pro tips for productive cross-team gatherings:
- The "No slides" rule: Ban PowerPoint presentations. Use working sessions instead. Get people interacting with prototypes, sketching ideas, or discussing real customer feedback.
- Feed people. Seriously. Nothing builds collaboration like shared carbs.
- Remote teams: send everyone the same lunch.
- In-person teams: bring donuts. I'm not kidding about this.
- The "Rotation system": Design attends business planning meetings one month, business attends design critiques the next. Make it a regular rotation, not a special occasion.
- "Working lunch" learning sessions:
- Month 1: Business team teaches design about customer acquisition
- Month 2: Design team teaches business about user research
- Month 3: Joint session analyzing user feedback and business metrics
- Create "Cross-team buddies": Pair each designer with a business counterpart. They grab coffee monthly and share what they're working on. Relationships beat processes every time.
- The "Two-pizza Team" principle: If your meeting needs more than two pizzas to feed everyone, it's too big. Keep collaboration sessions small and focused.
7. Prioritise viability and experience
The best products nail both. Not one at the expense of the other. The three-circle test for every feature:
- Feasible: Can we build this?
- Desirable: Do users want this?
- Viable: Will this help our business?
All three need to be "yes" or you're wasting everyone's time.
💡 Pro tips for nailing both viability and experience:
- The "Trade-off transparency" method: When you must choose between UX and business needs, make the trade-offs explicit. "We're choosing faster implementation over optimal UX because we need to test market demand first."
- Use the "Iteration roadmap": Plan features in phases:
- Phase 1: Minimum viable experience (covers business needs)
- Phase 2: Improved experience (addresses UX issues)
- Phase 3: Delightful experience (exceeds expectations)
- The "Business case for UX" template: For every UX improvement, calculate business impact:
- "Improving this flow could reduce support tickets by 30%"
- "Better onboarding typically increases activation by 15-25%"
- "This usability fix could prevent 200 users/month from churning"
- Create "Experience-business scorecards": Rate every feature idea on both dimensions (1-10 scale):
- Experience: How much will this improve user satisfaction?
- Business: How much will this drive key metrics?
- Focus on features that score high on both
- The "Reality check" process: Before any major feature:
- Will users pay for this (directly or through engagement)?
- Does it solve a real problem people have?
- Can we execute it well with our resources?
- Will it move our most important business metrics?
8. Define how both teams measure success
Nothing kills collaboration faster than misaligned success metrics.
❌ Instead of: Design measures user satisfaction, business measures conversion rates
✅ Try: Both teams measure "user activation rate" (business gets growth, design gets engagement)
💡 Pro tips for creating shared success metrics:
- The "Dual-purpose metrics" strategy: Find metrics that satisfy both teams:
- Feature adoption rate: Business sees growth, design sees engagement
- Time to first value: Business sees activation, design sees successful onboarding
- Customer satisfaction score: Business sees retention predictor, design sees UX validation
- Support ticket reduction: Business sees cost savings, design sees usability improvement
- Create "North star metrics": One primary metric both teams rally around:
- The "Leading vs. lagging" framework:
- Leading indicators: Predict future success (onboarding completion, feature adoption)
- Lagging indicators: Show what already happened (revenue, churn)
- Design typically impacts leading indicators first, which drive lagging business metrics
- Quarterly "Metrics alignment sessions":
- Each team shares their key metrics and why they matter
- Identify overlaps and conflicts
- Create shared dashboard with joint success metrics
- Define what "winning" looks like for both teams
- The "Correlation hunt": Find connections between UX and business metrics:
- Does improved task completion correlate with revenue?
- Do satisfaction scores predict retention?
- Does faster load time impact conversion?
9. Use creative thinking to solve business problems
.png?table=block&id=2092a971-edb7-8059-9053-ce56e6f4f684&cache=v2)
This is where design thinking becomes a superpower. Don't just solve "design problems"—solve business problems with design thinking.
💡 Pro tips for applying creative thinking to business challenges:
- The "How might we" reframe: Turn business problems into design challenges:
- Business: "We need to reduce churn"
- Design thinking: "How might we help users get more value from our product?"
- Business: "We need more revenue per user"
- Design thinking: "How might we help users accomplish more of their goals?"
- Use the "5 Whys" for business problems:
- Why? Users abandon the signup process
- Why? It's too long and complicated
- Why? We ask for information we don't immediately need
- Why? Legal team wants comprehensive data collection
- Why? They're worried about compliance issues
Problem: Low conversion rates
Solution: Design a progressive onboarding that collects minimal info upfront, then gradually asks for more as users get value
- The "Customer journey business impact" mapping: For each step in the user journey, identify:
- What business goal does this step serve?
- What user need does it address?
- Where do these align or conflict?
- How might we redesign to serve both better?
10. Create a culture where biz and design learn together
Monthly rituals that actually work:
- "What we learned" retrospectives
- Cross-functional project post-mortems
- Shared Slack channel for interesting insights
- Customer interview sessions (both teams attend)
The goal: Business people who think about user experience, designers who think about business impact.
💡 Pro tips for creating collaborative learning:
- The "Learning buddy system": Pair each designer with a business counterpart for monthly knowledge exchanges:
- Designer teaches user research methods
- Business person explains market dynamics
- Both attend customer interviews together
- Both analyze results and share insights
- "Failure parties": Monthly sessions celebrating what didn't work:
- Share experiments that failed
- Discuss what we learned
- Plan how to apply lessons to future work
- Make it fun, not finger-pointing
- Cross-team "certification" programs:
- Designers earn "Business basics" certification (understanding metrics, market dynamics, pricing)
- Business people earn "UX fundamentals" certification (user research, design principles, usability)
- Create fun badges, certificates, even small rewards
- The "Customer rotation program": Every quarter, someone from each team:
- Shadows customer support for a day
- Joins sales calls
- Attends user interviews
- Presents findings to the other team
- Create "Learning artifacts" together:
- Joint customer personas (business data + user research)
- Shared competitive analysis (market positioning + UX evaluation)
- Combined journey maps (business metrics + emotional states)
Want to learn more about UX Management?
Check out UX Management Playbook — made for first-time managers building healthier and happier design teams.
Your action plan (starting Monday)
Here's your step-by-step battle plan:
This week:
- Create a shared Slack channel for business-design collaboration
- Ask your design team to attend one business meeting as observers
- Schedule 30-minute coffee chats with three key business stakeholders
This month:
- Create your business-design dictionary
- Start a monthly "What we learned" session
- Run a joint workshop to define shared success metrics for one major project
This quarter:
- Use that success story to advocate for expanding the approach
- Pilot a major project using the collaborative framework outlined above
- Measure and share the results (both business metrics and user satisfaction)
This year:
- Document your processes and share them with other teams
- Make business-design collaboration your team's competitive advantage
- Become the person people come to when they want to see how this stuff actually works
The happy ending (with actual results)
When business and design teams stop fighting and start collaborating, here's what happens:
✅ Teams enjoy their work more (shocking, I know)
✅ Products ship faster because there's less back-and-forth
✅ User satisfaction AND business metrics improve together
✅ You become the design leader everyone wants to work with
✅ Your career accelerates because you're solving real business problems
The companies doing this right: Airbnb, Slack, Stripe, Notion. Notice anything? They're all companies where design and business success are inseparable.
The companies still figuring it out: Most of them. Which means there's a huge opportunity for design leaders who crack this code.
The real job of design leadership
Business and design collaboration looks impossible until you see it working. Then it looks obvious.
Your job isn't to choose sides. Your job is to build bridges.
Some days you'll feel like a translator at the United Nations, helping two groups who barely speak the same language understand each other. Other days you'll feel like a conductor, orchestrating different instruments to create something beautiful together.
Both are true. Both are necessary. Both are why design leadership is one of the most interesting challenges in tech right now.
So what's it going to be? Are you going to keep sitting in those awkward meeting rooms, watching two teams fight over button placement? Or are you going to be the design leader who figured out how to make business and design fall in love?
Your move.
Whenever you're ready, there are 4 ways I can help you:
1. Junior Designer Bundle: Transition into UX and craft an unforgettable portfolio & get hired.
2. Senior Designer Bundle: Become a design leader with systems to build healthier, happier teams.
3. UX Portfolio Critique: In less than 48 hours, get your 30-minute personalised video of brutally honest feedback.
4. Job Sprint Course: Stand out in an unpredictable job market by building a memorable personal brand and a killer job search strategy.
