More than 30 years ago, I read Joel Arthur Barker's Paradigms: The Business of Discovering the Future. One observation has stayed with me throughout my career.

When organizations ask internal teams to redesign the way they work, they're rarely asking them to change a process alone. They're asking people to reconsider the assumptions that have shaped how they've been successful. Those assumptions may be tied to established workflows, reporting structures, decision-making authority, or even professional identity.

As Barker observed, changing paradigms often means asking people to reconsider investments they've made in the current way of working—including status, authority, recognition, and the confidence that comes from being an expert within the existing system.

That's not resistance. It's human nature.

Process improvement isn't simply a technical exercise. It's an organizational one.

Many organizations are being asked to redesign proposal operations internally. They're evaluating software, revising workflows, documenting procedures, and looking for ways to improve efficiency.

The assumption is straightforward: "If we can identify the problems, we can design the solution."

Sometimes that's true. Sometimes the most significant challenges aren't the ones you've identified. They're the ones you haven't.

Many teams are facing mandates to make improvements. From what I’m hearing, these talented proposal teams are facing benchmarks and KPIs that they very much want to meet or exceed. Ironically, the same expertise that makes teams effective can also make it difficult to challenge the assumptions built into their current processes.

The people closest to the work often have the clearest view of the symptoms. In quality management, there's an old saying: "The expert is the one within 20 feet of the problem." The challenge is that proximity provides deep insight into the symptoms, but not always the broader system that created them.

It’s hard to think outside the box when you’re working in the very paradigm that needs to change.

Identifying operational friction and designing scalable systems are different skill sets. Most proposal teams do not have access to the core knowledge, principles, and experience that come with thousands of hours of engineering processes.

At the APMP Bid & Proposal Conference (BPC) in Denver last week, nearly every keynote and major theme could ultimately be distilled down to this:

• Attitude matters.

• Adaptability matters.

• Willingness matters.

Where have I seen this impact proposal operations most directly?

“I like doing my reports in Excel.”

This came from a leader who already had project management software that could automatically provide the information they wanted. Instead of leveraging the system, they continued requiring manual status reviews and duplicate reporting — consuming unnecessary time from both leadership and team members.

The issue wasn’t technology.

The issue was mindset.

I’ve also seen proposal teams resist using proposal management platforms as designed because “this is how we’ve always done it.” Instead of using structured content libraries, metadata, search functionality, workflows, and governance, they continued storing disconnected files in personal folders and recreating content from scratch.

The real question isn’t: “Are you using AI?”

The better question is: “What can AI help you do better, faster, smarter, or more consistently?”

Can it reduce administrative burden?
Accelerate first drafts?
Improve content retrieval?
Identify gaps in your knowledge library?
Support onboarding?
Surface patterns in win/loss data?
Help lean teams scale?

Probably.

Can it replace operational clarity, strategic thinking, governance, collaboration, trust, and human judgment?

Not even close.

Every major technological shift changed how work gets done. The organizations that succeeded weren’t necessarily the first to adopt new tools — they were the ones that learned how to integrate them intentionally.