In addition to being thoughtful and skilled at designing digital experience, interfaces, and web products – I’m also very conscious of the “process of design”. These images represent some design boards for an analytics dashboard project I was working on. Sure I could have assembled my wireframes into Invision or just projected a click-through of my design work in PowerPoint… but I needed something more than just single-page views of my work to solicit feedback. The challenges I was having with this product re-design while working at Adobe was one where the engineers and product managers I was working with needed to understand the screens and interaction through the entire experience (system) – which prompted me to present my product ideas onto large gator boards, thus better representing the system I was designing. Too often, experience designers and interaction designers try to express system designs using design methods more suited for expressing the “interaction” between elements – they don’t scale big enough for large system thinking. Designing for systems means having design methodologies that can account for systems and scale.
Having all the pages and interactions available to see at once, helped my stakeholders and I: A) better evaluate the concepts from a technical point of view, and B) better account for system constraints. Additionally, because these wireframes were low-fi and printed on boards, I was able to carry them around with me from room to room and the feedback I collected was mobile and in context of the design work. I didn’t have to worry about anyone erasing my work from the whiteboards!