A sensitively tailored combination of modes Efficiency is produced not by the sort of movement monoculture of cars-only American cities but by a sensitively tailored combination of modes sited to exploit the particular efficiencies of each and providing useful duplication and alternative. Michael Sorkin, 20 Minutes in Manhattan efficiencytransportation
Conversations, not commandments Good software comes from a vision, combined with conversations not commandments. In a craft-focused environment, care for efficiency, simplicity, and details really do matter. I didn’t leave my last job just because I wanted to make something new. I left because I wanted to make it in a way I could be proud of. Pirijan Ketheswaran, Why Software is Slow and Shitty pketh.org detailscraftsimplicityefficiency
Dwelling densities and diversity The reason dwelling densities can begin repressing diversity if they get too high is this: At some point, to accommodate so many dwellings on the land, standardization of the buildings must set in. This is fatal, because great diversity in age and types of buildings has a direct, explicit connection with diversity of population, diversity of enterprises and diversity of scenes. Among all the various kinds of buildings (old or new) in a city, some kinds are always less efficient than others in adding dwellings to the land. A three-story building will get fewer dwellings onto a given number of square feet of land than a five-story building; a five-story building, fewer than a ten-story building. If you want to go up far enough, the number of dwellings that can go onto a given plot of land is stupendous—as Le Corbusier demonstrated with his schemes for a city of repetitive skyscrapers in a park. But in this process of packing dwellings on given acreages of land, it does not do to get too efficient, and it never did. There must be leeway for variety among buildings. All those variations that are of less than maximum efficiency get crowded out. Maximum efficiency, or anything approaching it, means standardization. Jane Jacobs, The Death and Life of Great American Cities efficiency
The mirror-image economy When we enter the world of refuse and waste, we cross over into a mirror-image economy. In the "normal" world, we pay to acquire things; on the other side of the looking glass, we pay to get rid of them. Junk isn't merely worthless; it has negative value. A chemical engineer once told me about a recent improvement in a manufacturing process; by fine-tuning a chemical synthesis he had increased the yield of a certain commodity from 98 percent to 99 percent. I congratulated him, but I couldn't help remarking that this seemed like a rather paltry improvement. "Ah, you miss the important point," he said. "The amount of waste goes from 2 percent down to 1 percent. It's cut in half. We save tremendously on disposal costs." Brian Hayes, Infrastructure: A Guide to the Industrial Landscape wasterecyclingtrashefficiencyeconomics
Taylorism “In the past the man has been first. In the future the system must be first.” — Fred W. Taylor Taylorism was a way of thinking that came at the expense of the workers’ own knowledge of their system. Taylor summed up his philosophy thus: “It is only through enforced standardization of methods, enforced adoption of the best implements and working conditions, and enforced cooperation that this faster work can be assured. And the duty of enforcing the adoption of standard and enforcing this cooperation rests with the management alone.” The unscripted practices of the old offices would remain, but as a kind of subterfuge: in the future, a leisurely pace wouldn’t be the norm; time would not be given, but stolen. Nikil Saval, Cubed systemsefficiency
Efficiency is the Enemy An Article fs.blog Many of us have come to expect work to involve no slack time because of the negative way we perceive it. In a world of manic efficiency, slack often comes across as laziness or a lack of initiative. Without slack time, however, we know we won’t be able to get through new tasks straight away, and if someone insists we should, we have to drop whatever we were previously doing. One way or another, something gets delayed. The increase in busyness may well be futile. It’s Time to Embrace Slow Productivity efficiencyproductivitywork
Muda, Muri, Mura An Article mag.toyota.co.uk Eliminating waste is the key to efficiency – in the Toyota Production System, this is termed as: Muda (waste), Muri (overburden), and Mura (irregularity). productionwastemanagementefficiency
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.