The brass housing of the rotation gears is warm to the touch, and as I lean into the wrench, a sharp, white-hot needle of pain shoots from my shoulder down to my wrist. I slept on my arm wrong-pinned it under my own stubborn weight for at least 87 minutes of heavy, dreamless sleep-and now the world is paying me back in nerve endings. I’m Phoenix P.K., and I spend my nights making sure this light doesn’t blink out, but apparently, the administrative gods in the city think I’m doing it all wrong. They sent a memo. It arrived in a 47-page PDF that looked like it had been birthed by a committee of people who have never seen the ocean, much less smelled the rot of kelp on a low tide.

They want me to adopt the ‘Spotify Model.’ I’m a lighthouse keeper. I have exactly 7 responsibilities, and none of them involve ‘squads,’ ‘tribes,’ or ‘guilds.’ But the manager who visited last week, a man named Derek who wore shoes that looked like they cost more than my annual kerosene budget, was adamant. He stood there, shivering in the 57-degree dampness of the gallery, telling me that we needed to ‘agilize’ the beacon’s maintenance schedule. He didn’t ask if the light was working. He didn’t ask about the 17 different types of fog that roll in off the North Atlantic. He just wanted to know how I was tracking my ‘sprints’ on a kanban board that didn’t exist.

The Poison of Ritual

This is the poison of the modern era. We’ve reached a point where the ritual of the ‘best practice’ has become more sacred than the outcome it was originally designed to achieve. We are ossifying the habits of yesterday’s winners and calling them universal truths. It’s a cargo cult.

It’s a lie, of course. It’s a way to outsource the terrifying responsibility of actually thinking for yourself. If you follow the ‘best practice’ and you fail, nobody blames you. You did what the book said. You followed the industry standard. You were a ‘good’ professional. But if you ignore the best practice to do something that actually makes sense for your specific, messy, 37-person context and you fail? Then they crucify you. So, most people choose the safety of the herd over the efficacy of the individual. They choose the slow death of a thousand best practices.

The Complexity Trap

I’ve been guilty of it myself. About 27 years ago, when I first took over this post from my father, I tried to modernize everything based on a manual I found in a thrift store in the city. It was all about ‘Systemic Redundancy.’ I installed 7 back-up systems for the primary lens. It was a beautiful, complex web of triggers and failsafes. I spent months tweaking it. And then, during the first real gale, the complexity became its own point of failure.

A salt-crusted sensor in system 3 triggered a shutdown in system 7, which locked the manual override because the ‘best practice’ at the time was to prevent human error. I nearly let a freighter hit the shoals because I was too busy following a manual to look out the window. I had to break the glass with a hammer. Not exactly a best practice, but it saved 87 lives that night. I realized then that context isn’t just a detail; it’s the entire game.

“

What works for a software startup in Palo Alto will almost certainly fail for a lighthouse keeper in a storm, yet we continue to push these generic templates onto every industry as if they were divine law.

The Illusion of Control

We see this everywhere, especially in high-stakes environments where the pressure to conform is highest. In the world of digital platforms and complex systems, the urge to just ‘do what the big guys do’ is overwhelming. It’s why every app looks the same, every mission statement sounds like it was written by the same tired algorithm, and every user experience feels like a series of hurdles designed to fulfill a KPI rather than help a human.

But the real leaders… treat best practices as suggestions, not commandments. They understand that a practice is only ‘best’ if it solves the specific problem sitting on your desk right now. For instance, in the realm of complex user environments like ufadaddy, the success doesn’t come from blindly copying the giants; it comes from understanding the nuances of the local user and building a framework of responsibility that actually fits the culture of the people using it. You can’t just copy-paste a ‘Responsible Gaming’ framework from a UK-based white paper and expect it to work in a completely different psychological landscape without doing the hard work of observation.

Observation is painful. It requires you to admit you don’t know the answer. It requires you to sit in the 57-degree cold with your arm hurting and realize that the manual is useless. Derek, the manager, didn’t like that. When I told him the Spotify Model was for people who build music apps, not people who keep ships from sinking, he looked at me like I was a heretic. He told me I was ‘resistant to change.’ I told him I wasn’t resistant to change; I was resistant to stupidity.

Chaos Doesn’t Care About Jira

Change is necessary when the environment shifts. But most ‘best practices’ aren’t about adapting to change; they are about creating an illusion of control. If we have a process, we have a handle on the chaos. Except, the chaos doesn’t care about your Jira tickets. The ocean doesn’t care about your scrum master. The ocean only cares about the physical reality of the light hitting the water. If the light isn’t there, the ship hits the rock. It’s binary. It’s brutal.

We’ve lost the ability to be brutal with our own processes. I see it in the letters my niece sends me from her tech job in the city. She spends 27 hours a week in meetings discussing how to be more productive. She is drowning in the best practices of productivity. It’s a paradox that would be funny if it weren’t so tragic.

The Scaffolding Analogy

I told her to stop. I told her to just do the work and apologize later. She’s terrified, of course. She’s been trained to believe that the process is the product. But the process is just the scaffolding. If the building is ugly, nobody cares how sturdy the scaffolding was. We need to start tearing down the scaffolds that no longer serve us. We need to be willing to look at a ‘proven’ method and say, ‘This is garbage for us.’

The Unelegant Truth

There are 777 ways to fail at any given task, but there are only a handful of ways to succeed, and almost all of them involve paying close attention to the specific constraints of your reality. My reality involves salt, wind, and the slow, inevitable decay of mechanical parts. A ‘best practice’ that involves digital-first reporting is useless when the Wi-Fi signal is as thin as the mountain air.

My best practice is a rag and a bucket of grease. It’s not elegant. It won’t get me a speaking slot at a conference. But the light keeps spinning. I wonder sometimes if the people who invent these practices actually believe in them, or if they’re just selling a product. There’s a whole economy built around ‘Best Practices.’ There are consultants who charge $7,777 a day to tell you how to reorganize your office according to a philosophy they dreamed up in a hotel bar.

Reacting to Reality

I’m sitting here now, the pain in my arm finally dulling to a throb, watching the horizon. There’s a storm coming in. I can feel it in the way the air pressure is dropping-currently sitting at a 997 millibars and falling. The ‘best practice’ for this would be to file a weather-alert form with the regional office. Instead, I’m going to go down to the cellar and make sure the emergency gaskets are tight. I’m going to trust the 37 years of experience I have in this tower over the 47 pages of nonsense Derek left on my table.