Designers who "don't want to write" are going to have a really tough time in the future.

And yes, I’ve heard this from enough design leaders that I believe this is a real problem.

A short thread... 1/8
If a picture is worth a thousand words and a prototype is worth a thousand meetings (love you @mikeindustries but more like 1:10 at best 😬), why are we still spending an inordinate amount of time trying to get people to understand what they are looking at? 2/7
Design has a context problem. It’s almost impossible to glean all the necessary context from an image or a prototype. You can get a “gut reaction” from someone, which has some value, but we need to be more specific. 3/7
Frame up the problem, the constraints, what requires feedback or approval—tell me what you want me to focus on! 4/7
Otherwise, people tend to fixate on the color of a button instead of determining if the new card layout solves the usability issue we identified (user need) and is intended to increase conversion (business need) — as an example. 5/7
The reality is that we still need to communicate the 10,000 micro-decisions that resulted in what stakeholders are looking at, how it solves the problem, and how it will impact the customer and the business. 6/7
So designers, if you are complaining about having to write, you might want to consider a different career path. 7/7
You can follow @jbrewer.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: