Rapport "Bob's rapport with the workers is extraordinary. Reminds me of something Noguchi once pointed out about Bernini during the days he was building St. Peter's in Rome: how what made him so special, aside from his own obvious gifts, was his ability to extend himself through the work of others, to get them on his side and working in his direction." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees leadershipteamwork
Design Leadership Truisms An Article by Peter Merholz www.petermerholz.com PEOPLE ARE NOT THEIR JOB TITLES. TEAM MEMBERS ARE NOT “RESOURCES”. PEOPLE WORK BEST WHEN THEY CAN BE THEIR FULL SELVES. YOU CANNOT CALCULATE AN ROI FOR DESIGN. FRAMING THE PROBLEM IS MORE IMPORTANT THAN SOLVING THE PROBLEM. (DESIGN) LEADERSHIP IS MORE TALKING THAN DOING. YOU’LL DO A BETTER JOB IF YOU LIGHTEN UP IF YOU HAVEN’T PISSED SOMEONE OFF, YOU’RE NOT DOING YOUR JOB RIGHT. NO ONE OUTSIDE YOUR TEAM UNDERSTANDS WHAT IT TAKES TO DO GOOD WORK. THE OUTCOMES ARE BETTER WHEN EVERYONE IS A DESIGNER. AGILE TRANSFORMATIONS ARE HOSTILE TO GOOD DESIGN. WHAT A DESIGN TEAM NEEDS MOST IS A CLEAR SENSE OF PURPOSE. YOU ARE ON THE FRONT LINE OF A GLOBAL WAR FOR TALENT. EVERYONE APPLYING FOR A ROLE HAS AN INFLATED TITLE. INTERVIEWS ARE A POOR WAY OF ASSESSING CANDIDATES. DESIGN EXERCISES ARE A BAD INTERVIEWING PRACTICE. YOU WILL NEVER HAVE ENOUGH DESIGNERS. YOU WILL NEVER HAVE ENOUGH TIME. THE SKILLS THAT GOT YOU HERE ARE NOT THE SKILLS THAT WILL CARRY YOU FORWARD. Truisms designleadershipteamwork
Silicon Valley Product Group A Website by Marty Cagan svpg.com The best companies go about building great products differently. Silicon Valley Product Group (SVPG) was created to share lessons learned and best practices about how to build innovative products customers love softwareleadership
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