The other way to build a massive tech company - doing it slowly A Podcast by Howie Liu www.secretleaders.com I like to think about the early years of [Airtable] as not only a great time for us to be patient and to get a lot of details right in the product. I think some of those details had to be done in a slow, deliberate way with a small team. You can't necessarily parallelize the design and development of a really detail-oriented product. detailsproductsslowness
the speed of God An Article by Alan Jacobs blog.ayjay.org [Andy Crouch] quotes the Japanese theologian Kosuke Koyama saying that “the speed of God” is three miles an hour because that was the speed at which Jesus moved through his world. So maybe, and I think this is one of the chief burdens of Andy’s book, what makes the most sense for us is to try whenever possible to move at the speed of God – and in that way refuse the offer of superpowers. Of course, this dovetails with a lot of things people have been writing lately about slowness, but what I like about Andy’s book is that it specifies why we can find ourselves responding so warmly to the possibility of slowness. What happens when we seek superpowers, and especially super-speed, is the sacrifice of what I want to call our proper powers – the powers through the exercise of which we (heart-soul-mind-strength) flourish in love. The brain is wider than the sky religionloveeuphonyslowness
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