Artefacts of Work
One interesting notion in the last years was the question of how I can make the process of my work more engaging and transparent? An obvious direction is the idea of artefacts — the byproduct of the greater endeavormwhich can be used to present and narrate a project. The help document the process by making decisions legible.
And they‘re often too readily discarded. As Matt Webb rightly notes there‘s a hidden opportunity here, especially in the context of innovation work:
The idea is to follow early product innovation processes, but ship all the collateral around the product rather than the product itself.
Such artefacts can take on a lot of different forms. They can be reports, design drafts, wireframes, photographies, mock-ups, prototypes, or actual artefacts from field research, etc.
Design artifacts are not the deliverable. They just document the design decisions, and design decisions must be rooted in user research.— Pavel \#StopAsianHate (@PavelASamsonov) April 7, 2021
If you can't draw a direct line from the artifact to how the decisions it documents will be informed, you won't produce anything of value.
As such artefacts tend to increase in fidelity and detail throughout a project. Early artefacts may be a simple post-it or rough sketch, while later projects might include visually complex explorations, concepts and testable prototypes.
What combines them is their ability of making decisions legible.
One way of extending this idea is the act of crafting “Anchoring Artefacts”, as described in HDL‘s “Legible Practices“, (pg. 93).
Tangible artefacts—documents, objects and other material—subtly embody or express the values of an organisation. Especially when an organisation is growing rapidly or attempting to transform itself, high-res artefacts help embody organisational or operational change which is often more abstract and invisible.
One intriguing class of artefacts might be the “one pager“. A concise presentation technique for communicating the interactions within systems (i.e. in game design).
Making things stick
A more familiar example might also be NASA mission patches—easily replicated in the form of stickers or posters as used by the UK‘s Government Digital Service.
Stickers like that become tokens that represent something more – a shared experience, a shared set of memories that only people who worked on that project will remember and understand. A sticker, like a web page, can be a conscious act of institutional memory.
Facebook‘s “Analog Research Lab” operates on a similar level. Around 2010 two marketing manager set up a small print-shop on the company campus. A project, which inadvertently played an integral part in not only creating a common company culture, but also propagated it to offices world-wide.
“It‘s more observations across the company,” says Boms, who calls himself a workplace philosopher. “The hope is that the artwork is more empathetic, curious and diverse, and it looks at what‘s happening from a critical eye. It‘s the pulse of what‘s going on internally.”
Boms says the posters don‘t aim to dictate what employees should think. Rather, they offer a prompt for people to think about.
Another quirky example is the work of Craig Mod who seems to use every opportunity to turn projects into a book. Be that via SMS during long walks through Japan or by laying out every commit ever made on a software project. Here he is talking about both.