Peer networking in the design community is thankfully not the rarity it used to be. Where there were onceinfrequent events based around an occasional high-brow lecture or overly self-conscious ‘networking opportunity’ (ugh), thanks to any number of driven and enthusiastic individuals we now have conferences, unconventions, informal meet-ups and increasingly relevant and compelling talks.
Industry peers aside though, our professional communications take place with a number of other key groups: colleagues, clients and end users. It’s worth considering how we handle these conversations.
A couple of years back the excellent UX Bookclub Belfast covered ‘How to Use Your Eyes’ by James Elkins. Each chapter delivered a brief but compelling insight into the expertise of others. By deconstructing (amongst other things) a culvert, an oil painting and the Periodic Table, the book revealed hidden mechanics and meanings, inspiring admiration for those whose contributions you might not otherwise consider.
Had there been a chapter devoted to the makeup of a graphic user interface or how a web browser renders HTML, no doubt most in the web design industry could have articulated something to inspire similar, admiring reactions from readers outside our sphere of activity. Indeed, expertise is (or should be) the minimum price of entry into the increasingly crowded Service Industry Club. A key question to consider then, is: how do we convey our knowledge to those we most need to engage with?
It just works
Almost everything we interact with or consume is the product of others’ technical mastery; their input is largely invisible, allowing us to go about our day without having to consider theories, systems or production processes. We care about these things, only in the sense that they just work without insight on our part.
The same goes for most experts we come into contact with. Be it a doctor or a car mechanic, we appreciate it when these people frame problems and solutions in the simplest possible simple terms, revealing more detail only when we request it.
In UX design, and I’d suggest pretty much every other design discipline, expertise should manifest itself in simplicity. Or to rephrase that, the science we incorporate into what we produce should be invisible to a non-expert; and we should be able to communicate our expertise while remaining intelligible to the listener.
Too often we trip over ourselves to prove our competence rather than communicate it effectively. In many ways our ability blinds us. We should not berate the client for, as designers are so fond of saying, “not getting it”. Others do not see as we do. We are the ones who have the responsibility of making sure clients “get it”… whatever “it” may be.
So perhaps the truest test of our competence is how simply we can share it. When we discuss a project’s challenges and potential solutions with a client, make it simple to understand. Communicate like a true expert.
One reply on “Practise like an expert, don’t communicate like one.”
Great article Rick, I fully agree having an open line of communication makes the project much easier and ensures you have a happy client.
I wrote a post in a similar vein: http://paulmaloney.net/speaking-geek