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
Figma's Engineering Values: Craftsmanship An Article www.figma.com Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users. What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless. craftsoftwarequality