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
"Continuous feedback is anonymous and focused on teammates’ goals to help keep focus on what matters most."
Ignacio MartinezFair and Effective Designer Evaluation
September 25, 2024
"Preparation is key: pilot studies and a data analysis plan before launching ensure data quality and study success."
Amelia ColeData-Prompted Interviews
December 17, 2021
"2020 was challenging but joyful; it was a place where people could be authentic and talk about burnout and attrition."
Kristin SkinnerTheme 1 Intro
September 29, 2021
"I find the existing patterns in my product and use those because it’s easier to bring things back in."
Billy CarlsonTips to Utilize Wireframes to Tell an Effective Product Story
June 6, 2023
"Feeding the power of self-definition to other groups replicates existing power hierarchies and must be avoided."
Yolanda RankinBlack Feminist Epistemology as a Critical Framework for Equitable Design
March 11, 2021
"To reclaim our value, we must regain our agency and renew our passion as researchers."
Eduardo OrtizTheme 3 Intro
March 13, 2025
"We wrote our toolkits in plain English so people understand the tactics without getting lost in jargon—they can learn the jargon later."
Toby HaugDiscussion
June 9, 2017
"To me, sweating the pixel means paying attention to the details of interactions and keeping our eye on quality as designers."
Joseph MeersmanSweating the Pixel: Scaling Quality through Critique
June 10, 2021
"Design is problem-solving, and part of the problem is the environment in which you’re trying to work."
Bob BaxleyLeading with Design Operations Past and Present
December 19, 2019
