AI-driven "Design"? An Article by Jorge Arango jarango.com Like a programming language interpreter, GPT-3 translates the designer’s intent from a language they’re already familiar with (English) to one they need to learn (Figma’s information architecture, as manifested in its UI.) This can be easier for a new/busy designer, much like Python is easier and faster to work with than assembly language. But that’s not “designing” — at least not any more than compiling Python code is “programming.” In both cases, all the system does is translate human intent into a lower level of abstraction. Sure, the process saves time — but the key is getting the intent part right. I’ll be convinced the system is “designing” when it can produce a meaningful output to a directive like “change the product page’s layout to increase conversions.” aidesignintentabstraction
Two types of work An Article by Jorge Arango jarango.com There are two types of work: growth work and maintenance work. Growth work involves making new things. It can be something big or small. In either case, growth work often follows a loose process. Maintenance work is different. Maintenance work involves caring for the resources and instruments that make growth work possible. This includes tools, but also body and mind. Maintenance is ultimately in service to growth. But effective growth can’t happen without maintenance. As with so many things, the ideal is a healthy balance — and it doesn’t come without struggle. organizationinformationmakingwork
Internal design teams and thought leadership An Article by Jorge Arango jarango.com The design industry is an ecosystem. External design teams provide critical functions beyond augmenting internal design resources. Thought leadership — pushing the field’s boundaries — is indeed one of them. Many practices and tools we take for granted — journey maps, personas, conceptual frameworks — were pioneered and/or popularized by ‘outies.’ Most of the field’s foundational books and blogs are by people outside ‘client’ organizations. This isn’t because internal designers aren’t as clever or dedicated as their external colleagues. (Many ‘innies’ are former ‘outies.’) It’s because internal design roles are structurally misaligned with public thought leadership. designux
Not Just a New Feature; a New Compact A Fragment by Jorge Arango jarango.com My sense is that Slack’s teams think of themselves as adding ‘features’ to a ‘product,’ instead of as stewards of a place where people work. featuresplace
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. Erick Greene, Why Keep a Field Notebook? Five basic rules indexes