“For practicing User Experience Designers, one of the most important laws isn’t Fitts’s Law, which helps us understand how to design interactive elements. Nor is it Hick’s Law, which describes how long people take to make decisions.The pull-no-punches opening to Jared Spool’s article today on
It’s Sturgeon’s Law, which tells us that 99% of everything is crap.”
5 indispensible skills for UX mastery, which he lists as:
Sketching, Storytelling, Critiquing, Presenting, and Facilitating.
I like that list.
case study
Speaking Up Effectively
In a recent team meeting, we talked about how our circle of influence is different—wider—than our circle of responsibility. This reminded me of something I posted three years ago almost to the day, so I decided to re-post it here, to remind myself to “speak up” outside my role—but to do so appropriately.
In our department, we’re constantly encouraged to “Speak Up” as one of our core “cultural beliefs.” Sounds straightforward enough. But what factors affect how and when you should speak up? After being asked to present some thoughts on this topic to our design team, I decided that a lot of it depends on my role, how much I really know, and who I’m talking to. As in so many things, Context is King. Here’s a diagram of how I broke it down:

My Role. The first thing to ask is whether the thing I want to address falls within the responsibilities of my role. Not that I can’t speak up outside my role – in fact sometimes that is when it is most important, because within my role I have greater freedom of action anyway. Within my role, I can often dispense with talk – I just decide and do (though if I’m smart, I will clearly explain my decisions to those who care). When I speak up outside my role on the other hand, I am necessarily treading on someone else’s turf; if I want to be effective, I’d better watch my tone and respect their role, even if I’m an expert.
What I Know. The next thing to ask is how much I really know about the topic I want to address. Sometimes, especially within my role, I know a lot; I can be more confident, assertive, and insistent. I can propose, decide, and strongly advise. But sometimes I don’t know that much – even within (hopefully small) areas of my own role. That should change the way I communicate; I should be asking questions, taking feedback, helping others brainstorm, generating ideas for my own or others’ exploration.
Others’ Roles. Sometimes an issue is clearly my responsibility, but often it falls under another role or into a shared stewardship. “Speaking Up” in this case calls for diplomacy and negotiation. This is true even if I happen to know more about the subject at hand; I can propose solutions, but can’t run roughshod over another co-owner. Likewise, if I don’t know as much as the other person, it is still my job to carefully consider and ratify decisions relating to my role; I can’t abdicate my responsibility and then point a finger the other way if things go wrong.
Others’ Knowledge. Sometimes other people know more than me – even within my own role. This is where humility and the ability to take counsel is needed. “Speaking Up” here might mean asking for help when I need it. On the other hand, sometimes others know less than me – even within their role. Effective persuasion is key.
When I look at how these factors overlap, I realize that “speaking up” effectively is a lot more nuanced (or should be more nuanced) than just always “speaking your mind.” Depending on the context, “speaking up” could mean pronouncing, proposing, advising, negotiating, questioning, reviewing & ratifying, or even admitting that I don’t know everything I should. (In fact, this last can be the most courageous and important form of “speaking up”.)
Of course – as my team pointed out today – all of this begs the question of whether something is even worth discussion. If it’s not important, if the right people are not in the room, or if the time just isn’t right, then don’t Speak Up – just Shut Up, at least for now.
“Tweet happens.”Overheard in scrum this morning, in discussing whether Twitter would be a good way to keep an extended team in the loop.
Terry Coatta makes a good case for why self-documenting code is often insufficient to a complete understanding of the code.
“You’ve got to nail the human-to-human interaction before you even think about human-computer interaction.”Jason Lynes discussing the importance of communication with our new intern (and we’re still hiring, by the way)
And as an alumnus, I’d highly recommend the University of Washington’s Technical Communication program as a great way to transition from “pure” TC into usability or design.
As a designer who started out as a technical writer, I enjoyed reading Theresa Putkey’s article on Using Technical Communication Skills in User Experience . Whenever people ask me how or why I got into design with an English degree, now I can point them here instead of re-tracing my own circuitous route to design nirvana. (My own career history also included a very satisfying 5 year stint as a usability engineer, but the general career path and motivations are the same as outlined here by Theresa.) A good read for anybody whose job is essentially “explaining why it doesn’t work right”—and is tired of it.
“Good designers decorate.Cameron Moll, 9 Skills presentation
Great designers communicate.”
“Speaking Up” in the context of my role and how much I know