Simplicity is contextual
I have worked on products for travelers, property owners, job seekers, employers, developers, partners, and families. Every team wanted a simple experience. They did not mean the same thing by simple.
For a consumer, simplicity can mean confidence and momentum: help me understand the choice and keep moving. For a business user, it may mean control, auditability, and the ability to recover when reality does not match the happy path. Removing information can make one experience clearer and another one dangerous.
Different customers change the evidence
Consumer products often produce behavioral feedback quickly. Business products can involve longer cycles, multiple roles, contractual expectations, and work that happens outside the interface. A click can be meaningful, but so can a support escalation, an integration failure, or a workaround living in a spreadsheet.
The research plan has to follow the work rather than the screen. That means understanding who decides, who configures, who uses, who supports, and who carries the risk when the system is wrong.
The product still needs one point of view
Serving several audiences does not require making the product vague. It requires being explicit about the promise to each group and the tradeoffs between them. The design leader helps the organization see those relationships before individual teams optimize their part of the system in isolation.
The transferable skill is not expertise in one interface pattern. It is learning how to locate trust, value, and complexity in a new context—and then making them discussable across the team.