Every person on your team is pushing the cart or riding in it

The tell is not talent or seniority. It is whether a person turns a problem into a step or into a rabbit hole.
By Vadim Zolotokrylin Vadim Zolotokrylin
TLDR

If you have someone on the team who is never the problem, always has a reason, and somehow leaves every conversation heavier than it started, this article names what you are looking at. You'll learn the one tell that separates the people who create opportunity from the people who wait for it, what creating and waiting look like in marketing, operations, design, partnerships, and hiring, and why the mediocre are far harder to remove than the disasters.

Two people bring you the same problem this week. Growth has stalled.

The first one explains why. The market is dead, the channel is saturated, the tooling is worse than it used to be. Every answer you offer opens another hole underneath it. You leave the conversation heavier than you went in, and slightly less sure the company is going to make it.

The second one names the same problem, then keeps going. The market is not dead, it moved, and here is where it went. Here is what we should try first, and here is what I need to try it. You leave that conversation lighter.

Same problem. Same information. Opposite effect on the company.

That difference is not seniority, and it is not talent. It is the only trait we screen for in every role now.

The tell is in the questions people bring you

Listen to the shape of the question, not the topic.

One person raises a problem as a rabbit hole. There is no bottom to it, no move they can name, and the effect on everyone listening is that the future gets dimmer. The other person raises the same problem so everyone can see it, and treats it as the next step to climb.

This is not optimism, and the second person is not pretending things are fine. Both are reading the same numbers. One is working to prove it is impossible. The other acts as if it is possible and goes looking for the way in.

You hear it in the language. "This partner is difficult and does not understand what we do" is one version. "This partner thinks differently, so I am going to find the key to how they think, and we will build something bigger together" is the other. Both are true descriptions of the same person on the other side of the table.

It is every role, not the technical ones

This is not a standard for engineers. It reads the same in every function.

In marketing, creating is talking to people, testing assumptions, building a brand and real relationships with the people you want to serve. Waiting is expecting the market to arrive on its own, as if attention is owed to you.

In operations, creating is hunting inefficiencies and closing them ruthlessly, automating what repeats, making sure things do not break where they should never break. Waiting is sitting on an inefficiency everyone can see until it breaks the business for you.

In design, creating is building an identity that pulls people in and makes their life easier and more exciting. Waiting is producing something mediocre and blaming the absence of direction.

In partnerships, creating is finding the right people and keeping those relationships warm for years, because introductions are what convert. Waiting is sitting in isolation and hoping someone knocks.

In hiring, creating is having the hard conversation early, choosing people for their potential rather than their record of past work, and knowing that money is not what attracts the best. Culture is. Waiting is letting mediocrity settle in because the conversation is uncomfortable this month.

Nothing stands still, so waiting is expensive

There is no neutral state in a business. You are either growing or you are in a slow failing cycle, and the second one is quiet for a long time.

The partner stops finding you interesting. The way things are done moves on while someone keeps doing them the old way, so your costs drift up and nobody can point at when it happened. The marketing gets stale. The design gets worse. None of it arrives as a crisis. It arrives as a series of months where nothing improved.

There is also a noise problem, and it is worth saying plainly. The person quietly pushing the cart up the hill is usually the quietest one in the room. The people sitting in the cart are often the loudest, because being visibly present is the substitute for pulling. That noise is not harmless. It confuses you about who is actually carrying the business, and it slows down the decision you should be making.

A and B, and how long you tolerate B

Every team has A people and B people. That is not a moral judgment, and it is not permanent.

People move from A to B and back again. A bad quarter, a personal crisis, a project that grinds someone down. That is normal, and we have all been there. What matters is how long they stay there, whether they can see it themselves, and how fast they climb back.

Your job is not to fix them. It is to decide how long your A people have to carry weight they did not sign up for. They notice that long before you do.

Here is the uncomfortable part. Firing someone who fails spectacularly is easy. Removing someone mediocre is the hardest thing a founder does, because the signals are small and they always leave room for the thought "maybe next quarter, and maybe I am the one who is wrong." That thought is expensive. It is usually the most expensive thought in the company.

What works is unglamorous. Nudge people directly when you see it. Benchmark them against each other so the comparison is real and not a feeling. Then cut the tail, and do it while the problem is still small.

The half that is yours

None of this is fair unless the room to act is genuinely there, and this is where founders break their own teams.

Publish the vision, the mission, the code of conduct, the operating principles, and the goals with their key results. Ours live in version control alongside the code, where anyone can read them without asking us. That is the founder's half of the deal. Everything after that is theirs to figure out. Rules on paper are also what replaces the management layer you decided not to build.

Then let people perform without babysitting them, even when it is itchy to jump in and help. Keep professional boundaries. Spend less time with them, not more. Ownership without authority is just exposure, and people stop taking it quickly.

Waiting has one legitimate use, and it is yours. Wait to see whether someone moves on their own. Do not remind people of what they should be doing themselves, because the reminder destroys the only clean signal you had. When someone commits to a date, let the date arrive.

Do not confuse initiative with results. Initiative guarantees an outcome, and the outcome is sometimes a failure. What separates people is what happens next. Some recalibrate fast and never make that mistake again. Some repeat it in the same spot, quarter after quarter. And sometimes it is not the person at all. The work may be stuck in the seam between two teams, where the fix is ownership rather than an exit.

When you reject a proposal, say exactly why, and expect a better one back. The ones worth funding carry vision and some wisdom, grounded in reality. Not the most detailed execution plan.

Stay honest about how waiting starts, because it starts in anyone. It starts as fear of what facing the real situation will cost, and fear never announces itself as fear. It starts when someone lets you down and going passive feels principled. What breaks it is dropping the ego and going past what the other person expected of you. Anyone can do that, which is why this belongs in a conversation with the person rather than only in a private judgment about them.

Pay for it, or you will be the only source of it

Someone who consistently creates opportunity is making the business scalable, and that is co-ownership work. We treat it that way. People who bring opportunity in become partners with a direct share of what it produces, because they are creating the thing rather than consuming it.

When someone says just give me an opportunity and I will take it, we give them one if we have it. From that same moment we start looking for the person who would have created it themselves. Not out of spite. A company where the founder is the only source of opportunity has exactly one bottleneck, and it is the founder. That is also what a technical partner is for: not more hands on work you already scoped, but someone who brings you the work you had not named yet.

This gets more important every month. Execution keeps getting cheaper and AI is making it cheaper still. Doing the task is no longer the scarce thing. But AI is an amazing helper and a terrible leader, and it will not decide what is worth doing. Knowing which direction is worth walking in, and having the conviction to move before anyone confirms it, does not commoditise.

So the practical version, for the week you are in right now. Listen to the questions people bring you and notice which ones open a hole and which ones open a path. Ignore the volume, because the title on the door and the noise in the meeting tell you nothing about who is pushing. Then look for the quiet person with their shoulder against the cart, and make sure they are not carrying anyone who could be walking.

Have a suggestion? Edit this page
Newsletter
Fresh insights,
straight to your inbox