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
Don’t Be an Ostrich An Essay by Chuánqí Sun medium.com You just handed off a major redesign. Three months of research, twenty-seven major revisions, and hundreds cups of coffee have all culminated in this pinnacle of glory. It’s finally done! Except it’s not. It’s not, even after you have answered every single question the developers have about your red-line. It’s not, even after you have addressed all the technical constraints developers encountered during the implementation. It’s not, even after you meticulously documented all the patterns and styles into a library for reference and reuse. It’s not, because neither you nor the developers have talked to a real user. At the bottom of your heart, you are secretly wishing: My design looks great on paper, so let’s keep it on paper. You are an ostrich. Post-occupancy evaluation
Post-occupancy evaluation Post-occupancy evaluation (POE) is a practice in the building industry where an architect would visit the building after its occupancy and interview its residents. It sounds like a great opportunity for collecting feedback and learning from mistakes, but it’s rarely practiced. Why? Many awe-inspiring, prize-winning architectures are half building, half sculpture. Often made of specially molded concrete and steel, they are extremely expensive to alter, let alone any alteration would also attack the architect’s prestige and pride. So whatever usability issues the POE identifies will remain as issues, unless the architect wants to accept the public criticism and shame that comes with the remodeling. In fear of criticism, an architect would turn down the opportunity for POE, and continue to design the same roof that would leak water in future projects. In fear of criticism, a developer would use customer service representatives as a shield against user complaints, while focusing on the “technical” aspect of things. In fear of criticism, a designer would close the contract as soon as the client accepts the design, even though none of the real users are represented by the client. architectureux