Most organizations have some version of this story. A new team member arrives with an impressive resume — two decades of experience, relevant certifications, a title that suggests seniority. Leadership sees the profile and feels reassured. But the people working alongside them start noticing patterns that don’t align with the credential set.

The terminology is wrong. Not subtly wrong — consistently wrong in ways that would surface immediately in a technical review. Security habits are casual in an environment where compliance should be non-negotiable. Direction isn’t absorbed well. Interruptions are frequent. And the instinct to trust their judgment on shared deliverables quietly erodes.

This is not a personality conflict. It’s an operational risk that sits inside a project timeline, wearing a senior title.

—

### The Credential-Capability Gap

Certifications confirm exposure to a body of knowledge. They don’t confirm the ability to apply that knowledge under real operational conditions. Years of experience can mean deep accumulated wisdom — or it can mean one year repeated twenty times over. The resume and the reality are not always the same document.

In ERP and CRM environments specifically, this gap matters because the work is inherently cross-functional. A mistake in terminology during a finance module configuration isn’t a vocabulary issue. It’s a signal that the conceptual model might not be correct. And when that model is wrong, the downstream effects hit reporting, integrations, and user trust.

—

### The Escalation Question

The decision to raise concerns is rarely straightforward. The person wasn’t your hire. Their relationship with leadership predates yours. And the issues are cumulative — each individual instance might seem small, but the pattern is what carries the weight.

What often works is reframing the conversation entirely. Instead of asking whether someone is competent, ask whether specific risks are being managed. Document where decisions could affect outcomes. Tie observations to deliverables, not to character. Make the discussion about protecting the project, not judging the person.

—

### What Silence Costs

Staying quiet on a critical project with a weak link in the chain doesn’t preserve harmony. It defers cost. The correction that could have been a conversation early on becomes a recovery effort months later — after integration testing fails, after the vendor flags the configuration, after the go-live date slips.

In systems work, capability gaps don’t remain contained. They travel through dependencies. They surface in handoffs. They become expensive downstream.

—

### A Practical Approach

Before escalating, build a record. Not a case against the person — a case for project integrity. Note specific instances where terminology, judgment, or security behavior diverged from what the project requires. Frame every concern around operational impact.

Then have the conversation with leadership — not as a complaint, but as a risk assessment. The goal isn’t to get someone removed. It’s to ensure the right oversight is in place before the project absorbs damage that could have been prevented.

Often, leadership already senses something is off. They just need someone to connect the dots in a way that’s professional, specific, and focused on the work.

This is not about being right. It’s about making sure the project doesn’t quietly go wrong.