“Design” is now “Product” An Article by Dorian Taylor dorian.substack.com Design has very little to do with what tools or methodologies you use, or what your job title is, or what you have a degree in, or even anything like “creativity”; design is about your relationship to constraints. Rather: to what extent are you defining constraints rather than just obeying them? Design is about taking a universe of possibilities and converging onto exactly one outcome. Being handed a set of constraints which you treat like immutable laws of physics (because many of them are) and solving within that envelope is what engineering is. To wit: what most designers are doing most of the time is actually a form of engineering, and engineers are always doing at least some design. This is because genuine design—the power to define constraints—is a privileged political position within an organization, and not everybody can occupy it. In other words, the “seat at the table” comes first. Design is Steve Jobs infamously dropping an iPod prototype into his fish tank, pointing at the bubbles coming out and yelling at his staff to make it thinner. It doesn’t matter what your title is; Jobs is the designer in that scenario. Steve Jobs designengineeringconstraints
Navigation by shibboleth An Article by Dorian Taylor doriantaylor.com The inverse-chronological colly on the front page is exactly what I didn’t want to end up with. I have tried my damnedest to keep everything on this site as temporally neutral as I can make it. I even intentionally leave the dates off the documents. Temporality only matters if you’ve already read everything and you want to see what’s new or changed, like if you’ve subscribed to a feed. Which is exactly what that is on the front page. Reverse chronology bias bloggingtime
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
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
On the "Building" of Software and Websites An Essay by Dorian Taylor doriantaylor.com I’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project. You are agreeing to make a ThingThe Thing-deadline calculusTrees and graphsContent as value The Battle for the Life and Beauty of the EarthHofstadter's Law softwarebuildingwwwconstruction
Agile as Trauma An Essay by Dorian Taylor doriantaylor.com The Agile Manifesto is an immune response on the part of programmers to bad management. Many a corner officeIntramural brownie pointsFeature factories agilemanagement
Why Keep a Field Notebook? An Essay from Field Notes on Science and Nature by Erick Greene Pick one thingLab notebooksHybrid journalsA fertile incubatorBest practices
Pick one thing I recently started a field notebook assignment for my upper-level Ecology class at the University of Montana. I asked my students to pick one “thing” and observe it carefully over the entire semester. In addition to their field notebooks, the students also had to suggest at least ten research questions inspired by their observations. One brick seeing
Lab notebooks Most of my colleagues who conduct laboratory research not only keep extremely thorough and complete lab notebooks, but they teach their students how and why to keep data in them. Some labs even have friendly competitions in which prizes for the best-kept notebooks are awarded. In stark contrast to the vibrant culture of keeping lab notebooks in molecular biology, my informal polling suggested a lack of interest in notebooks in field biology. “I have a GPS for that.” “My data are in a spreadsheet.” “I write things down when I get home.” “I have a computer.” The general consensus seemed to be that field notebooks are quaint, archaic, and obsolete in field biology.
Hybrid journals The most useful and interesting notebooks of field biology are hybrids; as well as recording details and data of field research, they record the observations, thoughts, musings, and peregrinations of the author. notetaking
A fertile incubator Another value of field notebooks is their ability to serve as an incredibly fertile incubator for your ideas and observations. By jotting down interesting observations, questions, and miscellaneous ideas, your field notebook can serve as a powerful catalyst for new experiments and projects. notetaking
Best practices Use a hardbound notebook. Keep your contact information in a prominent location. Write for yourself and for posterity. Write pertinent field information with every new entry. You should enter the date, time, and location at the top of every page. Add information on your location. Record your methods. Make backup copies. If you use abbreviations, make sure there is a key in your field notebook. Don’t leave home without it. Form a writing habit. Thomas Jefferson was such an inveterate chronicler of daily events in his notebooks that he even took the time to record the weather four times on the day he helped write the Declaration of Independence. So unless you have something far more pressing than writing the Declaration of Independence, you have no excuse for avoiding your field notebook! Set up a structure for your field notebook. Create an index. Treat your field notebook like a scrapbook. You should view your field notebook as a central clearinghouse for miscellaneous information that is relevant to your research project. If there are related bits of information that you will find useful later on, sketch them, write them down, photocopy them, and staple or tape them in your notebook. Five basic rules indexes