The stronger the culture, the less process a company needs. When the culture is strong, you can trust everyone to do the right thing. People can be independent and autonomous. They can be entrepreneurial.
The simplest way to describe the design process is to divide it into two phases: analysis and synthesis. Or preparation and inspiration. But those descriptions miss a crucial element—the connection between the two, the active move from one state to another, the transition or transformation that is at the heart of designing.
See on dubberly.com
A wireframe is not the same as a prototype but even seasoned design professionals can sometimes get the two terms mixed up.
It’s time to set things straight once and for all, since (semantics aside) the difference between a wireframe and a prototype is actually quite substantial.
See on sixrevisions.com
If you have any experience with SharePoint as a document management platform today, you know that most organizations struggle to use it effectively. You’re also likely familiar with the negative impacts that typically result from using SharePoint ineffectively: a proliferation of sites, often on a proliferation of SharePoint versions, with no clear standards on what documents should (and shouldn’t) be stored there or how, no clear guidelines for users on how to classify their documen Topic: Information Management.
See on cmswire.com
The 10 Commandments of Typography
For those who believe that user experience can be handed off as a deliverable—likewireframes—this process might make a little sense. For UX practitioners, however, the end product is the user experience, so the UX team needs to be involved all along the way, up until the very end, ensuring the final product is the best experience it can be. The UX team can’t just pass off a concept and turn it loose. They have to stay involved. They have to lead, and not in the traditional authoritarian sense, but with humility and bycommunicating the importance of user-focused design to the entire project team.
See on uxmag.com