Episode Overview
Most project teams don’t fail because they lack a plan: they fail because they believe it. Travis Arlitt has spent more than 25 years in capital project delivery, 16 of them on the owner’s side, across Angola LNG, Wheatstone LNG, Chevron’s Big Foot TLP, the nearly $1B Superior Refinery rebuild and Santos’s Pikka Seawater Treatment Plant. In 93 recorded minutes with Orion Matthews he lays out execution realism and progress truth: stop grading the project against a static plan, measure the pace the field is actually producing, and redistribute what’s left forward, so leaders see the bow wave while the expensive decision is still cheap.
Reality collects either way
“Reality, it’s there whether you’re acknowledging it or not. And eventually it’s gonna get you. You are infinitely better acknowledging it early.” ~1:03:05
The field-truth specialist
Travis’s career runs from refinery turnarounds and fabrication yards to owner-side assurance for Chevron and Santos: the seat where you learn what contractor-reported progress is worth.
Day1Model
His progress-based planning and forecasting approach, named after Jeff Bezos’s “day one mentality”: every status state is a fresh day one, and the go-forward redistribution buys you months on the key decisions.
“I’ve been the guy behind the box, and I can make that schedule tell you whatever you want it to.” ~54:15
A written companion to the released episode, built from the full transcript. Quotes are verbatim, lightly condensed for readability: false starts and fillers removed, meaning untouched. Timestamps are approximate (they come from the transcript’s minute markers and may drift slightly from the published cut). Biographical facts come from Travis’s public LinkedIn profile and what he says on the show; the talk-time and word-count tiles are computed from the transcript. No licensed photos of the featured projects could be verified, so the hero runs the show’s gradient treatment.
Episode Timeline
The conversation as it actually unfolded: eleven chapters across roughly 93 minutes, following the show’s four-act arc. The strip below maps each chapter’s share of the runtime; timestamps are approximate. Click any block to jump to its chapter.
Act II is the engine room: nearly 78% of the episode lives in the model, the measurement system and the psychology of schedule optimism. Timestamps follow the transcript’s markers, which run a few minutes long of the 1h 33m published cut.
The Note Card
The welcome, a construction family, Texas A&M, and the note card on a kitchen island that led to Angola.
The Corporate Jet Test
The Colorado compressor station, the first progress system, the vital four, and the meeting that fired up the jet.
Strategic Speed, Not SPI
The race-car frame, why bow waves grow non-linearly, and level 3 as no-man’s-land.
Forward Redistribution & Day One
Mike Tyson, the mechanics of the go-forward view, and the Bezos sunrise that named the model.
Selling Realism Upstairs
Do the core job first, the “fertilizer spreader,” three charts for thirty minutes, and reframing (not ditching) the plan.
Work Hours, Not Dollars
Unit rates, rules of credit, holding 30% for completion, and why work-in-progress kills projects.
Why Schedules Lie
Incentives, the guy behind the box, the P90 that was 18 months wrong, and reality’s collection schedule.
AI & the Defensible Forecast
A changed mind, 400 uploads and 50–60k words of prompts, black boxes vs. defensible outputs, and being off by 10x.
The $200M Save
Spot price, the post-Katrina levee, and the $5M signature that headed off $60M.
Go Through the Hard
The note card again, stillness, the shade of the fence, and the truth about time writing.
The Bookshelf & Close
Roark vs. Keating, AACE, and where to find Travis and the free app.
Who carried the mic
A strongly guest-forward split, measured by words across the full transcript: Orion’s longest turns are the “let me play that back” translations that keep the model accessible.
The Guest · Travis Arlitt
Travis grew up in a construction family, started Texas A&M in computer science (marching in the Aggie Band along the way) and found his home in the construction science program. He came up through contractors (Morrison Knudsen, URS, Zachry), then crossed to the owner’s side around 2010–2011: Chevron’s Angola LNG in Soyo, Big Foot TLP integration in Ingleside, and Wheatstone LNG module fabrication from Lumut, Malaysia. After an entrepreneurial detour building a cabinetry manufacturer in Austin and forensic claims work for TxDOT, he returned to megaprojects with the nearly $1B Superior Refinery rebuild, then owner-side planning for Santos’s Pikka Seawater Treatment Plant from Kuala Lumpur, with fabrication assurance in South Korean yards. In 2024 he co-founded Day1Model, the progress-based planning and forecasting approach this episode unpacks; on air he mentions he’s now supporting an operator out of Perth on an offshore Papua New Guinea platform and production facility.
“Reality, it’s there whether you’re acknowledging it or not. And eventually it’s gonna get you. So you are infinitely better acknowledging it early.”Travis Arlitt · on the show, ~1:03:05
Career journey
Roles and years from Travis’s public LinkedIn profile; the pre-2008 contractor years (Morrison Knudsen, Zachry) come from the conversation. “Chief Product Officer” is how he describes his Day1Model role on air (~1:07:55).
Credentials & the record
- Education
- BS Construction Science, Texas A&M University (1995–1999). Started in computer science; Aggie Band, Corps of Cadets.
- Certifications
- Sat for and passed AACE’s EVP and PSP exams, since lapsed, by his telling: “I don’t necessarily practice a lot of those.” (~1:33:10)
- Flagships
- Angola LNG · Wheatstone LNG · Big Foot TLP · Superior Refinery rebuild · Pikka Seawater Treatment Plant.
- Now
- Supporting an operator out of Perth on an offshore Papua New Guinea platform and production facility (per the episode).
The model & the toolkit
- Day1Model
- Co-founder of Day1Model, progress-based planning and forecasting; a free app lets you convert your own chart to the forward-redistribution view “in 30 minutes or so.” (~1:35:10)
- Unit rates
- Keeps 40–50 unit rates “in my pocket” (Gulf Coast norms) and has shared them on LinkedIn for anyone who wants them. (~40:15)
- The detour
- Founded a cabinetry manufacturing company between megaprojects: a factory is a masterclass in real production rates.
- Find him
- LinkedIn: /in/travisarlitt · day1model.com
The Host · Orion Matthews
Orion is an award-winning programmer, entrepreneur and technology executive who has spent the last decade in the engine room of major capital projects. He founded Queryon in Washington, D.C. in 2015 with a focus on data analytics and software for the construction industry, starting with bellwether client BP, whose project-controls solutions his team deployed globally, from the North Sea to Azerbaijan to Houston. Today he's a recognized expert in PMO data analytics and project-controls reporting, serving billion-dollar portfolios for owners including BP, Santos, Balfour Beatty and Turner & Townsend, a regular speaker at major industry conferences on AI and analytics in capital projects, and the host of this show.
Why this pairing works
- Same pipeline
- Orion builds the project-controls reporting owners read, for portfolios including Santos, whose Pikka project is Travis’s latest owner-side assignment. This conversation is the reporting layer interviewing the layer where the data is born.
- The translator
- Orion’s “let me play that back for you” passes (the race car, the house build, the high-school game theory) are the episode’s connective tissue, turning a specialist’s system into something any project person can carry out of the room.
Beyond the PMO
- The builder’s arc
- Founded Introspect Software out of high school; built and sold Design-PT (acquired 2015). His software has run from McMurdo Station to aircraft carriers, with write-ups in Scientific American, CNN and Maxim, and a BP Helios Award.
- The race-car playback: “You’re the RPM guy: this is your velocity right now, and at this speed you’re not gonna make that final lap on time.” ~13:45
- The rollup theory: “There’s something like quantum physics and general relativity going on in an organization: everything works at this level, but as you roll it up, the models break.” ~18:15
- The AI quadrants: know what you know and it’s a huge multiplier; don’t know what you don’t know and it may lead you down the wrong path: “you don’t want someone doing surgery on you using AI.” ~1:11:50
- The time-sheet heresy he baits Travis into: “I think time sheets are a complete lie when it comes to knowledge workers… those hours don’t sum, they’re on different number lines, man.” ~1:26:00
The Note Card
Orion opens with the show’s standing frame and the guest’s résumé in one breath: 25+ years, 16 owner-side, Angola LNG to Pikka. Then Travis tells the origin story: a construction family, a computer-science start at Texas A&M that became a construction science degree, contractor years with Morrison Knudsen, URS and Zachry, and the note card that engineered his own career the way he’d later engineer forecasts.
“I kept a note card on my little kitchen island that said Work for the owner. International. I listed my salary, and I just kept looking at that for a year. Right at the end of that project, I got the call that they needed a planner urgently in Angola.”Travis Arlitt · ~3:25
The known-commodity effect
“When you impress a project team or a business manager, they just take you with them as a known commodity, especially going from domestic to overseas. They don’t want to take a risk on an unknown.” The same Chevron group carried him from Colorado to Angola, to Malaysia for Wheatstone in 2013, and back for the Santos job in 2020. ~4:45
Filling in on the inside
In Angola he was OSBL (“outside of boundary limits, just housing developments and roads”) until the main planner’s back-to-back left and he got to fill in on the ISBL side. “It was just so exhilarating to me to set foot in Africa for a big LNG.” ~4:15
- The intro lands the frame: execution realism and progress truth, “grounding schedules in field reality and helping leadership make decisions before problems become really expensive.” ~0:45
- A construction family: his great uncle traveled construction and took his dad along: “I’ve always had that idea that it’s a potential career.” ~1:30
- Seeing the owner-side planner on a Chevron CM job in Colorado: “I just realized that’s what I wanted to do.” ~3:10
- The thesis of the whole Act: “That note card led to those thin threads, just doing good work for the right people, and some luck involved. You kind of get what you keep your mind focused on.” ~5:20
The Corporate Jet Test
Asked to define execution realism, Travis goes back to the project that created it: a Chevron compressor-station job off I-70 in Colorado: his first field assignment as lead planner, armed with “the ubiquitous level three” and three-week look-ahead meetings that were helping nobody. What he built instead became the founding story of the whole approach, and it comes with a built-in effectiveness metric: did leadership fire up the jet?
“These guys had been building these facilities since before I was born, some of them. And here I was telling a pipeliner, hey, next week you gotta dig a trench and bed the pipe. They were looking at me with blank stares… I kept wanting to just keep driving all the way to Texas and go back home.”Travis Arlitt · ~7:50
The pivot
“I’m not really helping the project with these three-week look-aheads. These guys are gonna build this compressor station without me. They don’t need me to tell them you need piles before foundations. So what can I do?… Let’s get under this schedule and start to tell these guys something they might not know.” ~8:40
The new conversation
“Instead of ‘you need to lay your eight-inch gas line next week,’ it’s: Hey Paul, I know you’re running a Microsoft Project schedule for your guys, I support that, but right now you’re installing a hundred feet of pipe a day, and we have this committed date. You really need to be putting in two hundred feet a day. Can we talk about how we can maybe do that?” ~9:25
- The first progress system reveals “a massive, what I call bow wave now”: doing ~1% a week when the committed date needs 2–3%. “It was a really shocking view of the project.” ~9:50
- The tale of two stories: Chevron corporate audits his schedule and gives it bad marks for best-practice compliance, while leadership “were firing up literally the corporate jet to have an emergency site meeting after I showed them the progress picture.” ~10:30
- The lesson: “You need a schedule, but you need to understand your audience for that schedule. If you don’t have that underlying progress picture, that’s what really gets the leadership engaged. If you can back up your milestones to progress.” ~10:50
- The vital four, introduced: average pace (a 3–6 week rolling average: “people have that good day in their head, but that’s not reality”), the required pace after redistributing to the plan date, the compression factor between them, and the impact, the equalized end date at current pace. ~11:10–13:10
- Why he calls it a deterministic forecast: “That leader can now see. I see the bow wave, I see where we’re heading at our current pace… If you’re gonna do a probabilistic or a schedule quality score, eh, you may not have the jet.” ~13:15
Strategic Speed, Not SPI
Orion translates the model into a race car (you’re the RPM guy, and at this velocity you lose), and Travis sharpens it: “planning” is a hopelessly loaded term (the refinery job had five planners with five different roles), and this is strategic planning, not tactical. The chapter then goes after two industry defaults: SPI-style variance math, and the level-5-to-level-1 rollup.
“Normally you’d say: Mr. Race Car Driver, you’re 10 laps in and we thought you’d be at 12, then do some SPI calc, divide the 10 by the 12, and the driver gets a bit confused. Whereas if you just tell them: your average pace is 170 miles an hour, we need to pick it up to 175, that’s a lot simpler and more actionable.”Travis Arlitt · ~16:20
Bow waves grow non-linearly
“If you have a fixed end date, every period that goes by you have fewer periods to spread it by, and more volume. If you’re not on top of that, it’s gonna build under you and you’re not gonna be aware of it. And then it’s a two or three x bow wave.” The fix: keep the team sensitive from lap two: 169.8 vs. a 170 goal means the target is now 170.2. ~16:55
Level 3 is no-man’s-land
“Rolling up a level five all the way to the level one and back down has never worked that great for me. Level three, to me, is almost a no-man’s-land: it doesn’t do much good for the field guys, and it’s really hard to report to the executive team.” ~19:45
- Orion’s organizational physics: “everything works at this level, but as you try to roll it up, the models break”: a phase transition between the field and the boardroom. Travis: “We’re gently poking the established order here.” ~18:15
- Wayne, the URS project-controls director, on the planner/cost split: “a good strategic planner thinks very naturally at a higher level”, and asking the same person to go granular with field execution and roll it up is a genuine skill gap. ~20:15
- The line Travis carries from a talk he heard: “The truth is rarely in the middle; it’s always lying at the extremes. You do your detailed work for the people that really need it, and then you translate it. It’s not a rolling up or down.” ~21:00
Forward Redistribution & the Day One Mind
Orion lands the summary (don’t worry about what you planned to do; look at what you have done and roll it forward), and Travis calls it “the fundamental building block of everything I’ve done on projects that have moved the needle.” Then the mechanics, and the sunrise in Batam that gave the model its name.
“Like Mike Tyson said, everybody has a plan until they get punched in the face. What really is happening under the surface of that plan?”Travis Arlitt · ~22:25
The mechanics, in one pass
Keep just two components from the S-curve: your actuals by period, and the remaining profile. If the remaining bars sum to 100,000 but you actually have 150,000 left, spread the extra 50,000 across the remaining periods and grow the curve, then compare that required pace to your actual pace. “Now you’re going to see if you’re pushing a bow wave or not, using the same exact data.” ~23:10
What it buys you
“Going backwards to the plan can be lagging. It doesn’t drive urgency, it doesn’t drive action… If you’re doing a go-forward redistribution, I’d expect you’re gaining minimum three months, probably six to nine months, on those key decisions.” ~24:35
- The naming story: breakfast at a Batam Marriott, watching the sunrise and a Bezos–Fridman podcast. “Jeff Bezos said when you get into a day-two mentality, it leads to stasis, it leads to death… I thought: that’s exactly what we’re doing. Every status state is a fresh day one.” ~25:30
- The day-two tax: “You’re gonna have to make those decisions after that plan has deviated enough that they’re gonna be expensive to make. They’re gonna surprise you.” ~26:10
- The Beautiful Mind line: “I always look at the schedule, but the governing dynamics of all that logic is the progress picture. You gotta get under and into that progress picture if you’re gonna get ahead of those tough decisions.” ~26:45
Selling Realism Upstairs
Orion plays the busy practitioner: fine, I buy it: how do I actually run this alongside my day job, and how do I sell it to a project director who’s never seen it? Travis’s answer covers the craft (earn the right first, keep it at a manageable level) and the politics (never ditch the plan: reframe it), capped by the module-yard story where the in-your-face view moved twenty thousand tons.
“You have to do your core job extremely well. You have to have that under wraps, and only then can you dip your toe and start experimenting with stuff that’s beyond that core job function people brought you on to handle.”Travis Arlitt · ~28:00
The fertilizer spreader
On the Malaysia module yard he used Primavera level-of-effort activities (“I call it my fertilizer spreader”) and asked the contractor for progress on the major components only. No data at all? “I’ve never been one to just sit on the bench. You gotta grab drawings and go do field walks and takeoffs. That’s the worst-case scenario.” ~28:50
Three charts, thirty minutes
“We just scrolled up and down these three charts for thirty minutes, and it sunk in.” Start from the variance chart they know, then show the same data reframed: “the contractor needs to do fifty percent more progress next week just to achieve the plan date they say they’re gonna meet. And then there’s not much talking anymore… It’s not gonna be story-based. It’s gonna be action-based, because it’s so in your face.” ~32:00
- The objection every planner will hit: “He said, well, my board’s not gonna let me ditch the plan. And that’s not what we’re doing: the plan is now reframed. It’s still the same plan, but now we’re gonna look forward from the status state and see what we have to achieve to make the date.” ~34:15
- The “magic six weeks”: stand up a progress system with no history, spend six weeks getting the speedometer revved, then do your first redistribution. “A major project has a pulse and a pace to it… three periods isn’t enough.” ~34:55, ~38:15
- The Wheatstone module yard story: a 10,000-line schedule and dozens of progress charts said things weren’t right, but it took an A0 plot of bow waves (“you need to do two times the production you’re doing”) for the director to see train two was in dire straits. Bechtel leadership spent two or three weeks being pointed at those charts; ~20,000 tons of modules moved to another yard. ~35:30–36:50
- The planner’s duty: “They would’ve made that decision eventually… but when you see it, the urgency gets amped up tenfold. It’s your job as a planner to have an uncomfortable conversation with that one guy or gal in the chain of command that needs to pull a lever, and needs to pull it fast.” ~37:15
Work Hours, Not Dollars
The longest chapter of the episode is the measurement system underneath everything else: how you actually quantify progress so steel can talk to pipe can talk to equipment. Travis’s rules: earn it in direct work hours, componentize at the level you can physically count, and never, ever give the credit away up front.
“If you want to know when a project’s gonna complete and where your progress pinch points are, you should probably keep cost out of the mix. That’s my opinion.”Travis Arlitt · ~39:45 · on the government EVMS approach he met on a Corps of Engineers job
The common denominator
The tip came from Donnie, his project controls manager, on a call from Colorado: “It’s work hours, Travis.” “I said, how do you get steel to talk to pipe, to talk to equipment? He said, you just assign that unit rate.” 25 work-hours per cubic yard for a spread footing, more for a pier; ranges for large bore, small bore, exotic pipe; hours per ton of steel by tier. ~42:45
Hold 30% for done
His first system “hit 90 to 95% and just stuck there for three to six months”, because he followed everyone’s advice and front-loaded the credit. The fix he’ll fight for: “I would like to keep 30% of the progress bucket for that final sign-off, the torque sheet, the check sheet, the final walk… Work in progress kills your project more than you would ever imagine it would.” ~44:40
- The Colorado backstory: 2008, a bustling Houston office where nobody wanted the field assignment: Travis volunteered for $214.50 a day per diem and 50 hours a week. “I thought it was a gold mine and why didn’t anybody else want this?” Weeks later the bottom fell out of the economy, and the office jobs turned out to be “far less secure than if you were supporting a field assignment.” ~41:20
- Componentize and you’ve covered the job: pipe spools (which carry insulation and heat trace), the cable schedule, the instrument index, seal pieces, equipment, buildings and HVAC: “all that stuff can just be componentized… and then you just earn that progress back.” ~29:50, ~43:20
- Orion’s house-build playback (lumber, concrete, unit rates and a manpower plan) and Travis’s upgrade: the estimate gets you started, but “projects are unique beasts”; from the first pours, the performance index takes over the go-forward. ~46:00
- “A project’s like a brand-new car: you don’t know how fast the thing’s gonna go. People might think you do, but I’ve seen contractors in the same part of the world, on the same project, have vastly different unit rates.” ~50:10
- The density caveat: he’s watched Big Foot hull videos from South Korea (“it’s like ants”), so don’t let a density calc veto what crews are demonstrably producing. ~52:00
Why Schedules Lie
Orion asks the title question: why is schedule optimism so persistent: culture, systems, or something else? Travis tries not to throw rocks, then gives the most honest answer you’ll hear from someone who has been “the guy behind the box”: the 10,000-line schedule nobody quite understands is infinitely steerable, and every party in the soup has incentives not to look under it.
“I’ve been the guy behind the box, and I can make that schedule tell you whatever you want it to. Generally, if I’m with a contractor, I’m gonna make it suit the contract.”Travis Arlitt · ~54:15
Freakonomics on a jobsite
“That book Freakonomics, you open it and it says incentives are the cornerstone of modern society. Of course it boils down to incentives. If I was with the contractor and I showed data in this redistributed manner, the same data we’re giving the client, but more direct, they’d probably show me the door.” ~54:35
The regime-change window
“Unless there’s a regime change, which happens all the time, that’s your window to really pop in some realism, because they want it. If they’ve had their hand on the wheel for a year, it’s not necessarily in their best interest for you to show a two-x bow wave they didn’t see.” ~55:35
- The sacrificial problem: once everyone quietly knows the job is behind, “there’s a good chance something’s gonna happen that you can pin a lot of stuff on… so the incentive to come clean early is less.” ~56:20
- His own wiring: “I don’t know if it’s the Eagle Scout in me or what, but no matter what the incentive is, if I’m not reporting the absolute truth as I can see it to the person in charge of the decisions, I won’t sleep well at night.” ~56:45
- The assurance-theater story: a schedule assurance firm spends a month tying up the logic, runs the Monte Carlo, hands over a P90, and a week and a half later the project director comes clean: “we’re actually a year and a half past your P90.” “Everybody had egg on their face, because you’re not in the governing dynamics.” ~57:30
- Where the dates come from in the first place: “Nobody’s ever said, hey Travis, put this schedule together and tell me when we’re gonna finish this job. It’s always: we’re gonna finish this job at this point, and you’re building the plan around that.” ~58:45
- What “catch up” means when you make it concrete: “You’ve been driving fourteen piles a day per rig on average. You need twenty to make your plan. So tell me how we’re gonna catch that up. It’s no longer a variance, it’s very direct.” ~59:15
- The strange physics of train two: a 40-year Chevron friend found LNG train two goes slower than train one: “he thinks it’s because people know there’s no train three after it. They might not even know it consciously.” ~1:03:50
Orion’s “98% of all projects are off schedule or off budget” framing (~53:00) is a from-memory industry statistic offered in conversation. Treat it as directional rather than precise.
AI & the Defensible Forecast
Orion asks whether AI, the dispassionate observer, might finally fix progress truth. Travis’s answer is unusually candid for this debate: his views changed in the last month, he now uses AI relentlessly, and the constraint isn’t capability. It’s that a project leader betting their career on a decision needs a defensible “why”, and a black box doesn’t give them one.
“I use AI; if somebody took it away from me, I’d hunt them to the end of the earth to get it back… But you always gotta get back to the defensible. It just can’t be a black-box output.”Travis Arlitt · ~1:06:40
The CPO with a chatbot
Day1Model was built out with a developer, then parked for cost until customers and revenue arrive. Travis says he’d turned his Excel original into a web app with “a few prompts.” So the chief product officer went direct: “Hey Claude, what can we do with this? … I’ve done this 400 times now. I’ve probably written fifty, sixty thousand words of prompts and really understood how it works from using that code base.” ~1:07:55
Bid docs, distilled
Building an execution schedule, he feeds the documents through an API workspace (“so you’re sectioning off the data privacy issue”) and asks for an activity list against his straw-man WBS. “Instead of spending days and weeks, you get a very, very distilled view of the plan.” And it shows its work: “Claude, you said we need X component on this platform, show me in the contract what page that was. Boom, boom, boom.” ~1:09:40
- What changed his mind: “The models have just gotten crazy better”. Orion name-checks the new model generation, and Travis admits he was “not necessarily for it” before. ~1:07:30
- The power-plant experiment: he backed a full progress picture and schedule out of model shots of a combined-cycle power plant, using all three frontier models to dial in quantities. ~1:10:50
- Orion’s quadrant theory: if you know what you know, AI is a 1000x lift; if you don’t know what you don’t know, “I’m not sold yet that AI is gonna be your hundred-x multiplier… you don’t want someone doing surgery on you that doesn’t know how to do surgery, using AI.” ~1:11:50
- The off-by-10x check: “This has definitely got 50,000 tons of steel in the pipe rack. Are you sure? That seems like a lot. Oh, you’re absolutely right, it’s actually 5,000 tons. I was off by ten. That happened a lot… It can sound extremely confident. If you take that confidence without knowing the fundamentals, you’re gonna get bit for sure.” ~1:13:30
The $200M Save & Other Receipts
Orion asks the ROI question straight: you’ve been doing this for decades on billion-dollar jobs: what has it actually saved? Travis answers with three stories where the redistributed view triggered a decision the variance view couldn’t: a commercial hedge, a rescue subcontract, and a $5M signature.
“The commercial team could see that direct link. They bought the product at spot price, and I found out it saved them two hundred million dollars. I had kind of estimated fifty. I didn’t know it was that much.”Travis Arlitt · ~1:16:15
Assuring the assurance
A non-operating partner wanted a second opinion on the operator’s P90. Travis’s redistribution showed a 3x bow wave: flatten it and the “January” P90 lands in October, ten months later. The project team balked; the commercial team covered the supply gap at spot price. ~1:15:10
The levee rescue
Post-Katrina New Orleans, a five-mile levee, six pile rigs. The crews’ gut said 21–22 piles per rig per day; the rolling average said 14: two months late and ~$10M in liquidated damages, “which for that project was devastating.” Shown the math, they hired a subcontractor “with weeks to spare.” ~1:16:50
The $5M signature
A craft incentive bonus everyone wanted was “a dead issue” until the director saw the carryover bow wave: ~300,000 hours spilling from a $7/hour yard to a $250/hour destination, roughly $60M. “He signed it that week. They couldn’t sway his brain based on variances.” ~1:19:10
- The planner’s adage inside the levee story: “Early starts matter. If you miss those starts, you start to get that compression.” ~1:17:30
- The invitation: “If you have the ear of the decision maker and you have the data, dabble in this redistribution off to the side and show them a different view. It shakes people into action. You might have some of these wins that I’ve had, and I hope you do.” ~1:19:55
The $200M, $10M, $60M and $5M figures are Travis’s own accounts, recalled on air, including one he says he only learned recently, having estimated it at $50M. They’re the guest’s telling of real outcomes, not audited numbers; treat magnitudes as directional.
Go Through the Hard
The advice act, for students and career shifters: know what you want (the note card returns), say yes to mobility even when the posting has no wind and no sailing, and, in the AI era, protect the stillness where the valuable ideas come from. Then Orion baits him into the most honest riff of the episode, about time sheets.
“Not every move is gonna be sunshine and roses. I’m a sailor. I love wind, I love water. Malaysia has no wind and no sailing… If it’s hard, don’t leave. Go through the hard. Out of that Colorado job I wanted to drive away from was born the impact, the ideas that have carried with me.”Travis Arlitt · ~1:21:50
The shade of the fence
“The most important thing I did on that module yard wasn’t counting pipe spools, although I did that every week. It was the day I sat in the shade of a fence and watched a module for almost two hours… That’s where the idea of the progress system clicked. It wasn’t because I was in a meeting and busy.” ~1:24:50
Imagine, then execute wildly
“Your most valuable skill in the world of AI is your ability to imagine and create… If you’re quiet, ideas are gonna come to you that would never come from AI. And then you use AI to execute wildly on those ideas. But you can’t be a meeting man or woman, meeting to meeting to meeting; you gotta have time to think.” ~1:23:40
- “Know what you want. That note card is important: get really clear about what you want out of your career and what kind of lights you up.” ~1:20:50
- Strengths over weaknesses: “Find out what you’re really good at and just quadruple down on that. Whatever in the project world comes as natural as breathing, go all in on that, and you’re probably gonna do pretty good.” ~1:23:10
- Orion’s heresy: time sheets assume time is fungible: “you can’t sum the Travis-shade-in-the-tree moment with some random meeting. They’re on different number lines, man.” ~1:26:00
- Travis’s confession (“something I don’t put on LinkedIn”): after setting up the Wheatstone system, “I worked probably 30 minutes a week, 45 minutes max, and I shifted the entire trajectory of a whole train of one of the biggest LNGs… That little component was worth two or three months of strategy.” ~1:27:50
- The hard part of easy: “You have to be comfortable with not working so hard and thinking that your worth is coming from the work… If you’re uncomfortable with that, you’re gonna work yourself to the bone, jump meeting to meeting, and you’re not gonna get those insights.” ~1:28:55
- The closer: “We all have access to this. If you just give yourself stillness, you’re gonna have access to an infinite world of knowledge that will surprise you… I think project meetings have completely gone overboard.” ~1:29:50
The Big Ideas
Three ideas carry the episode. Sketched here the way a field-execution planner would whiteboard them.
One progress picture, four numbers: the deterministic forecast Travis has run from the Colorado compressor station to Pikka. No plan variance anywhere in it.
A rolling average of what the field actually produced: three to six weeks of it, because “people have that good day in their head, but that’s not reality.”
Redistribute everything remaining to the committed date. The plan is no longer a curve: it’s a date and the pace that date demands from here.
Required ÷ actual. Above 1 and you’re pushing a bow wave, and with a fixed end date it grows non-linearly: fewer periods left, more volume in each.
Let the end date float instead: equalize required with actual pace and read off the honest finish. This is the chart that fires up the corporate jet.
Hidden schedule compression: slipped work doesn’t disappear: it piles up in front of the finish date, invisible to a report that still shows the original plan.
The episode’s central pivot: stop grading the project against a static baseline, and start forecasting from what the field is actually producing: the same data, looked at forward.
The rear-view world…
- Variance to a day-one baseline
- % complete vs. a static plan
- Explaining last month
- “They’re gonna pull that line up”
· the Day1Model ·
…the forward world
- Actual production rates
- Forecasts from real pace
- Decisions 3–9 months earlier
- Direct, action-based conversations
The Bookshelf, the Close & the Links
The wrap-up runs from Paulo Coelho to Ayn Rand (with Travis declaring himself “a little more Howard Roark; I’m not a joiner”), through AACE’s forensic publications, and out on where to find him. Every recommendation from the episode, in his own words, plus all the links.
“Find me on LinkedIn, that’s my only social media outlet right now. And go to day1model.com, get that free app, look at some examples, and convert one of your own charts into that forward-redistribution view in 30 minutes or so.”Travis Arlitt · closing, ~1:35:10 (lightly condensed)
Travis’s bookshelf, in his own words
- The journey
- The Alchemist · Paulo Coelho. “Always a great read for people to kind of understand the journey… there’s a lot of wisdom within The Alchemist.” (~1:30:50)
- Conviction
- The Fountainhead · Ayn Rand. “When you read that, you get inspired to take a little more boldness and unique ideas… but it’s long: you gotta listen to it while you’re flying or driving.” (~1:31:30)
- Mindset
- Reality Transurfing · Vadim Zeland. “The idea of the essence of where you want to go, and keeping that in your mind. It’s been really enlightening to me.” (~1:30:30)
- Performance
- The Alter Ego Effect · Todd Herman. “If you find somebody you really want to emulate, you can do what a lot of sports figures do and have an alter ego that you channel into your work.” (~1:31:00)
- Incentives
- Freakonomics · Steven D. Levitt & Stephen J. Dubner. “You open the book and it says incentives are the cornerstone of modern society.” (~54:35)
- Community
- AACE International · “They have wonderful publications on forensic schedule analysis. If you ever get into a claim situation… you can fall back on that.” (~1:33:50)
- The model
- Day1Model · the progress-based planning and forecasting approach, with the free forward-redistribution app.
The episode
- Listen
- Episode page (Podbean) · Apple Podcasts · Spotify
- The guest
- Travis Arlitt on LinkedIn · day1model.com
- The host
- Orion Matthews on LinkedIn · Queryon
- The show
- themajorprojectpodcast.com · new conversations from the people building projects over US$1 billion.
- The Bookshelf
- The Major Project Bookshelf · every recommendation from every episode, with the reasoning in the speakers’ own words.
Highlights at a glance
Three moments to start with
- The note card ~3:25
- The corporate jet ~10:30
- The $200M spot-price save ~1:16:15
If you run project controls
- The vital four ~11:10
- “The plan is now reframed” ~34:15
- Hold 30% for completion ~44:40
The late-episode gold
- Off by 10x · AI confidence ~1:13:30
- The shade of the fence ~1:24:50
- The time-writing confession ~1:27:40
Quote Bank
The best on-the-record lines, gathered in one filterable place. “Highlight” marks the lines most worth scrubbing back for; quotes are lightly condensed and timestamps are approximate.
The Note Card 0:00–5:45
- Highlight“I kept a note card on my little kitchen island that said Work for the owner. International. I listed my salary, and I just kept looking at that for a year. Right at the end of that project, I got the call that they needed a planner urgently in Angola.”
- “When you impress a project team or a business manager, they just take you with them as a known commodity, especially when you’re going from domestic to overseas. They don’t want to take a risk on an unknown.”
- “That note card led to those thin threads, just doing good work for the right people, and some luck involved. You kind of get what you keep your mind focused on.”
The Corporate Jet Test ~5:45–13:40
- “These guys had been building these facilities since before I was born, some of them. And here I was telling a pipeliner: hey, next week you gotta dig a trench and bed the pipe. They were looking at me with blank stares.”
- Highlight“They were firing up literally the corporate jet to have an emergency site meeting after I showed them the progress picture of this job, while I was getting a pretty tough write-up on my schedule.”
- “You need a schedule, but you need to understand your audience for that schedule. If you don’t have that underlying progress picture, that’s what really gets the leadership engaged.”
- Highlight“You’re not looking at a plan variance. The plan is now a date and a set of progress that’s required to meet that date. And if your average pace is less than what’s required, then you’re pushing a bow wave. You have schedule compression.”
- “If you’re gonna do a probabilistic or a schedule quality score, eh, you may not have the jet.”
Strategic Speed, Not SPI ~13:40–21:40
- “If you just tell them your average pace is 170 miles an hour, but we need to pick it up to 175, that’s a lot simpler and more actionable.”
- Highlight“It’s not linear. If you have a fixed end date, every period that goes by you have fewer periods to spread it by and more volume. If you’re not on top of that, it’s gonna build under you, and then it’s a two or three x bow wave.”
- “Rolling up a level five all the way to the level one and back down has never worked that great for me. Level three, to me, is almost a no-man’s-land.”
- “The truth is rarely in the middle; it’s always lying at the extremes. You do your detailed work for the people that really need it, and then you translate it. It’s not a rolling up or down.”
- “I have this theory that there’s something like quantum physics and general relativity going on in an organization: everything works at this level, but as you try to roll it up, the models break.”
Forward Redistribution & Day One ~21:40–27:05
- “Like Mike Tyson said, everybody has a plan until they get punched in the face. What really is happening under the surface of that plan?”
- Highlight“Going backwards to the plan can be lagging. It doesn’t drive urgency, it doesn’t drive action… If you’re doing a go-forward redistribution, I’d expect you’re gaining minimum three months, probably six to nine months, on those key decisions.”
- Highlight“Jeff Bezos said when you get into a day-two mentality, it leads to stasis, it leads to death: you always have to keep a day-one mentality. And I thought: that’s exactly what we’re doing. Every status state is a fresh day one.”
- “I always look at the schedule, but the governing dynamics of all that logic is the progress picture. You gotta get under and into that progress picture if you’re gonna get ahead of those tough decisions.”
Selling Realism Upstairs ~27:05–38:45
- “You have to do your core job extremely well. Only then can you dip your toe and start experimenting with stuff that’s beyond that core job function people brought you on to handle.”
- “I’ve never been one to just sit on the bench. You gotta grab drawings and go do field walks and takeoffs. That’s the worst-case scenario, but you can usually tease out quite a bit of data from what you’re getting.”
- Highlight“The contractor needs to do fifty percent more progress next week just to achieve the plan date they say they’re gonna meet. And then there’s not much talking anymore… It’s not gonna be story-based. It’s gonna be action-based, because it’s so in your face.”
- Highlight“He said, my board’s not gonna let me ditch the plan. And that’s not what we’re doing: the plan is now reframed. It’s still the same plan, but now we’re gonna look forward from the status state and see what we have to achieve to make the date.”
- “They would’ve made that decision eventually… but when you see it, the urgency gets amped up tenfold. It’s your job as a planner to have an uncomfortable conversation with that one guy or gal in the chain of command that needs to pull a lever, and needs to pull it fast.”
Work Hours, Not Dollars ~38:45–52:55
- “If you want to know when a project’s gonna complete and where your progress pinch points are, you should probably keep cost out of the mix. That’s my opinion.”
- “I keep about forty to fifty unit rates in my pocket, and I’ve shared them on LinkedIn if anybody wants them. The Gulf Coast norms kind of get you in the ballpark; you go down to the direct work hour.”
- “I said: how do you get steel to talk to pipe, to talk to equipment? He said: you just assign that unit rate… you have to use that common denominator of work hours.”
- Highlight“I would like to keep 30% of the progress bucket for that final sign-off, the torque sheet, the check sheet, the final walk… Work in progress kills your project more than you would ever imagine it would.”
- Highlight“A project’s like a brand-new car: you don’t know how fast the thing’s gonna go. People might think you do, but I’ve seen contractors in the same part of the world, on the same project, have vastly different unit rates.”
- “If you can get to that system, project predictability is in your pocket… you’re gonna be able to make it boring, predictable.”
Why Schedules Lie ~52:55–1:04:45
- Highlight“I’ve been the guy behind the box, and I can make that schedule tell you whatever you want it to. Generally, if I’m with a contractor, I’m gonna make it suit the contract.”
- “Unless there’s a regime change, which happens all the time, that’s your window to really pop in some realism, because they want it.”
- “I don’t know if it’s the Eagle Scout in me or what, but no matter what the incentive is, if I’m not reporting the absolute truth as I can see it to the person in charge of the decisions, I won’t sleep well at night.”
- Highlight“A week and a half after they left, the project director came clean: sorry guys, that’s not it: we’re actually a year and a half past your P90. Everybody had egg on their face, because you’re not in the governing dynamics.”
- “Nobody’s ever said: hey Travis, put this schedule together and tell me when we’re gonna finish this job. It’s always: we’re gonna finish this job at this point, and you’re building the plan around that.”
- Highlight“Reality, it’s there whether you’re acknowledging it or not. And eventually it’s gonna get you. So you are infinitely better acknowledging it early. Not even close to orders of magnitude better, because you can just face it, and everybody gets on the same page.”
- “Train two of an LNG, you’d expect it to go faster because you got it all worked out. He said it’s the opposite. He thinks it’s because people know that there’s no train three after it.”
AI & the Defensible Forecast ~1:04:45–1:14:20
- Highlight“I use AI; if somebody took it away from me, I’d hunt them to the end of the earth to get it back… But you always gotta get back to the defensible. It just can’t be a black-box output.”
- “Hey Claude, what can we do with this? Oh, we can do this: just upload the code here. I’ve done this 400 times now. I’ve probably written fifty, sixty thousand words of prompts.”
- “Instead of sifting through these bid docs and picking out the calendars and all the stuff… you get a very, very distilled view of the plan, instead of spending days and weeks.”
- Highlight“‘This has definitely got 50,000 tons of steel in the pipe rack.’ Are you sure? That seems like a lot. ‘Oh, you’re absolutely right, it’s actually 5,000 tons.’ I was off by ten, and that happened a lot… It can sound extremely confident. If you take that confidence without knowing the fundamentals, you’re gonna get bit for sure.”
- “If you don’t know what you don’t know, I’m not sold yet that AI is gonna be your hundred-x multiplier… you don’t want someone doing surgery on you that doesn’t know how to do surgery, using AI.”
The $200M Save ~1:14:20–1:20:20
- Highlight“The commercial team could see that direct link… they bought the product at spot price, and I found out it saved them two hundred million dollars. I had kind of estimated fifty. I didn’t know it was that much.”
- “Early starts matter. Because what happens if you miss those starts: you start to get that compression.”
- “As soon as he saw that carryover bow wave (we’re gonna have 300,000 hours spill up to this area of the world that we’re not ready for, and it’s gonna cost us $60 million), well, yeah, let’s sign this. He signed it that week… they couldn’t sway his brain based on variances.”
- “If you have the ear of the decision maker and you have the data, dabble in this redistribution off to the side and show them a different view. It shakes people into action.”
Go Through the Hard ~1:20:20–1:30:15
- Highlight“Not every move is gonna be sunshine and roses. I’m a sailor. I love wind, I love water. Malaysia has no wind and no sailing… If it’s hard, don’t leave. Go through the hard.”
- “Find out what you’re really good at and just quadruple down on that. Whatever is in the project world that you love, that comes as natural as breathing, go all in on that.”
- Highlight“Your most valuable skill in the world of AI is your ability to imagine and create… If you’re quiet, ideas are gonna come to you that would never come from AI. And then you use AI to execute wildly on those ideas.”
- Highlight“The most important thing I did on that yard wasn’t counting pipe spools. It was the day I sat in the shade of a fence and watched a module for almost two hours… It wasn’t because I was in a meeting and busy.”
- “That two-hour walk in the woods might be more valuable than two months of actively working, if you can come up with an idea. And the wonderful thing about AI is you can execute so fast now.”
- “I worked probably 30 minutes a week, 45 minutes max, and I shifted the entire trajectory of that whole train of one of the biggest LNGs… That little component was worth two or three months of strategy.”
- “You have to be comfortable with not working so hard and thinking that your worth is coming from the work… If you’re uncomfortable with that, you’re gonna work yourself to the bone and you’re not gonna get those insights.”
- “I think time sheets are a complete lie when it comes to knowledge workers: they assume that time is fungible… they’re on different number lines, man.”
The Bookshelf & Close ~1:30:15–1:36:00
- “Hopefully I’m not a Peter Keating, and I wish I was more of a Howard Roark… when you read that, you get inspired to take a little more boldness and unique ideas.”
- “I’m a little more Howard Roark. I’m not a joiner.”
- “My business partner coached me: Travis, you don’t need to be against this stuff. You need to be for the truth and the redistribution.”
- Highlight“Get that free app, look at some examples, and convert one of your own charts into that forward-redistribution view in 30 minutes or so.”