Last week I wrote about how the EMBL Corporate Design Sprint distilled a brand map into a brand structure. Today I’m writing the second installation with a post on how we’re using those core principles as the base for our brand information architecture (hereafter: IA) and a unique tool: the EMBL Triangle Key.
During EMBL’s 43 years it has grown in size, scope and geography. Today EMBL has six sites, many activity areas and focuses on five related but distinct missions.
There is a very strong unifying concept at the core of EMBL. However, during those years of growth a solid conceptual view of how websites, brochures and newsletter relate to each other has not yet been forged and adapted holistically.
As part of the Corporate Design sprint, we had need to set up a GitHub team and repositories to home and share work on the EMBL Design Language and Design Lab (more on what those are in a future post).
As an abstract task, it’s easy. Except what to name the team? What to name the repositories?