Executive Advising
Ongoing counsel for leaders making decisions on the structures they build, the systems that support them, and who bears the costs incurred.
Learn more →And how organisations move faster.
Steve C. Landes writes, advises and builds on a single idea seen from two sides: trust as a human practice, and trust as an operational advantage.
Services
Counsel for leaders who want clarity, confidence and momentum.
Ongoing counsel for leaders making decisions on the structures they build, the systems that support them, and who bears the costs incurred.
Learn more →Sessions built from the book's chapter reflections, giving a board a shared vocabulary for trust and risk, and a test of who is actually exercising judgment in the room.
Learn more →Cohort sessions for organizations building judgment in their next generation of leaders, before the system teaches them to look away.
Learn more →
Trust. Risk. Technology. Human behaviour.
For more than three decades Steve has worked at the intersection of trust, resilience, and the systems we depend on. How institutions, supply chains, and digital infrastructure fracture under pressure, and what it takes to rebuild them so they hold.
About Steve →Essays, media and conversations.
The Field
This field doesn't hand out solutions or reforms, it names patterns that already shape people's experience, patterns that felt personal or inevitable until they were seen as structural instead. The restraint here is intentional: action taken before real seeing just reproduces the same architecture under a different name, and repair attempted without diagnosis becomes its own quiet form of displacement. So this stops at recognition, on purpose, because naming what's actually happening has to come before any responsible attempt to change it.
18 Aug 2026
The Field
Dashboards glow, reports circulate, and meetings recur, so it looks like someone is flying the plane, but the empty cockpit names a system running on momentum instead of stewardship, autopilot engaged with no one quite sure how to disengage it. People trust the system precisely because the instruments exist and the outcomes keep arriving, so coordination quietly gets mistaken for comprehension, and drift becomes indistinguishable from strategy. Before assuming the system's continued function means someone is steering it, check whether anyone can actually explain the whole, not just their own piece of it.
18 Aug 2026
Trust
Every system has people it treats as exceptions, the ones the form breaks on, the sensor misses, the chart won't hold, and calling them edge cases makes them sound rarer than they are. Design for the imagined average and you quietly encode who counts as a real user, but design for the person at the edge first and you usually design better for everyone, captions help the whole noisy room, not just deaf users. Treat the edge as the center of the lesson rather than the margin of the problem, and check who your own systems are quietly filing as a nuisance.
18 Aug 2026
The Field
A dashboard reading green gets trusted more than the lived conditions it was only ever meant to represent, and once a system organizes around that proxy, attention stops at its surface. People learn to optimize the metric instead of the thing it was measuring, and when the two contradict, a system that trusts what it can see resolves the conflict in favor of the number, letting real harm persist as long as it doesn't register. Periodically go check what the metric was originally standing in for, directly, since a proxy that's stopped pointing at reality will keep reading green long after it's stopped meaning anything.
18 Aug 2026