What I learned about leadership from people who never had the title

The best piece of vineyard advice I received in the first three years at Alexandrea Winery didn't come from a consultant. It did not come from a winemaker. It came from a man named Karen who had been working the Proshyan hillside since before I bought the land.

He didn't present it as advice. He walked me to a specific row in the east block, pointed at the soil color at the base of three vines, and said something in Armenian that translated roughly to: "These are thirsty in a different way than the others."

I didn't fully understand what he meant for another six weeks, until that section showed different ripening patterns than the rest of the block. He had seen it coming in the soil. I had been looking at the same rows every morning and seen nothing.

That moment has stayed with me more than most of what I learned in fifteen years of doing business in tech.

The org chart is a map of authority, not a map of knowledge

Every organization I have ever built or led has had the same structural problem: the people who knew the most about what was actually happening were rarely the ones with the most formal power over what would happen next.

At Cynora, the lab technician who ran our synthesis had a gut feel for how he could reduce the synthesis time by a factor of 2 that our senior scientists could describe in theory but couldn't replicate in practice. He wasn't modeling the chemistry. He was reading it. The knowledge was real, and it lived in his hands and his attention and his fifteen years of watching how materials behave, and none of it was in any document.

At Alexandrea Winery, it is Karen and the soil, and Jeff Ritchey and the way he tilts a glass before he says anything about what's in it. The harvest crew moves through the rows faster than I can follow and somehow knows, without instruments, which clusters are ready and which need three more days.

None of these people needed a title. They had something better: proximity, attention, and years of accumulated pattern recognition that no amount of formal authority can manufacture.

The founders and leaders who figure this out early build something the others can't. They build organizations where knowledge actually flows, where the person at the front of the room draws on the room's full intelligence rather than presenting a version of it that has been processed until most of the signal is gone.

What gets in the way

In my experience, what prevents this is not malice or stupidity. It is a very understandable human instinct: we trust the voices that sound most like authority.

Authority sounds confident. It uses the right vocabulary. It presents in the right format. It arrives with credentials, titles, and the implicit endorsement of whoever put it in the room.

Domain expertise often sounds different. It is specific in ways that seem narrow. It uses language that hasn't been translated into executive-meeting vocabulary yet. It sometimes comes packaged with uncertainty — "I think it's this, but the east block is different from what I've seen elsewhere" — which we are trained to read as weakness when it is actually precision.

The result is that organizations systematically underweight the knowledge that matters most and overweight the knowledge that presents most fluently. This is a serious error, and it rarely gets corrected unless the leader actively works to fix it.

What working on it actually looks like

I don't have a system for this. I have habits.

I try to find the person in any room who knows the most about the specific thing we are deciding and spend time with them before the decision gets made — not in the meeting, but before it, in the context where their knowledge lives. The vineyard, not the conference call. The lab, not the presentation. The factory floor, not the executive summary.

I have learned to distrust my own confidence when I haven't done that. If I feel certain about something I haven't gotten close to, I have usually been given a story rather than information.

Before any major decision, a good leader asks for a minority-opinion report to dig deeper and better understand why there is no consensus. Only after examining and questioning all options can a good decision be made. It may not be the right decision, but it will most often lead to a better outcome. And I have learned to notice the people who are quiet in meetings but whose work keeps producing results. They are almost always the ones worth listening to most carefully, because they have stopped wasting time explaining themselves and are just doing the work.

Karen doesn't attend meetings. He wouldn't have much to add. But I don't make decisions about the Proshyan vineyard without walking it with him first.

That's not a management philosophy. It's just paying attention to where the knowledge actually lives.