One of the things I genuinely love about this work is helping leaders and their teams develop a vision and a strategic plan — and then watching them actually bring it to fruition. There’s something rewarding in that. Not just the planning part. Watching a direction someone named out loud become something real.

Over the years, there are a couple of things I’ve run into when it comes to building vision. One is a generic vision. The other is people believing that only a visionary can build a vision.

I was in a session with one of my executive coaching clients. We were talking about their strategic plan, and when we got to the company’s existing vision, he said, “Yeah, well, the current vision is really generic.” And when he said that, I had one of those moments and responded with “Generic vision leads to generic actions, which yields you generic results.” He stopped, looked at it, wrote that down. “Yeah, that’s good, and that’s why we need to develop a new vision,” he said.

Subscribe now

As we started the process of developing the vision, he was very hesitant about putting forward any ideas. As we worked through it, he asked:

For him this was a statement of fact. He didn’t think he had the ability to create a vision, because he’d decided there was a category of person who gets to do that, and he wasn’t in it.

Once that’s the story running in your head, it stops mattering how capable you actually are. You’ll never start because you won’t see the point. So if that’s the sentence sitting in your head, “I’m not a visionary, so I can’t do this,” let that belief go. That’s something you’re using as an excuse, and it’s absolutely holding you back.

You have to learn to look at building a vision as a skill and not an inherent trait. Skills can be learned and improved. With a trait, you either have it or you don’t.

Building a Vision is a Skill

A visionary is a person with original ideas about what their future will or could be like, who’s capable of providing a picture and sharing that vision with others. That’s the common definition, and it’s true. But here’s the trap: when you hear “visionary,” it conjures up images of extraordinary people with an innate ability to see the future — Jeff Bezos taking a bookstore and turning it into Amazon, Satya Nadella walking into Microsoft and remaking it around a mobile-first, cloud-first vision. Those are extraordinary individuals. No doubt about it.

So where’s the myth? The myth is that only visionaries can develop compelling visions. That’s just not true. Vision creation is not limited to a select group of special people with special powers. It’s a skill that can be developed by anyone willing to put in the effort.

Creating a vision is a process that involves tapping into your own aspirations — or the aspirations of your organization, or your customers — your values, and your understanding of the world around you. It’s about setting a direction. And it’s a skill, learned and formed over time.

Subscribe now

Training the skill

Building a vision is a skill you develop through practice, self-reflection, and learning from your own experience and other people’s. Here are some of the steps that I walked through with my client.

Brainstorm without judgment. Spend some time and just brainstorm ideas. Approach it from a position of curiosity. This is where it gets hard, because there are times you’ll come up with an idea and judge yourself for it — that’s a stupid idea. No, it’s not. It’s an idea you came up with in the process. Do not stifle your creativity through judgment. Get a piece of paper, start writing your ideas down, and if one doesn’t sound like it’ll work, keep it on there anyway. Keep writing. All this part is about is collecting the ideas — not deciding yet which ones are good.

Get clear on your why. This is the deeper thing underneath the vision — what you’re honoring, what would still matter to you even if it didn’t have to matter to anyone else. A vision that’s linked to your why gives you a reason to get up in the morning, a reason to keep moving forward, a reason to press on when things get hard. Without it, the vision doesn’t have anything underneath it to pull from when the work gets difficult.

Visualize the impact. Not a picture of yourself succeeding — the actual effect on the people this touches. What’s different for your team, your client, the person on the other end of what you’re building.

Your why is what’s driving you. The impact is what actually happens as an end result of your vision. You need both — a vision that’s strong on why but vague on impact is still going to feel thin to the people you need to bring along with you.

Seek outside perspective. Surround yourself with people who have a different vantage point than you. If you’re building a vision for your team or your company, go get those perspectives. A lot of times, people can see the value we have — even when that value is a blind spot to us, because to us it’s just who we are, it’s just how we show up. But people on the outside looking in, they see something very special. Getting that outside view is often genuinely eye-opening, for exactly that reason: it’s showing you something you structurally cannot see on your own.

What’s the difference between a vision built by a visionary and one that’s not?

Nothing.

When we finally rolled out the vision, nobody in that room treated it like a rough draft from a guy who wasn’t a visionary. They owned it and started executing on it. That’s really the only test a vision has to pass. Can the team move it forward.

He built a vision and still doesn't call himself a visionary. He didn't need to. He just had to treat it the way he'd treat any other skill worth having — something you design your way into on purpose, not something you wait to feel.

— Dr. James Bryant, P.E.

Leave a comment

P.S. — Where have you gotten stuck trying to build a vision — brainstorming, getting outside perspective, something else? Reply and let me know — I read every one.

If you’ve been told you’re a micromanager and part of you doesn’t buy it — this is for you.

Not because the feedback is automatically right or wrong. But you now have an opportunity to choose how to respond to that feedback.

You and the feedback are not the same thing.

You are not the label. The label isn’t a verdict on your worth as a leader, on the years of judgment you’ve built, or on whether you care about the people you lead. It’s data — imperfect, filtered through someone else’s experience — about how the current arrangement between you and this person is landing on their side of it.

Share

In a recent issue of the win by DESIGN newsletter, titled “Who wants to be micromanaged,” I argued that micromanagement and hands-on guidance can look identical on the surface — that what separates them is context: competence, trust, stakes, and clarity. What felt like a lifeline in month one can feel like a leash in month four without anyone doing anything wrong. The permission to be closely involved has a shelf life.

If you got the feedback, one of those variables has shifted. The feedback isn’t telling you what kind of manager you are. It’s telling you that from where they’re sitting, the arrangement the two of you set up doesn’t fit anymore.

You don’t have to agree with the feedback to use it. But if you skip the interior work first, every move you make from here will be a reaction to how the feedback made you feel, not a response to what’s actually happening in the working relationship.

Most managers walk through one of two wrong doors. The first is to dismiss it — they don’t get the pressure I’m under, backing off would allow everything to fall apart. No self-reflection. No accountability. No changes needed. Just a commitment to keep the status quo.

The second option is to capitulate — fine, you want less of me, you’ve got it — and pull back on everything at once. It feels like relief, but it’s temporary and without any resolution. Now you’re less involved with no real read on whether the work is holding up. This lasts up until the first missed deadline or deliverable, then it’s back to the previous cadence.

Three questions to sit with before you do anything else.

The goal isn’t to talk you into agreeing that you’re a micromanager. That word will still trigger defense the moment you put yourself under it. The goal is smaller: to see whether, from some honest vantage, someone could experience your approach the way this feedback describes it.

Answer these just for this relationship, not for your whole leadership career. You’re looking for any place where your involvement is heavier, more frequent, or more correcting than the two of you intentionally designed — and where their behavior has started to change because of it.

If you can honestly answer “yes, sometimes” or “I’m not sure” to any of those, you’re not admitting to the label. You’re admitting that your involvement is visible from angles you might not be looking from. That’s the opening.

Subscribe now

What may be driving your level of involvement.

Closely involved managers rarely became that way by accident. There’s usually something underneath, and until it’s named, no conversation about how to work together differently is going to hold. Three layers worth checking: the pressure you’re carrying, what you believe about this person or team, and what you believe about yourself.

If fear is driving the involvement and you don’t name it, you’ll agree to less oversight in a conversation and be back to twice-weekly check-ins within a month. The words changed and nothing underneath them did.

Four moves to grow as a manager

1. Get curious before you get defensive. Have one conversation with the person, and don’t make it about defense. Try: I heard you’re feeling over-managed. Before I react, I want to understand what’s changed for you. Then let them talk. If you find yourself explaining before they’ve finished, you’re not there yet.

2. Check your own read honestly — starting with the fear. Which layer are you operating from? The pressure? The trust? Yourself? The self-scan isn’t complete until you can answer that — because the response to each is different:

• If it’s pressure, you need clearer risk thresholds and better visibility into the work.

• If it’s trust, you need cleaner decision rights and a plan for rebuilding it.

• If it’s identity, you need to practice letting go in low-stakes places first, before the high-stakes ones.

3. Build or revise the working agreement. Have an actual conversation about decision rights, cadence, escalation, and what would signal a need to revisit. Something like: When we started, I stayed close because the stakes were high and you were new to this client. You’ve grown since then. Here’s what I propose we shift — and here’s where I still need to stay involved for a while, and why.

4. Meet on the working agreement itself, on a schedule. Thirty minutes, once a quarter, with the person you manage — separate from your normal work updates. And they run it. They bring what’s shifted for them, what level of support they need now, and where the agreement should move. Your job in that meeting is to listen and respond, not to lead. This is what keeps the redesign from drifting back to where it started.

You might hear that less involvement is what’s needed. You might hear that the involvement is fine but the way it’s landing — the tone, the timing, the interruptions — is what’s actually costing trust. Or you might hear that your involvement isn’t the real issue at all, and something else has been quietly bothering them that finally came out through this label.

Your willingness to hear any of them is what makes this work.

Design your level of involvement

Getting feedback that you are considered a micromanager is not a failure. The failure is dismissing it — or acknowledging it and doing nothing about it.

The leaders who grow from these moments are those who objectively consider — not just accept — feedback, and take the opportunity to improve.

Don’t ignore feedback. Use it to design your involvement to fit the situation.

I want you to win by design.

— Dr. James Bryant, P.E.

P.S. I'd love to hear where you landed on this. What came up for you? Hit reply — I read every response.

Leave a comment

An employee tells her manager she needs more hands-on guidance. She means it — the last project felt underdefined, and she doesn’t want to fly blind again.

Her manager listens. Takes it seriously. Puts real structure in place — twice-weekly check-ins, a shared doc, regular calibration on what’s working. Everything the employee said she wanted.

A few weeks later, the same employee is telling colleagues she’s being micromanaged.

The manager hasn’t changed what she’s doing. The employee hasn’t changed what she originally asked for. Nothing obvious in the behavior has shifted. But the label has.

Share Win By DESIGN

The question underneath the label

Ask a room “who wants to be micromanaged?” and no hands go up. Of course they don’t. Micromanagement is a slur. You can’t defend being micromanaged any more than you can defend being condescended to. You can only deny it’s happening to you, or deny you’re doing it to someone else.

But ask the same room a different question — “who wants hands-on guidance to succeed at work?” — and different hands go up. Not all of them. But some go up quickly. New hires. People stepping into unfamiliar work. People who felt like they were flying blind on their last project and don’t want to repeat it. People who know they do their best work with someone actively engaged in it.

The behavior being described is often the same. Close involvement. Frequent check-ins. A manager watching the work as it’s being done.

Same activity. Opposite label.

Micromanagement and hands-on guidance can look identical on the surface. What separates them isn’t just the behavior — it’s how that behavior is experienced, and that experience is shaped by context: competence, trust, stakes, and clarity.

The same level of involvement can land as support for one person and surveillance for another. And even for the same person, that reading can flip over time as those variables shift. Competence grows. Trust builds. Stakes rise or fall. Clarity about the work — or the working relationship — sharpens or fades. What felt like a lifeline in month one can feel like a leash in month four, without anyone doing anything wrong.

That’s why any “permission” to be closely involved has a shelf life. It’s not a standing agreement. As capability grows, trust builds, or the stakes change, what once felt helpful can start to feel constraining.

Both sides carry responsibility here. Managers can’t assume past alignment still holds. Employees can’t assume intent without testing that assumption against what’s actually happening.

The practical move is simple but often skipped: periodically renegotiate how you work together — decision rights, check-in cadence, and when to step in. What was right three months ago is not automatically right now.

Subscribe now

What the research actually says about micromanagement

None of this dismisses the fact that micromanagement in its genuine form is real, widespread, and costly.

The behavioral signs are well documented, too:

• Excessive check-ins

• Requiring approval on decisions that shouldn’t need it

• Fixating on details instead of results

• Difficulty delegating

• Redoing work that was already done

• Resistance to any approach that isn’t the manager’s own

So micromanagement is a real thing. It has a shape. It has a cost.

But if hands-on guidance and micromanagement can look identical from the outside, then the behaviors on that list aren’t reliably the thing the word names. Which is exactly what the story at the top of this piece was pointing at.

Both people in that story are real

The manager isn’t a villain. She listened, she responded, she did exactly what her employee asked her to do. If you told her she was micromanaging, she’d be genuinely confused — and rightly so.

The employee isn’t lying or manipulating either. What she’s feeling is real to her. The check-ins that sounded reassuring in the abstract feel different when they’re happening. The shared doc that seemed supportive when it was proposed feels like being watched now. She isn’t inventing the discomfort. She’s living it.

Two real people. One behavior. Two incompatible readings — and no reliable way to resolve it without both of them coming back to the table.

And here’s the twist most management writing skips: one survey suggests that 91% of managers who are micromanaging don’t realize they’re doing it. They think they’re being thorough, supportive, or detail-oriented. Which means the manager in this story could genuinely be over-involved and genuinely believe she isn’t — and the employee could genuinely be receiving good support and genuinely feel micromanaged — and both of them could be telling the truth about their own experience at the same time.

Neither of them can solve this alone. That’s the part the rhetorical question in the lecture hall can’t touch.

Before you take this into a conversation

You’ve probably been on both sides of this. Most leaders have.

Before renegotiating anything with anyone, it’s worth spending some time with your own patterns. Not to diagnose yourself as the villain or the victim of this dynamic — but to notice, honestly, where you actually sit inside it right now.

If you’re the one managing someone —

• When you check in more than usual, what are you actually checking on: the work, or your own discomfort with the work being out of your hands?

• When was the last time you asked the person you manage what level of involvement is actually useful to her right now — not what she agreed to weeks ago?

• What’s changed in her competence, in your trust in her judgment, or in the stakes of the work since you two set up your current arrangement?

• The support you set up months ago — is it still the support she needs, or is it the support you’ve gotten used to providing?

If you’re the one being managed —

• What did you actually ask for the last time you asked for support, and does it match what you’re now receiving?

• When the discomfort shows up, is it about what your manager is doing — or about being seen while you’re still figuring it out?

• What’s changed in your own competence, or in the stakes of what you’re working on, since you and she set this up?

• What you asked for months ago — do you still need that level of help, or has something shifted that you haven’t said out loud yet?

The questions don’t resolve anything on their own. They’re not supposed to. Their job is to make sure that when you do take this into a conversation — with the person you manage, or with the person managing you — you’re bringing your actual situation, not the loaded version of it that the word micromanagement delivers pre-decided.

Whichever seat you’re sitting in, the move begins with being honest about what’s actually changed — and being willing to say so out loud, to the person who needs to hear it.

I want you to win by design, not by drift.

— Dr. James Bryant, P.E.

PS — I’d love to hear from you on this one. Have you been on either side of this dynamic? What did you notice? Hit reply and tell me — I read every response.

This year I agreed to make it a priority to invest in my own learning and development. I know that should be a no-brainer for me of all people — but I’ve learned that when something isn’t intentional, it just doesn’t happen, no matter how obvious it should be.

So I was at a conference back in March, and I remember meeting a handful of other consultants there. One story in particular stood out to me. I don’t think you’d guess it.

I was waiting in the hotel lobby and looked over to see this guy who looked dog tired — like he’d been traveling for days, not hours. I asked if he was okay. He laughed a little and said, “Yeah, I’m just glad I’m finally here — my rental car fell through over my license, so it’s taken me a few extra days to get to this thing.”

Naturally, I asked what happened. Turns out his driver’s license had expired the day before he left for the trip. My first thought was how he even made it onto the flight — but that part was easy. TSA gives a two-year grace period on expired IDs, so he got through security without a second look. The problem showed up at the rental counter. No grace period there. No negotiation. And the venue wasn’t an easy one to reach — no quick Uber, no Lyft waiting outside. He’d made it to the trip, just in time for parts of the meeting that he desperately wanted to attend.

That whole exchange stuck with me. Not because of the travel headache but it’s the whole thought of the limitations of not having a current ID. It brings to mind the limitation of living from an expired Identity.

Early in your career, you built an identity around something specific — maybe it was being the one who could solve the technical problem no one else could touch. The one who outworked everyone in the room. The one who said yes to the assignment nobody else wanted.

As you progressed, some of that stayed. Some of it evolved into something else — the identity of the person clients trusted with the hard conversations, or the one the team looked to when things got uncertain.

Now you’re at this level. And it might be time to evolve again.

Here’s what you probably haven’t noticed: every time you stepped into a new role, you were quietly building an identity for who you wanted to be — while you were still standing in the old one. The version of you that earned the next promotion was built while you were doing the job before it. You didn’t wait until you had the title to start becoming the person who deserved it.

So here’s where it gets personal: how do you want to be in the future — not just what do you want to accomplish, but who do you want to be while you’re doing it?

What does success actually look like for you in this next season — in your leadership, and in your life? Not the version you’d give in an interview. The honest one.

Are there things you need to change, or shore up, to become that person? Not flaws to fix — just places where the identity that got you here hasn’t caught up to where you’re trying to go.

And what support structures do you need in place to actually hold the dream you’re building? A leader, a habit, a relationship, a rhythm — something underneath you that wasn’t necessary for the role you used to have, but is necessary for the one you’re growing into.

This isn’t about building a plan today. It’s about being honest enough to name what you’d need to develop in order to grow toward where you actually want to go. The plan can come later. The honesty has to come first.

If this stirred something — even just a question you didn’t expect to be asked — sit with it before you move on to the next thing. You don’t need an answer today. You just need to be honest about what you’re carrying.

I’d love to hear what came up for you. Leave a comment, or send me an email directly.

I want you to win by design, not by drift.
— Dr. James Bryant, P.E.

There is a specific kind of company problem that only shows up after things are going well.

Not the early problems — scrambling for revenue, building credibility, finding the right people, figuring out whether the market actually wants what you have. Those problems are hard, but they have the clarity that comes with urgency. The path is obvious even when it is steep.

The harder problem arrives after those are solved.

The company is growing. The work is good. The reputation is real. And something is still wrong — not in any one place, but everywhere at once, in a way that is hard to name until the cracks are large enough to see.

Work is getting done, but no one has clean visibility into whether it’s getting done profitably. Decisions that used to take a five-minute conversation now take two weeks, three email threads, and an unscheduled call nobody was prepared for.

The best people are buried — not in the work they should be doing, but in the organizational weight that has quietly redistributed itself onto whoever is most trusted and available. Hiring is happening, but in response to pressure rather than strategy, which means the team is larger without being stronger in the ways that actually matter.

And the culture that used to hold everything together without anyone having to name it starts to feel thinner. It is still there. But it is not doing the same work it used to do, because the organization it is being asked to hold has changed shape.

When Instincts Stop Being Enough

The problems described above are not evidence that something went wrong. They are evidence that something went right.

Organizations that never hit this threshold never grow past a certain point. The scramble for visibility, the decision bottlenecks, the culture that used to hold everything together without any formal support — these are not signs of a broken company. They are signs of a company that built something real enough to outgrow its original infrastructure.

That distinction matters, because it shapes how leadership responds. If this moment looks like a problem to fix, the response is reactive: patch the most visible crack and get back to work. If it looks like a threshold to cross, it becomes a design question: what does this organization need to become to be ready for the growth we actually want — not just the growth that happens to us?

That shift in posture is the difference between managing what the company is and building what it needs to become. The instincts that built the company — respond fast, trust the people closest to the work, stay lean, keep things moving — were exactly right for as long as they worked. The problem is that those instincts are not a system.

They are a person, or a handful of people, functioning as a system through proximity, judgment, and accumulated trust. At a certain scale, that stops being enough. The company starts needing things it was never designed to have.

Most leaders can remember the moment when someone finally says what everyone has been circling: we can’t keep running this like a startup. The specific words change; the recognition is the same. What got us here will not get us to where we want to go.

What usually follows is some version of strategic planning. Not because someone had a bright idea in isolation, but because it is the most available vocabulary for the work the organization is now being asked to do: to stop operating from instinct alone and start deliberately designing what the next stage needs to become.

The word “strategic” is easy. The practice is not. The first time a team sits down to do real strategic planning, they discover they do not entirely agree on where the company is going, or why, or what they are willing to trade to get there. Those conversations are harder than the work was.

And the plan that comes out of them — if it stays honest — is not a document. It is a decision framework: a way of making choices the organization can act on without routing every question back through the same two people. Strategic planning, done seriously, does not make the hard decisions disappear. It creates the structure that lets you make them consistently, without starting from scratch every time.

Why Culture Is the Hardest Thing to Carry

Of everything that gets harder to carry through this transition, culture is the one that surprises leaders the most. Not because they didn’t value it. Because they never had to think about how it traveled.

In the early stages of a technical firm, culture is not a program. It is a presence. It lives in proximity — in who is in the room, on the job site, on the drive to the project. It runs through the founder or principal being close enough to the work that their standards, instincts, and way of handling hard situations are visible to everyone around them.

The team learns what quality looks like not because it was written down, but because they watched it happen. That is a remarkably effective system. It is also a system that was never designed to scale.

As the organization grows, the math changes. The people who have been there from the beginning carry the culture in their bones. The people who joined in the last two years often learned it secondhand, or not fully at all, because no one had time to be deliberate about transmission when the priority was getting them productive.

In industries like transportation infrastructure, firms live in a constant split between the office and the field. Crews, project sites, remote assignments, people who spend more time in a truck or on a job than at a desk — that is what the work requires, and the culture was built with that reality in mind.

The issue is not the structure. The issue is that the informal, presence-based system that carried culture worked only while the organization was small enough for senior people to stay close to most of it.

As the firm grows, that coverage thins. Not because the structure changed, but because the organization got larger than any informal system can reach.

The gaps that open up — between people who have been there long enough to carry the culture instinctively and those who joined recently, between crews who work close to leadership and those who don’t — are not caused by having field staff. They were always there. Growth just makes them visible.

Most leaders sense this before they can name it. Something feels different. The company they are running doesn’t feel quite like the company they built, and the instinct is to blame size — to treat growth itself as the problem.

But size is not the problem. The problem is that the system for carrying culture was personal, informal, and proximity-dependent, and the organization has grown beyond the reach of that system.

Beyond the Poster on the Wall

When culture starts to slip, most organizations respond by writing things down: core values, a mission statement, a set of principles meant to capture what the company has always stood for.

That work is necessary, but it is not sufficient. Culture is not what an organization says it values. Culture is what it consistently reinforces — and what it quietly tolerates. The distance between those two is the real measure of cultural health.

A firm can have a beautifully written set of values and a lived reality on job sites and in project offices that tells a different story. People inside the organization feel that gap long before leadership names it.

Closing that gap is not a communications problem. It is a leadership and accountability problem. The standards the firm intends to hold have to be visible in behavior — in how senior people respond when something goes wrong, in what gets addressed and what gets walked past.

In a distributed firm, where leadership cannot be in every room, behavior is the only carrier that reaches everywhere. Making culture operational means being willing to hold the standard even when it is inconvenient, and building enough structure around that commitment that it does not depend on one leader’s presence or energy on any given day.

What that work produces is not a nicer poster. It is an organization where the culture can travel — where crews three states away and remote staff who have never been to the main office still know what the firm stands for, because they see it in how the work gets done around them every day.

Four Questions Worth Sitting With

The questions below are not an assessment. They are the questions a good advisor would ask in the first honest conversation about culture — questions that are easy to answer in the abstract and much harder to answer about your specific firm, your specific people, right now.

If you asked someone who joined your firm in the last eighteen months — not a senior leader, someone closer to the field or the project work — what this company actually stands for, what would they say? How confident are you in that answer?

What is your culture currently running through — which people, which relationships, which presence — and what happens to it when those people are not in the room?

Those questions are worth sitting with. And they do not stop at the organization. The same logic — the gap between what you say you stand for and what actually gets reinforced, the informal systems that stop scaling, the question of what got you here and whether it will take you where you want to go — applies to a career, to a leadership identity, to the person running the firm as much as to the firm itself.

If you do not protect and evolve your culture on purpose, it will drift to places that cannot hold what you are trying to grow. That is a conversation for another issue.

— Dr. James Bryant, P.E.

P.S. If you found this article useful, I’d love to hear from you — and please consider sharing it with a friend or colleague who might need it.

The meeting ended at 5:47. There were three texts waiting before the door closed behind the last person out of the room. One from a client. One from a project manager who needed a decision by morning. One from someone on the team who had been meaning to schedule a conversation for two weeks and finally found the window — at 5:47 on a Tuesday.

The decision got made in the parking lot. The client got a response on the drive home. The team member got a “let’s connect tomorrow” that both of them know means next week at the earliest.

This is not a bad day. This is just another Tuesday.

How did you get here? The same answer, at every stage — know the work better than anyone else, stay closer to the client, make the call faster, be the most reliable person in the room. That answer worked at every level. New complexity arrived and the same instinct solved it. Show up more, carry more, deliver more. The authority, the reputation, the seat at the table — all of it was earned through that pattern, one stage at a time.

What nobody tells you is that the structure you built to get here becomes the structure you’re trapped inside once you arrive. You built the system. Now the system runs on you — and everything that matters flows through a single point.

Not because the team isn’t capable. But because there has never been enough uninterrupted space to build the structures that would let anything flow differently.

The calendar runs six weeks deep. Every meeting on it was necessary when it was scheduled. Most of them still are. Somewhere in the last hour of every week there is a task list that didn’t get touched, a conversation that keeps getting moved, a piece of thinking that requires more than four uninterrupted minutes to do properly.

And it’s not just the operational things that accumulate. It’s the thinking that would actually change the organization’s direction — the kind that requires stillness and a whiteboard and no notifications and keeps getting deferred because the day has a different opinion about what’s urgent. It’s the conversation with the person on the team who is quietly deciding whether their future is here — the one that deserves real attention, not fifteen minutes between calls. It’s the strategic question that three months of meetings hasn’t answered because nobody has had the protected space to think it through properly.

It accumulates. Quietly, invisibly, in the background of an organization that looks healthy from the outside.

Revenue is solid. The team is good — genuinely good. By every visible measure, this is what success looks like.

And still, there is the quiet awareness that the whole thing runs on one person’s energy. That the decision-making, the client relationships, the culture, the direction — all of it flows through a single point. The weight of that is not dramatic. It doesn’t announce itself. It’s just there — in the background of every meeting, every weekend that almost became rest, every conversation where someone needed the answer and there was only one person they knew to ask.

Nobody talks about this part. Not honestly. The peers are carrying the same weight and performing fine in public. The team sees the leader, not the cost of leadership. There’s no one above you — that’s partly why you’re here. And the leadership content — the books, the conferences, the feeds — talks about vision, delegation, culture, scale. It doesn’t talk about what it costs to carry a system that was built to run on you, for longer than you planned to carry it.

What it also doesn’t talk about is what happens to the person doing the carrying.

Somewhere along the way, the investment started flowing in one direction. Into the organization, into the team, into the clients, into the next problem that needed solving. The development, the thinking space, the honest conversation about where you are and where you’re going — all of it kept getting deferred. Not out of negligence. Out of necessity, or what felt like necessity, for long enough that it started to feel like just the way things are.

You are the resource everyone draws from. And the resource hasn’t been replenished in a long time.

And depletion doesn’t clock out. The presence that isn’t fully there. The conversation that gets a fraction of the attention it deserves. The relationship that’s fine — technically fine — but operating on the fumes of a person who gave everything else away first. The version of themselves their family gets at 7pm versus the version that showed up at 8am ready to solve problems for everyone else.

Not dramatically. Just consistently.

That’s not a complaint. It’s not a crisis. It doesn’t feel like either. It feels like Tuesday. Then Wednesday. Then a quarter that looked fine on paper and left you more depleted than the one before it.

Nobody gave you a blueprint for this part. Not for the weight of it, not for the cost of it, not for what to do when the thing you built is running well and something important is still quietly losing ground.

That’s what this is for — to give language and a way of thinking for the part nobody prepared you for.

If this landed somewhere real for you, I’d like to hear about it. Hit reply and tell me where you are in this.

I want you to win by design, not by drift.

— Dr. James Bryant, P.E.

P.S. If something in this issue sparked a real question about your firm or your leadership — I'm a conversation away. Book a call →