Why the Hard Problems Aren't Technical

After sixteen years of implementing enterprise systems for federal agencies, I've come to a counterintuitive conclusion: the technology is almost never the hard part.

I've worked on Oracle ERP implementations, procurement automation, data migrations, and system integrations across dozens of federal agencies. Every one of those projects had a significant technical component. But the ones that failed — or nearly failed — didn't fail because of a bug or a bad architecture decision. They failed because of people.

The hard part is helping a procurement officer trust a new system enough to actually use it. The hard part is getting a CFO to sign off on a cutover date when they're terrified of what happens if it goes wrong. The hard part is training fifty users across three offices when half of them still think the old system was fine.

What I've learned is that technical skill gets you in the room. But organizational understanding is what gets things done. The best engineers I've worked with aren't just strong technically — they're translators. They can take what a system does and explain it in terms of what a human needs. That translation work is where most projects succeed or fail.

If you're early in your career and wondering what to invest in next: spend as much time understanding people and organizations as you do understanding technology. The ROI is much higher than you'd expect.