Page_6df62578 https://www.whitespace.ch/ Enterprise User Experience | UX FIRST Sun, 18 Oct 2026 08:21:38 +0000 en-US hourly 1 https://www.whitespace.ch/wp-content/uploads/2022/11/cropped-Favicon-Large-Black-32x32.png Page_6df62578 https://www.whitespace.ch/ 32 32 Page_6df62578 https://www.whitespace.ch/insights/blog/wild-west-journey-management/ Sun, 12 Apr 2026 15:57:36 +0000 https://www.whitespace.ch/?p=18620 The Wild West of Journey Management Why the current state of Service Design feels like a new Gold Rush By Peter Horvath, Strategy and Service Design Lead Date: 12 April 2026 Blueprints and Customer Journeys have come a long way, from being paper-based exploration and prototyping tools to the collaborative management tools they are today. ...

Read more

The post The Wild West of Journey Management appeared first on Whitespace.

]]>

The Wild West of Journey Management

Why the current state of Service Design feels like a new Gold Rush

By Peter Horvath, Strategy and Service Design Lead

Date: 12 April 2026

Blueprints and Customer Journeys have come a long way, from being paper-based exploration and prototyping tools to the collaborative management tools they are today.

We argue that far from the end of the journey, we are merely getting started. The ways of working with these tools, as well as the roles involved, are just emerging. In fact, the landscape is more similar to the Wild West than to a mature society.

Life on the frontier

Service designers used to labor over intricate customer journey designs. We then struggled to keep the design’s integrity as projects evolved. And finally, while journeys are blueprints meant to be used, they barely made it beyond presentation or becoming a poster. Most often, they remained criminally underused. Shared ownership, the whole point of journeys, remained a dream.

Digital tools that not only create but also manage user journeys are part of the solution. These tools are becoming more common, turning static visual artifacts into dynamic collaborative platforms. But the current state of journey management tools reminds us of the Wild West in many aspects:

  1. There is a shift from freedom to structure
  2. Opportunities seem endless
  3. The current state is a chaotic structure
  4. Everyone has their own strengths
  5. Roles are shifting

Let’s explore these interconnected points one by one and find out how they resemble the Wild West.

1. Shift from freedom to structure

Untamed nature characterized the Wild West until roads, towns, and cities appeared. Similarly, the complete freedom to use legacy tools like Figma, PowerPoint, Miro, and Mural, and even Photoshop, has traditionally characterized journey mapping.

But there were many downsides. Limited reusability or portability, frequent single-use journeys (beyond some templates and models), growing complexity, and, of course, visual representation taking prominence over substance – all of these locked in knowledge & information.

Journey mapping tools introduced structure to the mapping process about a decade ago. This meant more limitations, but also the promise of more value. The invested effort started shifting from creating the map (output) to working with the map (outcome). And as journey became working documents, the opportunities seemed endless.

2. Opportunities seem endless

In the Wild West, opportunity awaited everywhere. You could get your own land just by claiming it. Or you could dig for gold to try to get rich quick. Or opt for a steady income by selling picks and shovels to people digging for gold. And the list goes on.

Similarly, the world of journey tools is no less versatile. You will find different categories of journey tools on the market, the main types being:

  • Journey mapping: Aggregating and visualizing information using personas, pains, insights, and proposals. See Smaply or UXPressia.
  • Journey analytics: transaction-focused user flows and funnels informed by real-time data, usually focused on sales. See Adobe Analytics, or Funnelytics.
  • Journey orchestration: real-time, personalized updates to digital properties (offer, content, CTA, etc.) based on past actions & value of individual users. Usually focused on marketing. See Adobe Experience Platform or Salesforce Marketing Cloud Engagement.
  • Journey management: organization-wide, user-centered project management and collaboration. See JourneyTrack, TheyDo, or Cemantica.

The downside of this versatility is the rise of some market chaos.

journey market landscape
journey mapping landscape in table format

3. Today’s chaotic structure

The Wild West relied heavily on unwritten law, and lawlessness remained prevalent. Similarly, the logic of different journey tools varies widely. While the tool ecosystem has notably matured, we are not yet in a phase of convergence.

One contributor to a bit of chaos among journey tools is that price differences are staggering. Pricing seems to be audience-based rather than cost- or functionality-based. Even the more closely related categories, mapping tools and management tools, can show a drastic, 240x difference in cost (not a typo!).

The other contributor to the chaos is the lack of a consistent logic. We looked at Smaply, TheyDo, Cemantica, and JourneyTrack in detail and found differences in operating logic, nomenclature, and functionality. A few examples:

  • Main elements of Journeys are called “stages” in some, and “phases” in other tools
  • While there are over 30 different types of swimlanes across the tool, less than a third of these are common across all tools, and over a third exist only in one of the tools
  • Smaply and Cemantica handle “Pains” as a specific field type. But TheyDo and JourneyTrack handle it as a type of the “Insight” field type.
  • Insights (complex summaries of different types of information) are a well-established concept in design. Yet TheyDo and JourneyTrack handle them as just Pains, Gains, or Needs.
  • Most tools have “smart field types", complex fields that allow adding metadata such as tags, values, and linkages. But none of the smart field types are shared across all 4 tools.

This means that even if you are proficient at one tool, another one will take getting used to. And each tool will shape your process to some degree. But this also means that each tool has its own strengths.

journey management comparison table

4. Everyone has their own strengths

The Wild West had its main roles, including cowboys, lawmen, settlers, builders, and many others, each with their own strengths. They often collaborated, had their quarrels, but they were all needed.

Similarly, the various types of journey tools also have their own strengths. But organizations will usually only work with one tool, meaning you can’t get the ideal combination of tools as the Wild West featured. Below are some of our favorite features, though not exhaustive. (You can find a complete analysis in the Forrester Wave report.)

Fortunately, journey tools evolve quickly, so they will learn from each other’s good practices.

Similarities across tools

While different in many ways, both TheyDo and JourneyTrack separate “customer value” and “business value” of “Solutions” and “Recommendations”.

TheyDo
JourneyTrack

Many parameters

Smaply’s “Solution” swim lane cards have “impact”, “feasibility”, and “reach” scores, but also “desirability”, “viability”, and “feasibility” scores.

onboarding

Good use of AI

All tools have some type of AI functionality, but JourneyTrack’s “add insights” stands out. It allows users to upload files (such as interview transcripts) for AI to extract insights from. What’s great is that sections of the uploaded document are highlighted as the source of the insights, making them easy to verify and fine-tune.

JourneyTrack

Beyond journeys

While most venture beyond simple maps, arguably Cemantica offers the most complex package. The Define, Execute, and Measure sections of the app are more than simple add-ons and are on par in complexity with the journey design itself.

Cemantica

Linking journeys

All tools offer “nested journeys”, where you can embed a journey into another journey. But TheyDo takes this to the next level by allowing users to link an individual Step from one journey to another. These tools allow you to link almost anything to everything, e.g., opportunities to journeys, other opportunities, solutions, insights, etc.

TheyDo

Embedded journeys

Most tools enable embedded journeys, following the JourneyOps concept. Cemantica visualizes it in a unique visual way, emphasizing the multiple levels of embeddedness. JourneyTrack does a good job of visualizing macro and micro stages and combining journeys into what they call a “Journey atlas.”

Cemantica, embedded journeys
Cemantica

Boardroom-ready visualizations

JourneyTrack and TheyDo offer various ways to visualize, making parts of hard-to-consume journeys understandable at a glance, such as in their opportunity map, which is informed by various opportunity scores across the journey.

journey visualizations

Journey routes

Cemantica handles Main routes and Alternative routes within journeys.

Cemantica

5. Roles are shifting

Historically, diverse Indigenous nations maintained sovereignty over Western lands through complex agricultural and nomadic systems until they were systematically displaced by U.S. federal policy, military force, and waves of Euro-American settlement. This frontier era—characterized by resource extraction and a blend of legal ambiguity and localized violence—was eventually transformed. The expansion of the federal government, the arrival of the railroad, and the institutionalization of statehood replaced the transient dynamics of the frontier with a structured society governed by formal legal and economic systems.

Similarly, journey tools are also shaping the landscape of today's professions.

One aspect is the agency vs corporate divide. Journeys used to be a go-to tool for agencies to distill findings or proposals into a succinct yet human-centered format. But it is corporations that can make the most of today’s journey management tools, due to their scale, price tag, and the way they link research, design, and execution across projects.

The other aspect is regarding roles within organizations. Static journeys used to have a creator and an audience. But with dynamic journey tools, two new roles will arise: the user and the manager.

  • The user role is a natural evolution of the traditional ‘audience’. Journeys become living documents closely connected to execution, with people across different departments actively using them as a daily tool rather than only consuming them during presentations.
  • As journeys become increasingly collaborative and share ownership, a manager role needs to emerge. Who will fill this role is still an open question. Some experience and service designers specialize in journey management roles. In response to them, some PMs’ or BAs’ responsibilities are expanding to include journey tool management as well. And a whole new type of person may arise, wielding quantitative data and qualitative insights with equal ease. The new role requires a mindset shift and a blend of capabilities from multiple worlds.

Just as the Wild West transformed settlers into a new nation, journey tools will transform the people who use them.

The promise of a grand future

Settlers came to the Wild West for freedom and opportunity, a better future for themselves. Similarly, the general shift from static visual journeys to dynamic collaborative tools is the right direction for any organization.

Journey tools should be a building block of a more human-centered operational culture. And traditional journeys can still have their place – just as design systems still leave room for creativity and original design. There can still be a place for unique solutions, e.g., when creating a journey for a future vision, and you can still use storytelling to present your journeys. For example, we recently created storytelling videos using subsets of the information already captured in a journey management tool.

paper vs tool-based journey management

How do we at Whitespace expect journey tools, especially journey management tools, to evolve in a preferred future?

  • Interoperability and standards
    Portability of journeys across tools would facilitate switching between and combining tools and introduce much-needed consistency for wider adoption.
  • Feature combination
    Bringing together the qualitative aspects of Mapping tools, the continuity provided by Journey Management tools, the quantitative aspects of Journey Analytics tools, and the real-world/real-time aspect of Journey Orchestration tools.
  • AI where you really need it
    Many current tools offer the ability to build Personas with AI. In our view, this is a misplaced effort. Fundamental elements of journeys (such as Personas) need to be thoroughly researched and constructed. But AI can be immensely valuable for summarizing and storytelling.
  • Summaries & storytelling
    Digesting a robust journey is no small effort. Tools don't yet allow quick, easy summarization of a single journey for senior stakeholders. Seamless creation of meaningful macro-journeys or journey summaries is a much-needed addition. But the icing on the cake would be creating engaging narratives, such as short movies, that convey information through a combination of narration, dialogue, props, scenery, and atmosphere.
  • Multiple visualization options
    Mature journey management tools handle some elements of a journey (e.g., pain points, insights, proposals) in a modular way. By infusing more journey elements with metadata (e.g., importance, value, cost), many visualization options open up, such as matrix, prioritized list, and heatmap views. These are perfect for presenting journey information to senior stakeholders.

If you have been thinking about getting started with journey tools, here’s what we propose you can do today:

  1. Research the field (reading this article is a great first step!) and request demos from as many vendors as possible to get a better sense.
  2. Start using a tool (or even multiple tools) this week – no excuses. Pick a pilot project or rebuild one of your past static journeys with a dynamic tool of your choice. Most important outcome: create a clear list of journey tool requirements for your company.
  3. As much as possible, partner with the company behind the tool you use by informing them of your needs, offering suggestions, and submitting feature requests.

In closing

As in the Wild West, so too in Journey tools, freedom is giving way to structure; the possibilities of dynamic collaborative tools seem endless, but chaos still contributes to divergence rather than convergence.

As each person in the Wild West had their strengths, so too the individual tools, meaning their feature set will shape the way you work.

And finally, at an individual level: your role. Bottom-up and top-down, peaceful and violent factors all helped shape the protagonists of the Wild West. These factors also influence the future of tool-based journey management roles. So, best be prepared, proactive, and determined if you want to play an active role in it.

Related content

The post The Wild West of Journey Management appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/hard-truth-enterprise-design-systems/ Fri, 31 Oct 2025 09:43:46 +0000 https://www.whitespace.ch/?p=17931 The hard truth about enterprise design systems Why DIY systems fail, and what to do instead By Jesse Anton, CEO & Co-Founder of Whitespace First published: 31 October 2025 Last updated: 30 September 2026 As AI transforms how we design and build software, design systems are undergoing a renaissance. Consistency, reuse, and fewer repetitive design ...

Read more

The post The hard truth about enterprise design systems appeared first on Whitespace.

]]>

The hard truth about enterprise design systems

Why DIY systems fail, and what to do instead

By Jesse Anton, CEO & Co-Founder of Whitespace

First published: 31 October 2025

Last updated: 30 September 2026

As AI transforms how we design and build software, design systems are undergoing a renaissance.

Consistency, reuse, and fewer repetitive design decisions are all valuable pursuits that drive in-house teams to build their own design systems. The hard truth is that all too often, these systems start strong and then quietly collapse under their own weight.

What's more, most DIY systems are not primed for agentic coding and MCP-powered workflows, leaving them vulnerable to obsolescence.

We’ve seen it happen in enterprises across various industries: well-intentioned, home-grown systems that accumulate design and technical debt — and ultimately fail.

Here’s why — and what to do instead.

The DIY trap

The scene:
A large traditional enterprise with ambitious AI-driven productivity goals bumping up against a culture that's anything but digital-native.

The plot tension:
Leadership wants to move fast and impress the Board with shiny AI objects while simultaneously cutting costs. A design system would help. But there's no design system. Or there was one, but nobody knows where it is anymore because the team that built it left to join Google. Or there are several design systems ... but it turns out they are essentially useless and gathering dust. Who will save the day?

The protagonists:
A dashing designer and daring developer come together to start a fresh new DIY design system project. It starts small. A Figma library. A few color tokens. Some code snippets. A bit of documentation in Confluence.

The build-up:
For a while, things are good. The system grows. Everyone feels aligned. Our protagonists feel like heroes. Will they live happily ever after?

The plot twist:
A blue-chip management consultancy is hired and begins working on top-secret 'disruptive' PowerPoint slides in a dark corner of the building. They have the ear of the executive committee. Nobody knows for sure, but they might be recycling last week's work for another client and using AI to 'adjust the tone and context'. A new CTO (formerly with the management consultancy) parachutes in and announces a comprehensive refactoring and overhaul of the tech stack.

The dénouement:
Cracks begin to appear in the now-doomed system, including duplicated components, mismatched patterns, and missing documentation. The users start complaining and demanding retribution. The system becomes harder to maintain — and the promise of speed turns into a drag on momentum. Funding is lost. The system is jettisoned.

The anti-climax:
Our heroes apply for jobs at Uber. The management consultancy moves on to the next victim client. The curtain falls.

The moral:
Most design systems don’t fail because they’re bad ideas. They fail because they don't have the right conditions in which to thrive.

Why failure happens

Internal design systems lack the necessary structure, skill, and stakeholder commitment to succeed. This is not a reflection on the latent talent within the organization. It reflects how the organization operates. It's cultural.

Common patterns we see:

  • No governance: departmental resources 'on loan' are not centrally accountable
  • No in-house expertise: designers lack sufficient knowledge of front-end code; development is outsourced and incentivized to build from scratch to increase billable hours
  • No design-to-code parity: what’s in Figma doesn’t match what's in code, with designers and developers 'detaching' from the system at will
  • No flexibility: product teams lack the freedom to use different JS frameworks
  • No data: metrics and KPIs are not available
  • No storytelling: the ROI is not clear to stakeholders
  • No funding: if nobody 'owns' it, the product dies on the vine

Without clarity and care, even the best systems turn messy. And the costs start to compound.

The result?

  • A fragile system: Multiple Figma files, naming conflicts, spacing inconsistencies — it all adds up when there is no process to govern the product. Every change becomes harder to trace, and risks begin to accumulate.
  • A system that costs more than it's worth: Intended to boost speed and save money, your DIY system ultimately erodes trust and efficiency while consuming precious time and resources. Developers doubt components, designers duplicate work, no one maintains the documentation (or the documentation is spread across too many tools for one team to maintain), and the system becomes a drain on delivery.

The highest cost? What you could be doing instead. Every dollar spent maintaining an unscalable system is a dollar not spent improving the actual products and business tools that the system is meant to support.

The problem is worse than it appears

We observe that most of our enterprise customers are being taken advantage of by their so-called 'strategic' development partners (big-box offshore IT services companies), who happily reinvent the wheel each time they assign a development team to build a new bespoke solution for the client.

Often, these partners are unaware that a design system even exists within enterprise accounts, let alone where to find a basic pattern library. They start from scratch, using off-the-shelf libraries like MUI and 'bending and twisting' them to match the client's brand identity. The same UI components are created repeatedly because every product is essentially treated as an independent 'project' that is built in silos by separate 'teams' — not 'empowered teams' in the SVPG sense, but rather more like 'mercenaries' working on the clock.

It's not entirely the partners' fault. As previously mentioned, we also observe that most of our clients struggle to establish an in-house design system that is adequately staffed, properly architected, and sufficiently evangelized. Design system resources are 'borrowed' from other departments and disappear when politics intervene and power centers shift. Initiatives are often launched but fail to deliver before leadership priorities change, funding is cut, or a reorg wreaks havoc. The momentum dies, and so does the design system.

At least for a while. Different parts of the company eventually spin up competing systems, 'skunkworks' style. There is a 'Wild West', shadow-IT mindset that pervades the product culture.

In the best-case scenarios, the design systems that do cross the chasm in enterprise environments are often challenging for both designers and developers to consume. Not to mention AI, which exposes fault lines in these systems that human processes have masked for years. As a result, adoption never reaches critical mass.

What good systems need

A scalable design system isn’t just a Figma library or a code repo that you download off the internet and 'tweak' — it’s a fully-fledged product. It requires:

  • 1-1 mapping between design and code (or code-native design tooling)
  • Robust, multi-tiered design token structure
  • Automated CI/CD pipelines
  • Flexibility for a changing technology landscape
  • Accessibility and security by default
  • Instrumentation for analytics and reporting
  • Clear, AI-friendly documentation and guidelines (contracts, schemas...)
  • MCP-powered agentic workflows
  • A skilled and dedicated team of design and development experts to govern it

Above all, it requires trust. And trust has to be earned. This doesn't happen overnight, which is why committed stakeholders and sufficient long-term funding are necessary to bridge the gap until trust can be established and ROI proved.

What you can do about this

Which brings us back to the original dilemma. The conditions for design system success rarely exist within a large enterprise. Digital-native companies can make design systems work, but even for them, it's a significant challenge. Outside of the tech industry, the rest of the world is still struggling to cross the chasm.

So what should enterprise technology leaders do? We believe we have the answer.

Consider your design system a product that you buy, not one that you build. It's ironic to say that, because a design system exists so that you can build products.

Having built numerous design systems for various organizations, we realized we could create one that is flexible, customizable, and future-proof enough to meet the needs of the most demanding enterprise clients. Our white-label solution delivers the full value of design systems to enterprise customers, without the hassle and headaches of a DIY approach.

Introducing Edelweiss

Edelweiss logo

At Whitespace, we have developed an agentic UI platform called Edelweiss™ that changes how product teams build software with AI.

Edelweiss is a turnkey 'UI infrastructure' solution for your enterprise AI architecture. Teams building software products on top of LLMs, data lakes, data virtualization, etc. — all that investment in AI-driven product development that large companies will be making over the next decade — now have a structured UI layer to tap into, meaning product builds become significantly more efficient, consistent, automated, and accessible.

Backed by an enterprise SLA, Edelweiss comes with customer success and support services that guarantee rapid returns and long-term value. Our experts stay up-to-date with the latest technology and tooling capabilities, so you don't have to. Right out of the gate, you need fewer internal resources allocated to core design system work, which means your designers and developers can stay focused on solving business problems, not reinventing the button.

We believe this is category-defining: an Agentic UI Platform-as-a-Service.

But the story doesn't end there. When AI and design systems meet, magic happens.

Set yourself up for success

AI is changing how software is designed and developed.

While vibe coding solutions, such as Lovable and V0, are interesting for ideation and rapid prototyping, they have no place in an enterprise's production software infrastructure.

Agentic coding assistants — such as Claude Code, GitHub Copilot, and Codex — are an entirely different story. They have real utility in your SDLC, provided they are given the context and guardrails in which to operate. Agentic workflows built on orchestration frameworks like n8n, and on-demand context-aware experiences facilitated by MCP Apps and A2UI, are further reasons to invest in AI-native UI infrastructure.

Edelweiss is the missing UI piece of the new agentic software ecosystem.

Context is king

Edelweiss is a platform comprising Harmony, Tuner, Composer, and Figaro. Everything is integrated and seamless. You want to build compliant, enterprise-grade products with AI assistance. We provide the UI infrastructure that makes this so much easier.

Code

For code, there's Harmony — customizable, branded libraries in both Web Components and React, ensuring that development teams are not locked into any particular framework. Great for SPAs, Web Components are portable and usable straight away on any platform and across your existing tech stacks. Our React library is for customers who have standardized on this framework or who need SSR capability. These libraries are maintained in parallel by our expert team and are evolving as quickly as different customer and industry use cases emerge.

Tokens & CSS

Tokens, CSS, and schemas are managed in Tuner, which also enables teams to manage multiple design systems built upon the Harmony foundation. Tuner is the most powerful tool on the market for generating and governing design systems. Tuner contains the logic and rules for ensuring your design systems are harmonious (see above, Harmony), accessible, on-brand, and easy to manage. The engine underlying Tuner is patent-pending.

Documentation

AI works best with structured documentation, and ours is complete and precise. Each component is fully documented in Storybook and JSDoc. We also provide an editable, centralized documentation repository in Tuner for specifying usage guidelines and generating well-formed schemas for AI to consume as opinionated design context at build time. AI can access guidelines and component props via Harmony MCP.

Design

Composer is an agentic and collaborative tool for product teams building brand-compliant, accessible front-ends with AI. Designers and developers work together in a design-with-code environment to craft patterns, templates, and connected screen flows that generate working prototypes and production-ready code. Patterns, flows, and screens can be shared across products and design systems. Everything is canvas-based and multi-user, like Figma, except the medium is real code on the canvas, not pictures of what the interface should look like.

Gone are the days of fumbling with Figma mocks, clunky Figma plugins, Figma MCP, and endless handover meetings to convey design intent to developers. Instead, designers can test earlier and more frequently with stakeholders and deliver artifacts that developers can use in production. For their part, frontend developers can now spend more time on backend integration tasks (e.g., hooking up to GraphQL or REST endpoints) and less time on interpreting 'fuzzy' design directions.

AI assistance

Both Composer and Tuner are powered by Figaro, our built-in AI assistant and vibe design agent, saving you time and effort as you deliver compliant, accessible, production-ready designs. Figaro makes a product team’s job easier:

  • You want to use Composer to vibe design a solution to a problem. Figaro gives you three options to choose from and uses fully compliant and tuned Harmony components to do it.
  • You want to connect pages into a flow or add more cards to a composition. Figaro makes the changes for you.
  • You want to darken the primary brand color across all design systems. Figaro traces every token that references “brand primary” and shows you the full impact before you commit.
  • You want to make sure your complex interaction specs are complete. Figaro checks for missing states, failure modes, contradictions, accessibility, and usability best practices.

MCP

AI agents can invoke Harmony-based design systems via MCP. The Harmony MCP Server enables product teams to ‘tame’ agentic coding assistants, ensuring they only use the coded components from the design system library. Effectively, agents will no longer pull from code found in the wild while you 'hope for the best' (aka 'prompt and pray'). Unlike tools such as Lovable or Claude Design, you get near-deterministic output whether you use Composer or go directly through an agentic assistant like Claude Code or Codex.

More bang for your buck

Code reuse is a big deal. Branded, accessible, and AI-ready code reuse is an even bigger deal.

We expect Edelweiss to save enterprise clients millions every year, not only on in-house DevOps and DesignOps costs, but also on product development and brand management costs.

  • Procurement can use it as leverage to renegotiate contracts with the 'strategic' development partners mentioned above.
  • Product teams can put working prototypes in front of business stakeholders more frequently, which reduces risk and shortens time to value.
  • Marketing and Brand teams can manage multi-brand ecosystems and global design updates from a single source of truth instead of 'policing brand compliance' ad hoc.
  • IT leaders can accelerate delivery in both agentic and traditional coding environments, while improving consistency, quality, and accessibility.

This solution delivers clear ROI. And this is just the beginning of our journey. HTML presentations are on the roadmap. Hello PowerPoint and Google Slides, you've got competition!

Interested in the private beta? We have already signed up several multinational companies — brands you're familiar with — as early adopters. Will you join us?

You can learn more at Edelweiss.build (private beta starting in 2H 2026). In the meantime, if you are interested in becoming an early adopter, get in touch with us to arrange a demo.

Related content

The post The hard truth about enterprise design systems appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/design-is-alive-in-age-of-ai/ Wed, 13 Aug 2025 14:27:57 +0000 https://www.whitespace.ch/?p=17841 "I'm not dead yet!" Why design will survive and thrive in the age of AI By Jesse Anton, CEO & Co-Founder of Whitespace Date: 13 August 2025 Bring out your dead! Every time a new technology emerges, someone proclaims the death of design. Now, with AI generating logos, layouts, and entire websites in seconds, the ...

Read more

The post Why design will survive and thrive in the age of AI appeared first on Whitespace.

]]>

"I'm not dead yet!"

Why design will survive and thrive in the age of AI

By Jesse Anton, CEO & Co-Founder of Whitespace

Date: 13 August 2025

Bring out your dead!

Every time a new technology emerges, someone proclaims the death of design. Now, with AI generating logos, layouts, and entire websites in seconds, the refrain is louder:

"Why pay for design when AI can do it instantly?"

The truth is, design isn’t dying. It’s evolving. And in the age of AI, it’s becoming even more valuable. Here’s why.

AI can generate, but it can’t reason

AI can give you 1,000 options in seconds. But which option fits your brand’s voice, supports your business goals, works across contexts, and resonates with your audience? That’s not an algorithmic decision — it’s a human one.

Design is fundamentally about making choices with intent. AI makes suggestions. Designers create meaning.

The hard part was never aesthetic

Anyone can make something look good. Tools like Canva and Figma already lowered that bar before AI came along.

What AI still can’t do:

  • Understand the political dynamics of an organization
  • Anticipate future needs so a solution scales
  • Balance user needs with business goals

Design is not about decoration — it’s about solving the right problem in the right way. That’s still a deeply human skill.

The world is getting more complex, not less

Ironically, AI makes the design challenge harder.

Why? Because now:

  • Users expect personalization at scale
  • Ethics and trust are non-negotiable
  • New interaction patterns (conversational UIs, autonomous agents) demand new mental models

When the complexity of the system increases, the value of human-centered design increases with it. We’re not just designing for humans — we’re designing with AI in the mix.

AI needs guardrails, and designers build them

Without intentional design, AI experiences can be:

  • Confusing (“Why did it do that?”)
  • Untrustworthy (“Can I rely on this answer?”)
  • Harmful (“This bias is built into the system.”)

Designers bring the skills to map user journeys, anticipate edge cases, and embed ethics into interfaces and workflows. We’re not just making things functional — we’re making them safe, understandable, and respectful.

Creativity isn’t just output — it’s framing

AI is a phenomenal assistant for exploring how.

But what to design, and why it matters, still comes from people. The magic of design has always been in framing problems differently — in seeing an unmet need or an overlooked opportunity.

In the AI era, the most valuable designers are those who know how to ask better questions, not just create better visuals.

The future is not Human or AI — it’s Human + AI

The winning combination isn’t replacing designers with machines; it’s augmenting designers with AI so they can:

  • Explore more ideas, faster
  • Test and iterate with less friction
  • Spend more time on strategic and human challenges

AI takes the repetitive strain out of design work. Designers then have the bandwidth to focus on research, vision, prototyping, storytelling, and orchestration — the parts of the craft that matter most.

Closing thought

AI is a powerful new tool in the designer’s kit, but it’s just that: a tool. What makes design work resonate, drive change, and build trust has always been — and will remain — deeply human.

So no, design isn’t dead. In fact, the more powerful AI becomes, the more we need designers who can guide it, challenge it, and shape it to serve human needs with clarity and care.

The age of AI isn’t the end of design. It’s the start of design’s most important era yet.

Related content

The post Why design will survive and thrive in the age of AI appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/service-design-meets-stakeholder-needs/ Thu, 24 Jul 2025 12:37:21 +0000 https://www.whitespace.ch/?p=17717 Service Design meets stakeholder needs Turn complexity into memorable takeaways and actions By Julia Borkenhagen, CXO and Co-founder of Whitespace Date: 24 July, 2025 Advice for designers on managing stakeholders You have done extensive research, analyzed, synthesized, and built amazing personas, user journeys, even blueprints — now what? You need to communicate all this valuable ...

Read more

The post Service Design meets stakeholder needs appeared first on Whitespace.

]]>

Service Design meets stakeholder needs

Turn complexity into memorable takeaways and actions

By Julia Borkenhagen, CXO and Co-founder of Whitespace

Date: 24 July, 2025

Advice for designers on managing stakeholders

You have done extensive research, analyzed, synthesized, and built amazing personas, user journeys, even blueprints — now what?

You need to communicate all this valuable information to your stakeholders and encourage them to take action. But how? As designers, we love complexity… But our stakeholders want clear solutions.

Here is some advice for Service Designers seeking to improve their stakeholder management skills.

This article is based on a talk delivered by Julia Borkenhagen at the annual Swiss Service Design Week event held in May 2025

Start by empathizing with your stakeholders

As designers, we pride ourselves on empathizing with the end users, and for good reason. But we often fail to do the same with our stakeholders. I am the first one to admit it, having produced massive research reports and visualizations over the years. These reports didn't always hit the mark, which got me thinking about stakeholder needs and how to address them.

designers love complexity
Designers love complexity
stakeholders want solutions
Stakeholders want solutions

At Whitespace, we collaborate with a diverse range of stakeholders. During an internal workshop, we conducted a quick mapping of different “client types” ranging from the Engaged Leader to the Know-it-all persona.

Considering the diverse personalities, contexts, and needs of stakeholders, it is crucial to tailor your communication style, tone, and ultimately, your services and deliverables to meet their specific requirements.

client persona and journey

While it’s useful to have an idea of different client or stakeholder personas, there are some fundamental truths about your stakeholders that are worth considering:

    1. They lack time
      Stakeholders are, above all, pressed for time: their agendas are packed with back-to-back meetings, inboxes and chats are flooded, and they can’t find space for deep work.
    2. They need just enough information
      Stakeholders are in a constant state of information overload and require just enough data to make informed decisions.
    3. They care about the business impact
      Stakeholders primarily care about the business impact, whether it is cost savings or revenue increase.
    4. They need to demonstrate value
      Stakeholders need to hit or exceed their KPIs, do their own PR, and look good in front of their peers and management.

So, once we have empathized with our stakeholders, where are the opportunities? To find out, let's dive a little deeper into these stakeholder truths, shall we?

1. Be mindful of people's time

If you are new to a project, try to understand what happened before. Are stakeholders frustrated with previous (maybe unsuccessful) attempts to fix the problem? Do they have interview and or workshop fatigue? What can be learned from the past, and how can we build on existing learnings?
Whether stakeholders are frustrated or willing to engage, they will appreciate it if you can find innovative ways to avoid long and frequent meetings or workshops. Consider whether a live discussion or brainstorming session is truly essential for the topic at hand, or if asynchronous collaboration could achieve the desired outcome.

When you have secured that precious time for a live session, make it count. Be prepared, share pre-reads or viewpoints in advance (a video walk-through can do wonders!), and make the time spent together fun and productive.

2. Simplify

Mark Twain famously said, “I didn't have time to write a short letter, so I wrote a long one instead.”

Simplicity is hard, especially with complex subjects, but not everyone needs the same level of detail.

Stakeholders don't have time for complex blueprints or multiple user journeys. They need highlights, "the drama," and storytelling.

Strategies include:

  • Telling a story with dramatic impact, e.g., the worst possible scenario
  • Illustrating user journeys visually (hand-drawn preferred), focusing on key pain points/insights tied to opportunities/recommendations
  • Creating a comprehensive one-pager

This does not negate the need for complex artifacts. They remain crucial reference points for the team during specification and implementation.

complex journey map
Example of a detailed user journey (tool: JourneyTrack)

Using a journey mapping tool such as JourneyTrack is a great way to manage all the insights. It allows for easy filtering and drilling down without losing oversight. While a great working tool for the project team, it would be completely overwhelming for stakeholders, who need a higher-level summary.

Here we have a summarized version that was used during a workshop to discuss the pain points and opportunities.

simple journey map
Example of a simplified, high-level user journey

Using hand-drawn sketches is another powerful way to illustrate the activities and sentiments. In this case, we also created a video narration to fully immerse the audience and help them empathize with the persona.

Story board, too many tools
story board using tablet
story board usability testing
story board user interviews

3. Speak their language

I mentioned earlier that stakeholders are usually interested in business impact. They may care about the users’ needs, but in the end, it is all about “optimization” and “growth” – reducing costs, increasing revenues. What can you do? Speak their language. I have found “de-risking” to be a great argument for doing more research or early prototyping. 🙂

Here are a couple of examples of how to translate Designer needs into Business needs:

Designer speak Stakeholder speak
We should do more research.Investing in user research helps de-risk the project by validating assumptions early and avoiding costly rework later.
We want to improve usability.Improving usability increases efficiency, reduces support costs, and accelerates adoption.
Let's test this with users before we build.Early user testing helps us avoid spending time and money on features that won’t deliver value.
We want to understand user needs.By aligning the product with real user needs, we can increase customer satisfaction and drive retention.
The flow is confusing.Friction in the user journey can lead to drop-offs, longer task times, and increased operational burden.
We should co-create with users.Engaging end-users early helps build buy-in and reduces resistance to change during the implementation process.
We should simplify this interface.A simplified interface shortens onboarding time and reduces training and support costs.
We're designing for edge cases.By accounting for critical scenarios and exceptions, we reduce operational risk and ensure compliance.

4. Turn insights into actions

Yes! The research report is finally complete, and it even looks quite professional. You have presented it to the steering committee, and people were duly impressed. Now what? How can the research have an impact beyond show and tell? And how can your stakeholders demonstrate the value they are seeking? The truth is, building actionable insights starts much earlier in the journey. Here are a few tips I have collected over the years.

hikers in the snow

Design your research with the end goal in mind

Before you begin your collaborative journey, it's essential to align on shared goals and desired impact. Are you conducting pure discovery research, or is your aim to enhance an existing workflow? Is the problem clearly defined, or is it overly vague or broad? What are the potential outcomes and applications of this research?

Understanding this context is paramount. For instance, if your stakeholders require the research to build a business case, the results should be more visionary in nature. Conversely, if the purpose is to offer tactical recommendations for an already budgeted upcoming release, the outcomes can be more granular.

mountain climbers

Bring your stakeholders along on the journey

Yes, they are pressed for time, but keeping stakeholders engaged and interested throughout will build trust and confidence.

If interviews are not "sensitive" and interviewee privacy is not a blocker, creating short “highlight reels” can amplify the voice of the customer. Participating in well-organized, outcome-focused workshops will make them feel heard and give a sense of ownership. Additionally, a brief weekly newsflash from the research and design team can help address “impatient” stakeholders who would like to see insights immediately.

low hanging fruit

Identify the “low-hanging fruit”

Stakeholders are often skeptical of research unless it shows value quickly. Identifying and acting on low-hanging fruit — simple improvements with high impact — shows that research isn’t just academic; it drives change and helps bridge the gap between insight and action.

Creating these “early wins” helps stakeholders who are under pressure to deliver results. An early win from research (e.g., a clearer form, better onboarding) makes it easier to justify deeper and longer-term efforts.

photographer

Always visualize your recommendations

Let’s face it: wordy reports are ineffective. Why not use the superpower we have been given? Whenever possible, designers should aim to visualize relationships, causations, flows, and visions.

Visuals serve as a shared language, bridging the communication gap between stakeholders, designers, and engineers who often think and speak in different ways. This shared understanding simplifies grasping problems and aligning on directions.

While many stakeholders may not read a detailed report, they are highly likely to engage with an interface mockup or a high-level flow diagram.

country road

Value-oriented roadmap/action plan

A value-oriented roadmap or action plan is one of the most important outcomes of service design and research because it bridges the gap between insight and implementation. It translates what we’ve learned about user needs, pain points, and systemic challenges into a clear, shared path forward—prioritized by value.

Without a roadmap, insights risk staying abstract and getting lost in strategy decks. A value-oriented roadmap is a joint effort and forces the team to agree on what’s most important to do next, and why. Who is impacted, and what value (to the users AND the business) does this change or feature generate?

Finally, aligning around values, rather than simple features, helps a multi-functional team focus and avoid politics, tunnel vision, and wasted effort.

To sum it all up

When working with stakeholders, it's all about putting yourself in their shoes. You need to respect their time, simplify complexity, speak their language, and translate your findings into actionable steps they can take.

By designing your research with the final goal in mind, involving stakeholders at every step, identifying easy wins, presenting your recommendations visually, and crafting roadmaps that demonstrate real value, you'll ensure that your design work truly makes a difference.

In other words, the best service artifacts don’t just inform — they align, convince, and motivate people to act.

Related content

The post Service Design meets stakeholder needs appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/talk-to-your-data/ Tue, 20 May 2025 14:00:52 +0000 https://www.whitespace.ch/?p=17626 Dashboards are dead. Talk to your data instead. Why the age of static reporting is over — and what’s replacing it By Jesse Anton, CEO & Co-Founder of Whitespace Date: 20 May 2025 For over a decade, dashboards have been the centerpiece of data-driven decision-making. From slick PowerBI reports to sprawling Tableau workspaces, organizations have ...

Read more

The post Dashboards are dead. Talk to your data instead. appeared first on Whitespace.

]]>

Dashboards are dead. Talk to your data instead.

Why the age of static reporting is over — and what’s replacing it

By Jesse Anton, CEO & Co-Founder of Whitespace

Date: 20 May 2025

For over a decade, dashboards have been the centerpiece of data-driven decision-making. From slick PowerBI reports to sprawling Tableau workspaces, organizations have invested heavily in building pipelines, modeling layers, and front-end visualizations to help business users answer one simple question: what is happening in my business?

But here's the problem: dashboards are static. They’re built for yesterday’s questions, not tomorrow’s. They're expensive to maintain, often out of date, hard to find, and require specialized skills to construct and interpret. And in most organizations, they’re the domain of data analysts, not decision-makers.

That era is coming to an end.

Enter conversational analytics

New tools like Databricks AI/BI Genie, Sigma, ThoughtSpot, and Denodo are quietly rewriting the playbook. ERP and CRM providers, such as SAP and Salesforce, are integrating AI-driven data analytics features directly into their products. These platforms combine natural language interfaces with direct access to enterprise-grade data, enabling users to ask questions in plain English and receive answers on the fly. No static dashboards. No SQL. No waiting.

Imagine a regional sales manager typing, “What were my top three underperforming products in Q1 compared to last year?” — and getting an instant, accurate, and visual answer sourced directly from the lakehouse, without going through an analyst or digging through thousands of (stale) dashboards.

That’s not a gimmick. It’s a shift in how data is consumed.

Above: a demo we built using Denodo's AI SDK

Whitespace has been designing and building solutions for enterprise clients that leverage these conversational data platforms, bringing data closer to the users who need answers to real-time business questions and changing the experience of data consumption for thousands of employees in the process.

We've seen frustrated business users go from extracting data from PDFs into Excel – because their IT teams didn't have the bandwidth to give these users the reports or access they need – to a self-service paradigm where they (non-technical users) run highly complex SQL queries and generate sophisticated reports in seconds using natural language. Thanks to AI (and some proper UX!), work is being done more efficiently, and the employee experience is significantly better. It's a win-win.

If you want to learn more about what we've been building and how we might help your company take advantage of new AI tooling, get in touch!

Why this changes everything

1. Real-time, contextual answers

Dashboards are predefined. They answer questions you think you’ll have. But business rarely follows a script. Conversational AI tools let users explore tangents, clarify anomalies, and iterate in real-time. The result? Insights that are timely, relevant, and tailored to the moment.

2. No more dashboard sprawl

Most enterprises are drowning in dashboards — with thousands built over the years, few maintained, many redundant. They are hard to find, let alone consume. Conversational interfaces reduce the need for dozens of static views by letting users generate the specific output they need, on demand.

3. Business users become data explorers

The knowledge gap between technical teams and business decision-makers has always been a bottleneck. With tools like Genie, managers, marketers, scientists, and finance leads can query data directly, without knowing SQL or relying on middlemen. That’s not just efficiency — it’s empowerment.

4. Faster time to insight

Traditional dashboards rely on complex data pipelines: extract, transform, load, model, visualize. This takes time and requires coordination across teams. Conversational tools often tap into unified data platforms (like Databricks or Snowflake), reducing the number of steps between question and answer. A data virtualization (or logical data) layer like Denodo can further mobilize heterogeneous data sources while maintaining access control and abstracting the complexity of data architectures. Simpler means faster.

5. Lower cost of ownership

Maintaining pipelines and dashboards is expensive. Analysts spend too much time fixing broken reports and fielding ad hoc requests, and many big-box consulting companies make a living building and supporting data pipelines for their clients. (Tip: If you're looking to cut costs and boost efficiency, look at your consulting data management spend and then read this article again.) Conversational analytics shifts that load from building artefacts to enabling self-service — which means more time on strategy, less time on maintenance.

What this means for the enterprise

Despite the clickbait title of my post 😇, this isn’t about replacing dashboards overnight. Dashboards still have a role in tracking key metrics and providing consistent reporting. But for exploratory analysis, operational questions, and agile decision-making, the dashboard is no longer the best tool.

Instead, organizations should focus on:

  • Investing in unified, queryable data platforms like Databricks or Snowflake, and in data virtualization (aka logical data) layers like Denodo
  • Enabling semantic layers that make data comprehensible to non-technical users
  • Training business users to ask good questions — not just interpret charts
  • Reframing the role of analysts from report builders to strategic partners and data curators
  • Leveraging UX Research and Service Design to uncover opportunities where these new technologies can be applied to meet real user needs
Data virtualization
Data virtualization, such as the platform provided by Denodo, is a key enabler in the conversational AI era.

A conversation worth having

The future of data in the enterprise is not static. It’s dynamic, dialog-driven, and democratized. The winners will be those who make their data talk back — clearly, quickly, and to everyone who needs it.

So yes, dashboards are dead. Or at least, they’re retiring from center stage.

It's time to talk to your data instead.

Related content

The post Dashboards are dead. Talk to your data instead. appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/webinar-human-centered-digital-transformation-part-5/ Tue, 13 May 2025 10:54:46 +0000 https://www.whitespace.ch/?p=17591 Wired to Win Human-centered Digital Transformation WEBINAR SERIES (PART 5) Date: May 2025 Part 5: Design Thinking In the final part of our Human-centered Digital Transformation webinar series, guests Michael McKay (VP Digital Products at Novo Nordisk) and Roos Müller-Durieux (Service Design Lead at Whitespace) discuss the boosters and barriers to delivering real value with ...

Read more

The post Part 5 – Design Thinking in Digital Transformation appeared first on Whitespace.

]]>

Wired to Win

Human-centered Digital Transformation

WEBINAR SERIES (PART 5)

Date: May 2025

Part 5: Design Thinking

In the final part of our Human-centered Digital Transformation webinar series, guests Michael McKay (VP Digital Products at Novo Nordisk) and Roos Müller-Durieux (Service Design Lead at Whitespace) discuss the boosters and barriers to delivering real value with Design Thinking.

This session, designed for senior digital leaders and UX research practitioners, will focus on the value of Design Thinking—when organizations aim for real impact, beyond the ‘theater’.

Highlights include:

  • Debunking common myths about Design Thinking
  • The benefits of a Design Thinking mindset and the value of an expert
  • Challenges faced by internal vs. external experts

Video replay

Play Video
Related content

The post Part 5 – Design Thinking in Digital Transformation appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/ai-powered-web-app-builders/ Wed, 30 Apr 2025 06:00:35 +0000 https://www.whitespace.ch/?p=17521 AI-powered vibe coding tools A hands-on comparison By Nathalie Raux-Copin and Jean-Michel Claus Date: 30 April 2025 AI-powered tools like v0, Bolt, and Lovable enable designers and developers to generate interactive web app prototypes in minutes. These platforms create responsive, functional websites with just a prompt or a link to a Figma file, offering real ...

Read more

The post A hands-on comparison of AI-powered vibe coding tools appeared first on Whitespace.

]]>

AI-powered vibe coding tools

A hands-on comparison

By Nathalie Raux-Copin and Jean-Michel Claus

Date: 30 April 2025

AI-powered tools like v0, Bolt, and Lovable enable designers and developers to generate interactive web app prototypes in minutes. These platforms create responsive, functional websites with just a prompt or a link to a Figma file, offering real content, clickable links, and code. We conducted an experiment, feeding the same prompt into each tool to compare their performance and outputs.

Key takeaways

  • Easy to use and very fast to provide a result
  • Good prediction of user intention
  • Interactive UI and clean code
  • Useful for ideation and scaffolding prototypes

* Authors' note: This article focuses on three popular "vibe coding" tools. Many others are available, including Cursor, Replit, Figma Make, and Figma Sites. We will test and review these and other tools soon, adding our thoughts here as we go.

How AI-powered coding assistants work

Once you submit your prompt, these tools rapidly generate code and display the resulting web interface. The speed of execution is remarkable, often delivering a functional prototype within seconds. But beyond speed, how well do these tools interpret design intentions? And how should designers and developers incorporate them into their workflows?

The prompt we used

Build a responsive website with four pages: Home, About, Components, and Services. Use the attached image to create a hero banner of 1280 x 615 pixels in size. Place it below the navigation and use a headline that reads "What's under the hood" in large white font on top of the image. Under the hero, stack horizontally three tiles of the same size, separated by 20 pixels. Each tile should have a title, a subtitle, and two lines of paragraph with an ACTION button. The action button should use a bright orange with white text. The footer should link to http://whitespace.ch and should have a CONTACT US button.

Uploaded image
Photo by Anurag Challa on Unsplash

Results at a glance

v0 Bolt Lovable
Use the provided imagery✅❌✅
Responsive layout and navigation⚖✅⚖
Propose content in subpages✅❌✅
Support other frameworks, e.g., MUI✅❌❌

v0 review

Tech stack

React, Next.js, RadixUI, Tailwind CSS

Execution time

1:17 secs

User interface

v0’s interface consists of three main panels:

  • Left panel: Vertical navigation for starting new chats, accessing knowledge bases, and reviewing recent chats.
  • Middle panel: Prompt entry with a step-by-step execution log and feedback options (copy, retry, like/dislike).
  • Right panel: Preview and code display, with actions like share, fork, and deploy.

Preview evaluation

✅ Real content generation – Sections include meaningful, relevant text.

✅ Intention prediction – The layout adapts based on section names (e.g., a product-style layout for “Components,” a feature-style layout for “Services”).

⚖ Responsive design – Content adapts to different devices, but the menu does not convert to a hamburger menu on smaller screens.

⚖ Imagery – The provided portrait image is resized correctly but is unnecessarily repeated across pages.

✅ Interaction – Hover states work as expected.

❓ Accessibility – Keyboard navigation is missing, and contrast for active elements is low.

Code evaluation

✅ Works well if you stick to the initial libraries used, i.e. React, Next.js, RadixUI, Tailwind CSS.

✅ Works if you ask to use another React library, like MUI.

❌ Can not display a preview if you ask it to use traditional CSS on top of it.

❌ Generates an error if you ask to use a less common React library, e.g., Mantine.

❌ Fails if instructed to use other frameworks, for example, VueJS Composition API + traditional CSS or Svelte + traditional CSS. As for using another meta framework, it works if asked to use Astro instead of NextJS but could not provide a preview.

Bolt review

Tech stack

React, Tailwind CSS, Lucide React for icons

Execution time

47 secs

User interface

Bolt’s interface is streamlined into two main sections:

  • Left Panel: Prompt and execution log.
  • Right Panel: Preview and code, with export, deploy options, and a Supabase link. Navigation is collapsed by default.

Preview evaluation

⚖ Real Content Generation – Only homepage cards contain real content; other pages display titles only.
✅ Responsive Design – The menu converts to a hamburger menu on smaller screens.
❌ Imagery – The provided image was ignored; a random image was used instead.
✅ Interaction – Hover states work as expected.
❓ Accessibility – Keyboard navigation is missing, and contrast for active elements is low.

Code evaluation

✅ Works well if you stick to the initial libraries used, i.e. React and Tailwind CSS.
✅ Works if you ask to use another React library, like MUI.
❌ Does not work well if another framework is specified (for example, VueJS Composition API) or another styling solution.

Lovable review

Tech Stack

React, RadixUI, Tailwind CSS

Execution time

1:51 secs

User interface

Lovable has a two-column interface:

  • Left panel: Prompt entry and execution log.
  • Right panel: Preview and code, with a publish option and links to GitHub and Supabase.
  • Notable feature: A "What’s Next?" guide for first-time users, though feedback and retry options are missing.

Preview Evaluation

✅ Real content generation – Sections include meaningful, structured text.
✅ Intention prediction – Advanced adaptation based on section names (e.g., “About Us” includes mission, values, and team CTA; “Services” offers paths and a quote request CTA).
⚖ Responsive design – The menu converts to a hamburger but remains expanded, and sections stack vertically.
✅ Imagery – The provided image is correctly resized and darkened for readability, but it repeats across pages unnecessarily.
✅ Interaction – Hover states work as expected.
❓ Accessibility – Keyboard navigation is missing, and contrast issues persist.
Code evaluation
✅ Works well if you stick to the initial libraries used, i.e. React, RadixUI, Tailwind CSS.
❌ Cannot use anything outside of React as a framework or Tailwind CSS as a styling solution.

Code evaluation

✅ Works well if you stick to the initial libraries used, i.e. React, RadixUI, Tailwind CSS.
❌ Cannot use anything outside of React as a framework or Tailwind CSS as a styling solution.

Final thoughts

In summary, AI-powered tools like v0, Bolt, and Lovable are changing the game for rapid prototyping—delivering interactive, high-fidelity outputs in a matter of minutes. Our experiment confirmed just how intuitive, efficient, and impressively accurate these platforms have become. From predicting user intent to generating clean, clickable UIs and (almost) production-ready code, they’re proving to be powerful allies in the early stages of design and development. While they’re not replacements for thoughtful UX or polished design, they shine when it comes to ideation, experimentation, and building momentum fast.

Why designers should care

AI-powered web builders offer a rapid way to prototype ideas without needing development resources. This enables:

  • Faster iterations: Test multiple layouts and structures in minutes.
  • Improved collaboration: Developers receive real, functional code instead of static mock-ups.
  • Concept validation: Designers can quickly validate their ideas with stakeholders.

Why developers should care

Overall, code quality is good, and the workflow is easy if you fit in the chosen tech stack. Any divergence from these defaults can result in the refusal to generate alternative code, compilation errors, or just heavily impact workflow when previews are unavailable. There are some key benefits, though, even when used out of the default:

  • Rapid scaffolding of a project: Invaluable for generating project file structure, especially when the number of pages and components is large.
  • Rapid experimentation: Try different UI structures with minimal effort and see how the code adapts.
  • Learning & adaptation: Understanding AI logic can help refine prompt engineering for better results.

Considerations

  • Accessibility improvements: These tools need better keyboard navigation and contrast handling.
  • More customization options: Allowing users to refine generated content and layouts, widening the choice of frameworks.
  • Integration with design tools: Smoother handoff from Figma and other design platforms.

AI-powered web app builders are not replacing designers or developers but augmenting their workflows. As these tools evolve, they will become even more valuable in accelerating digital product creation.

Related content

The post A hands-on comparison of AI-powered vibe coding tools appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/ai-design-thinking/ Mon, 28 Apr 2025 08:34:27 +0000 https://www.whitespace.ch/?p=17513 Tapping into the world of AI with a Design Thinking approach Lessons learned on the frontiers of GenAI and Vectorial Search By Roos Müller-Durieux, Strategy & Service Design Lead at Whitespace Date: 28 April 2025 In Q1 2024, we completed a large-scale GenAI-driven project in the life sciences sector. The focus was on consolidating scattered ...

Read more

The post Tapping into the world of AI with a Design Thinking approach appeared first on Whitespace.

]]>

Tapping into the world of AI with a Design Thinking approach

Lessons learned on the frontiers of GenAI and Vectorial Search

By Roos Müller-Durieux, Strategy & Service Design Lead at Whitespace

Date: 28 April 2025

In Q1 2024, we completed a large-scale GenAI-driven project in the life sciences sector. The focus was on consolidating scattered customer data in different formats and for various purposes, and the goal was to “navigate and leverage vast amounts of collective intelligence related to Customer Experience data.”

The client had already done user research and defined the problem. Our role was to refine the problem statement, set a North Star vision, translate these into (visualised) opportunities, and create an actionable implementation plan. This project resulted in a proposal and implementation plan for a research tool that enables client stakeholders to search and interact with existing customer experience (CX) data.

I want to share three key challenges we faced and the lessons we learned from a Service Design perspective. Our internal team included me as the Service Designer and project lead, a UX designer, and an AI expert.

content curation in AI search
Content curation of search results

Challenge 1: Entering a new field can feel uncomfortable

Key Learning

Clear communication, active collaboration, and visuals are key when stepping into new areas.

Although I thought I had a basic understanding of AI, I quickly realized there were more layers of complexity than I expected. Integrating AI was new for the designer and me. For the tech expert, our Design Thinking approach was unfamiliar.

We enthusiastically jumped into the project but soon realized we needed to step back and address some friction. More than with other projects, we encountered the differences in our ‘language’, and we needed to make concepts concrete and include examples.

We work remotely and often strike a balance between meetings and allowing each person time to focus on their area of expertise. This time, we held extra collaborative sessions, using tools to visualize AI models (LLM setups and RAG models) and align them with product concepts and user journeys.

This collaborative and iterative approach helped us align the design and flow with user needs, while ensuring that everything is technically feasible and we have the knowledge to guide the implementation of the different elements.

content curation with annotations and feedback
Content curation screen design with annotations and feedback in Miro
scalable enterprise RAG
Scalable enterprise RAG solution with annotations

Our highly visual way of working proved critical and helped tackle the next challenges, too.

Challenge 2: Diverging design approach vs. tech feasibility

Key Learning

Use visuals to communicate the North Star vision and explore and define what’s technically possible, with clear annotations.

Establishing feasibility with AI differs from many other technologies; it is not just a matter of ‘do we have the required data’ or ‘is there a way to calculate the desired results’, etc. With AI, the function is a black box. The lack of explainability makes it challenging to establish feasibility.

Design Thinking often encourages divergent thinking, postponing feasibility discussions to avoid limiting creativity. However, when working with relatively new technology, there was a fear of overpromising what was possible. We sometimes got stuck in discussions of limitations.

What worked was collaborating closely with our internal designer to visualize opportunities and add technical annotations. These visuals helped us differentiate between:

  • NOW: Feasible with minimal effort, with minimal changes to the client's technical environment.
  • NEXT: More complex ideas needing further exploration and requiring implementation changes.
  • NOT (yet): Not feasible yet and out of scope.
content curation technical feasibility annotations
Technical feasibility annotations for content curation

This approach helped us move beyond the North Star vision, uncovering ideas the client hadn’t thought of but that added real value. We included this in a high-level presentation, connecting visuals with technical considerations. These technical considerations were linked to an in-depth feasibility study, guiding various implementation options and the requirements to ensure their feasibility.

Combining the two helped us align internally, gave the client a clear understanding of the topic, and helped the client take over ownership of the deliverables.

Challenge 3: Without a holistic understanding, there is a high risk that the implementation will fail

Key Learning

AI’s value comes when the entire flow is designed, and the required behaviour change is defined and guided.

Like many other projects, implementing AI is not just a matter of back-end changes. In this case, how employees interact with knowledge systems and how they save, search, and update files impact the value of the search functionality.

We learned that the project’s value increased when we designed the full user flow and included change strategies, like guidelines for data hygiene (e.g., when insights become outdated) and processes for saving and categorizing data.

Besides, a commonly heard myth that AI can “think” or be “creative” often popped up during the project. AI is highly effective at generating fake responses, regardless of their accuracy. We worked to debunk this myth, clarifying that AI’s role is to assist in gathering, organizing, and communicating information based on searches and queries.

Conclusion

AI is still a relatively new field, and its feasibility and complexity remain unclear to many. This lack of clarity creates a high risk of false assumptions and inflated expectations. Holistic Service Design, combined with a creative Design Thinking approach, is an ideal match. Its interactive and iterative nature helps bridge differences in professional ‘languages’ and aligns visionary goals with practical feasibility. At the same time, the holistic perspective supports clear communication of user expectations and the behavioral shifts needed for successful adoption.

How is your organization approaching AI implementation and building user trust in the outcomes? Curious about where and how we can support you? We’re always happy to discuss this evolving space!

Related content

The post Tapping into the world of AI with a Design Thinking approach appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/webinar-human-centered-digital-transformation-part-4/ Wed, 12 Feb 2025 17:06:46 +0000 https://www.whitespace.ch/?p=17429 Wired to Win Human-centered Digital Transformation WEBINAR SERIES (PART 4) Date: January 2025 Part 4: Discovery Research Welcome to Part 4 in our series on Human-centered Digital Transformation. In this episode, guests Voula Gkatzidou (AstraZeneca) and Julia Borkenhagen (Whitespace) discuss how discovery research creates new value and reduces risks across digital product portfolios in the ...

Read more

The post Part 4 – Discovery Research in Digital Transformation appeared first on Whitespace.

]]>

Wired to Win

Human-centered Digital Transformation

WEBINAR SERIES (PART 4)

Date: January 2025

Part 4: Discovery Research

Welcome to Part 4 in our series on Human-centered Digital Transformation.

In this episode, guests Voula Gkatzidou (AstraZeneca) and Julia Borkenhagen (Whitespace) discuss how discovery research creates new value and reduces risks across digital product portfolios in the enterprise.

Join us to learn how your organization can strategically and pragmatically scale discovery research to get more value from digital transformation investments.

Video replay

Play Video

This webinar for senior digital leaders and UX research practitioners will focus on how organizations successfully…

  • Generate and measure business value from quantitative and qualitative research
  • Communicate and build on discovery research insights across sprints, products, teams, and services
  • Accelerate impact by using insight management tools

Highlights include:

  • Challenges in knowledge retention, preserving context, and aligning stakeholders
  • How AstraZeneca’s centralized Research Ops model supports their global organization
  • Balancing centralized vs embedded team org models
  • Using tools like Dovetail, GenAI, and integrations with Jira and airfocus to get the most out of qualitative research
Related content

The post Part 4 – Discovery Research in Digital Transformation appeared first on Whitespace.

]]>
Page_6df62578 https://www.whitespace.ch/insights/blog/webinar-human-centered-digital-transformation-part-3/ Mon, 02 Dec 2024 09:20:25 +0000 https://www.whitespace.ch/?p=17386 Wired to Win Human-centered Digital Transformation WEBINAR SERIES (PART 3) Date: November 2024 Part 3: Service Design Welcome to Part 3 in our series on Human-centered Digital Transformation. Digital transformation programs are like a maze. Leaders, employees, and customers tend to get lost in them. This webinar introduces an approach that not only guides people ...

Read more

The post Part 3 – Service Design in Digital Transformation appeared first on Whitespace.

]]>

Wired to Win

Human-centered Digital Transformation

WEBINAR SERIES (PART 3)

Date: November 2024

Part 3: Service Design

Welcome to Part 3 in our series on Human-centered Digital Transformation.

Digital transformation programs are like a maze. Leaders, employees, and customers tend to get lost in them. This webinar introduces an approach that not only guides people through the maze but also tears down its walls – those proverbial organizational silos – to bring a holistic, clear, and systemic view to transformation efforts.

This approach is called Service Design.

Service Design benefits the organization and its stakeholders, providing both a mindset and toolset that will improve any digital transformation initiative.

Video replay

Play Video

This episode focuses on how Service Design can help organizations better understand customers’ and employees’ contexts to deliver more value to them and boost the impact of digital transformation investments.

Our guests, Antonio Iadarola (Service Design Lead for JPMorgan Chase), and Peter Horvath (Service Design and Strategy Lead for Whitespace) discuss principles, practices, and stories of how Service Design methods and mindsets have changed the organizations they work with.

Antonio and Peter introduce Service Design as a solution-agnostic, human-centered practice, focused on aligning stakeholders, services, and processes to deliver employee and customer experiences that create value for organizations.

Some key takeaways:

  • Bridging silos and collaboration are essential for digital transformation projects to succeed
  • This cross-functional collaboration must be incentivized and be focused on clear, joint incentives.
  • Successful service delivery works on the ‘backstage’ as much as the ‘frontstage’ of digitally-powered services.
  • Service Design is needed for off-the-shelf tools and internal audiences as much as bespoke, custom applications for external customers.
  • Service Designers’ toolboxes include discovery research, prototyping & testing, journey design and management, co-creation methods, as well as orchestration and process improvement approaches.
  • Service Design is increasingly becoming part of ongoing operations and management of digital transformation projects, through ResearchOps, DesignOps, and dynamic journey management tools.
  • Playbooks are important for self-sufficient operations of teams – and their continuous update is as important as their creation.

Some of the stories you will hear include:

  • A project where a complex trading platform for investment banking faced user issues, and through research and journey management the root cause was traced back all the way to the onboarding process.
  • A large telecommunications company where each department believed they were excelling in customer satisfaction – only for a journey-based approach to reveal that the customer experience suffered during the hand-off points between departments.
  • A European shopping center development, where executives were encouraged to participate in overnight prototyping sessions, and after initial hesitance the impact of this practice was recognized.

Webinar participants were asked to consider their organizations and explore the following:

  • How deeply do your senior decision makers and product/service teams observe and understand end-to-end journeys of employees and customers?
  • Who is incentivized to improve end-to-end experiences for your employees and customers?
  • How well are you using your understanding of employees and customers’ experiences to make strategic decisions?

Discovery Research and Design Thinking, key components of Service Design, are so important to successful digital transformation that we focus on them in upcoming episodes.

Related content

The post Part 3 – Service Design in Digital Transformation appeared first on Whitespace.

]]>