A Bias for Making

Jared Spool

February 5th, 2014

Today’s UIEtips article looks at the communication process designers and developers follow to bring designs to life. From the waterfall approach to an Agile method, the common goal is creating, building, and executing better designs.

If you or your team struggles with communicating design objectives and process with developers and other key players, then you’ll want join us for Ben Callahan’s full-day workshop on workflow on responsive web design projects at UXIM April 7-9 in Denver, CO.

Here’s an excerpt from the article:

Step into the Wayback Machine, Sherman, and set the dial to 1994. You’ll find me in a conference room, explaining to a room of developers and product owners (back then, we called product owners either product managers or business analysts) how we would design their new product in less than a week. The expression on their faces would be one of OMG! This dude is insane. (Though, “OMG” or “dude” wouldn’t be common parlance for at least another half decade).

We look at paper prototyping now and we think how quaint. Yet, back in 1994, it was a radical departure from established practice. In those olden days, design wasn’t done the way it is today.

Read the article A Bias for Making.

Does your team have a bias for making? Tell us about it below.

Add a Comment