What Lobbying in Albany Taught Me About Leadership
Having the better argument is not the same as having influence.
By Eric J. Dalton · · 8 min read
The most useful leadership education I ever received did not happen inside a company.
It happened in advocacy work, spending time in Albany, through my involvement with the New York State Association of Health Care Providers and the broader homecare industry, trying to help people who make policy understand what our part of the healthcare system actually looks like from the inside.
I went into it thinking the job was to be right.
That turned out to be the least important part.
A different environment
Organizational leadership, whatever its difficulties, has a structural advantage that is easy to take for granted: within your own organization, there is a mechanism for decisions to become actions.
Government is not that.
A policymaker is operating inside competing constituencies with legitimate and incompatible needs. Severe time constraints. A regulatory environment of real complexity. Budget realities. Political considerations that are not going away because your issue is important. Multiple stakeholders with sophisticated representation, all of whom believe their position is the reasonable one, and many of whom are correct within their own frame.
Into that environment walks an advocate who has spent years thinking about one specific problem.
You may understand your issue in extraordinary depth. You may have lived it operationally for a decade. And you may get four minutes with someone who has eleven other meetings that day, none of which are about your subject.
You may have studied an issue for a decade. You may get four minutes to explain it.
That gap is not an insult. It is the actual working condition. And it produces a leadership question that turns out to be the same question executives face everywhere: can you explain why this matters clearly enough that another person can understand the human consequences?
What I actually learned
Know your audience. The way you talk to an industry expert is not the way you talk to an elected official, and the difference is not about intelligence. It is about context. The expert shares your assumptions, vocabulary, and mental model of the system. The policymaker does not, and should not be expected to. They are responsible for a hundred domains, none of which they can know as deeply as the person in front of them. Adjusting to that is not condescension. It is basic communication competence, and the advocates who cannot do it never get anywhere.
Simplify without dumbing down. These are different operations. Dumbing down removes information. Simplifying removes the parts that are not load-bearing for the decision at hand. Good policy translation reduces complexity to a clear set of human consequences and understandable choices, without misrepresenting what is actually true. If your simplification makes the issue sound easier than it is, you have not simplified. You have distorted, and you will be caught.
Stories and data need each other. Statistics establish that a problem is real, sized, and not anecdotal. Human examples establish why it matters and make it memorable. Data alone gets nodded at and forgotten. Stories alone get received as one person's experience. Together they do something neither can do alone, and any leader making a case to any audience should be thinking in both registers.
Relationships precede influence. This is the one I would put first if I were ranking them. If the only time you appear is when you need something, you are not building a relationship. You are making withdrawals from an account you never funded. The people whose input actually gets weighed are the ones who were present before the ask, who were useful when nothing was at stake, and who have a track record of being straight even when it did not serve them.
Preparation is the whole thing. Know the issue cold. Know the objections better than the people raising them. Know the specific ask. And know what can realistically happen, because an ask that ignores what is possible signals that you have not done your work, and it costs you credibility that is expensive to rebuild.
Authority and influence are different capacities. An advocate has zero authority over a policymaker and can still develop meaningful influence. That distinction turns out to be the most transferable thing in this entire experience, because most of modern leadership works the same way. Inside organizations, leaders constantly need to move peers, partners, boards, regulators, families, clients, and stakeholders they cannot direct. Authority handles a shrinking share of the work.
Change is usually incremental. The dramatic moment where one conversation reverses everything is largely a fiction. Durable change comes from persistence, from staying engaged after the meeting ends, following up, providing information that was requested, being useful across a cycle, and coming back next session. Advocates who treat a single meeting as the event will conclude the process does not work.
Listening is part of advocacy. If you do not understand the other side's constraints, you are not negotiating with reality. You are negotiating with a version of the situation you constructed. The constraints are often the most valuable information in the room, and you only get them by asking and then being quiet.
Be clear about the ask. A conversation without a defined ask is an interesting meeting with no consequence. I have watched well-prepared, passionate people spend their entire allotted time explaining a problem beautifully and then leave without ever stating what they wanted done. Everyone walks out feeling good. Nothing happens.
Never confuse passion with persuasion. Caring deeply about an issue does not automatically make your argument persuasive. It makes you sincere, which is necessary and insufficient. Passion without preparation reads as noise. Passion built on precision is formidable.
Caring deeply about something does not make your argument persuasive. It only makes it sincere.
The discipline of the short meeting
If I had to name the single most transferable skill I developed, it would be the ability to make a complete case in a very small amount of time.
That sounds like a communication skill. It is actually a thinking skill, because you cannot compress what you have not fully understood. Long explanations are frequently a symptom of unfinished analysis: the speaker has not yet determined which parts are essential, so everything gets included and the listener is left to sort it out.
The discipline that produces compression is uncomfortable. It requires deciding what the single most important thing is and accepting that four other important things will not be said. Advocates hate this, because every omitted point feels like a concession. But an argument with one clear load-bearing claim survives a four-minute meeting. An argument with six equally weighted claims does not survive any meeting, because nothing lands hard enough to be remembered afterward.
The practical version I came to rely on: know the one sentence you need the other person to still have in their head tomorrow. Everything else in the conversation is supporting material for that sentence, and if time runs out, the sentence has to have been said.
That habit changed how I run internal meetings, how I brief a board, and how I open any difficult conversation.
What I got wrong early
I would rather describe my own errors than imply I arrived understanding any of this.
I over-prepared the wrong things. I built comprehensive command of the issue and neglected to think about what the person across from me was weighing: their constraints, their other obligations, the competing interests already in their inbox. I knew my side of the conversation perfectly and had barely considered theirs.
I also mistook agreement for progress. A meeting where someone nods, expresses concern, and says the issue is important feels like a win. Frequently it is just politeness, and politeness is not commitment. The only way to know the difference is to make a specific ask and observe what actually happens next.
And I underestimated how much of the outcome was determined before anyone sat down, by who had been present over the preceding years, who was trusted, and whose information had proven reliable. The meeting is where the result gets recorded. It is rarely where the result gets decided.
Why this transfers
Everything above was learned in a policy context. Almost none of it stays there.
Consider how much of an executive's real work now happens without authority.
Negotiating with vendors and partners whose incentives differ from yours. Communicating with a board that has limited time and a different vantage point. Working with regulators whose constraints you do not control. Building coalitions across organizations. Managing change inside your own company, where formal authority exists but produces compliance rather than commitment. Selling anything. Navigating internal politics, which is really just influence operating without an org chart.
In every one of those situations, the skills are identical to advocacy: understand the audience, translate complexity into consequence, build the relationship before the ask, prepare thoroughly, listen for constraints, state the ask, and stay engaged over time.
A meeting without a defined ask is an interesting conversation with no consequence.
What it changed in me
The thing advocacy work eventually taught me is that being right is a starting position, not an argument.
I still believe you should be right. Preparation and accuracy are non-negotiable, and I have watched people lose permanently because they were caught overstating something once. But being right earns you the opportunity to be heard. It does not do the work of persuasion, and treating it as though it should is one of the more common ways that intelligent leaders become ineffective.
The work of persuasion is the harder, slower, more human part: understanding what the other person is actually weighing, making your case in terms that connect to it, being useful before you are needy, and returning again after nothing happened the first time.
Leadership is less about possessing authority than most people assume when they start out.
It is mostly about learning how to move people, institutions, and ideas toward action, usually without any structural ability to require it.
