Any good digital designer knows that architecture and hierarchy have a very significant influence on how people behave on a website or app. Yet getting designers and orgs to truly focus on architecture design is so hard. Why is that?
-
Most orgs are obsessed with "transformation" and delivering "cool" things but try to skip straight to the shiny deliverables without laying the groundwork - ending up with a house of cards essentially.
They fail to realise that when you start with 12 months of unsexy work, the pace at which you can then deliver "cool" shiny things increases *exponentially*. "Yes, we can now quickly ship Cool Thing X because we did Data Work Y six months ago."
-
-
And they could keep shipping cool things without having to keep going back to the hard work. The hard work is like a building’s foundation and load bearing posts. Within those constraints you can do a lot over and over.
-
So much this.
End of conversation
New conversation -
-
-
When was the last time any CEO ever asked for deliverables of taxonomies, hierarchies, classification systems, content models, ontologies? It's all home page this, chatbot that etc etc.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.