The 6:30 AM Walkaround: How a Daily Ritual Rebuilt a Broken Base Culture
My mother called my bosses because I hadn't been in touch for weeks. That alone should tell you something about how my career started.
I was 23, fresh out of school, and deployed to a remote oil field base in the middle of nowhere. No cell phone. A landline that felt more like a punishment than a communication tool. And apparently, a terrible habit of not letting the people who loved me know I was still alive. My mother, being my mother, skipped calling me directly (because, again, no cell phone) and went straight to my employer. I am still not sure whether to be embarrassed or impressed by the efficiency of that move.
That was my introduction to remote operations. Years later, in 2006, I went back. Not as a new hire this time, but as the base manager for that same kind of remote base: Hashkari/Badin, in Pakistan. I had actually requested the role. I knew what these places were like. I also knew what was possible if someone bothered to care about them.
What I walked into was worse than I expected.
## The Base Nobody Wanted
The culture at Hashkari was, to put it generously, a mess. There was a pattern of non-reporting, meaning things were going wrong and nobody was writing it down, flagging it, or telling anyone above them. There were side deals happening. The previous leadership had let personal problems bleed into professional ones in ways that corroded trust at every level. People were cutting corners that were supposed to be load-bearing.
And the industry attitude at the time was essentially: that's just how it goes out here. Remote base, rough conditions, low visibility from headquarters. What do you expect?
I expected better. Not because I was naive, but because I had seen what the alternative looked like, and I knew the gap between the two came down to something specific. It was not budget. It was not headcount. It was the daily, physical, consistent act of two people actually paying attention together.
So I found Chacha Shiva.
He was a senior person on the operator side, one of those quietly respected figures that every team has: soft-spoken, steady, the kind of leader people follow without being told to. He knew the base. He knew the people. And he was exactly the right partner for what I had in mind.
## The Walkaround
Every morning at 6:30, before anyone else had really arrived, the two of us met outside the gate. And we walked. Every single day, without fail.
The route covered everything: the office space, the warehouse, the welding area, the store. We were not inspecting in the punitive sense of the word. We were watching. Noticing. Asking. The point was to move through the physical reality of the base together, so that by the time anyone else showed up, we had already had the conversation that mattered.
Chacha Shiva would tell me where he needed support. I would figure out where I needed to go solve problems for him. We covered what had happened yesterday, what was on the schedule today, and what needed to move. Twenty minutes, same route, same time. Every day.
What I noticed quickly was that this ritual did something the reports never could. It transferred tacit knowledge, the stuff that lives in people's heads and never makes it onto a form, before it had a chance to become a crisis. Chacha Shiva knew things about that base that no incident report would ever capture. The walkaround was how that knowledge got out of his head and into a shared understanding between us.
And the team noticed. When people arrived in the morning and knew that the two of us had already walked the ground and already had the conversation, something shifted. The "no one told me" excuse stopped being available. Because we had been there. We had seen it. We had talked about it. The information was already moving.
Within about six months, the morale had changed in ways I had not fully predicted. We started doing movie nights. People who had avoided being assigned to this base were starting to actually want to go there. A place nobody wanted to work became a place people requested. Not because of some grand cultural initiative or a new policy binder. Because two people showed up at 6:30 every morning and walked around together.
That is it. That is the whole trick.
## What the Walkaround Actually Taught Me
What I took from Hashkari is something I have carried into every role since, including the work I do now helping founders and operators scale their businesses.
The walkaround was never really about the walk. It was a system for moving information from where it lived, inside people who knew the reality of the work, to where it needed to go, in the hands of people who could act on it. Consistently, in a format everyone understood, without waiting for something to break first.
When I became country manager later, I could not do a daily walkaround with every team. The scale was different. So I adjusted. Maybe it was once a week. Maybe it was a different format entirely. The principle stayed the same: you have to create regular, real touchpoints where information actually moves, not where information gets reported in the language of covering-your-bases. There is a difference between a status update and a real conversation, and one of them is what you actually need.
This is also where I see so many scaling businesses crack. Revenue is moving, the team is growing, and somehow the information is not. People are solving the same problem in four different parts of the organization and none of them know it. A new hire does something brilliant and never tells anyone because it just made their own life easier and it did not occur to them to share it. The tacit knowledge, the real operational intelligence of a business, stays locked inside individuals instead of becoming part of how the whole thing runs.
The fix is not a better reporting system, though systems help. The fix is the habit of showing up together, consistently, in the actual work, and pulling that knowledge out before it gets lost or before it becomes a problem.
I use this same instinct now when I am working with a team on their frameworks, their rollout plans, their communication structures. I am not just building a process document. I am trying to codify what the team actually knows, the stuff they have not written down yet, and turn it into something transferable. With AI and better tools, that process has gotten easier to do quickly. But the source material is still always the same: you sit with people, you ask real questions, and you listen for the knowledge that is not in any report.
Culture is not a poster on the wall. It is what you do at 6:30 in the morning when no one is watching, repeated until it becomes the way things work around here. It is the thread of consistent communication that means everyone already knows what's going on before the meeting starts.
Frameworks are how that culture survives scale. The walkaround works beautifully for two people at a remote base. But the principle behind it, moving tacit knowledge into shared knowledge through regular, real contact, scales into the six concentric circles of any organization if you build it in deliberately.
Murphy's Law will still show up. Something will still go wrong at the worst possible moment. But when the information is already moving, when people already know what's happening and who needs what, the firefighting gets a lot shorter. And a lot less dramatic.
Which, after enough years of this, is honestly the goal.