The Women Not Waiting for Permission
- Jonell Zimmerman
- May 26
- 3 min read
Last week someone sent me a message that I've been sitting with since.
She'd been thinking about using AI in her work for months. Had the tabs open. Had watched the tutorials. Had made the mental list of all the reasons she should wait a little longer.
"I keep feeling like I need to earn the right to start," she wrote. "Like there's a course I should finish or a certification I don't have yet."
I knew that feeling before she finished the sentence. I lived it.
The AI conversation has a permission problem.
Somewhere in the past three years, the narrative got set by people who were already technical. Already credentialed. Already inside the companies building these tools. And the implicit message that filtered down was: AI is for people who understand AI.
If you've ever read an AI explainer and felt more confused at the end than when you started, that's not a you problem. That's a translation problem. The room where these decisions were made wasn't built for you.
And here's the thing about rooms not built for you: you can wait for an invitation, or you can build a different room.
Women are building the different room. And the data is starting to show it.
Boston Consulting Group published findings this year that landed quietly and deserve to be louder: women-founded AI companies generate 22% more revenue per dollar raised compared to all-male founding teams.
Twenty-two percent. Consistent. Measurable. Not a rounding error.
When I read that, my first reaction was almost defensive on behalf of the data. Because I know what the immediate interpretation will be. "That's nice for equity. A good sign for representation." But that's not what 22% means. That's not the story.
The story is operational efficiency.
Women who have spent careers justifying every resource request, proving the ROI of every hire, making the case again and again for why their work matters— those women don't build wasteful systems. They build lean. They build intentionally. They solve the actual problem instead of the imaginary one.
They also build in community from the start. Not because they were told to. Because they've always known that the only way through hard things is with people. You test early, adjust often, listen to the people closest to the problem. That's not a soft skill. It's a competitive advantage.
And there's an ethics layer that I think gets undervalued. When you've been on the receiving end of systems designed without you in mind— and most of us have, in one form or another— you don't build products that way. You ask "who does this affect?" before you ship.
That's not slowing down. That's building right.
Here's what I watch in the women's AI spaces I'm in. The women moving fastest aren't the ones who waited until they felt ready. They're the ones who started with a small, real problem and let the learning happen in the work. A teacher rebuilding lesson planning. A nonprofit founder automating grant research. An operations manager who cut onboarding from three days to one.
They didn't wait for permission. They just started.
The permission myth costs us time we don't have.
Every week spent waiting to feel ready is a week someone else is learning by doing. And here's the thing about learning-by-doing in AI: the tools are more accessible right now than they have ever been. The starting line is free. The first experiment takes twenty minutes. The first win— however small— is usually enough to make you want another one.
Timnit Gebru and the team at DAIR just released a free, open-source ethics toolkit that gives non-technical people a structured way to audit AI systems in their own organizations. No computer science degree required. Just the questions, clearly written, in human language.
That's what women building infrastructure looks like. Not a product to sell. A resource to share. Here, take this. Use it.
The permission you're waiting for isn't coming from outside. It's already inside you. It's the curiosity you brought to every hard problem before this one. The pattern recognition that got you where you are. The judgment you've spent years building.
AI doesn't replace any of that. It runs on it.
This week, pick one thing you're already spending time on that you find tedious or repetitive.
Not something big. A meeting summary. An email you write the same way five times a week. A research task that takes forty minutes you don't have.
Take ten minutes. Open ChatGPT (free) or Claude (free). Describe the task. See what happens.
Don't try to automate your whole job in an afternoon. Just solve one small thing. See how it feels to get that time back.
That feeling— the "oh, that actually worked" feeling— that's the beginning. Chase it.
And if you know someone who's been waiting to start with AI, this is the issue to send them. Forward freely.
— Jonelle
Comments