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
"Everyone wants to see themselves reflected in the research questions and findings."
Jerome “Axle” BrownHow to Use Self-Directed Learning to Ensure Your Research Insights are Heard and Acted Upon
March 11, 2021
"We’re showing people how to collaborate like crazy and how to fail gracefully."
Phil GilbertA Consistent Culture of Design
May 14, 2015
"Research is democratized: if you’re not democratizing, you probably don’t even realize everyone in your company is talking to users in different ways."
Kate Towsey Basel Fakhoury Oren Friedman Graham GardnerParticipant Recruitment and Management Tools
March 12, 2026
"Personas like Nick and Shelley help us understand different user attitudes towards music listening and skipping."
Sohit KarolDesigning Delightful Listening Experiences: Mixed Methods Research in the Age of Machine Learning
March 31, 2020
"Designing as a team means centering all the humans involved, not just the users."
Christopher Taylor Edwards Valerie RoskeDesign as a Team Practice, A Practical Guide to Cross-functional Collaboration
September 30, 2021
"We have to be deliberate about the long-term change we are creating and consider unintended consequences more explicitly."
Sheryl CababaExpanding Your Design Lens with Systems Thinking
February 23, 2023
"You need to come up with your own definition of design maturity based on your team’s understanding and context."
Francesca Barrientos, PhDYou Need Your Own Definition of Design Maturity
June 8, 2022
"People coming from agencies sometimes need help dropping bad habits like working at 2am or stressful environments."
Allison SandersOperating with Purpose
January 8, 2024
"It’s not about the diagram, it’s about the dialogue."
Saara Kamppari-Miller"Prototype" vs "Prototype"--Breaking Down and Rebuilding Our Understanding of What We Do
October 24, 2019
