Software & Digital Products
A late change in requirements is a competitive advantage
Make the change easy
Software often feels inevitable
Growing in the correct way
It begins with craft
So insufficiently palimpsestic
Spatial software references
- Nototo
A great painting has to be better than it has to be
This sounds like a paradox, but a great painting has to be better than it has to be. For example, when Leonardo painted the portrait of Ginevra de Benci in the National Gallery, he put a juniper bush behind her head. In it he carefully painted each individual leaf. Many painters might have thought, this is just something to put in the background to frame her head. No one will look that closely at it.
Not Leonardo. How hard he worked on part of a painting didn't depend at all on how closely he expected anyone to look at it. He was like Michael Jordan. Relentless.
Relentlessness wins because, in the aggregate, unseen details become visible. When people walk by the portrait of Ginevra de Benci, their attention is often immediately arrested by it, even before they look at the label and notice that it says Leonardo da Vinci. All those unseen details combine to produce something that's just stunning, like a thousand barely audible voices all singing in tune.
Great software, likewise, requires a fanatical devotion to beauty. If you look inside good software, you find that parts no one is ever supposed to see are beautiful too.
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
Jacked in
In digital design, products and services are frequently imagined and implemented placelessly: as if the consumer were jacked into The Matrix, and considering this product or that product from among an infinite set of choices at an infinitely-provisioned mercantile. The things we make are good, by this way of reasoning, if they fit the market’s demand.
Losing meaning
The people who’ve proven that they can make very good individual products with the radical focus of a spotlight seem to be pushed ever further from making good ecosystems.
Products are being made “consistent” with the application of so-called “design patterns,” and rather than bringing coherence to these various touch-points, the painting-on of interface standards and interaction patterns did something far less valuable.
Rote consistency, in the way many seem to be going about it (Material Design being just one example), is at odds with making things be good. It simplifies what needs to remain complex.
Always, when simplification is underway, meaning is being lost.
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.
The Design of Design
A Book by Frederick P. Brooks, Jr.Visualizing Algorithms
An Article by Mike BostockManifesto for Agile Software Development
A DefinitionWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Stop Drawing Dead Fish
A Talk by Bret VictorThe Future of Programming
A Talk by Bret VictorDesign Links & Learning
A Blog by Nick TrombleyCollections of articles, links, and other material from around the web, relevant to software design and engineering.
Ensuring Excellence
An Article by Marty Cagan…in so many of the best product companies there is an additional dimension that goes beyond individual empowered product teams, and even goes beyond achieving business results.
It has to do with ensuring a level of what I’ll refer to here as “excellence” although that is clearly a very ambiguous term.
Over the years, this concept has been referred to by many different names, always necessarily vague, but all striving to convey the same thing: “desirability,” “aha moments,” “wow factor,” “magic experiences,” or “customer delight,” to list just a few.
The concept is that an effective product that achieves results is critical, but sometimes we want to go even beyond that, to provide something special.
Maybe it’s because we believe this is needed to achieve the necessary value. Maybe it’s because the company has built its brand on inspiring customers.
Often this dimension shows up most clearly in product design, where functional, usable but uninspiring designs can often achieve our business results, but great design can propel us into this realm of the inspiring.
On online collaboration and our obligations as makers of software
An Essay by Baldur BjarnasonIs it the notetaking system that’s helping you think more clearly? Or is it the act of writing that forces you to clarify your thoughts?
Is it the complex interlinked web of notes that helps you get new ideas? Or is it all the reading you’re doing to fill that notetaking app bucket?
Is all of this notetaking work making you smarter? Or is it just indirectly forcing you into deliberate, goalless practice?
In Search of Organic Software
An Article by Pirijan KetheswaranTwo different kinds of farms can grow vegetables. One is a factory farm built for scale, and the other takes the time to grow more expensive but healthier plants without pesticides.
Will everyone appreciate the difference? Of course not, but the latter plants are labelled ‘organic’ to give us the information and the choice, so that those of us who do care can make better decisions.
So maybe we should have ‘organic’ software as well, made by companies that:
- Are not funded in such a way where the primary obligation of the company is to 🎡 chase funding rounds or get acquired (so bootstrapping, crowdfunding, grants, and angel investment are okay)
- Have a clear pricing page
- Disclose their sources of funding and sources of revenue
Reflections on Software Performance
An Article by Nelson Elhage- Performance is a feature
- Performance changes how users use software
- Performance needs effort throughout a project’s lifecycle
- Architecture strongly impacts performance
- Performance isn’t just about hot spots
- Performant foundations simplify architecture
…we underrate performance when designing and building software. We have become accustomed to casually giving up factors of two or ten or more with our choices of tools and libraries, without asking if the benefits are worth it.
Undoing the Toxic Dogmatism of Digital Design
An Essay by Lisa Angela- Design educators and industry leaders have never reached a consensus about what comprises a “good enough” foundational education for digital design.
- We do not properly retire methods (or ways of conducting them) that have been shown to be ineffective.
- Design team seniority levels are meaningless.
- We’ve collectively lost the safety (and subsequently the desire) to explore and fail.
- We afford well-known design leaders too much power to dictate how design is discussed and conducted.
- We have no ethical standards.
- Inclusive design and accessibility are afterthoughts — both in design education and in practice.
The things that you’re meant to do
A Quote by Josh WardleI used to work in Silicon Valley, and I’m aware of the things that, especially with games, you’re meant to do with people’s attention. You’re trying to capture as much of people’s attention as you can. So that involves things like endless play, or sending them push notifications, or asking them for sign-up information.
And philosophically, I enjoy doing the opposite of all those things, doing all the things that you are not meant to do, which I think has bizarrely had this effect where the game feels really human and just enjoyable. And that really resonates with where we’re at right now in the world and with COVID, and then also we’re trying to figure out, what is tech? What has tech become? I think that really resonates with people, and no ads—well, no monetization. People ask me a lot about these things, and it was like, I was literally just making a game for my partner, and I made some decisions that we would like.
I don’t believe in Zoom fatigue
An Article by Matt WebbIt’s not Zoom fatigue, it’s Zoom whiplash.
It’s a hunch. I can’t prove this.
The trick to get around this is to move smoothly up and down the gradient of social interaction intensity, never dropping below a basic floor of presence: the sense that there are other people in the same place as you.
Instead of having two modes, “in a call” and “on my own,” we need to think about multiple ways of being together which, minimally, could be:
- In a video call
- In an anteroom to a video call, hearing the sound of others
- In a doc together
- On my desktop but with the sense that colleagues are around
And the job of the designer is to ensure that their software ensures the existence of these different contexts, instead of having the binary on-a-call/not-on-a-call, and to design the transitions between them.
Spatial Software
An Article by John PalmerScales of cities, scales of software
An Article by Linus the SephistAmerican cities seem like a product of industrial processes where older European cities seem like a product of human processes. This is because most American cities were built after and alongside the car and the industrial revolution – the design of cities took into account what was easily possible, and that guided the shape and scale of everything.
Software has similar analogues. There are software codebases that feel much more industrially generated than hand written, and they’re usually written in automation-rich environments fitting into frameworks and other orchestrating code.
…But despite the availability of cars, I still much prefer the scale and ambiance of European, human-scale cities, because ultimately cities are places humans must inhabit and understand. In the same way, I still much prefer the scale and ambiance of hand-written codebases even in the presence of heavy programming tooling, because ultimately codebases are places humans must inhabit.
Driving engineers to an arbitrary date is a value destroying mistake
An Article by Gandalf HudlowWhat happens when you apply date pressure to software engineers working on high value software projects? The engineers will focus on delivering Something™ by the Date™! This fatal flaw results in delivery of a Something™ full of chaos and features that nobody really wants or needs.
How can we develop transformative tools for thought?
A Research Paper by Andy Matuschak & Michael NielsenConventional tech industry product practice will not produce deep enough subject matter insights to create transformative tools for thought.
...The aspiration is for any team serious about making transformative tools for thought. It’s to create a culture that combines the best parts of modern product practice with the best parts of the (very different) modern research culture. You need the insight-through-making loop to operate, whereby deep, original insights about the subject feed back to change and improve the system, and changes to the system result in deep, original insights about the subject.
Software Engineering as a Craft
An Article by Thomas WilsonThe decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance.
So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it.
Why Scrum is killing your product
An Article by Henry LathamDeadlines are bullshit
An ArticleIn software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
Software developers have stopped caring about reliability
An Article by Drew DeVaultOf all the principles of software engineering which has fallen by the wayside in the modern “move fast and break things” mentality of assholes modern software developers, reliability is perhaps the most neglected, along with its cousin, robustness. Almost all software that users encounter in
$CURRENTYEAR
is straight-up broken, and often badly.The Rise Of User-Hostile Software
An Essay by Den DelimarskyWe are truly living in an era of user-hostile software, and when I say “user-hostile” I mean it as “software that doesn’t really care about the needs of the user but rather about the needs of the developer.”
I personally do not know anyone who asked for an online account requirement before they can use a keyboard; however, some product lead somewhere decided that it’s important to better “understand the customer” and “maximize marketing reach” through some weekly “Hey, we have a new keyboard!” newsletter.
Minimum Awesome Product
An Article by Carlos BeneytoUsers are accustomed to a minimum of quality, and they expect that of all new products.
If our product does not [meet basic expectations of quality], people will automatically believe that it is a bad product and they will not take it seriously. It is not what they expect.
Hence my suggestion that the MVP has died and the MAP: Minimum Awesome Product was born.
Traditional companies are losing because they mismanage software engineers
An Article by Emma WattersonInnovation is messy, and frankly Anti-Steve [Jobs] can’t figure out why you wouldn’t just tell people the right thing to build and skip all the trial and error that comes with innovation. Anti-Steve and his board of directors that keep him in place fundamentally believe that they know what needs to be built. Or at least that they can hire the messiah that will come down off the mountain and tell everyone what to build. There is no such messiah.
Research, empathy, simplicity, speed
An Article by Matthew StrömAs Nosrat provides a simple list of essential ingredients for any great meal, can we describe a simple list of essential components for digital products?
Here are four elements that I believe are the foundation of great digital products: Research, Empathy, Simplicity and Speed.
Craft and Material in Digital Design
An ArticleProduct Design Resources
A Reference Work by Brandon DornThings I‘ve read, people I‘ve tried to learn from, and things I‘ve done to become a better designer. This is an idiosyncratic list reflecting what has helped me along the way, rather than an exhaustive list of design classics.
Though the list leans toward theory — principles are more durable than technique — I offer a few ideas further down about how to practice design. It also leans toward information design, because the task of presenting rich, dense information in an accessible way is ultimately the task of any digital product.
Functional Prototyping. A Missed Opportunity in Web Design
An Essay by Chuánqí SunPrototyping allows engineers in various industries to “fail fast, fail cheap”, “select the best from the pool”, and “bring in the reality”.
Apps Getting Worse
An Article by Tim BrayToo often, a popular consumer app unexpectedly gets worse: Some combination of harder to use, missing features, and slower. At a time in history where software is significantly eating the world, this is nonsensical. It’s also damaging to the lives of the people who depend on these products.
...Maybe we ought to start promoting PMs who are willing to stand pat for an occasional release or three. Maybe we ought to fire all the consumer-product PMs. Maybe we ought to start including realistic customer-retraining-cost estimates in our product planning process.
We need to stop breaking the software people use. Everyone deserves better.
Feature parity
An ArticleWhilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business.
Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'.
The return of fancy tools
An Article by Tom MacWrightTechnology is seeing a little return to complexity. Dreamweaver gave way to hand-coding websites, which is now leading into Webflow, which is a lot like Dreamweaver. Evernote give way to minimal Markdown notes, which are now becoming Notion, Coda, or Craft. Visual Studio was “disrupted” by Sublime Text and TextMate, which are now getting replaced by Visual Studio Code. JIRA was replaced by GitHub issues, which is getting outmoded by Linear. The pendulum swings back and forth, which isn’t a bad thing
On Design Engineering: I think I might be a design engineer...
An Article by Trys MudfordDesign engineering is the name for the discipline that finesses the overlap between design and engineering to speed delivery and idea validation. From prototyping to production-ready code, this function fast-tracks design decisions, mitigates risk, and establishes UI code quality. The design engineer’s work encapsulates the systems, workflows, and technology that empower designers and engineers to collaborate most effectively to optimise product development and innovation.
— Natalya ShelburneWebsites are not living rooms and other lessons for information architecture
An Essay by Sarah R. BarrettWhile there is a lot that IA can learn from actual architecture or city planning, websites aren’t buildings or cities, and they don’t have to work like them. Instead, they should be designed according to the same principles that people’s brains expect from physical experiences.
Software that nobody wants
An Article by Gandalf HudlowFinding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
Guidebook: Graphical User Interface Gallery
A WebsiteGuidebook is a website dedicated to preserving and showcasing Graphical User Interfaces, as well as various materials related to them.
A Mindful Mobile OS
An Article by Clo S.I read and loved Potential's "iOS 15, Humane" proposition. Published earlier in June by co-founders Welf and Oliver, it tackles how iOS could help us better protect our attention.
As a designer who cares about and writes about digital wellness, I'm profoundly aligned with their suggestions.
- Persuasive design
- Disclosure requirement
- From infinite feeds to pages
- Was this time well spent?
- Regret tax
- Conditions of use
Clues for software design in how we sketch maps of cities
An Article by Matt WebbGiven there’s an explosion in software to accrete and organise knowledge, is the page model really the best approach?
Perhaps the building blocks shouldn’t be pages or blocks, but
neighbourhoods
roads
rooms and doors
landmarks.Or rather, as a knowledge base or wiki develops, it should - just like a real city - encourage its users to gravitate towards these different fundamental elements. A page that starts to function a little bit like a road should transform into a slick navigation element, available on all its linked pages. A page which is functioning like a landmark should start being visible from two hops away.
Fast Software, the Best Software
An Essay by Craig ModI love fast software. That is, software speedy both in function and interface. Software with minimal to no lag between wanting to activate or manipulate something and the thing happening. Lightness.
Software that’s speedy usually means it’s focused. Like a good tool, it often means that it’s simple, but that’s not necessarily true. Speed in software is probably the most valuable, least valued asset. To me, speedy software is the difference between an application smoothly integrating into your life, and one called upon with great reluctance. Fastness in software is like great margins in a book — makes you smile without necessarily knowing why.
A Plea for Lean Software
An Essay by Niklaus WirthSoftware's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials.
Speed is a feature
An Article by Nikita ProkopovMillions of programs have that unfulfilled potential of becoming your second nature, something you don’t even think about when interacting with. They’re waiting to be enabled to “click”. Speed is a feature.
The Great Divide
An Article by Chris CoyierOn one side, an army of developers whose interests, responsibilities, and skill sets are heavily revolved around JavaScript.
On the other, an army of developers whose interests, responsibilities, and skill sets are focused on other areas of the front end, like HTML, CSS, design, interaction, patterns, accessibility, etc.
The care and feeding of software engineers (or, why engineers are grumpy)
An Article by Nicholas ZakasWe do say “no” very quickly, not just to designs, but to everything. That led me into thinking about the psychology of software engineers and what makes us the way we are.
Web Brutalism, seamfulness, and notion
An Essay by Brandon DornHow a tool for sensemaking reconciles two distinct software design ideologies.
- Seamful vs. seamless
- Reveling in infrastructure
- The brilliance of notion
- How our understanding is working
Dear Microsoft
An EssayWe realized a few years ago that the value of switching to Slack was so obvious and the advantages so overwhelming that every business would be using Slack, or “something just like it,” within the decade. It’s validating to see you’ve come around to the same way of thinking. And even though — being honest here — it’s a little scary, we know it will bring a better future forward faster.
However, all this is harder than it looks. So, as you set out to build “something just like it,” we want to give you some friendly advice.
How Microsoft crushed Slack
An Article...and why the era of worker-centered work tools may be over.
Technical debt as a lack of understanding
An Article by Dave Rupert"If you develop a program for a long period of time by only adding features but never reorganizing it to reflect your understanding of those features, then eventually that program simply does not contain any understanding and all efforts to work on it take longer and longer.” — Ward Cunningham
People expect technology to suck because it actually sucks
An Article by Nikita ProkopovI decided to record every broken interaction I had during one day.
If I decided to invest time into thinning this list down, I could theoretically...reduce this list from 27 down to 24. At least 24 annoyances per day I have to live with. That’s the world WE ALL are living in now. Welcome.
Why Software is Slow and Shitty
An Article by Pirijan KetheswaranPlanning doesn't make for better software
A Fragment by Robin RendleMy own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it.
Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me.
After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64.
Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way.
Figma's Engineering Values: Craftsmanship
An ArticleCraftsmanship 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.
On the "Building" of Software and Websites
An Essay by Dorian TaylorI’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project.
Yagni
A Definition by Martin FowlerYagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
The State of Agile Software in 2018
A Talk by Martin FowlerOn the surface, the world of agile software development is bright, since it is now mainstream. But the reality is troubling, because much of what is done is faux-agile, disregarding agile's values and principles. The three main challenges we should focus on are: fighting the Agile Industrial Complex and its habit of imposing process upon teams, raising the importance of technical excellence, and organizing our teams around products (rather than projects).
Product vs. Feature Teams
An Article by Marty CaganThis article is certain to upset many people.
Silicon Valley Product Group
A Website by Marty CaganThe 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
Like, just a post complaining that screens should be better
An Article by Matt WebbIt’s been 19 years since Pixar released Monsters, Inc. with all that CGI hair. Where are my hairy icons? Ones that get all long and knotted as the notifications number goes up.
Why can’t I feel my phone? I found that paper from 2010 (when I was complaining about keyboards) about using precision electrostatics to make artificial textures on touchscreens.
I should be able to run my thumb over my phone while it’s in my pocket and feel bumps for apps that want my attention. Touching an active element should feel rough. A scrollbar should *slip. Imagine the accessibility gains. But honestly I don’t even care if it’s useful: 1.5 billion smartphone screens are manufactured every year. For that number, I expect bells. I expect whistles.
The Death and Life of Great American Cities
Dead cities
If you can understand a city, then that city is dead.
The dishonest mask of pretended order
There is a quality even meaner than outright ugliness or disorder, and this meaner quality is the dishonest mask of pretended order, achieved by ignoring or suppressing the real order that is struggling to exist and to be served.
The plan must anticipate all that is needed
Ebenezer Howard set spinning powerful and city-destroying ideas: He conceived that the way to deal with the city’s functions was to sort and sift out of the whole certain simple uses, and to arrange each of these in relative self-containment.
And he conceived of good planning as a series of static acts; in each case the plan must anticipate all that is needed and be protected, after it is built, against any but the most minor subsequent changes.
The city's most vital organs
Streets and their sidewalks, the main public places of a city, are its most vital organs.
They serve many purposes besides carrying vehicles, and city sidewalks—the pedestrian parts of the streets—serve many purposes besides carrying pedestrians. These uses are bound up with circulation but are not identical with it and in their own right they are at least as basic as circulation to the proper workings of cities.
Eyes on the street
You can’t make people use streets they have no reason to use. You can’t make people watch streets they do not want to watch. Safety on the streets by surveillance and mutual policing of one another sounds grim, but in real life it is not grim. The safety of the street works best, most casually, and with least frequent taint of hostility or suspicion precisely where people are using and most enjoying the city streets voluntarily and are least conscious, normally, that they are policing.
The Great Blight of Dullness
Equipped to handle strangers
A city street equipped to handle strangers, and to make a safety asset, in itself, out of the presence of strangers, as the streets of successful city neighborhoods always do, must have three main qualities:
- First, there must be a clear demarcation between what is public space and what is private space.
- Second, there must be eyes upon the street, eyes belonging to those we might call the natural proprietors of the street.
- And third, the sidewalk must have users on it fairly continuously.
The sight of people attracts still other people
This last point, that the sight of people attracts still other people, is something that city planners and city architectural designers seem to find incomprehensible. They operate on the premise that city people seek the sight of emptiness, obvious order and quiet. Nothing could be less true—People’s love of watching activity and other people is constantly evident in cities everywhere.
This trait reaches an almost ludicrous extreme on upper Broadway in New York, where the street is divided by a narrow central mall, right in the middle of traffic. At the cross-street intersections of this long north-south mall, benches have been placed behind big concrete buffers and on any day when the weather is even barely tolerable these benches are filled with people at block after block after block, watching the pedestrians who cross the mall in front of them, watching the traffic, watching the people on the busy sidewalks, watching each other. Eventually Broadway reaches Columbia University and Barnard College, one to the right, the other to the left. Here all is obvious order and quiet, no more stores, no more activity generated by the stores, almost no more pedestrians crossing—and no more watchers. The benches are there but they go empty in even the finest weather. I have tried them and can see why. No place could be more boring. Even the students of these institutions shun the solitude. They are doing their outdoor loitering, outdoor homework and general street watching on the steps overlooking the busiest campus crossing.
Without effective eyes to see, does a light cast light?
Street lights can be like that famous stone that falls in the desert where there are no ears to hear. Does it make a noise? Without effective eyes to see, does a light cast light? Not for practical purposes.
I know the deep night ballet and its seasons best
This order is all composed of movement and change, and although it is life, not art, we may fancifully call it the art form of the city and liken it to the dance—not to a simple-minded precision dance with everyone kicking up at the same time, twirling in unison and bowing off en masse, but to an intricate ballet in which the individual dancers and ensembles all have distinctive parts which miraculously reinforce each other and compose an orderly whole. The ballet of the good city sidewalk never repeats itself from place to place, and in any one place is always replete with new improvisations.
Togetherness
“Togetherness” is a fittingly nauseating name for an old ideal in planning theory. This ideal is that if anything is shared among people, much should be shared. “Togetherness,” apparently a spiritual resource of the new suburbs, works destructively in cities. The requirement that much shall be shared drives city people apart.
When an area of a city lacks a sidewalk life, the people of the place must enlarge their private lives if they are to have anything approaching equivalent contact with their neighbors. They must settle for some form of “togetherness,” in which more is shared with one another than in the life of the sidewalks, or else they must settle for lack of contact. Inevitably the outcome is one or the other; it has to be; and either has distressing results.
City residential planning that depends, for contact among neighbors, on personal sharing of this sort, and that cultivates it, often does work well socially, if rather narrowly, for self-selected upper-middle-class people. It solves easy problems for an easy kind of population. So far as I have been able to discover, it fails to work, however, even on its own terms, with any other kind of population.
Self-appointed public characters
The social structure of sidewalk life hangs partly on what can be called self-appointed public characters. A public character is anyone who is in frequent contact with a wide circle of people and who is sufficiently interested to make himself a public character. A public character need have no special talents or wisdom to fulfill his function—although he often does. He just needs to be present, and there need to be enough of his counterparts. His main qualification is that he is public, that he talks to lots of different people. In this way, news travels that is of sidewalk interest.
If children are transferred from a lively city street
In real life, what significant change does occur if children are transferred from a lively city street to the usual park or to the usual public or project playground?
In most cases (not all, fortunately), the most significant change is this: The children have moved from under the eyes of a high numerical ratio of adults, into a place where the ratio of adults is low or even nil. To think this represents an improvement in city child rearing is pure daydreaming.
They act on their environment
Little tots are decorative and relatively docile, but older children are noisy and energetic, and they act on their environment instead of just letting it act on them. Since the environment is already “perfect” this will not do.
Men are not an abstraction
Placing work and commerce near residences, but buffering it off, in the tradition set by Garden City theory, is fully as matriarchal an arrangement as if the residences were miles away from work and from men. Men are not an abstraction. They are either around, in person, or they are not. Working places and commerce must be mingled right in with residences if men, like the men who work on or near Hudson Street, for example, are to be around city children in daily life—men who are part of normal daily life, as opposed to men who put in an occasional playground appearance while they substitute for women or imitate the occupations of women.
Wide sidewalks
The narrower the sidewalks, the more sedentary incidental play becomes.
Sidewalks thirty or thirty-five feet wide can accommodate virtually any demand of incidental play put upon them—along with trees to shade the activities, and sufficient space for pedestrian circulation and adult public sidewalk life and loitering. Few sidewalks of this luxurious width can be found. Sidewalk width is invariably sacrificed for vehicular width, partly because city sidewalks are conventionally considered to be purely space for pedestrian travel and access to buildings.
The boon of life and appreciation
Conventionally, neighborhood parks or parklike open spaces are considered boons conferred on the deprived populations of cities. Let us turn this thought around, and consider city parks deprived places that need the boon of life and appreciation conferred on them.
Indeterminate land oozes
City people would have to devote themselves to park use as if it were a business (or as the leisured indigent do) to justify, for example, the plethora of malls, promenades, playgrounds, parks and indeterminate land oozes afforded in typical Radiant Garden City schemes.
City districts with relatively large amounts of generalized park, like Morningside Heights or Harlem, seldom develop intense community focus on a park and intense love for it.
Intricacy, centering, sun, enclosure
Parks intensely used in generalized public-yard fashion tend to have four elements in their design which I shall call intricacy, centering, sun and enclosure.
Sentimentality plays with sweet intentions
Neighborhood is a word that has come to sound like a Valentine. As a sentimental concept, “neighborhood” is harmful to city planning. It leads to attempts at warping city life into imitations of town or suburban life. Sentimentality plays with sweet intentions in place of good sense.
We shall have something solid to chew on if we think of city neighborhoods as mundane organs of self-government. Our failures with city neighborhoods are, ultimately, failures in localized self-government. And our successes are successes at localized self-government.
The doctrine of salvation by bricks
When we try to justify good shelter instead on the pretentious grounds that it will work social or family miracles we fool ourselves. Reinhold Niebuhr has called this particular self-deception, “The doctrine of salvation by bricks.”
City neighborhoods cannot be self-contained
Whatever city neighborhoods may be, or may not be, and whatever usefulness they may have, or may be coaxed into having, their qualities cannot work at cross-purposes to thoroughgoing city mobility and fluidity of use, without economically weakening the city of which they are a part. The lack of either economic or social self-containment is natural and necessary to city neighborhoods—simply because they are parts of cities. Isaacs is right when he implies that the conception of neighborhood in cities is meaningless—so long as we think of neighborhoods as being self-contained units to any significant degree, modeled upon town neighborhoods.
City districts
Districts have to help bring the resources of a city down to where they are needed by street neighborhoods, and they have to help translate the experiences of real life, in street neighborhoods, into policies and purposes of their city as a whole. And they have to help maintain an area that is usable, in a civilized way, not only for its own residents but for other users—workers, customers, visitors—from the city as a whole.
To accomplish these functions, an effective district has to be large enough to count as a force in the life of the city as a whole. The “ideal” neighborhood of planning theory is useless for such a role. A district has to be big and powerful enough to fight city hall. Nothing less is to any purpose.
The "ideal" neighborhood
The “ideal” neighborhood of planning and zoning theory, too large in scale to possess any competence or meaning as a street neighborhood, is at the same time too small in scale to operate as a district. It is unfit for anything. It will not serve as even a point of departure. Like the belief in medical bloodletting, it was a wrong turn in the search for understanding.
Such places are forever way stations
Neighborhood accommodations for fixed, bodiless, statistical people are accommodations for instability. The people in them, as statistics, may stay the same. But the people in them, as people, do not. Such places are forever way stations.
The blind men who felt the elephant
It is so easy to fall into the trap of contemplating a city’s uses one at a time, by categories. Indeed, just this—analysis of cities, use by use—has become a customary planning tactic. The findings on various categories of use are then put together into “broad, overall pictures.”
The overall pictures such methods yield are about as useful as the picture assembled by the blind men who felt the elephant and pooled their findings. The elephant lumbered on, oblivious to the notion that he was a leaf, a snake, a wall, tree trunks and a rope all somehow stuck together.
Half as many people will not support half as many enterprises
In a given geographical territory, half as many people will not support half as many such enterprises spaced at twice the distance. When distance inconvenience sets in, the small, the various and the personal wither away.
Exuberant diversity in a city's streets
To generate exuberant diversity in a city’s streets and districts, four conditions are indispensable:
- The district, and indeed as many of its internal parts as possible, must serve more than one primary function; preferably more than two. These must insure the presence of people who go outdoors on different schedules and are in the place for different purposes, but who are able to use many facilities in common.
- Most blocks must be short; that is, streets and opportunities to turn corners must be frequent.
- The district must mingle buildings that vary in age and condition, including a good proportion of old ones so that they vary in the economic yield they must produce. This mingling must be fairly close-grained.
- There must be a sufficiently dense concentration of people, for whatever purposes they may be there. This includes dense concentration in the case of people who are there because of residence.
Primary uses
Any primary use whatever, by itself is relatively ineffectual as a creator of city diversity. If it is combined with another primary use that brings people in and out and puts them on the street at the same time, nothing has been accomplished. In practical terms, we cannot even call these differing primary uses.
Secondary diversity
Secondary diversity is a name for the enterprises that grow in response to the presence of primary uses, to serve the people the primary uses draw.
If secondary diversity flourishes sufficiently and contains enough that is unusual or unique, it seemingly can and does become, in its accumulation, a primary use itself. People come specifically for it. This is what happens in good shopping districts or even, to a humble extent, on Hudson Street.
A city's chessmen
One land-use economist, Larry Smith, has aptly called office buildings chess pieces. “You have used up those chess pieces already,” he is said to have told a planner who was trying to revitalize an unrealistic number of spots with dreamy plans for new office buildings. All primary uses, whether offices, dwellings or concert halls, are a city’s chessmen. Those that move differently from one another must be employed in concert to accomplish much. And as in chess, a pawn can be converted to a queen. But city building has this difference from chess: The number of pieces is not fixed by the rules. If well deployed, the pieces multiply.
Frequent streets are not an end in themselves
Frequent streets are not an end in themselves. They are a means toward an end. If that end—generating diversity and catalyzing the plans of many people besides planners—is thwarted by too repressive zoning, or by regimented construction that precludes the flexible growth of diversity, nothing significant can be accomplished by short blocks.
New ideas must use old buildings
Old ideas can sometimes use new buildings. New ideas must use old buildings.
The economic value of old buildings
But the economic value of old buildings is irreplaceable at will. It is created by time. This economic requisite for diversity is a requisite that vital city neighborhoods can only inherit, and then sustain over the years.
highdensityandovercrowding
They hated both equally, in any case, and coupled them like ham and eggs, so that to this day housers and planners pop out the phrase as if it were one word, “highdensityandovercrowding.”
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.
Scenes of thoroughgoing sameness
In places stamped with the monotony and repetition of sameness you move, but in moving you seem to have gotten nowhere.
North is the same as south, or east as west. Sometimes north, south, east and west are all alike, as they are when you stand within the grounds of a large project. It takes differences—many differences—cropping up in different directions to keep us oriented.
Scenes of thoroughgoing sameness lack these natural announcements of direction and movement, or are scantly furnished with them, and so they are deeply confusing. This is a kind of chaos.
Googie architecture
Where uses are in actual fact homogeneous, we often find that deliberate distinctions and differences are contrived among the buildings. But these contrived differences give rise to esthetic difficulties too. Because inherent differences—those that come from genuinely differing uses—are lacking among the buildings and their settings, the contrivances represent the desire merely to appear different.
Some of the more blatant manifestations of this phenomenon were well described, back in 1952, by Douglas Haskell, editor of Architectural Forum, under the term “googie architecture.” Googie architecture could then be seen in its finest flowering among the essentially homogeneous and standardized enterprises of roadside commercial strips: hot-dog stands in the shape of hot dogs, ice-cream stands in the shape of ice-cream cones. These are obvious examples of virtual sameness trying, by dint of exhibitionism, to appear unique and different from their similar commercial neighbors. Mr. Haskell pointed out that the same impulses to look special (in spite of not being special) were at work also in more sophisticated construction: weird roofs, weird stairs, weird colors, weird signs, weird anything.
Art is the one medium in which one cannot lie successfully
When we build, say, a business area in which all (or practically all) are engaged in earning their livings, or a residential area in which everyone is deep in the demands of domesticity, or a shopping area dedicated to the exchange of cash and commodities—in short, where the pattern of human activity contains only one element, it is impossible for the architecture to achieve a convincing variety—convincing of the known facts of human variation. The designer may vary color, texture and form until his drawing instruments buckle under the strain, proving once more that art is the one medium in which one cannot lie successfully.
The air doesn't know about zoning boundaries
Work uses suggest another bugaboo: reeking smokestacks and flying ash. Of course reeking smokestacks and flying ash are harmful, but it does not follow that intensive city manufacturing (most of which produces no such nasty by-products) or other work uses must be segregated from dwellings. Indeed, the notion that reek or fumes are to be combated by zoning and land-sorting classifications at all is ridiculous. The air doesn’t know about zoning boundaries. Regulations specifically aimed at the smoke or the reek itself are to the point.
The greatest flaw in city zoning
Raskin, in his essay on variety, suggested that the greatest flaw in city zoning is that it permits monotony. I think this is correct. Perhaps the next greatest flaw is that it ignores scale of use, where this is an important consideration, or confuses it with kind of use.
But then the knoll was gone
These banks were making the same mistake as a family I know who bought an acre in the country on which to build a house. For many years, while they lacked the money to build, they visited the site regularly and picnicked on a knoll, the site’s most attractive feature. They liked so much to visualize themselves as always there, that when they finally built they put the house on the knoll. But then the knoll was gone. Somehow they had not realized they would destroy it and lose it by supplanting it with themselves.
So many tactics, so well entrenched
I am going to deal with several subjects that, in themselves, are already well recognized as within the province of city planning: subsidized dwellings, traffic, city visual design, analytical methods. These are all matters for which conventional modern planning does have objectives and therefore does possess tactics—so many tactics, so well entrenched, that when their purposes are questioned they are generally justified in terms of the conditions laid down by still other tactics (e.g., We must do this for the purpose of getting the federal loan guarantees). We become the prisoners of our tactics, seldom looking behind them at the strategies.
A warning against the limitations of my own prescriptions
It is always necessary to check tactics against the specific needs that become evident in specific places. We should always be asking, “Does this device do the job needed here? And if not, what would?” Deliberate, periodic changes in tactics of subsidy would afford opportunity to meet new needs that become apparent over time, but that nobody can foresee in advance. This observation is, obliquely, a warning against the limitations of my own prescriptions in this book. I think they make sense for things as they are, which is the only place ever possible to begin. But that does not mean that they would make the best sense, or even good sense, after our cities had undergone substantial improvement and great increase in vitality.
Choked by their own redundancy
We went awry by replacing, in effect, each horse on the crowded city streets with half a dozen or so mechanized vehicles, instead of using each mechanized vehicle to replace half a dozen or so horses. The mechanical vehicles, in their overabundance, work slothfully and idle much. As one consequence of such low efficiency, the powerful and speedy vehicles, choked by their own redundancy, don’t move much faster than horses.
A city cannot be a work of art
There is a basic esthetic limitation on what can be done with cities: A city cannot be a work of art.
The order of life
Like the housers who face a blank if they try to think what to do besides income-sorting projects, or the highwaymen who face a blank if they try to think what to do besides accommodate more cars, just so, architects who venture into city design often face a blank in trying to create visual order in cities except by substituting the order of art for the very different order of life.
Complex systems of functional order
To see complex systems of functional order as order, and not as chaos, takes understanding. The leaves dropping from the trees in the autumn, the interior of an airplane engine, the entrails of a dissected rabbit, the city desk of a newspaper, all appear to be chaos if they are seen without comprehension. Once they are understood as systems of order, they actually look different.
Think better of it
This is, of course, the best way to salvage any kind of sorted-out project, up to the time it is actually built: Think better of it.
Places, services, techniques
It is not enough for administrators in most fields to understand specific services and techniques. They must understand, and understand thoroughly, specific places.
Nature, sentimentalized
Nature, sentimentalized and considered as the antithesis of cities, is apparently assumed to consist of grass, fresh air and little else, and this ludicrous disrespect results in the devastation of nature even formally and publicly preserved in the form of a pet.
The kind of problem a city is
Dr. Weaver lists three stages of development in the history of scientific thought: (1) ability to deal with problems of simplicity; (2) ability to deal with problems of disorganized complexity; and (3) ability to deal with problems of organized complexity.
The history of modern thought about cities is unfortunately very different from the history of modern thought about the life sciences. The theorists of conventional modern city planning have consistently mistaken cities as problems of simplicity and of disorganized complexity, and have tried to analyze and treat them thus.