Killing the blank page
Summary
This talk is a case presentation about using generative AI and graph languages to come up rapidly with complex enterprise designs. We are using a repository based enterprise architecture tool and EDGY, an open source visual language, to feed GPT4 with context-rich queries. The resulting maps and models are ... wrong. But they have proven to be inspiring or even triggering for conversations across a diverse stakeholder community, and shortcut our way to a set of correct and useful models that inform design decisions. Moreover they can highlight blind spots and interrelationships previously unknown and thereby enrich the design process with minimal effort. Takeaways Recognising blank page moments in complex challenges How to embed context and an ad hoc Training in an LLM prompt How to make generate a web of coherent maps such as Journey, JTBD, Organization, Process Maps that cover a complete design related to a given challenge How to use these maps and how not to use them when co-creating with others When to keep tackling the blank page yourself instead
Key Insights
-
•
Designers often face the 'blank page' problem when tackling complex enterprise domains without sufficient research or domain knowledge.
-
•
Enterprise design requires making the invisible 'dark matter'—complex social, technical, and political systems—visible and understandable.
-
•
EDGY is an open source graph language that models enterprise complexity across three facets: customer experience, enterprise architecture, and organizational identity.
-
•
AI, particularly GPT-4, can augment designers by consuming structured repositories as context, reducing reliance on generic internet knowledge.
-
•
Using AI in enterprise design is more effective as augmentation of human creativity rather than automation or replacement.
-
•
Three AI collaboration modes identified are the 'jester' for provocative incorrect ideas, the 'sidekick' that integrates research context, and the 'matrix' that transforms knowledge across enterprise perspectives.
-
•
AI-generated diagrams are imperfect but valuable as starting points to defeat the blank page and stimulate discussion.
-
•
Inputting domain-specific research and insights into the AI prompt improves the relevance and quality of generated task maps.
-
•
Biases can be intentionally introduced in AI prompts to explore specific enterprise perspectives, such as organization design or brand identity.
-
•
Enterprise design must bridge silos by fostering knowledge sharing and cross-team collaboration, which AI and graph languages can facilitate.
Notable Quotes
"Designers are thrown into environments with experts that have decades of experience, and we have to come up with something relevant really quickly."
"The blank page can be terrifying because you don’t want stakeholders to laugh or say you got it all wrong."
"Behind simple tasks, there’s often big complexity hiding, especially in enterprise environments."
"We think the problem of 'dark matter' in enterprises is about making invisible things visible and bridging silos."
"AI is better seen as augmentation to make us more efficient, not automation to replace us."
"We use our model repository as context to help AI generate answers based on our specific enterprise knowledge rather than general knowledge."
"The jester mode throws something in your face, maybe wrong or uncomfortable, but at least it moves the conversation forward."
"AI-generated diagrams are usually not perfect, but they offer a better starting point than a blank page."
"If you say, ‘let’s look from an organization design perspective,’ AI reproduces the bias of that perspective in its output."
"Enterprise design is about sharing knowledge, analyzing it, improving it, and then consuming it to create better outcomes."
Or choose a question:
More Videos
"Picking the wrong size image can impact customer experience as much as what you see on screen."
Erin WeigelUX Lessons from running more than 1,200 A/B Tests
July 10, 2024
"Position your discovery work as de-risking investments rather than just fuel for innovation or empathy building."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"Regulations are design problems, not just technical ones, influencing how we create products and experiences."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Threat actors probably know your system better than you do and are looking for any entry points to exploit."
Heidi TrostWhen AI Becomes the User’s Point Person—and Point of Failure
August 7, 2025
"Culture eats strategy for breakfast, but culture isn’t something you can just buy or transplant."
Adam CutlerPeople + Places + Practices = Outcomes
June 8, 2016
"Buttons should be sized 48 pixels and above to avoid fat finger errors for seniors."
Rittika BasuAge and Interfaces: Equipping Older Adults with Technological Tools
February 23, 2023
"Accessibility ownership should never fall on just one person but be understood and shared across entire product teams."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"Practical ops is about getting stuff done because it’s our job to scale the organizational ability to design and amplify the work of designers."
Bria AlexanderTheme Two Intro
October 3, 2023
"These brand new practitioners can bring fresh perspectives and new ways of thinking to hopefully see current problems in a new light."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
