Things Learned Blogging An Article by Jim Nielsen blog.jim-nielsen.com Eschew anything beyond writing the content of a post. No art direction. No social media imagery. No comments. No webmentions. No analytics...Imagine stripping away everything in the way of writing until the only thing staring you back in the face is a blinking cursor and an empty text file. That’ll force you to think about writing. ...[And] write for you, not for others. And if you can’t think of what to “write”, document something for yourself and call it writing. If there’s one thing I’ve learned about the mystery of blogging, it’s that the stuff you think nobody will read ends up with way more reach than anything you write thinking it will be popular. So write about what you want, not what you think others want, and the words will spill out. How to blogWrite the books you want to read bloggingwritinginterest
Skeleton, Organs, Circulation, Sinew, Skin An Article by Dorian Taylor I’m concerned with how I witness the work of user experience practitioners getting treated: like it’s just a set of motions toward a product’s all-important implementation, and one that we try to compress, due to its ostensible superfluity. Once the implementation is finished, the UX work appears to usually get discarded. Tracing the answer backThe UX coral reef ux
Tracing the answer back I submit that the materials that form the precursors to a product’s implementation have considerable value on their own. My vision is that I will be able to ask a question as mundane as one about the wording of a single button, and trace the answer all the way back to the overarching business strategy to see that it makes sense. decisions
The UX coral reef It isn’t a site, or a service, or even an identifiable product at all, but rather a system for creating a skin around and connective tissue between things like: Demographic studies Contextual inquiries Stakeholder and user interviews Surveys The business ecosystem Personas Scenarios Sketches, storyboards, wireframes Mockups, models and prototypes Email and IM conversations Meeting notes Content inventories and audits Concept schemes, taxonomies, thesauri A UI style guide A branding and visual identity guide A voice and tone guide A code style guide ...etc The individual elements of such a corpus represent the work of half a dozen specialist sub-disciplines, and are useful for realizing a product’s implementation. But if you hook them all up together, they merge to become a strategic artifact that transcends products and operates as a critical control surface for the business. This is because what such an artifact represents is a coral reef of deeply-considered and hard-fought decisions, and a story of the process that yielded them. connection