Skip to content
Systems & Soul
(09) Society & What Comes Next

Lessons From Being a Woman in Tech

July 24, 2026 4 min read

I did not enter technology through a polished front door with a welcome sign. I built my way in. I founded CI Web Group in 2006, served the trades, took early bets, and learned that being a woman in technology often means you are evaluated twice: once for the idea and once for the audacity of saying it out loud. That can make you smaller if you let it. I chose to let it make me more exact.

What did being a woman in tech really teach me?

It taught me that competence is not always recognized at the same speed it is earned. It taught me not to confuse being underestimated with being unqualified. It taught me to bring proof, build systems, and stop making my confidence dependent on whether the room was generous.

That is the deeper story behind Confidence as a Female CEO. Confidence was not handed to me. It was built through decisions that had consequences.

When does this lesson matter most?

It matters when you are early. Early on an idea, early on a market shift, early on a technology the room still thinks is optional. Being early already makes people uncomfortable. Being a woman and early can make them question your tone before they question their own delay. That is when you need evidence, not permission.

What fails when women absorb the room's doubt?

They over-explain. They wait to be invited. They soften the sentence until the truth loses its edge. They collect credentials to earn a confidence no credential can give. I understand the instinct. I have felt it. But the market does not reward the version of you that made everyone comfortable and nobody move.

The company loses too. When women shrink their point of view, businesses lose pattern recognition, customer empathy, operating truth, and leadership range they badly need.

The lesson was never "be louder." The lesson was "stop negotiating with the part of the room that benefits from your hesitation."

What proved it to me?

The trades proved it. I built in an industry that values proof. Owners care whether the phone rings, the system works, the customer experience improves, and the vendor tells the truth. Over time, that gave me a cleaner scoreboard than approval. Writing Hands Up gave me another one: say the real thing, in my voice, with the receipts I am allowed to carry.

How should you use this?

If you are a woman building in tech, write down the evidence you already have. Not the affirmations. The proof. Decisions made, problems solved, systems built, people helped, standards kept. Then choose the next room based on the work, not the room's comfort with you. If you want to hear the story live, start at speaking. The point is not to become less human. It is to become harder to move off the truth. That is the lesson I keep handing forward: the room's reaction is data, but it is not your identity and it is not your strategy.