Awards Do Not Run Remote Companies. Habits Do.

Note: This story was written with AI assistance and edited by me.

Note: An earlier version of this piece, "What Being Named One of Silicon Review's 30 Best CEOs Taught Me About Leading Remotely," was published on DEV.

In January 2020, The Silicon Review named me one of its 30 Best CEOs of the Year for leading TopDevz, a software development consultancy built around complicated delivery for North American companies. I was grateful. I was also careful not to confuse a list with an operating system.

An award does not answer Slack at 9 p.m. across three time zones. Cadence does. Trust does. Transparency does. Years later, those are still the habits I look for in any remote services team.

Recognition Is a Mirror

Outside praise is useful when it forces you to write down what you actually believe. The narrative people wanted was growth and headlines. The work that kept customers was quieter: how a distributed company decides, how it shares bad news and how it keeps quality from depending on one hallway.

If the recognition taught me anything, it is that lists arrive after systems already work. Chase the systems.

Trust You Design, Not Trust You Declare

In an office, trust can hide behind proximity. Remote removes that cover. That is a gift if you treat trust as something you design.

Design looks like clear outcomes, named owners and a shared definition of done. It looks like hiring people who create clarity, then matching authority to responsibility. It does not look like a slogan about adults with no feedback loop.

When trust is real, managers watch results instead of calendars. When trust is fake, chat becomes a surveillance channel and honesty gets expensive.

Cadence Beats Heroics

Distributed teams rarely fail from a lack of talent first. They fail from a lack of rhythm. Healthy remote companies keep a boring beat:

1. A written weekly plan with one owner per outcome.

2. Short updates in a shared channel so status does not need a meeting.

3. Documented decisions, including the why, where a new hire can find them.

4. Overlap windows across time zones treated as scarce.

5. One-on-ones about blockers and growth, not status theater.

6. A playbook that grows when the same question is asked three times.

Heroic late nights may save a sprint. Cadence saves the company.

Those same habits showed up when I helped scale consulting work earlier in my career and when I later founded and led remote delivery teams. Recognition did not invent the discipline. The discipline made the recognition make sense in hindsight.

Transparency Closes the Distance Gap

Remote teammates and remote customers share a fear: that they are last to know. Transparency closes it.

For teams, put priorities, risks and tradeoffs in writing early. Celebrate the person who escalates on Tuesday, not only the person who fires a drill on Friday. For customers, honest status and clear owners beat a polished apology after the fact.

I would rather send an uncomfortable update early than a beautiful explanation late. Distributed companies that hide bad news do not stay calm. They stay reactive.

What the List Did Not Change

The Silicon Review list did not rewrite how I hire, price or run a week. Those were already the job. What it changed was my willingness to talk about the unsexy parts in public.

Leaders get rewarded for narrative. Companies get rewarded for habits. Optimize only for the first and you get a nice quote and a fragile org chart. Optimize for the second and you can survive a bad quarter or a key person going on leave without the whole system wobbling.

When I look at a remote team now, I ask:

• Can a new hire learn how work gets done without pinging the same three veterans?

• Are outcomes owned by names, or by a group channel?

• Do people know what good looks like without watching someone perform it?

• Is writing valued enough that meetings actually shrink?

• When something breaks, does the truth surface early?

If those answers are weak, no award or tool migration will repair the culture.

A Small Scene That Keeps Repeating

Picture two remote managers on the same Friday. One spent the week chasing people in private chats and hoping the demo would hold. The other published a short weekly plan on Monday, named owners, escalated a risk on Wednesday in a shared channel and walked into Friday with no surprises. Same tools. Different operating system. Guess which team still trusts the calendar next quarter.

Habits Over Headlines

Leading remotely well is not about proving you do not need an office. It is about building trust people can feel, a cadence people can plan around and transparency people can rely on when things go wrong.

The Silicon Review recognition was a kind milestone. The lasting lesson was simpler. Be the kind of leader whose company still works on the weeks nobody is writing about you.

I took a firm from $6M to $60M in under three years.

This week, write down one decision your remote team keeps re-explaining in chat. Put the why next to it and name a single owner. That page is often worth more than another all-hands.