More easily asked than definitively answered Some design questions are more easily asked than definitively answered. Inventors are seldom at a loss for problems, and so they must choose which ones they will work on. Henry Petroski, The Evolution of Useful Things inventionquestionschoice
When Movable Type ate the blogosphere Here’s the crux of the problem: When something is easy, people will do more of it. When you produce your whole site by hand, from HEAD to /BODY, you begin in a world of infinite possibility. You can tailor your content exactly how you like it, and organize it in any way you please. Every design decision you make represents roughly equal work because, heck, you’ve gotta do it by hand either way. Whether it’s reverse chronological entries or a tidy table of contents. You might as well do what you want. But once you are given a tool that operates effortlessly — but only in a certain way — every choice that deviates from the standard represents a major cost. Movable Type didn’t just kill off blog customization. It (and its competitors) actively killed other forms of web production. Amy Hoy, How the Blog Broke the Web constraintschoicetools
Junctions The junction, or place of a break in transportation, has compelling importance for the city observer. Because decisions must be made at junctions, people heighten their attention at such place and perceive elements with more than normal clarity. This tendency was confirmed so repeatedly that elements located at junctions may automatically be assumed to derive special prominence from their location. Kevin Lynch, The Image of the City citieswayfindingchoice
What kind of world it's going to be The wonderful thing about living in a world of our own creation is that we get to choose what kind of world it's going to be—at least in principle. But the promise is meaningful only if a broad enough "we" can be engaged in the process. At present, mechanisms and democratic institutions for making collective decisions about the deployment of technology are hopelessly cumbersome. How can anyone make a sensible choice without being able to weigh one alternative against another? Brian Hayes, Infrastructure: A Guide to the Industrial Landscape democracypoliticsclimatechoice
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
What Le Corbusier got right about office space An Article by Tim Harford timharford.com In the 1960s, the designer Robert Propst worked with the Herman Miller company to produce “The Action Office”, a stylish system of open-plan office furniture that allowed workers to sit, stand, move around and configure the space as they wished. Propst then watched in horror as his ideas were corrupted into cheap modular dividers, and then to cubicle farms or, as Propst described them, “barren, rathole places”. Managers had squeezed the style and the space out of the action office, but above all they had squeezed the ability of workers to make choices about the place where they spent much of their waking lives. ...It should be easy for the office to provide a vastly superior working environment to the home, because it is designed and equipped with work in mind. Few people can afford the space for a well-designed, well-specified home office. Many are reduced to perching on a bed or coffee table. And yet at home, nobody will rearrange the posters on your wall, and nobody will sneer about your “dog pictures, or whatever”. That seems trivial, but it is not. workpersonalityownershipmodularitychoice
In Praise of Small Menus An Article by Rachel Sugar www.grubstreet.com The best way to experience a restaurant, I have always felt, is by eating exactly what it wants to feed you. I do not want choices. I want the best thing. A restaurant might have five or ten best things, but it cannot have 45. There are many infuriating things about the world, but one of the more fixable is the sensation of acute regret from having ordered wrong. Why are there possibly wrong orders? Recently, I was at a fancy restaurant with great pastas and bad pizzas. So cut the pizzas! A kitchen that focuses on its strengths turns out consistently excellent things, even if that results in fewer total things. fooduxchoicesimplicity
Become a person who actually does things An Article by Neel Nanda www.lesswrong.com If there’s one thing you take from this post, let it be this: notice the next time you agonize over a choice, or pass up an opportunity. And ask yourself not “what is the right decision” but rather “which decision will get me closer to the kind of person I want to be”. wisdomchoiceprogress
The Fidelity Curve An Article by Ryan Singer m.signalvnoise.com How do we choose which level of fidelity is appropriate for a project? I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing. I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing. Four levels of fidelityTime to build versus confidence gained prototypesinterfaces
Four levels of fidelity Suppose we have four levels of fidelity… Rough sketch (on paper or an iPad) Static mock-up (eg. Photoshop or Sketch) Interactive mock-up (eg. Framer, InVision) Working code prototype (HTML/CSS, iOS views) Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained Show image 0 Show image 1 Show image 2 Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it. Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.