At a glance
- Ambiguous problems create hidden cost through misdirected technology, process changes, reporting and organizational effort.
- Design-led problem solving treats design as a management discipline that aligns user needs, commercial logic, operating reality and implementation.
- The strongest outputs are not workshops alone; they are problem statements, architectures, prototypes, decision rules, measures and execution roadmaps.
- AI accelerates synthesis and prototyping, but increases the importance of context, judgment, governance and cross-functional alignment.
Research signals: design is economically material
Design is sometimes treated as a visual or communications activity. The evidence suggests a broader management relevance. McKinsey's analysis of 300 publicly listed companies across a five-year period found that top-quartile performers on its design index achieved materially stronger business outcomes than industry peers. The research reported 32 percentage points higher revenue growth and 56 percentage points higher total shareholder-return growth over the period. The study identified a correlation rather than a guarantee of causation, but the scale of the difference is significant enough for leadership teams to treat design capability as an economic issue rather than a finishing activity.
Research reference points: McKinsey, The Business Value of Design; World Economic Forum, Future of Jobs Report 2025; IBM Institute for Business Value, Hybrid by Design.
Ambiguity is an operating cost
Organizations rarely begin with a perfectly framed problem. They begin with symptoms: customers complain, management reports arrive too late, a digital product is not adopted, approvals take too long, margins are falling, teams duplicate work or a transformation program loses momentum. Each symptom invites a familiar solution—new software, more reporting, a restructuring, a campaign or another control.
The risk is that the selected intervention may be locally sensible but systemically wrong. A reporting problem may actually be a data-ownership problem. A software problem may be a workflow and decision-rights problem. A sales problem may begin with an unclear service proposition. An employee-adoption problem may be caused by a process designed around departmental convenience rather than the work people need to complete.
The cost of ambiguity is not limited to delay. It includes technology built around the wrong assumptions, duplicated analysis, change fatigue, inconsistent customer experiences and management attention spent reconciling different versions of the problem.
Design-led problem solving makes ambiguity visible before the organization commits too deeply. It asks who is affected, what they are trying to achieve, where value is created or lost, what evidence exists, which constraints are real and what must be true for a solution to work.
Design is a management discipline—not decoration
In a consulting and enterprise context, design is the disciplined shaping of how a product, service, workflow, report or system should work. Visual quality matters, but it is one layer of a broader architecture.
A design-led team combines four perspectives. The first is human: what customers, employees, managers, suppliers or citizens need to understand and accomplish. The second is commercial: how the solution supports revenue, cost, risk, capital or strategic objectives. The third is operational: how roles, capacity, controls, data and systems will deliver the promise. The fourth is implementation: how the organization can test, govern, sequence and sustain the change.
This is why design-led work frequently overlaps with strategy, operations and digital transformation without duplicating them. Strategy defines direction and choices. Operations improves performance and control. Technology enables scale and automation. Design-led problem solving translates those intentions into an experience and operating logic that people can use.
A practical discovery-to-delivery model
The Design Council's Double Diamond remains a useful way to explain the movement between exploration and focus. Its four phases—Discover, Define, Develop and Deliver—show that effective problem solving alternates between divergent thinking and convergent decision-making.
| Phase | Management question | Typical work | Decision output |
|---|---|---|---|
| Discover | What is really happening? | Interviews, observation, journey review, process and data analysis | Evidence base and stakeholder view |
| Define | What problem should we solve? | Root-cause analysis, problem framing, prioritization and design principles | Agreed problem statement and criteria |
| Develop | What could work? | Alternative concepts, service blueprints, workflows, report or interface prototypes | Shortlisted concept and assumptions |
| Deliver | How will we test and implement? | Pilot, requirements, governance, measures, ownership and roadmap | Implementation-ready plan |
The model is not a rigid waterfall. Teams may return to discovery when a prototype exposes a faulty assumption. The discipline lies in making the learning, trade-offs and decision gates explicit.
Five architectures that must align
An actionable solution is more than an attractive concept. It requires several architectures to reinforce one another.
| Architecture | What it defines | Common failure when missing |
|---|---|---|
| Business architecture | Strategic purpose, value proposition, economics, stakeholders and success measures | A solution that is usable but commercially or strategically weak |
| Process and service architecture | Journey, roles, handoffs, decisions, capacity, controls and exceptions | A strong front-end promise with unreliable delivery |
| Information and reporting architecture | Data definitions, KPI hierarchy, evidence, status and management visibility | Activity without decision-grade insight or accountability |
| Interface architecture | Navigation, tasks, forms, content, interactions, states and accessibility | Users work around the system or make avoidable errors |
| Governance architecture | Ownership, approvals, risk, escalation, change control and review cadence | A pilot that cannot scale or deteriorates after launch |
These layers explain why design-led engagements benefit from multidisciplinary teams. A UI specialist may understand interaction quality, while a process specialist sees operational dependencies, a finance professional sees controls and economics, and an industry advisor understands context. The designed solution must integrate those perspectives.
Where design-led problem solving creates value
The method is useful wherever complexity must be converted into a clear experience and operating model.
| Business area | Typical ambiguity | Design-led output |
|---|---|---|
| Management reporting | Too much data, inconsistent KPIs and limited narrative | Decision architecture, KPI dictionary, report sequence and commentary framework |
| Finance operations | AR/AP delays, unclear approvals and fragmented visibility | Future-state workflow, portal interaction, exception logic and control dashboard |
| Healthcare services | Patient friction across referral, appointment, diagnostics and results | Journey map, service blueprint, communication standards and digital touchpoints |
| Franchising and retail | Inconsistent onboarding, customer experience and central/local responsibilities | Franchisee journey, operating blueprint, service standards and performance measures |
| MRO and operations | Complex work orders, inspections, approvals, parts and completion evidence | Workflow architecture, job-card logic, dashboard and control-room experience |
| NGO and donor programs | Programs designed around activities rather than user adoption and measurable outcomes | Stakeholder journey, program logic, evidence architecture and reporting design |
AI accelerates production—but raises the value of judgment
Generative AI can summarize interviews, generate alternative concepts, draft journey hypotheses, produce interface variations and accelerate prototyping. These capabilities reduce the cost of exploring options. They do not eliminate the need to determine whether the evidence is reliable, whether the problem is correctly framed, whether a concept fits the operating environment or whether stakeholders will adopt it.
The World Economic Forum's 2025 research reinforces this balance. Technology skills are rising quickly, while creative thinking, resilience, flexibility and analytical capability remain critical. IBM's research similarly found that 81% of executives considered design thinking especially vital in a hybrid operating environment. As production becomes easier, differentiation increasingly comes from the quality of questions, context, judgment, systems understanding and implementation.
AI-resistant design work is not manual production. It is the work of framing ambiguous problems, reconciling stakeholder interests, understanding real operations, making trade-offs, designing governance and leading adoption.
An executive diagnostic
| Question | Warning sign | Design response |
|---|---|---|
| Do stakeholders agree on the problem? | Each function describes a different cause and solution | Evidence-led problem framing and decision criteria |
| Can users complete the journey without workarounds? | Email, spreadsheets and informal follow-up hold the process together | Journey, workflow and interaction redesign |
| Does reporting lead to decisions? | Reports are reviewed but actions, owners and thresholds are unclear | Reporting architecture and management rhythm |
| Can the service promise be delivered consistently? | Quality depends on individual effort or local knowledge | Service blueprint, standards and operating model |
| Can the concept scale safely? | Pilot success depends on exceptions, manual controls or undocumented assumptions | Governance, requirements, controls and implementation roadmap |
How Ghories Consulting helps
Ghories Design Lab works across strategy, finance, operations, technology and industry teams to convert ambiguous business challenges into designed solutions. Engagements may include stakeholder discovery, problem-framing workshops, journey and workflow mapping, service blueprints, reporting architecture, interface prototypes, design systems, decision rules and implementation playbooks.
Our differentiation lies in connecting design to the business system around it. A report is designed with an understanding of finance and management decisions. A workflow is designed with controls, roles and operating realities in view. A digital product is shaped around the service, data and governance required for adoption. The objective is not design theatre; it is clearer decisions and more executable change.
Author
Sources and reference points
- McKinsey & Company — The Business Value of Design
- World Economic Forum — Future of Jobs Report 2025
- IBM Institute for Business Value — Hybrid by Design: Operating Model
- Design Council — Framework for Innovation and the Double Diamond
Figures are presented as reported by the cited organizations. External research is used as a reference point and should be interpreted in the context of each organization, sector and engagement.