In 1800, if you’d said that you wanted something ‘made by hand’, that would be meaningless - everything was handmade. But half a century later, it could be a reaction against the age of the machine - of steam and coal-smoke and ‘dark satanic mills.’ The Arts and Crafts movement proposed slow, hand-made, imperfect craft in reaction to mass-produced ‘perfection’ (and a lot of other things besides). A century later this is one reason I’m fascinated by the new luxury goods platforms LVMH and Kering, or indeed Supreme. How do you mass-manufacture, mass-market and mass-retail things whose entire nature is supposedly that they’re individual?
...we keep building tools, but also we let go. That’s part of the progression - Arts and Crafts was a reaction against what became the machine age, but Bauhaus and futurism embraced it. If the ‘metaverse’ means anything, it reflects that we have all grown up with this now, and we’re looking at ways to absorb it, internalise it and reflect it in our lives and in popular culture - to take ownership of it. When software eats the world, it’s not software anymore.
The traditional process of delivering design, vs. delivering design just in time.
Designers are often working at least one sprint ahead of engineers. While one sprint might not seem like much of a lag, a typical product team learns a lot after the design hand-off. ...Instead of working ahead, we should finish designing as close to the end of a sprint as possible: just-in-time design.
Get embedded in the team. Designers should use sprint planning, grooming, standup, and retro as opportunities to provide design to — and receive feedback from — the rest of the team. Designs can take the form of written or verbal descriptions, not just wireframes and high-fidelity mockups.
Only design what’s needed. Use constant communication between engineering and product partners to understand what your collaborators will need next. Then, plan on delivering only what is needed, and nothing more. Use the agile process — grooming, planning, and retro — to find any shortfalls or excesses.
Avoid creating a backlog of designs. Designs don’t age well. In the time between finishing design and shipping code, it’s likely that you’ll learn something new that changes your understanding. If you’re producing more design than can be implemented, focus more on the quality of each design.