Design for Software: A Playbook for Developers

Part II: Design Thinking

It’s time to move on to the meat and taters of this book. Changing gears a bit, the next few chapters explore the nitty-gritty of designing software (and any type of design for that matter). I elaborate on specific techniques and methods that are commonly found in most traditional forms of design but that are largely absent from the technology world. I share the specific techniques I use on my personal projects and examples of how to incorporate these tactics into the software design process. I consider these techniques to be of high importance in the design process, and for advocates of user experience, I’m obliged to say they’re required. You will probably be familiar with some of the content, but given the digital context, the contents should provide a fresh perspective on how to incorporate specific tools and techniques into your day-to-day work.

In my office, I often see folks wrestling with wire harnesses, soldering irons, Arduino controllers, and RFID chips. Most of the time, I find an engineer hacking these things together and my piqued interest prompts me to ask, “What’s this crazy mess all about?” And the usual conversation begins with, “I have this awesome idea; I want to build [insert nerdy idea here].” To be honest, the idea is usually quite insightful and clever. However, these brainy concepts are seldom accompanied by a design direction or a rough sketch of how they will actually be used. When I check in a couple of weeks later to see how ...