Stop Hiding That You Use AI at Work

You're not cheating

Let's get this out of the way: using AI to help you write a donor letter is not plagiarism. Using it to summarize a 40-page report before a meeting is not cutting corners. Using it to brainstorm program evaluation frameworks is not intellectual dishonesty. It's using a tool that makes you better at your job, which is something professionals have been doing since the invention of the calculator and arguably since the invention of the pencil.

The discomfort people feel is real, and it's worth understanding where it comes from. Most of us spent years in school being told that the point of writing was to prove we could do it ourselves. Using outside help was cheating. That instinct doesn't vanish when you enter the workforce, even though the rules have completely changed. Nobody at your organization is grading you on whether you produced every word unassisted. They're evaluating whether the work is good and whether the mission moved forward.

The secrecy is the problem

When people use AI quietly and pretend they didn't, a few things go wrong.

First, nobody learns from each other. If your development director found a way to cut grant report drafting time in half but keeps it to herself because she's embarrassed, the entire organization misses out. The best AI workflows I've seen at mission-driven organizations spread through informal sharing: someone mentions a technique in a team meeting, a colleague tries it, and suddenly a whole department is working more effectively.

Second, leadership can't make informed decisions about tools and policies if they don't know what staff are using. A lot of organizations have a gap between their official position on AI (which is often silence) and what's happening in practice (which is often widespread quiet adoption). That gap creates risk, because the people using AI without guidance are also the people most likely to make a mistake with sensitive data.

Third, and most simply, hiding something that helps you work better is exhausting. The mental overhead of concealment takes energy that could go toward the work itself.

What "of course we use AI" looks like

The healthiest organizational cultures around AI are the ones where using it is simply expected. Not mandated, not policed, but normalized the way using a spreadsheet or a search engine is normalized. Nobody announces that they used Google to research a funder before a meeting. Nobody discloses that they used Excel to calculate their budget projections. AI should eventually occupy that same unremarkable space.

Getting there requires leadership to say it out loud. Something as simple as an executive director mentioning in a staff meeting that she used AI to help organize her board presentation does more to shift culture than any formal policy memo. It gives people permission in a way that a written document, however well-crafted, often doesn't.

A few organizations I've worked with have gone further and built AI sharing into their team routines. One runs a monthly "what worked" session where staff share AI techniques they've tried. Another added a Slack channel specifically for tips and experiments. These aren't mandatory or performative; they just create space for people to be open about how they work. The result is that new hires absorb the culture immediately: here, we use the best tools available, and we talk about it.

But there is a line

Normalizing AI use doesn't mean anything goes. There is a meaningful difference between using AI as a thinking partner and outsourcing your thinking entirely.

Using AI to generate a first draft that you then reshape with your expertise and judgment? That's leverage. Pasting a funder's RFP into ChatGPT and submitting whatever comes back without reading it critically? That's abdication, and it usually produces work that reads exactly like what it is.

The distinction matters because the value your organization provides comes from the people in it: their knowledge of the community, their relationships with stakeholders, their understanding of what the data means in context. AI can accelerate how that expertise gets expressed, but it can't replace the expertise itself. A grant narrative written by someone who deeply understands the program and uses AI to help articulate it clearly is a fundamentally different document from one generated by someone who doesn't understand the program and hopes the AI will cover for them. Funders can tell the difference. (They're reading a lot of AI-generated proposals right now, and the bar for what passes as "good enough" is rising fast.)

Making it part of your culture

If you're in a leadership role, you can shift the culture around AI use with a few deliberate moves:

Name it openly. Mention your own AI use in meetings and communications. If you used AI to help prepare something, say so casually. The casualness is the point.

Frame it as professional development. Using AI well is a skill, and like any skill, people get better with practice and peer learning. Position it as something the organization invests in rather than something people do furtively on their own.

Draw the line clearly. An AI use policy that distinguishes between appropriate and inappropriate use gives people the confidence to use AI openly. When staff know where the boundaries are, they stop worrying about whether they're crossing them.

Celebrate the time savings, not the tool. When someone finds a way to reclaim hours in their week, the interesting part is what they did with those hours. The program coordinator who used AI to streamline reporting and then spent the reclaimed time on client follow-up deserves recognition for the outcome, and that recognition reinforces the culture you're building.

The real waste

Here's what I keep coming back to: people who work in the mission-driven sector are some of the most committed professionals you'll find. They took roles that often pay less than the private sector because the work matters to them. Asking those people to spend their finite hours on tasks that a machine could handle, tasks like reformatting data, drafting routine correspondence, or compiling information from one format into another, is not protecting the integrity of their work. It's squandering their talent.

The organizations that figure this out first won't just be more productive. They'll be better places to work, because the people in them will spend more of their time on the parts of the job that drew them to mission-driven work in the first place.