Author Archives: daniel
i don’t care what you think about the entire body of work, any one who can put on a momma dress and grey wig and imitate patti labelle is OK in my book. also, i think my hair has looked exactly like that in the mornings. i know my dreams really DoOoOoooOoOooOooOooOooOOOoo come true. of …
Check out Miss Susan Boyle.
The first video wednesday is dedicated to Improv Everywhere. Never been more inspired.
blog to book
Lots of books get inspired by blogs. Why is a book a good thing for you (other than being a life-goal)? Are there methods of publishing outside the major publishers, or how do you work inside that system? What kind of information is book appropriate? The bottom line: Find something to say. Write good stuff. …
universal by design
This ain’t your mom’s accessibility panel. This is how universal design benefits everyone, not just those with disabilities. Universal design is “design that is so thoughtful that it works for everyone from the start instead of needing to be ‘patched’ for the disabled.” The idea is to make a more enabled future for everyone, not …
designers and developers:why can’t we all just get along?
I arrived at this session and it was SRO and full. I got some final ideas (after making it inside with 15 minutes to go): When designers push their vision out to “version 10”, it can cause tension with developers who are usually starting from the other end (i.e., Agile). Developers want to start small …
Continue reading “designers and developers:why can’t we all just get along?”
developing super senses: tools to know your users
holy crap, it’s andy budd. holy crap, it’s mark trammell. usability testing and user research should be at the beginning, middle, and end of of a project. regularly scheduled user research sessions can start interweaving user research into the entire process. Presenters Mark Trammell (Digg) Juliette Melton (User Experience Mgr, Lumos Labs) Nate Bolt (Bolt|Peters) …
Continue reading “developing super senses: tools to know your users”
wireframes for the wicked
There is not just one wireframe for a project. You need a wireframe for each type of documentation user: design team, business people (how does this affect them during day to day), managers (are the ideas good ones?), developers (details so they know how to build). Presenters Nick Finck (Principal / Director of User Experience, …