Hey there! Brian Dys here — I’m a visual and visceral person at heart. Ever since my mom lent me her old film camera, I fell in love with photography. All of my creative musings were exemplified by my second brain, the computer. This journey is a topsy-turvy ride of creative pursuits — from electronic music to UX design.
I enjoy every dull and wild moments of it — yes, this life of mine that I share with a woman named Jaycelle and a boy named Bryce. Take a peek into my kaleidoscope!
Innovation is not a skill. It is a culture, it is a mind set, a destination rarely reached, and the bountiful return on an investment made in the education of people unafraid.
Aaron Madolora, Chief Innovation Officer, Voyager Innovations
Wireflows. First time today that I’ve read about this fairly novel artifact. What I’ve been using (and sharing with my team) is called an Interaction Diagram—which, basically, is a Task Flow Diagram plus Wireframes.
Reading that article from Nielsen Norman Group, I’ve found out that there could be a high–fidelity wireflow—which in the example given, it showed a high–fidelity mockup.
As I understand it, there’s a distinction between a wireframe and a mockup. So, how would one call a “wireflow” that instead of wireframes, uses mockups as its visuals? Mockflow?
I’m taking a refresher on Information Architecture by reading Information Architecture: For the Web and Beyond by Louis Rosenfeld, Peter Morville, and Jorge Arango.
Information Architecture is as important as planning and strategizing in general—it’s one of the first steps when designing for many kinds of information systems and digital products.
Yesterday, our team attended a lecture in Agile and Scrum.
I realized that some of its principles are familiar based on our practices as designers.
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
That is, while there is value in the items on the right, we value the items on the left more.
—
