Your Logo Doesn't Own the Issue

The Military Community Nonprofit Industrial Complex

The Good, the Bad, and the Ugly

Day 5: Your Logo Doesn't Own the Issue

Military and veteran advocacy has a strange territorial streak.

Organizations don't just develop programs.

Sometimes they start behaving as though they own the issue.

Our legislation.

Our veterans.

Our survivors.

Our congressional office.

Our coalition.

Our initiative.

Our advocacy campaign.

Some of that language is harmless shorthand.

Organizations need branding.

They need to distinguish their programs.

They need to communicate their accomplishments to donors, members, and the public.

They need to protect resources they have spent time and money developing.

And yes, sometimes one organization really did create an initiative and deserves credit for it.

But let's establish something before we go any further:

No nonprofit owns veterans.

No organization owns survivors.

No organization owns caregivers.

No organization owns military families.

No organization owns a public-policy issue.

And nobody gets exclusive custody of Congress.

Branding Is Not the Enemy

Let's start with the good.

Organizations need identities.

A recognizable name and logo can build trust.

If someone sees an organization's logo and knows:

“They help with VA claims.”

That's useful.

If survivors recognize an organization as somewhere they can find support, excellent.

If congressional staff know which organization has expertise on a particular issue, that credibility can take years to build.

Branding also helps organizations raise money.

Donors want to know who they are supporting.

Sponsors want recognition.

Members want to identify with the organization.

The public needs to distinguish one program from another.

There is nothing inherently wrong with putting your logo on something you created.

There is also nothing wrong with saying:

“Our organization helped accomplish this.”

If you did the work, take the credit.

Just don't confuse taking credit with taking ownership of the entire cause.

Expertise Deserves Recognition

Some organizations develop extraordinary expertise in particular areas.

One may understand survivor benefits exceptionally well.

Another may specialize in disability claims.

Another may have decades of experience with employment programs.

Another may understand caregiver policy.

Another may specialize in homelessness, mental health, toxic exposure, education, or military-family issues.

That expertise has value.

Organizations invest years developing it.

They build relationships.

They hire professionals.

They collect data.

They train volunteers.

They develop resources.

They learn from mistakes.

When an organization has earned credibility in a particular area, respect it.

But expertise is not ownership.

Other organizations are still allowed to work on the issue.

Independent advocates are still allowed to have opinions.

People affected by the policy are still allowed to organize themselves.

And someone else may occasionally develop a better idea.

Collaboration Does Not Mean Everything Is Free

This distinction matters.

If another organization creates a training program, database, software platform, research product, mailing system, donor list, membership database, curriculum, or other resource, that resource does not automatically become community property because everybody involved cares about veterans.

Organizations spend money developing infrastructure.

Sometimes a lot of money.

They may pay licensing fees.

Software fees.

Consultants.

Researchers.

Designers.

Attorneys.

Technology companies.

Staff.

Vendors.

Those resources belong to the organization that created, purchased, licensed, or maintains them according to whatever agreements apply.

Collaboration means:

“How can we work together?”

It does not mean:

“I like what you built, therefore I am entitled to use it however I want.”

Resource Theft Is Not Advocacy

This is where things get ugly.

Suppose an organization pays for an advocacy platform that allows supporters to send messages to Congress.

Every message sent through that system costs the organization money.

Another group disagrees with the organization's position.

Fine.

Disagreement is healthy.

Oppose the position.

Write your own letter.

Create your own campaign.

Contact Congress directly.

Build your own advocacy page.

Ask your members to call.

Publish your argument.

Do all of it.

What you don't do is deliberately hijack someone else's paid advocacy infrastructure, rewrite the message for the opposite position, and encourage people to send it through the system knowing the organization you're opposing is paying the bill.

That's not clever advocacy.

That's using somebody else's resources against them.

And the size of either organization doesn't change the ethics.

A multimillion-dollar organization does not get to do it to a small grassroots group.

A small grassroots group does not get to do it to a multimillion-dollar organization.

Wrong does not become right because you think the other organization can afford it.

If your argument is strong, build your own damn campaign.

Protecting Resources Is Reasonable

Organizations should protect certain things.

Member information.

Donor information.

Personal data.

Confidential case information.

Proprietary materials.

Licensed software.

Internal databases.

Passwords.

Research that isn't ready for publication.

Private strategy discussions.

Intellectual property where applicable.

Those boundaries are not evidence that an organization “doesn't collaborate.”

Responsible organizations have legal and ethical obligations to protect information and resources.

Collaboration does not require handing everyone the keys to the building and hoping nobody steals the copier.

Boundaries are healthy.

Territorialism is something different.

Congressional Offices Do Not Belong to You

This one occasionally gets weird.

An organization develops a good relationship with a congressional office.

Excellent.

That's valuable.

Then another advocate meets with the same office.

Suddenly somebody acts like their date was stolen.

Congressional offices represent constituents and work with stakeholders.

They are allowed to talk to more than one veterans organization.

In fact, they should.

An office hearing multiple perspectives on an issue is not betrayal.

It's representative government.

Organizations can absolutely coordinate congressional outreach.

That can prevent duplication and strengthen messaging.

But:

“We have the relationship with that office”

should never become:

“Nobody else should talk to them.”

Congress does not have assigned nonprofit custody.

Neither Do Legislative Issues

Sometimes organizations become closely identified with particular legislation.

That's understandable.

Maybe they helped develop it.

Maybe they found a congressional sponsor.

Maybe they spent years building support.

Maybe their members drove the advocacy campaign.

They deserve recognition for that work.

But once legislation enters Congress, it becomes public policy.

Other organizations are allowed to support it.

Oppose it.

Suggest amendments.

Research it.

Discuss it.

Contact Congress about it.

And yes, criticize it.

The fact that your organization spent five years advocating for something does not mean everyone else has to ask permission before having an opinion.

If anything, broad engagement can make legislation stronger.

Credit Matters

Now let's flip this around.

Just because nobody owns an issue does not mean nobody deserves credit.

If another organization did the work, acknowledge it.

If someone spent years developing a policy proposal, don't suddenly act like your organization discovered it last Tuesday.

If another group built the coalition, don't erase them from the story.

If a volunteer developed the research, recognize them.

If multiple organizations contributed, say so.

There is plenty of credit to go around.

And sharing it costs nothing.

Well, except perhaps a little ego.

Budgets remain unaffected.

Stop Taking Credit for Other People's Work

There is a subtle version of this that happens frequently in coalition work.

A coalition accomplishes something.

Then every member organization sends an email:

“WE DID IT!”

Technically, maybe.

But there is a difference between:

“We were proud to be part of the coalition that accomplished this.”

and:

“Our organization made this happen.”

Words matter.

Coalition work should produce coalition credit.

If ten organizations worked on something, there is no reason nine of them need to disappear when the victory graphic gets designed.

Good partners celebrate each other's contributions.

Bad partners start rewriting history before the ink on the bill is dry.

Competition Is Not Always Bad

This series isn't going to pretend every nonprofit needs to hold hands and sing around a campfire.

Organizations compete.

For donations.

For grants.

For members.

For media attention.

For congressional access.

For talented staff.

For volunteers.

For corporate partnerships.

Sometimes competition is healthy.

It can encourage innovation.

It can push organizations to improve services.

It gives veterans and families choices.

It prevents one organization from becoming the sole gatekeeper for an entire community.

The existence of multiple organizations working on similar problems is not automatically wasteful.

Sometimes different approaches are exactly what the community needs.

But competition becomes destructive when beating the other organization becomes more important than solving the problem.

Duplication Deserves Examination

There are also legitimate reasons to ask whether organizations should collaborate or consolidate efforts.

If six organizations are running nearly identical programs in the same community while another critical need receives almost no attention, that deserves discussion.

Could resources be shared?

Could referrals be coordinated?

Could organizations specialize?

Could one organization provide infrastructure while another provides expertise?

Could they jointly fund research?

Could they share training?

Could they coordinate advocacy?

Collaboration does not always mean merging.

Sometimes it simply means:

“You do this well. We do that well. Let's stop pretending we each need to do both.”

That's not weakness.

That's efficiency.

Referrals Are Advocacy Too

One sign of a strong organization is the willingness to say:

“We don't do that, but I know who does.”

You do not have to provide every service.

You do not have to solve every problem.

You do not have to keep every person who contacts you inside your organizational ecosystem.

Sometimes the best service you can provide is sending someone somewhere else.

A veteran doesn't need your organization to be the hero.

They need the problem solved.

If another nonprofit, government agency, community organization, attorney, VSO, or specialist is better equipped to help, make the referral.

You didn't lose a customer.

You served the mission.

The People Are Not Leads

This deserves repeating.

Veterans are not customer acquisitions.

Survivors are not membership prospects.

Caregivers are not donor-conversion opportunities.

Military families are not email-list growth.

Organizations need membership.

They need donors.

They need supporters.

They need email lists.

Those things help organizations operate.

But there is a difference between inviting someone into a community and treating their need as an opportunity to expand your database.

Help first.

Brand second.

Don't Make People Navigate Your Turf War

This is perhaps the most important part.

The veteran needing help should not have to understand which organizations are feuding.

The surviving spouse looking for benefits information should not care which group gets credit for the referral.

The caregiver looking for respite care should not need a flowchart showing which nonprofits cooperate with each other.

The congressional staffer trying to understand legislation should not receive five conflicting versions of the same facts because organizations refuse to coordinate.

The people being served should not become collateral damage in organizational politics.

They have enough problems.

They don't need ours too.

Good Collaboration Has Boundaries

Healthy collaboration does not require organizations to agree on everything.

You can work together on one bill and oppose each other on another.

You can share research without sharing donor lists.

You can coordinate congressional meetings without merging organizations.

You can refer clients without surrendering your identity.

You can publicly disagree without becoming enemies.

You can say:

“We disagree with their position on this issue, but they do excellent work in another area.”

Imagine that.

Nuance.

Wild concept.

Good, Bad, and Ugly

The good: Organizations develop expertise, infrastructure, trusted brands, strong congressional relationships, useful programs, and specialized resources. Collaboration can multiply those strengths and get people help faster.

The bad: Competition for funding, recognition, members, access, and attention can create unnecessary duplication and discourage organizations from sharing information or credit.

The ugly: Organizations can become territorial, claim ownership over issues or communities, hijack resources, erase other contributors, discourage people from working with “competitors,” or prioritize organizational victory over community outcomes.

The military community does not need nonprofit turf wars.

It needs solutions.

The Logo Is Not the Mission

Put your logo on the program.

Put it on your research.

Put it on your annual report.

Put it on the banner.

Put it on the T-shirt.

Put it on the coffee mug if you really must.

Branding is fine.

Take appropriate credit for the work you actually did.

Protect resources that genuinely belong to your organization.

Build relationships.

Develop expertise.

Compete when competition makes everyone better.

But don't confuse your organization's investment in an issue with ownership of the issue itself.

Your logo doesn't own veterans.

Your logo doesn't own survivors.

Your logo doesn't own caregivers or military families.

Your logo doesn't own Congress.

Your logo doesn't own the cause.

And if another organization can solve the problem better, faster, cheaper, or more effectively?

Work with them.

Refer to them.

Learn from them.

Or get better.

Because the person waiting for help probably does not care whose logo is on the solution.

They care whether the solution works.

And if getting your organization's name on the victory matters more than getting the victory?

You may want to check the mission statement again.