For the first year of running PipelineRoad, I prided myself on being accessible. Slack was always open. My calendar had gaps for impromptu conversations. If someone on the team had a question, they could reach me anytime. I thought this was good leadership — approachable, responsive, available.
It almost broke the company.
The Accessibility Trap
The open-door policy is one of those management ideas that sounds obviously correct. Of course leaders should be accessible. Of course team members should feel comfortable asking questions. Of course the hierarchy should be flat enough that anyone can raise a concern at any time.
The problem is that “anytime” quickly becomes “all the time.”
What started as occasional questions became a constant stream. Every decision, even small ones, got routed through me or Bruno. A designer would Slack me about a color choice on a client deliverable. A content writer would ask whether a particular angle was right before starting a draft. Someone would interrupt a deep work session to get approval on something that didn’t need approval.
I was responding to messages within minutes, feeling productive the entire time. I was also getting nothing of substance done. My days had become a series of micro-decisions and context switches, each one trivial on its own, each one stealing five or ten minutes of focused work that I never got back.
By the time I sat down to do actual strategic work — client proposals, positioning frameworks, product planning — it was 8 PM and I was running on fumes.
The Dependency Problem
The deeper issue wasn’t the interruptions. It was what the interruptions revealed: a team that had learned to depend on me for decisions they were perfectly capable of making themselves.
This was my fault, not theirs. By being instantly available and instantly responsive, I’d trained the team to check with me rather than trust their own judgment. Why agonize over a decision when you can get an answer in two minutes? Why develop your own framework for evaluating a design choice when the founder will just tell you what he thinks?
The open-door policy hadn’t empowered the team. It had infantilized them. And it had turned me into a bottleneck — the single point through which every decision had to pass, no matter how minor.
I remember the moment it clicked. I was in a cafe in Barcelona — I travel a lot, and I’d been working remotely for a few weeks — and I had eleven unread Slack messages waiting when I woke up. All of them were questions. None of them were emergencies. Every single one was something the person asking could have resolved on their own if they’d been forced to.
That’s when Bruno and I decided to change the system.
What We Built Instead
We didn’t go from open door to closed door. That would have been equally dysfunctional — a leadership team that’s unreachable creates a different set of problems, primarily fear and disengagement.
What we built was a structured communication system with three layers.
The first layer is asynchronous by default. Questions go into designated Slack channels, organized by client and by function. They get answered within a defined window — usually four to six hours, sometimes end of day. Not immediately. This sounds simple but it was transformative. The four-hour buffer forced people to sit with their question and, more often than not, figure out the answer themselves before the window closed.
The second layer is scheduled synchronous time. Every team member has a weekly one-on-one and access to a weekly team sync. If something needs real-time discussion, it goes into those sessions. This replaced the constant pinging with dedicated, high-quality conversation time.
The third layer is the emergency channel — a separate Slack channel reserved for genuinely urgent issues. Client escalations. System outages. Time-sensitive decisions that can’t wait for the async window. In the six months since we set it up, it’s been used maybe a dozen times. Which tells me that almost nothing we were treating as urgent was actually urgent.
The Discomfort Period
I won’t pretend the transition was smooth. The first two weeks were uncomfortable for everyone.
Team members felt like they were bothering us by putting things in the async channel — even though that was the entire point. I felt guilty not responding immediately — years of instant-response conditioning don’t disappear overnight. There were a few instances where a decision sat for too long because the new system hadn’t fully calibrated yet.
But by week three, something remarkable happened. People started solving their own problems. The designer who used to ask me about color choices started making bolder decisions and bringing them to the one-on-one for feedback. The content writer who used to check every angle before writing started producing drafts that were 90% there without any input from me.
The quality of the work didn’t drop. It went up. Not because I’d been giving bad guidance before, but because the team members were now investing their full thinking into decisions rather than outsourcing the hard part to me.
What I Got Back
The practical impact was immediate. I went from maybe two hours of uninterrupted deep work per day to five or six. Client proposals that used to take a week started getting done in two days. Strategic planning that I’d been perpetually deferring finally had space on the calendar.
But the more significant change was psychological. The constant low-grade anxiety of being always-on — the feeling that something was waiting for me, that I was falling behind, that my responsiveness was somehow the measure of my leadership — dissipated. I could be fully present in whatever I was doing, whether that was a client call or a strategy session or a walk through whatever city I happened to be in.
The Lesson I Wish I’d Learned Earlier
Accessibility is not the same as availability. Being accessible means your team knows they can reach you when it matters, that you’ll listen when they speak, and that you care about their challenges. Being available means you’re interruptible at any moment, which means you’re never fully engaged in anything.
The best leaders I’ve observed — not in books, but in person, at companies I’ve worked with across forty-something countries — are deeply accessible and strategically unavailable. They create systems that handle the routine so that their presence is reserved for the consequential.
An open-door policy sounds generous. But generosity without structure is just chaos with good intentions. Close the door. Trust your team. Build the system. Then open the door on your terms, at the moments when it actually matters.