When the expert can't show up, your interface has to

Some sustainability tech platforms are built to be used by experts.

Not because the team couldn’t make them simpler, but because they decided not to. A biologist on every client call. An environmental consultant sitting between the dashboard and the decision-maker. This isn’t a workaround. For a lot of companies, it’s the product.

It works. More than most people outside the industry realize.

The consultant doesn’t just translate the data. They add context the platform can’t carry: local conditions, methodological nuance, the kind of judgment that comes from years in the field. When you’re selling to government agencies or institutional buyers who need that level of interpretation, embedding the expert is not a gap in your product. It’s a feature you’re charging for.

So this piece isn’t an argument against that model. It’s about the specific moment where it runs out of runway.

The model holds until the context changes

Every platform built on people-as-infrastructure eventually meets a situation where the people can’t show up. Three of them come up often enough to be worth naming.

The first is enterprise procurement. A buyer’s procurement team reviews your platform as part of their due diligence process. No one from your team is in that meeting. They open the dashboard, they look at what they see, and they make a judgment before a single expert has a chance to contextualize anything. The interface is doing the talking. The question is whether it says what you need it to say.

The second is partner ecosystems. You’ve built a relationship with a consultancy or a distribution partner who wants to white-label your data or integrate your platform into their client workflow. Their people are not your people. They have different training, different context, different relationships with the end user. The layer of expertise you’ve built your product model around doesn’t transfer with the license.

The third is geographic or sector expansion. The consultants who understand your domain in your current market are expensive and finite. Moving into new markets where that depth of expertise isn’t yet available means the platform has to operate without the safety net. Sometimes faster than expected.

None of these situations are failures of execution. They’re structural limits of people-as-infrastructure as a scaling model.

The reframe: not a replacement, a backup

This is where design systems often get sold wrong to companies in this position. The pitch lands as: “your product is too hard to use, let us fix it.” That’s not the conversation worth having.

The right frame is narrower: what needs to be true about the interface for it to carry weight in the specific moments when the expert isn’t available?

That’s a different design problem. It’s not about making the platform usable by anyone. It’s about making it legible enough for the right people, in the right contexts, without interpretation. The consultant doesn’t disappear. They stay where they add the most value. The design system handles the moments they can’t reach.

When I worked on complex data systems in financial services, this was the tension underneath almost everything: the people who understood the data best were not the people who had to read it on screen. The design work wasn’t about replacing expertise. It was about making sure the interface didn’t undo it.

The sustainability tech version of this problem is more specific, but the logic is the same. Your data is credible. Your science is solid. The interface needs to communicate that credibility without a biologist in the room to vouch for it.

A question worth sitting with

If you recognize your platform in this, the question I’d ask is not “do we need a design system.” It’s more specific: in which contexts does your product currently have to operate without the expert? And what does the interface do in those moments?

That answer tells you more about what you actually need than any audit I could run from the outside.