No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
==={{colored link|gray|Facet Elements}}=== | ==={{colored link|gray|Facet Elements}}=== | ||
''' | '''{{colored link|#00e664|Identity Elements}}''' | ||
*{{colored link|#00e664|Purpose}} | *{{colored link|#00e664|Purpose}} | ||
*{{colored link|#00e664|Story}} | *{{colored link|#00e664|Story}} | ||
*{{colored link|#00e664|Content}} | *{{colored link|#00e664|Content}} | ||
'' | ''{{colored link|#1450e6|Architecture Elements}}''' | ||
*{{colored link|#1450e6|Capability}} | *{{colored link|#1450e6|Capability}} | ||
*{{colored link|#1450e6|Process}} | *{{colored link|#1450e6|Process}} | ||
*{{colored link|#1450e6|Asset}} | *{{colored link|#1450e6|Asset}} | ||
''' | '''{{colored link|#ff005a|Experience Elements}}''' | ||
*{{colored link|#ff005a|Task}} | *{{colored link|#ff005a|Task}} | ||
*{{colored link|#ff005a|Journey}} | *{{colored link|#ff005a|Journey}} | ||
Revision as of 19:34, 25 January 2023
Enterprise Design with EDGY: a language for co-creating better enterprises
Colorem: a generative artwork by Fabio Catapano illustrating the EDGY Enterprise Design Facets
We never really understand each other, do we? The process architect ignored your well-researched customer journey map. The executive couldn't relate to your strategic product roadmap. The organisation designer failed to see the impact of that messed up application architecture you found.
If this sounds familiar, EDGY is for you. Introducing a simple but powerful graphical language everybody can understand and relate to, EDGY enables designers, architects and change makers to co-design a coherent enterprise by identifying the most impactful perspectives and translating between them. Well-defined, reusable Enterprise Elements turn a complex enterprise into a set of interconnected parts, ready to be designed, mapped and transformed.
We all love our maps and diagrams. It's time to make them talk to each other.