Confidence Comes Early, Competence Takes Time

Early in my career, I was confident about the wrong thing.

I believed that if a company had a UX team, then UX must already be understood, supported, and structurally embedded. I assumed that designers on the org chart meant there was shared agreement about process, authority, and value.

That belief wasn’t grounded in reality.

But I spent years trying to force it into existence.

What followed looked like what most people would call UX evangelism. Proving value by any metric that would listen. User metrics. Business metrics. Conversion data. Research decks and case studies. I assumed that if the evidence was strong enough, minds would change.

They rarely did, at least not in the rooms that mattered.

Slowly and painfully, I learned that most key stakeholders had already made their decisions long before any UX work showed up. When UX aligned with their gut, it was treated as validation. When it did not, it was treated as “misunderstanding the business.” Change, when it happened at all, was incremental and usually aligned with biases that already existed.

Evangelism didn’t fail because the data was weak.

It failed because it arrived after authority had already hardened.

That realization cracked my belief about how change actually happens.

I assumed confidence followed competence. In reality, confidence was mostly a function of visibility, authority, and timing. Competence was something else entirely.

Confidence without constraint

In most organizations, confidence attaches to teams early. It attaches to fluency, speed, and presence. UX environments amplify this because the work is visible and feedback usually arrives early. But that feedback is almost always about polish and clarity, not judgment.

For a long time, I mistook that feedback for progress.

I thought being articulate meant being right. Defending work felt like protecting users. I treated confidence as something to project harder when challenged.

It worked just well enough to be dangerous.

I remember bringing a strong research case to leadership. Clear findings. Clear risks. A clear recommendation. The response was simple. They believed their use case was different, and they wanted to try it anyway.

The outcome did not fully fail. It performed decently. Worse than the alternative, but well enough to embolden the original instinct.

That moment mattered more than the decision itself.

It taught me that partial success can be more damaging than clear failure. Failure forces recalibration. Partial success hardens confidence, especially when that confidence already belongs to the person with formal authority in the room.

The authority gap

That was when I learned something uncomfortable.

Data is not authority by itself.

Competence is not authority by itself.

Titles and decision rights are.

Authority decides which data and which competence get a hearing.

I didn’t like that truth. I resisted it. I tried to outwork it. Eventually, I had to accept it.

What changed wasn’t my belief in users or research. It was my understanding of how influence actually works. I stopped trying to convert people in rooms where the decision was already written in invisible ink on the whiteboard. I started paying attention to who decision-makers listened to, and why.

That required a different kind of competence.

Not better artifacts, but better timing.

Better restraint.

A better understanding of people.

I stopped trying to make data speak for itself. It never does. Someone always carries it. For a long time, I didn’t want that to be me. I wanted objectivity to win.

But organizations don’t work that way.

Eventually, the data and I became a package deal, whether I liked it or not. That was hard. It meant accepting that influence is personal before it’s rational, and that credibility accumulates through trust long before it shows up in decisions.

Silence as a skill

Earlier in my career, silence felt like failure. My instinct was to fill any gap with answers.

So I answered. Often for requirements that weren’t mine. Often for business logic I only partially understood. Often because I thought not answering would make me look unprepared.

Over time, I realized I was crowding out better answers. From product owners. From engineers. From the people who actually owned the decision.

When I stopped filling the silence, something unexpected happened.

Other voices emerged.

Intent surfaced.

Motivations became visible.

Silence stopped signaling ignorance and became a deliberate leadership tool.

I learned to let a question hang long enough for the right owner to feel it.

That shift did more to recalibrate my confidence than any framework or process ever did.

Competence takes time

Competence grows under constraint.

Not theoretical constraint. Real constraint. Authority you don’t have. Decisions you can’t override. Outcomes you have to live with months later. Repeated exposure to tradeoffs that do not bend for passion or correctness.

That friction changed how I measure myself as a practitioner and a leader.

Not by how often I’m right in the room.

Not by how convincingly I argue.

But by whether decisions age well.

By whether teams stay intact under pressure.

By whether trust compounds or erodes over time.

Confidence still matters, but it no longer comes from certainty.

It comes from owning what I decide and what I do not.

It comes from truthfulness.

It comes from knowing what I own, what I do not, and being honest about both.

Early confidence performs.

Earned confidence survives because it is accountable.

The rest of this work builds from that distinction, between confidence that performs and judgment that survives.