I used to think competence would speak for itself. Build the thing. Solve the problem. Learn the market. Know the customer. Do the work until nobody can deny it. That is still the foundation, but it is not the whole story. Competence without confidence can become a beautifully built cage. You know enough to move, but you keep asking the room whether you are allowed.
What is the difference?
Competence is capability. Confidence is permission you learn to give yourself after the evidence is strong enough. Competence says, "I can." Confidence says, "I will." The danger is confusing one for the other. Confidence without competence becomes noise. Competence without confidence becomes invisible labor.
I wrote Confidence as a Female CEO because that distinction cost me enough to respect it.
When does the gap show up?
It shows up when the stakes rise. A bigger room. A harder negotiation. A technology bet that makes people roll their eyes before they see the proof. A season where the company needs you to decide before everyone claps. I have lived that from the early days of CI Web Group through the rebuild, the stages, and the writing of Hands Up.
What fails when you have only one?
Confidence without competence damages trust. The room may follow the energy for a while, but customers eventually experience the gap. Competence without confidence damages impact. The best idea stays muted. The more prepared woman waits while someone less prepared explains the future with more certainty.
Companies lose when they reward only volume. They also lose when competent people hide behind "I'm just being humble." Humility is not self-erasure. Humility is being honest about the work, including the fact that you are ready.
Competence is the receipt. Confidence is the courage to hand it to the room without apologizing for the total.
What has proved this to me?
The proof is every time I moved before consensus and had to let the work catch up to the room's belief. Building for the trades, talking about AI before it was comfortable, and leading a company through reinvention all required both. Becoming Dallas's grandmother made the balance clearer. I do not want to model arrogance. I also do not want to model a life where earned capability keeps asking to be excused.
How do you build both?
Start by separating the two on paper. Where are you genuinely not competent yet? Go learn. Where are you competent and still acting like a guest in your own field? Move. Ask for the stage, make the offer, name the standard, publish the point of view. If your next step is building the operating system around that confidence, work with Jennifer. Confidence is not a costume. It is what competence looks like when it stops hiding. And if you are still waiting to feel fully ready, ask whether readiness has become a respectable name for delay. The market will not grade your hesitation kindly just because your preparation was sincere. Move.