The Power of Both

I've managed programs at Fortune 500 aerospace, enterprise technology, and international aviation companies — spanning aerospace, aviation, AI, and enterprise technology. Over $100M in delivered portfolio value across the US, Europe, Asia, and the UAE, with a 100% on-time delivery record.

That track record didn't come from credentials alone. And it didn't come from experience alone. It came from combining both.

My Master's in Project Management from George Washington University gave me the frameworks: Earned Value Management, critical path methodology, risk quantification, stakeholder analysis. My PMP certification gave me a shared language with program managers across industries and geographies.

But frameworks only take you so far. The real test is knowing when to apply them, when to adapt them, and when the situation demands something no methodology anticipated.

That's where experience comes in — the lessons learned at 11pm when a critical milestone is at risk, on calls with suppliers who just told you something that changes everything, in the quiet moment after a review where you realize the one thing that mattered wasn't said.

Trust Is Built in Small Moments

Early in my career, I thought trust was earned through big deliveries. It's not.

The trust that holds programs together is built in smaller moments:

Calling a stakeholder before a review to give them a heads-up — rather than surprising them in front of others
Admitting you don't know the answer instead of guessing
Following up on the small action item everyone else forgot

In aerospace, these small moments compound. The program manager known for "no surprises" gets more honest information. The one who protects people in difficult conversations gets earlier warnings. The one who follows through on small commitments gets trusted with big ones.

This isn't soft skills. This is how programs survive.

The Most Valuable Skill Isn't Technical

When I started, I thought the job was about schedules, budgets, and technical oversight. Mastering Earned Value Management. Understanding critical path methodology.

Those are table stakes. They get you in the room. They don't make you effective once you're there.

The most valuable skill is synthesizing information across domains, organizations, and timelines — and translating it into a narrative that drives decisions:

Enough information to ask the right questions
Enough contracts to know where the risk lives
Enough organizational dynamics to know who actually makes decisions
Enough program history to know which patterns are repeating

My Master's program introduced these as separate subjects. Experience taught me how they intersect — and that the intersections are where the real decisions happen.

Programs Are Human Systems First

The biggest misconception: aerospace program management is primarily a technical discipline.

It's not. Programs are human systems that happen to produce technical outcomes.

The technical challenges — engineering problems, manufacturing issues, integration complexity — are solvable. What makes programs succeed or fail is almost always human:

Communication quality between organizations
Trust between leaders
Willingness to surface problems early
Organizational dynamics that influence resource allocation

I've seen technically straightforward programs struggle because alignment wasn't there. And technically nightmarish programs succeed because people trusted each other enough to solve problems in real time.

If you're spending 80% of your time on technical management and 20% on relationships, you probably have the ratio backwards.

The Best Program Managers Are Translators

In any complex aerospace program, you have at least five groups speaking different professional languages: engineering, contracts, finance, operations, and the customer.

The program manager's job isn't to be an expert in all of them. It's to translate between them.

The best program managers can walk into any meeting — with engineers, executives, suppliers, or customers — and adjust their communication to match the audience without losing the substance.

This isn't about being a generalist. It's about being a connector. In programs that span multiple organizations, countries, and disciplines, connectors are the difference between coordination and confusion.

Why I Started TelosFlow

After nearly a decade inside these programs, I had deep conviction about two things:

The aerospace industry is full of exceptional people doing extraordinary work under enormous pressure
The tools they rely on haven't kept pace with the complexity they're managing

I started TelosFlow to close that gap. Not by replacing the people who make this industry work, but by building something worthy of their expertise.

That's the standard. That's what this industry deserves.