Musings on designing experiences & (re)engineering complexity
There is always a level of snark when looking at acronyms constituting various attitudes and responses this day and age. Some of those acronyms really are nothing more than language making itself more convenient for highly connected individuals. But every once in a while, there’s an acronym which comes along sounding on the surface like an arrogant response to or from a technologist to someone else. But when you peel beyond the surface, it speaks to a deeper structural issue. One in which it’s possible that the culture which has developed is actually incapable of sustaining itself.
Is every team organization constrained by what they are willing to pursue? Should knowledge be contained in the reputation or accessibility of those who are capable, or the systems that those teams in organizations maintain?
What is the culture of search? What is the culture of a manual?
For many years, have had the approach of designing software and processes which require very little explanation, but the joy was found in the story created in order to explain it. When someone says “let me Google that for you,“ are they also continuing with the story? Or, is the culture-response something more along the lines of “here’s how something could’ve been better designed for you, let me show you?“
A preface to this could be heard in arrogance — part of this composition is drafted before a few workshops where much of the work could be reduced to finding the answer in a search on YouTube. And yet, what people aren’t able to do, what some are paid to do, is to take the impersonal search engine and be a personal search agent. A personal search agent… let me google that for you.