Every organisation that adopts Design at Scale™ encounters a familiar tension: ideas are fragile. Jony Ive captured this perfectly when he said that ideas are, by definition, unresolved. They are partial, tentative, and unproven - and therefore easy to damage. Problems are concrete, measurable, and comfortable to focus on. Ideas are not. When teams concentrate only on problems, they erode belief in possibility.

DaS™ exists to protect that belief and turn ideas into outcomes.

Historically, consultancies and frameworks - Agile Alliance, Scrum Alliance, IDEO, McKinsey, IBM, and others - have attempted to merge disciplines into a unified delivery approach. Each has achieved progress, but the same challenges recur: mindset, bias, culture, and integration. These challenges determine whether an organisation evolves or retreats back into silos.

Below, we explore each challenge and how DaS™ addresses it in practice.

2.2.1 The Mindset Challenge

Most organisations are built around specialised departments that guard knowledge. This structure ensures quality. You don’t want a designer doing tax returns or an accountant rewriting your design system. But it also creates isolation. As systems become more interconnected, especially in digital environments, teams must share knowledge to work effectively.

DaS™ reframes this by establishing a shared organisational knowledge base. Instead of information scattered across Slack, Teams, PDFs, and private folders, DaS™ centralises context, decisions, and rationale into a structured wiki (typically Confluence). This transforms knowledge from static documentation into operational intelligence.

The effect is immediate:

— Teams make faster, more connected decisions
— Noise reduces; signal increases
— Rework drops
— Accountability becomes shared
— Designers, engineers, and product practitioners operate from the same truth

A healthy mindset starts with an environment where knowledge is visible, useful, and reusable. DaS™ creates that environment.

2.2.2 The Bias Challenge

Bias is unavoidable. It comes from culture, experience, background, and past environments.
But bias is not the same as:
— fear of adoption
— poor articulation
— an uninformed decision
— adherence to organisational norms

DaS™ helps teams separate bias from clarity.

For over two decades, DaS™ has helped designers and non-designers build shared understanding through behaviour models, prototypes, and mental models. By visualising concepts early and testing assumptions openly, ideas become tangible and objective. The team no longer debates abstractions - they discuss evidence.

When ideas are made visible:
— bias decreases
— alignment increases
— contribution becomes measurable
— teams attach themselves to solutions, not opinions

DaS™ ensures ideas “stick” by transforming subjective fragments into shared, validated models.

2.2.3 The Culture Challenge

Many company cultures unintentionally limit transparency, clarity, and cross-functional collaboration. Training hubs focus on compliance topics - health and safety, conduct, digital risk - but they rarely address how design delivery actually works. The result of this: designers feel more emotionally aware but less operationally empowered. They attend meetings without clear direction, struggle to articulate impact, and lose motivation as small wins disappear under noise.

DaS™ restores cultural clarity by:
— grounding teams in purpose-driven work
— emphasising skill development over social bonding
— building self-organised communities
— encouraging cross-team learning
— connecting each task to real business impact

The result is a culture where:
— wins are visible
— relationships strengthen naturally
— teams deliver ahead of schedule
— individuals end the day with recognition, not frustration

DaS™ builds culture through practice, not perks.

2.2.4 The Integration Challenge

Integration is often the hardest shift. In many organisations, Agile has become synonymous with engineering, reducing everything else - design, research, content, service operations - all the way to “supporting functions.” This creates a product-led bias where design work is seen as cheap, interchangeable, or unnecessary.

DaS™ does not compete with Product Owners or Engineers. It complements them by clarifying how design integrates into delivery. When integrated well:
— design becomes systematised
— development becomes faster and cleaner
— product outcomes improve
— handover friction disappears

To illustrate this balance, DaS™ uses a metaphor: a tennis ball on a three-legged table.
— The ball = the product
— The tabletop = DaS™
— The three legs = business, design, and development

If any leg is shorter, longer, weaker, or overextended, the ball rolls - the product becomes unstable. If all legs are equal, stable, and supported by shared knowledge, the ball stays firmly in place.

As products grow more complex, the table and legs must be redesigned - stronger foundations, bigger surfaces, different proportions. Every organisation requires its own adaptation. DaS™ provides the method to find that balance.