Creative Operations · 2021–2026
Tools, Not Artifacts: The Systems Behind Five Years of Output
- Branding
- Content
- Marketing
Overview
A creative function’s real output is less about campaigns than cadence, and Filecoin makes that demand unusually heavy: a sprawling ecosystem of foundation teams, independent businesses, developers, investors, storage providers, grantees and community organisers, spread across every timezone and answerable to no one in particular. Over five years the production tracker logged around 2,400 deliverables against it: 170-plus designed blog headers, launch graphics for successive network upgrades, bi-weekly governance decks, 147 video edits, and the constant churn of speaker cards, one-pagers and social graphics a live network generates. I began as the Foundation’s only designer and built the team as the work grew: an art director in the Bay Area, then a content producer in Vermont, three people covering the ecosystem’s clock, with motion and contract designers directed in at the peaks. The three of us sat inside a fifteen-person marcomms function, so the work was cross-functional before it was creative.
Approach
Any request likely to recur got a system instead of a file. Deck production runs from one Figma master to the Google Slides templates the entire organisation presents from. Blog headers, speaker cards and upgrade announcements come from template systems designed once and produced in minutes. Merch runs through an automated store the team never touches; event identity runs on FIL City. None of it could be imposed: nobody in a decentralised ecosystem answers to the creative team, so a system only spread if it was more useful than whatever a team would have built alone. The design decisions were made once, made well, and encoded, so the team’s actual creative hours stayed free for the work that needed them. Building the tool is the creative direction: a system carries the decision to everyone who uses it, long after the designer has moved on to the next thing.
Build tools, not artifacts.
One look, at volume
Blog headers are the clearest case. Every post gets its own, but they all come off one template system - so the look holds across 170-plus of them without a designer starting from a blank canvas each time.
Scope as a design decision
Requests came from across the Foundation and beyond it: the tracker names twenty-five-plus different stakeholders - comms, governance, events, ecosystem teams, executives - and that’s only the ones who filed tickets. Behind them sat the wider community, with every reason to ask. The same hub that set the philosophy set the boundary: an in-house team of this size is not a design agency. The remit stayed wide (brand, events, marketing, media production, merch, internal comms), but ad hoc work for external entities was out, replaced by tools to self-serve: brand guidelines and assets at hub.fil.org/design, event identity at fil-city.io, templates for non-design teams. Where a project needed more hands, I directed external partners instead of growing the team to match a temporary peak: LIT Collective, a fast, cost-effective Web3 design studio already fluent in the brands; The Branding Kings, the custom merch makers behind the corgis; and Invisible North, the full-service experiential agency brought in for the strategic heavy lifting.
The craft the systems paid for
The point of systematising the recurring work is what it buys: time for the pieces that need actual thought. One example - when Filecoin Foundation and Protocol Labs archived New York City’s Open Data on the network, the project needed explaining to policymakers and civic technologists with no web3 context. The answer was an infographic built on the NYC subway map: a system New Yorkers navigate intuitively, running on the same logic as a distributed network - nodes, routes, transfers, endpoints. Data flows and storage deals mapped onto the diagram so no technical background was needed to follow them.
That infographic is one piece in a wider range - product launches, event identities, annual-report spreads and explainer graphics that make hard ideas legible.
Outcomes
Roughly ten pieces a week, for five years, from a team that never grew past three - that’s the number the systems bought. The organisation presents from the deck masters, publishes on the header templates, and orders merch without a designer in the loop. The tools are public where it counts: brand assets at hub.fil.org/design and the event system at fil-city.io, given away so an ecosystem no one controls could still hold one bar. What started as one designer’s way of keeping up became how the whole function runs, and the systems outlast the team that built them, which was always the point. The newest layer of that tooling - the agents, knowledge bases and generative pipeline - is covered on its own in AI Adoption.