Field-First Design

Roots don't follow a plan. They follow conditions — pressure, moisture, chemical gradients, pockets of resistance and air. Technology built for people working in the field has to operate the same way: adaptive, constraint-aware, designed for what's actually there.

A tree's root system is one of the most efficient space-filling structures in nature. It doesn't map its territory in advance and allocate resources accordingly — it explores through growth. Where conditions are favorable, roots proliferate. Where they encounter compacted soil or stone, they redirect. The architecture that emerges isn't the product of planning; it's the record of conditions encountered over time. The root system knows the soil better than any survey because it has lived through it.

Most technology is designed for average conditions in controlled environments: a laptop, reliable WiFi, a user with time to learn the interface and the institutional context to understand what the system is asking. Field-based conservation work exists in the exact opposite environment. A land steward documenting a photo check-in may be working on a phone with 2G signal, in a language that isn't the platform's primary language, under time pressure, without institutional support. Software designed around ideal conditions fails in these moments — not catastrophically, but persistently, and the cumulative effect is that people stop using it.

Field-first design inverts the process. You start with the constraint: intermittent connectivity, small screens, unfamiliar interfaces, physical activity happening simultaneously. You build the minimum viable interaction for that context first, and add richness only where the field environment genuinely supports it. The resulting system often looks simpler than what a boardroom-first approach produces — fewer features, less visible sophistication. But like a root system shaped by real soil, it actually works where it needs to work.