How to Take Your Inbox Back in 30 Days
A military decision filter that makes your communication cleaner and your job easier.
👋 Hey, Kyle here! Welcome to The Influential Project Manager, a weekly newsletter covering the essentials of successful project leadership.
Today’s Overview:
Most project teams don’t have an information problem, they have a decision-making problem.
Without a protocol, “keep you in the loop” turns into noise, missed signals, and late decisions.
A CCIR is the simplest and most effective ways I learned to control information flow without turning into a bottleneck.
👀 TrueLook Captures Everything… Even the Unexpected.
Jobsites are full of surprises (like this raven). The ones that hurt are the ones nobody captured.
If you’re leading a project, you know you can’t be everywhere at once.That’s when schedules slip, details get missed, and your team starts arguing from memory instead of facts.
TrueLook Construction Cameras give you the missing piece: a simple way to see what’s happening, document progress, and tighten communication without living in your truck.
With live viewing, time-lapse documentation, and AI-powered motion detection, you get a clean visual record of the job.
Tools like Image Markup (annotate a live feed image and send it straight to a Procore RFI) and TrueAI PPE (automatic alerts when hard hats, vests, or hi-vis gear are missing) are where it starts to actually help you run the job, not just document it.
Get a free quote and build the camera package that fits your jobsite.
Not ready for a quote? Calculate the ROI on a jobsite camera.
📧 How to Take Your Inbox Back in 30 Days
Filed under: Leadership & Managing People, Project Management
Every project leader gets issued the same gear on day 1: a phone, a laptop, an inbox, and a calendar full of meetings.
Then the war begins.
Not metaphorical war. Real war.
Jason Schroeder said it best: “Construction is war; waste and variation is the enemy.”
Every day is a battle against waste and variation, and believe me, we are at war. Everything in the construction process is literally trying to kill us on-site or waste countless hours of time and money.
Don’t believe me? Audit your last seven days of inbox, chats, and texts. The battlefield is right there:
62-email reply-all chains where nobody owns the next step
RFIs and submittals routed through 4 people “just to keep them in the loop”
A text chain that becomes the decision record
The quiet stuff that never reaches you until it’s already on fire
Communication is the oxygen of the project. Cut it off and the team suffocates. Flood it with noise and the signal disappears. Bad oxygen makes great people look mediocre.
So most teams default to one thing: copy the leader on everything.
Every question funnels to you. Every decision waits for you. Every problem ends up in your inbox. And you spend your best hours sorting noise instead of leading.
When everything funnels to you, it feels like ownership. In reality, it robs your team of theirs. When you take the decision off their plate, you take the reps off their plate too.
The best teams flatten leadership instead of stacking it. Decisions get made closer to the work. People learn to weigh the situation, decide what matters, and escalate only when the commander’s judgment is actually required.
That builds the next generation of leaders on your project.
But it only works when everyone knows the rules of engagement.
This is where the CCIR comes in. It stands for Commander’s Critical Information Requirements.
It’s a simple protocol for defining what information must reach the commander, how fast, and through what channel. Your team keeps moving. You get pulled in only when your judgment is actually required.
Understanding Today’s Complex Environment
A modern project is not a simple equation of time, cost, and scope.
It is a living system. Layered. Dynamic. Interdependent.
Your project sits inside a network of moving parts that all push and pull on each other:
Owners, designers, and consultants
Donors, investors, & political figures
AHJs and inspectors
Communities and relationships
Trade partners with their own priorities
Internal teams juggling 10 jobs at once
Now stack the information firehose on top. Email. Texts. Teams. Procore. RFIs. Submittals. Photos. Daily schedule updates.
There’s a Joint Staff focus paper on CCIRs written for military commanders that nailed it:
Modern operations drown commanders in information. The volume hides the signal.
That’s construction. Maybe more than any other industry.
Our decisions are interdependent with the decisions of every partner around us. A late owner decision changes your manpower plan two weeks downstream. A design RFI stuck in someone’s queue stops a trade. A delayed steel package shifts your concrete pour. Your project is a chain of decisions, and every link has a different person holding it.
Then layer in the human limit.
Decades of research is consistent: the average person can hold roughly seven things in their head at one time.
A single phase of a complex construction project has hundreds of moving pieces in any given week.
Hundreds of decisions. Thousands of micro-actions. Dozens of stakeholders. One brain.
The math doesn’t work.
The complexity isn’t going to slow down. What has to change is how you choose to receive it.
You have to design a system that brings the right information to the right person at the right time, in the right format.
That is the entire mission of a CCIR.
What is a CCIR?
The Focus Paper’s clean definition:
Information the commander identifies as critical to timely decision making.
Construction translation: a CCIR is your filter for communication and decisions.
It defines four things:
What must reach you
How fast it must reach you
What channel it comes through (call, text, email, meeting)
What “good information” looks like when it arrives
CCIRs aren’t a hard set of reporting requirements limited to specific actions or events. They’re a philosophy of command and feedback that creates decision space.
That is the goal. Decision space. Room to think, plan, and call the next move before the next problem hits.
A CCIR has two components:
PIR (Priority Information Requirements): changes outside your team that force a decision. Owner, investor, designer, AHJ, trade partners, deliveries, permits, claims.
FFIR (Friendly Force Information Requirements): changes inside your team that force a decision. Safety, manpower, constraints, quality, schedule performance.
PIRs scan the outside force. FFIRs scan your own force.
Together, they replace “copy me on everything” with “tell me when this happens.”
Without a filter, you don’t get “informed.” You get buried.
Story Time: The SPM Who Couldn’t Control His Inbox
I remember a Senior PM who couldn’t control his inbox.
On paper, he was the full package. Organized, technically sharp, great with owners.
But balls kept getting dropped. Not because he didn't care.
We started to look for the root cause of the issue.
He was CC’d on everything. Every RFI, every submittal cycle, every trade-to-trade coordination email that didn’t require his expertise.
His unread count lived in the hundreds and his stress level tracked it perfectly.
Two things happened to him at the same time.
His attention got shredded into slivers. He couldn’t decipher what was important and what wasn’t. Every email looked urgent. Nothing got the focus it deserved.
The volume of information became unmanageable. Internal traffic from his own team doing the work. External traffic from owners, designers, AHJs, and trades. All of it pouring into the same inbox at the same time.
It started to impact his ability to lead. Decisions got slower. Follow-ups got missed. He became a bottleneck.
After several attempts, we built and tested his first CCIR. He defined what rises to his level, how fast it needs to get there, and through what channel. Everything else stayed where it belonged, with the person closest to the work.
He rose above the noise. The team sped up. The bottleneck cleared. He got his head back.
Lesson: as a project leader, you can’t let “keep you in the loop” become your operating system. Define the protocol, or your inbox will define it for you.
How to Build Your CCIR in 5 Steps
Step 1: Name the decisions that actually require you
Write down 5 decisions you’ll personally make in the next 30 days.
Client communication. Schedule gates. Budget approvals. Scope changes. Trade sequencing. Inspection hold points.
If you can’t name the decision, you can’t name the information.
Step 2: Write your PIRs (external triggers)
Ask yourself: what outside change forces a decision from me?
Examples:
Owner request above $X
AHJ fails an inspection (any trade)
Design issue stops work and requires an RFI
Key material delay > X days
Sub issues notice of claim or dispute
Permit or regulatory hold
Step 3: Write your FFIRs (internal triggers)
Ask yourself: what inside change forces a decision from me?
Examples:
Safety incident or near-miss
Trade manpower below plan with no recovery
Critical submittal rejected
PPC drops below X% for 2 weeks
Constraint past due with no plan
Team performance issues
Step 4: Build the reporting protocol
This is where most CCIRs die. People write the list and forget to define how the information actually travels.
For every trigger, define 5 things:
Channel: phone call, text, email, or meeting?
Process: what gets attached, completed, or referenced when the trigger fires
Who first: PE, super, or you?
How fast: now, same day, or next stand-up?
What “done” looks like: decision requested, recommendation included, owner named.
Step 5: Run it (monitor, display, update)
A CCIR isn’t a document. It’s a system.
Put it somewhere visible (job trailer wall, dashboard, team page)
Review it weekly
Update it when the job phase changes
A CCIR built for foundations doesn’t work the same way during MEP rough-in or owner punch. Rebuild as the war moves.
TL;DR
You are the Commander of your project. Act like it.
Communication is the supply line. Protect it.
A CCIR is your filter for what reaches you, how fast, and through what channel.
PIRs scan externally (owner, design, trades). FFIRs scan internally (safety, schedule, manpower, quality).
Build it during planning, not during the fire.
A CCIR isn’t a document. It’s a system. Display it. Review it. Update it.
Your One Action This Week
Open a blank page and write down 5 decisions you’ll personally make in the next 30 days.
Then ask: what would I need to know to make each one fast and right?
That is your first CCIR. Pin it to your jobsite trailer wall by Friday.
The war on waste and variation isn’t going away. The commanders who fight it with a real communication protocol win the job, hit the numbers, and still go home on time.
Take command.
Until next week,
Kyle
Ready to level up? Here are 4 ways I can help you:
Get ProjectOS. The AI-powered Notion project operating system I use to manage $300M+ in projects. Set up in 1 day, not 3 years. Save 10+ hours weekly.
Join Antifragile Project Management. Leadership development course and community built on the 7 Archetypes Framework. Transform from project witness to project leader. Earn promotions and reach senior leadership levels.
Read the Book. No Bullsh*t Project: A Project Manager’s guide to successful project leadership. Available on Amazon.
Promote Your Business. Get your brand in front of 8,600+ highly engaged construction leaders and decision-makers with a 51% open rate.
The CCIR framework maps almost exactly to the AI governance problem in enterprise PMOs — and the failure mode is identical. It's not that there's too much AI. It's that nobody defined the protocol - which decisions still require a PM's judgment, the speed the determination needs, and through what channel. "Let AI handle it" becomes the new "copy me on everything" — feels like efficiency, functions like abdication. Same inbox problem, two levels up.
Kyle, have you trained any AI (Claude Cowork, etc.) on this process? I gotta think AI monitoring of incoming communication is the next great unlock, right?