IoT friction | The canyon principle

“Rivers don’t intend to carve canyons.” The principle relates to efficiency. Water flows downhill. It seeks the most direct path, yet most rivers, even the great ones, end up in meandering courses that eventually collapse into the sea.

In business a similar thing happens; incentives, power laws, career risk and cash flows dictate how companies function. The system is not intended to stifle flow, but it does anyway, as a byproduct of existence. There is a second rule; once a pattern becomes profitable, it gets reinforced. Just like our riverine example, a groove cuts deeper. Standards lock in assumptions, interfaces hide complexity, training pipelines entrain compliant operators, not curious experimenters.

Friction tends to slow your roll. Many projects are heavily influenced at the beginning by a committed driving force. Management buy-in is a given (otherwise you would not get the approval), which means a budget and collective top-down push. A freedom to suggest edits, discover novel ways of using tools and fluidity when it comes to making radical changes in design; this is the moment (of force).

Most people in a system are not villains or saboteurs. Passengers convinced they are the only ones navigating reality, like a city child frantically hammering a crosswalk button.

Boots on the ground

An installer, directly communicating with reality, is “boots on the ground.” Frontline crews can see where a design stops serving your expressed goal, where sight lines are bad, where signal strength drops off a cliff. An installer knows when a map stops reflecting terrain. Maybe there is no means of sending messages back up the corporate slope, they might just have to go with the flow.

You will find no single countervailing force of inertia. Each actor optimizes locally. A farmer who dams the flow upstream, doesn’t really care about what happens around the next bend. Protecting one’s territory is enough, both as claim and justification. While seeming to be a limiting, general construct; this principle suggests a few ideas:

🟧1. There are natural systemic and cultural forces at work, even in business.

🟧2. Use initial force to shape the pathway you want, not the one you’re forced into.

🟧3. A natural loss of energy, direction and speed occurs in any project over time.

🟧4. Keeping project scope narrow assists speed and flow.

🟧5. An IoT project is shaped by and shapes terrain.

Grasping the moment

When we go into discussions with partners, opening a discovery call, or having an exploratory conversation, this is a moment of greatest fluidity. Both parties have the opportunity to shape what happens. That moment should be grasped.

Over time, as decisions are made, built upon and processes codified, the project assumes a different form. It is hard to describe how that change happens without taking a bird’s eye view. There are similar touchpoints in the actions and behaviors of a startup, a mid sized company and a giant, ponderous, multinational corporation.

Systems are not designed to end freedom, but often designed in ways that don’t value it, unless someone deliberately puts it back in.

You've got an IoT idea?

Our engineers have the right tools.

Talk to us today