As change accelerates, that relationship is everything.
Every input and output is visible. Every decision ripples into the long-term. There is no externalizing its cost.
That makes islands, real and imagined, the sharpest medium we know for designing in systems. Each a case study for adaptation to a set of hyperlocal conditions, they make complex stories readable without reducing them. Islands ask the question: is this system moving toward balance, or toward collapse?
To answer that question, you first have to know the place: its character as well as its data. For coastal communities, the ocean is the hardest part to know: changing fast enough that old patterns are less reliable, and monitored by tools built without local context. And so we build imagined islands first: gatherings and prototypes that compress a system to a testable human scale, where earth and water are active participants. What emerges shapes solutions, and deepens the relationship between a community and the place it depends on.
That is the work of Island Lab: making invisible systems legible enough to steward, and co-creating the tools to do so with the community.
Every coastal community is part island, surrounded on one or more sides by the sea.
Three ways we help.
We show up. We embed. We sit with existing data, ecological, economic, cultural, political, and with the people who know what the data doesn't capture, especially what's happening in the water. We map relationships within the system and surface where the record and reality diverge.
We convene, by the water, or on it. Alongside bringing people and perspectives together, we bring lateral thinking: analogies, possibilities, and patterns from far outside the problem. What emerges (insights, hypotheses, collective practices) belongs to the place.
We design and build tools for the specific conditions of a place: sensor networks, data visualizations, mapping systems, community-owned data infrastructure, software and hardware products, from blue-sky concept through to field deployment.
Alongside the technical work, we prototype in other registers: simulations, stories, experiences. A prototype is a question made tangible, whatever form lets you test the hypothesis that most needs testing.
Coastal change needs three: a government body, a community organization trusted on the ground, and a partner who turns direction into tools and knowledge a community can use and own. We are that third partner. We work alongside the ports, cities, tribes, and community centers, through the relationships they already hold, toward the futures they are working to secure.
A first engagement starts focused: a deep read of the place, a clear set of needs, one prototype worth testing. From there we scale to the size of the work.
Where the practice shows up: the gatherings we convene, and the projects we build with partners on the coast.