The Quietest Person in the Room May Know Where the Project Will Break

The room is not always telling you the truth

ERP steering committees are built for momentum. Vendor selection. Budget approval. Timeline optimism. Executive sponsorship. The people who speak up are often the people most invested in the project happening, or most invested in being seen as supportive.

The quietest person in the room is not always disengaged. Sometimes they are the person who has watched prior system initiatives fail. Sometimes they are the project accountant who knows the WIP is wrong. Sometimes they are the operations leader who has seen principals override process rules for years. They may already know where this implementation will break.

If leadership only hears the loud voices, the firm is not getting an honest readiness picture. It is getting the political picture, which is not the same thing.

Why the quiet voices stay quiet

In AEC firms, silence is rarely neutral. People stay quiet because they have learned what happens when they raise problems before a major initiative is approved.

They may have raised data quality concerns in a prior project and been told it would be handled during implementation. They may have challenged a principal's exception to billing workflow and been sidelined. They may be overloaded and cannot afford to become the person who "slows down" ERP.

Passive resistance does not always look like resistance. It often looks like compliance in meetings and quiet non-adoption later. The CFO should assume that silence in readiness conversations is information, not agreement.

Where quiet knowledge usually points

When Sarah works with AEC firms before Deltek or ERP implementation, the quiet voices often surface the same categories of risk:

• Billing and WIP reality. Someone knows which offices fudge WIP, which project managers resist timesheet discipline, or where revenue recognition is negotiated after the fact.
• Principal and partner exceptions. Someone knows which leaders will not follow the standard process once the system enforces it, and which exceptions leadership will quietly approve.
• Data ownership conflicts. Someone knows which project data finance cannot trust, and who has been protecting that information politically.
• Capacity and adoption. Someone knows which teams are already too overloaded to support workshops, testing, and training without something else breaking.
• Partner and scope assumptions. Someone knows the implementation partner's proposal assumes a level of process discipline the firm does not actually have.

These are not abstract concerns. They are specific predictions from people who live inside the firm's operational friction every day.

What CFOs can do differently

CFOs do not need to become facilitators of group therapy. They need to create conditions where operational truth can be spoken before contracts and timelines make honesty expensive.

That means smaller working sessions with the people who run billing, project accounting, and firm reporting, not only steering committee presentations. It means asking direct questions about what will break, not only what will improve. It means separating "support for the initiative" from "confidence in readiness."

Readiness work is partly an excavation project: finding the knowledge that already exists inside the firm but has not been invited into the decision.

The cost of hearing only the loud voices

When ERP projects fail, leadership often says nobody warned them. Someone usually did, just not in the room where decisions were being made, and not in a format leadership was structured to hear.

The quietest person in the room may not have the title or temperament to drive the narrative. That does not make their knowledge less accurate. For CFOs, surfacing those voices before implementation spend commits is one of the highest-leverage readiness moves available.