Leadership creates distance from execution unless the leader deliberately works against it. Everett Barry has experienced that problem from several angles: technical work, company building, growth, management, and now go-to-market engineering at Clay.
His central lesson is that operating judgment does not survive indefinitely on old frontline experience. Leaders need recurring contact with how the work actually feels, where it breaks, and what people do when the formal process is not enough.
Good instincts are not yet an operating system
Everett is candid about his first leadership experience:
I had some instinct for what made sense in terms of leading people, but in terms of operationally managing the team, I was super, super green.
Many strong individual contributors encounter the same gap. They understand the work and may be trusted by peers, but management introduces different responsibilities: setting priorities, creating feedback loops, allocating capacity, communicating context, and making performance expectations explicit.
Instinct is useful. Repeatable leadership requires operating mechanisms that help other people act without waiting for the leader's next intervention.
Distance changes what leaders can see
As responsibility increases, leaders spend more time in summaries: dashboards, forecasts, planning meetings, and management updates. Those tools are necessary, but they filter reality.
Everett argues that leaders lose touch when they no longer feel the frontline periodically. A metric can show that conversion declined. A frontline conversation can reveal that the new workflow makes the most important customer evidence difficult to capture.
The point is not for executives to perform every task. It is to maintain enough proximity to recognize when the model and the work have diverged.
Go-to-market engineering joins technical and commercial judgment
GTM engineering sits between systems and execution. It uses data, automation, and technical workflows to improve how revenue teams identify, reach, and serve customers.
The role is valuable because commercial problems rarely respect functional boundaries. A weak territory model affects routing. Poor enrichment affects prioritization. Unclear ownership produces duplicated outreach. A disconnected tool may create more work while reporting that automation increased.
A GTM engineer needs enough technical ability to build and enough field understanding to know what should be built. Without both, the function risks optimizing an activity that should not exist.
Strong organizations teach people how decisions get made
Everett highlights the quality of leadership at Clay, particularly its understanding of organization and efficient growth. That does not come from micromanagement. It comes from giving people enough context to make aligned decisions.
Teams move faster when they understand:
- The result the company is trying to produce
- The constraints that matter
- Who owns the decision
- Which evidence should change the plan
- When escalation is required
That clarity is especially important in fast-growing companies, where yesterday's informal coordination quickly becomes tomorrow's operating bottleneck.
Frontline proximity improves prioritization
The farther a leader moves from execution, the easier it becomes to overestimate the value of a new initiative and underestimate its adoption cost.
Staying close to the work changes prioritization. Leaders see which manual steps are genuinely painful, which exceptions are frequent enough to deserve design attention, and which complaints are symptoms of a deeper ownership problem.
That is where technical teams can create real leverage. The best automation does not simply save clicks. It removes a recurring constraint that prevents the commercial team from doing higher-value work.
The practical lesson for GTM leaders
Leaders can preserve operating judgment with a simple recurring rhythm:
- Review quantitative performance.
- Observe or perform a small amount of frontline work.
- Compare the formal process with the real one.
- Choose the constraint worth solving.
- Verify that the change improved the user experience and business result.
The objective is not permanent immersion. It is enough contact to keep strategy, systems, and execution connected.
About the guest
Everett Barry leads Go-to-Market Engineering at Clay. His background includes technical work, founding, growth, and revenue leadership across different stages of company development.
