About PlanP6

I started working with Primavera P6 back in the early days of EPPM — before the cloud was a thing anyone took seriously, before REST APIs existed in the product, and before most organizations understood that their scheduling tool needed the same rigor as any other enterprise system. That early exposure gave me a front-row seat to how the platform evolved, and more importantly, how the gap between what P6 can do and what most organizations actually do with it has only grown wider.

What makes my practice different is something I call dual-threat expertise. I can sit in a room with planners and schedulers and have a meaningful conversation about schedule logic, critical path methodology, and earned value metrics. Then I can walk down the hall to the IT team and debug a WebLogic deployment, write a REST API integration, or tune an Oracle database that's choking on 50,000 activities. That crossover is rare, and it matters — because the best P6 implementations happen when someone understands both the functional requirements and the technical constraints.

Over 15+ years, I've worked across industries that don't tolerate half-measures. In defense, I supported fighter jet development programs and electronic warfare systems where schedule integrity directly affects national security. In oil and gas, I managed multi-billion dollar project portfolios across the Middle East — environments with 4,000+ users where a misconfigured global security profile means thousands of people see the wrong data. In mega-infrastructure, I've worked on airports and bridges where the schedule is the contract, and slippage has consequences measured in millions per day.

Through all of it, I've come to believe that the best solutions aren't just technically correct — they're operationally practical. A perfectly architected P6 environment means nothing if the people using it don't understand it, can't maintain it, or quietly revert to spreadsheets the moment you leave. That's why knowledge transfer isn't something I bolt on at the end of an engagement. It's built into how I work from day one.