đźš© Tactical Memo 036: The Only 3 Project Management Lessons That Actually Matter
Justin Bateh
January 07, 2026
In partnership with
How much could AI save your support team?
Peak season is here. Most retail and ecommerce teams face the same problem: volume spikes, but headcount doesn't.
Instead of hiring temporary staff or burning out your team, there’s a smarter move. Let AI handle the predictable stuff, like answering FAQs, routing tickets, and processing returns, so your people focus on what they do best: building loyalty.
Gladly’s ROI calculator shows exactly what this looks like for your business: how many tickets AI could resolve, how much that costs, and what that means for your bottom line. Real numbers. Your data.
Read time: 4 minutes
Welcome to Tactical Memo, my newsletter where I share frameworks, strategies, and hard-earned lessons for leaders navigating project execution, AI fluency, and leadership.
If you’re looking for my cheat sheets and deep-dive guides, the vault is linked at the bottom of this email.
👉 Why Read This Edition: You will learn the three project management truths that matter more than any framework, certification, or tool. If you get these right, projects move. If you ignore them, no process will save you.
The Briefing: Today’s Focus
What project management books get right
Why most project failures are not technical
The three leadership lessons I keep seeing repeat
How to apply them immediately
Early Registration for February Cohort is Open
The next cohort of the AI-Powered Project Management cohort is now open for enrollment. The January cohort sold out! So our next start date is February 2nd.
Rated #1 Project Management course on Maven.
4.7/5 rating (50 reviews)
Awarded Maven Best Seller
Awarded best course for “Ready to Use Skills.”
40 people joined the January cohort and, in 4 weeks, will have reached the highest level of their skills.
Don’t miss the opportunity to do the same in February.
Complete Early Bird Registration
What Five Project Management Books Taught Me
I have read a lot of project management books. Five that shaped my thinking the most were The Phoenix Project, Scrum, Rework, Making Things Happen, and Extreme Ownership.
They all come from different angles. Technology. Agile. Startups. Leadership. Execution. But underneath the language and frameworks, they point to the same uncomfortable truth.
Most projects do not fail because teams do not know what to do. They fail because leaders avoid doing what is hard.
The Rule: Project Failure Is Almost Always a Leadership Problem
When deadlines slip, roles blur, and outcomes disappoint, it is tempting to blame the process. But process rarely causes failure on its own. What actually breaks projects is hesitation, avoidance, and fear of conflict.
This edition breaks down the three lessons I see repeated across every successful project and every failed one.
A Tactical Playbook: The 3 Lessons That Decide Project Outcomes
1. Most projects fail because leaders avoid hard conversations
Missed deadlines, weak ownership, and vague roles are rarely accidents. They happen when leaders delay conversations they know they need to have. I see this constantly. A role is unclear, but no one wants to offend. A deadline is unrealistic, but no one wants to push back. A team member is underperforming, but feedback gets softened until it means nothing.
When leaders avoid these conversations, teams fill the gap with assumptions. Assumptions create confusion. Confusion kills execution.
What I do instead is address issues early, while they are still small. I name ownership clearly. I challenge timelines when they are fiction. I give feedback when it can still help. Courage early saves time later.
2. Perfection is the enemy of delivery
I have watched teams hide behind planning, documentation, and meetings because shipping feels risky. Planning feels safe. Delivery invites judgment.
Perfect plans do not create impact. Delivered work does. I treat planning as a support activity, not the main event. Once we have enough clarity to move, we move. We learn from real outcomes instead of hypothetical debates.
When teams struggle to deliver, I ask one question. “What are we afraid will happen if we ship this.” The answer usually reveals the real blocker.
3. If it does not move the business, it is a useless project
On time and on budget means nothing if the outcome does not matter. I have seen perfectly managed projects that delivered zero impact. They checked every box and changed nothing.
Before I greenlight work, I force clarity on business impact. What decision will this enable. What cost will this reduce. What risk will this remove. If we cannot answer that plainly, the project does not deserve time or resources.
Execution without impact is just motion.
What To Do Right Now
Identify one hard conversation you have been avoiding. Schedule it this week.
Kill one layer of planning or documentation that is slowing delivery. Replace it with action.
Ask this question about your current project: “If this succeeds, what actually changes.”
Name one owner for every outcome. Not a group. One person.
Set a delivery date that forces learning. Adjust later based on reality, not fear.
These actions matter more than any new framework you could adopt.
Cheat Sheet Vault
p.s… As promised, click the link below to download my free cheat sheet and infographic vault.
Until next time,
Justin
✍️ From the Desk of Justin Bateh, PhD
Real-world tactics. No fluff. Just what works.
