Towards a crap decision You have a thing. You would like to improve said thing. So, you ask a bunch of people what they think, giving more weight to those with relevant expertise. It’s a time-tested strategy. The pitfall here is that if the participants are aware of each other’s contributions, they will almost always automatically switch to consensus-building instead of providing their honest feedback. Worst case scenario: the bandwagon effect gathers steam and drives you toward a crap decision. Baldur Bjarnason, On online collaboration and our obligations as makers of software collaborationdecisions
Adding up to hair-brained I have for myself come to the point where I say that people or groups or governments make the decisions that make sense to them, even if they look totally hair-brained to me. My task then is to figure out the constellation of forces, the pushes and pulls, that in fact do add up to that hair-brained decision-making. Then we can go into the next iteration and say, "What can we do about the balance of the push and the pull that seems to result in totally non-constructive decisions?" Ursula M. Franklin, Every Tool Shapes the Task decisionsrationality
It was all change until the very last second Every work of literature is the result of thousands and thousands of decisions. Intricate, minute decisions—this word or that, here or where, now or later, again and again. It's the living tissue of a writer's choices, Not the fossil record of an ancient, inspired race. Verlyn Klinkenborg, Several Short Sentences About Writing A concept of style decisionscraft
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. Dorian Taylor, Skeleton, Organs, Circulation, Sinew, Skin decisions
Art and science "What the artist does is essentially the same as the scientist. In other words, what you do when you start to do a painting is that you begin with a basic idea, a hypothesis of what you're setting out to do. Then it's just a million yes-no decisions. You try something in the painting, you look at it, and you say, 'N-n-no.' You sort of erase it out, and you move it around a little bit, put in a new line; you go through a million weighings. It's the same thing in science, the only difference in the character of the product." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees sciencedecisionschoice
The complexity and the gray One thing I assume of age is weariness. Damned if I don’t get more tired every day. Tired of what I do, following arcs like lobbed rocks — the inevitability of truth. But the complexity and the gray lie not in the truth, but in what you do with the truth once you have it. Rian Johnson, Knives Out truthlifeagedecisions
The management strategy that saved Apollo 11 An Article by Matthew Ström matthewstrom.com In 1969, the people in charge of Apollo 11 trusted a 23-year-old engineer in a back room of mission control to make one of the most consequential decisions of this decade-defining mission. And they did so in seconds, without deliberating or debating. Next time you’re faced with a decision, ask yourself: how can this decision be made on the lowest level? Have you given your team the authority to decide? If you haven’t, why not? If they’re not able to make good decisions, you’ve missed an opportunity to be a leader. Empower, enable, and entrust them. Take it from NASA: the ability to delegate quickly and decisively was the key to landing men on the moon. Central planning gives poor resultsBeware SAFe, an Unholy Incarnation of Darkness managementdecisionstrust
Goodbye, Google An Article by Douglas Bowman stopdesign.com Without a person at (or near) the helm who thoroughly understands the principles and elements of Design, a company eventually runs out of reasons for design decisions. With every new design decision, critics cry foul. Without conviction, doubt creeps in. Instincts fail. “Is this the right move?” When a company is filled with engineers, it turns to engineering to solve problems. Reduce each decision to a simple logic problem. Remove all subjectivity and just look at the data. Data in your favor? Ok, launch it. Data shows negative effects? Back to the drawing board. And that data eventually becomes a crutch for every decision, paralyzing the company and preventing it from making any daring design decisions. Yes, it’s true that a team at Google couldn’t decide between two blues, so they’re testing 41 shades between each blue to see which one performs better. I had a recent debate over whether a border should be 3, 4 or 5 pixels wide, and was asked to prove my case. I can’t operate in an environment like that. I’ve grown tired of debating such minuscule design decisions. There are more exciting design problems in this world to tackle. designdecisionsdata
Collaborative Information Architecture at Scale An Article by Brandon Dorn www.viget.com Here I describe an approach for defining new information architectures for large organizational websites managed by many stakeholder groups. Broadly speaking, there are four general phases to the approach: Auditing. Begin by immersing yourself in existing content and encourage stakeholders to adopt a critical, audience-minded perspective of their content. Diagramming. Work with stakeholders to develop new conceptual categories that better serve audiences and organizational direction. Elaborating. Think through content in detail and test new categories against specific instances and edge cases. Producing. Prepare content teams for production using a shared database of new sitemap pages and editorial considerations that you’ve developed incrementally. Half of design is facilitation The Ladder of AbstractionA Pattern Language decisionsorganizationpatternsanalytics
Design System as Style Manual With Web Characteristics An Article by Dorian Taylor doriantaylor.com In my opinion, what makes a designer competent is precisely their ability to credibly justify their conclusions. If you can’t do this as a designer—no matter how successful your results are—then neither I nor anybody else can tell if you aren’t just picking things at random. What I am proposing, then, is no less than to make a designer’s entire line of reasoning a matter of permanent record. On the surface is the familiar set of prescriptions, components, examples and tutorials, like you would expect out of any such artifact. Attached to every element, though, is a little button that says Why? You click it, and it tells you. The proximate explanation will probably not be very satisfying, so you click on the next Why? until you get to the end, at which point you are either satisfied with the explanation, or you aren’t. The Design of Design decisionsdesignsystemsstyle
Brilliant Hardware in the Valley of the Software Slump An Article by Craig Mod craigmod.com It begins with craftPenn StationEdgesThe business case for craft
It begins with craft Something strange is happening in the world of software: It’s slowly getting worse. Not all software, but a lot of it. It’s becoming more sluggish, less responsive, and subtly less reliable than it was a few years ago. In some ways this is hyperbole. Objectively, we’ve never been able to do so much, so easily with our smartphones and laptops and tablets. We’ve never pushed more data between more places more readily. But while the insidious “worseness” I mention falls only in part on the engineering side of things, it falls harder on the more subjective, craft side of things, making it all the more worrisome. Why should we care about this? Because the majority of our waking hours take place within the confines of applications. A truth recently amplified by the covid pandemic. And I believe software used by millions (if not billions) has a moral duty to elevate the emotional and intellectual qualities of its users. That elevation begins with craft. Apps Getting Worse performancecraftsoftware
Penn Station In the same way that physical architecture can affect a mind, so too can software. Slower, less reliable software is like Penn Station: Sure, you can catch a transfer from one train to another but the dreary lowness of the place, the lack of sunlight or sensible wayfinding will make you feel like a rat, truculent and worthless, and worse: You’ll acclimate to that feeling and accept it as a norm. softwaretransportation
Edges Hardware has literal and metaphorical edges — it must be fully complete and largely bug free to ship. Software? It’s far more amorphous, like mist. Patches can be endlessly pushed. It never ends. Faulty hardware can destroy a company. Faulty software can be patched. The butterfly keyboard debacle may never be lived down. Even as I type on this improved Magic Keyboard, I can’t help but wonder: Did they really test this thing? I had three butterfly keyboards die on me, twice in the field. Not fun. Hardware failures live long in the mind.
The business case for craft macOS software that adheres to craft — Things or Carbon Copy Cloner or BBEdit or Sublime Text (which, despite not being “native native” feels so solid and so responsive you’re willing to overlook its quirks) or Bear or Alfred or iA Writer or Keynote (arguably one of the best pieces of macOS software of all time) or anything by Panic, heck, even Terminal or Quicken (which, against all rational expectations is just a joy to use)5 — exists in troves, the existence of such proves to the Slacks or Twitters or Adobes of the world that it’s not impossible nor rare to produce craft-oriented software in service to user fluency, and still make a profit. In fact, there’s a business case to be made for being craft- and fluency-focused. We’ve seen entire companies with business models that could be summarized as “Bloat-Free X” emerge in recent years. Affinity is bloat-free Adobe. Install Adobe Creative Cloud on your laptop and marvel at the no fewer than a dozen processes whirling around in the background for unknown purposes. It’s no surprise Affinity Photo and Publisher and Designer have taken off. Sketch’s main feature for many years was simply: Not Adobe. And the web! When you care — when you really give a shit — the web is awe inspiring. I still can’t believe Figma is web-native (also born from the Not Adobe camp). That an application can feel so powerful, so fast, so well-crafted and be fully web-based should be a kind of lighthouse-archetype for all other sites lost in a sea of complexity and muck and unnecessary frameworks. More profitable and a better buy craftbusinesswww