“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
Linking Researchers Across Generations An Essay from Field Notes on Science and Nature by Anna K. Behrensmeyer Future valueTime capsulesTools of the digital ageFive basic rulesBonewalks+1 More
Future value In the field, there is a continuous flow of information that consists of daily observations, insights, and data. How can I capture these data and thoughts in notes, maps, and images so that they will be of value both to me and to future generations of scientists?
Tools of the digital age The myriad tools of the digital age that provide quick ways to capture words, images, and data have added to the perception that handwritten field notebooks are passé. As someone who routinely encounters objects that can speak to us over millions of years, I may have a bias towards things that have stood the test of time. That said, it is clear that there is still much to recommend preserving records and information in traditional paper field notes. Over the course of my career, I have developed a habitual field note protocol in which a paper notebook is used both to record information and to integrate records made on standardized data sheets, in computer files, and in photographs. tools
Five basic rules Five basic rules: (1) Record your work as notes to your future self and colleagues. Write notes so that someone fifty years from now (or more) will understand and be able to use the factual information you collected, perhaps for purposes quite different from the original reasons. Clearly separate facts from interpretations so these are not confusing to a future reader. (2) Establish a clear and consistent notebook format and process. I always include the data, place, main activities or events, weather conditions, and other people involves. The day, month, and year is the most important link between that particular point in time and other people’s records, separate data sheets that I filled out myself, photos, and most important, collected specimens. Documenting collecting strategies and protocols receives special attention. In the moment, these may seem like common knowledge for the field team, so sometimes no one bothers to write them out. (3) Don’t lose your field records! (4) Pack a camera, create a visual record. No matter how many words you write to describe a fossil locality, you can’t beat an actual photo, taken on the spot, annotated in pen, and pasted into your notebook. There is no substitute for a photograph you actually mark in “real time” in the field as the best way to preserve a lasting, accurate record for yourself, or for someone who has never seen the site or object in question. (5) Learning through sketches and diagrams. Photographs are great, but drawn what you see is a more powerful way to learn about spatial patterns and relationships. Even if you are not an expert at drawing, you can make sketches that are much more informative than words would be. Always include a scale, an orientation, and labels in your diagrams. Best practices
Bonewalks Example of a standardized field data collection form used to record all the fossil bones encountered along a transect. Informally I refer to these as “bonewalks.” euphony