Scapegoat or Secret Agent? Operation Credible Dates!

TL;DR: How to uncover false-green status, ask better questions, and build alignment without becoming the project police.

Abstract: Ever seen a project marked “on track” while deadlines keep slipping? In this interactive, humorous session, Sreeraj introduces his CAT framework - Clear the Fog, Ask Better Questions, and Target Behavior/Mitigation—to help project professionals uncover risks, challenge assumptions, and build more credible commitments.

Full Article:

Have you ever felt that being a project or program manager requires several professions - none of which appeared in the job description?

Week-1, you are an auditor, examining status reports with a fine-tooth comb.

By Week-2, you are a lawyer, cross-examining engineers and their leaders to determine whether they are describing the same project.

By Week-3, you are Sherlock Holmes, hunting for clues to answer one surprisingly difficult question: “Are we actually on track?”

Welcome to Operation Credible Dates. No secret clearance required. Just curiosity, persistence, and perhaps a strong cup of chai.

The dream project

Let me tell you a story - short but bitter-sweet at the end!

Many years ago, I was happily managing a big, shiny, greenfield initiative.

I was excited about joining a new company and being given the ownership to run an exciting new software product that is going to be cutting-edge in the industry.

On paper, this project was a dream.

Then the plan met the people.

We had conflicting assumptions, multiple owners, and decisions that seemed to be waiting for someone else to make them.

What started as a career-development story was becoming a horror movie. The villain was the status report!

Week after week, milestones slipped.

Week after week, the status remained “on track.”

Apparently, the dates were flexible. The color was not.

After three consecutive weeks of missed milestones, I asked:

“Are we off track now?”

You might think that would be a straightforward question.

You would be wrong.

Scene-1: Software becomes the villain

In week four, a senior director walked into the conference room.

I had arrived early, eager to hear about our progress.

Instead I heard" "You know, these deployment tools are very painful. I saw your questions about the missed milestones. It's all because of the tools"

Ah. Software was the villain.

The tools might genuinely have been a problem. But explaining why we were delayed did not change the fact that we were delayed.

By the end of the meeting, we agreed in the delay. I saw that as a progress, although not necessarily on the project, but at least in the conversation.

Scene-2: Mr Optimism Returns

The following week brought a new explanation:

“We’re past the tool issue. We’re catching up, and the team is working really hard.”

I acknowledged the effort, turned toward our executive, and said: "The milestones were still beyond their original commitments.". Since it is not the popular line in the room, I did not repeat it but entered this in our status log for the executive review "We are still delayed".

Then came week-6 and my favorite character Mr Optimism came back with a new punchline "We have a plan to catch up. We have new engineers joining".

Great news. One small question: Do they come with a time machine that can fix the delays from the past weeks?

As much as I appreciate the leadership bringing additional help, until they are ramped up it wont be clear what work would be expedited, and if we can identify a new credible date. At this point, it was just a new reassurance, not yet a recovery plan.

Scene-3: Watermelon Status, Anyone?

I put on my hat as the angry auditor and list out all the discrepancies between the original commitments and the reality. The status was green on the outside, but off track and red on the inside. How useful was it in an executive review?

My instinct was to escalate.

Scene-4: The Tension Builds

My instinct was to escalate.

Find the inconsistency. Highlight the risk. Make the problem impossible to ignore.

I did not want to worship ambiguity; I wanted to remove them…

So, I did what any self-respecting PM would do,

and I kept raising the same red flag to my PMO leadership:

I kept raising the concerns weekly - “We’re missing dates, the risk is escalating, and the ‘we’re still on track’ message is not persuasive.”

Eventually, my leadership did their part by escalating this to the big boss.

Senior leaders started to notice that the status reports looked like a crime scene: Dates crossed out, new dates scribbled in, and yet the status column still said, “on track.”

Scene-5: New VP & CIA Mode

That’s when the organization decided to “fix” the problem.Enter: a brand-new VP of Engineering.

He looked at the situation and said,“We need credible dates. I will recruit… the TPM.”

He asked me to come up with realistic delivery dates.Sounds reasonable, right?

Here’s the catch:I was asked to do it without working with the director that I’d been dealing with all along.

Instead, I was told,“Work directly with this lead engineer you’ve barely interacted with. He reports into the same leadership, but don’t loop the director in.”

Scapegoat or a Secret Agent

At that moment, I had two thoughts.

First: “Am I being trusted?”

Second: “…or am I being set up as the official scapegoat?”

So when the VP asked to avoid the directors….

And that is when my TPM job suddenly felt like the CIA.

I was expected to gather intelligence with one lead engineer, while avoiding others, more importantly his own manager!

Well. The easy choice would have been to play along: ask for optimistic dates, put them in a pretty slide, and hope no one remembered what I said.

But I didn’t want pretty fiction; I wanted credible dates.

Scene 6: Curious TPM vs Angry Auditor

The useful answer was neither blame nor espionage.

It was partnership.

Instead of approaching the engineer as someone whose estimate I needed to challenge, I needed to approach them as someone whose judgment we needed.

The question changed from:

“Why is your date wrong?”

to:

“What must be true for this date to hold?”

That changed the conversation….The lead engineer stopped sounding defensive and started sounding thoughtful.

He said, “Okay… if we’re honest, that date is aggressive.”

– “dates were aggressive, we learned new things as we were developing, but we were told not to raise them…see….fear our executives…I was slapped multiple before and I am not willing to be exposed”

“My goal was never to expose anyone. The goal was to make it safe for the team to tell the truth early enough to do something about it.”

Turning Point

“That was the turning point for me.”

I said, “Good. Then let’s build a credible plan around what is possible.”

1. We looked at which dependency worries him most.

2. What changed since last week.

3. Who owns the decision on this slips.

With the new VP, something interesting happened. I shared the new plan, explained the logic, and focused on the project’s success.

He didn’t love the bad news, but he respected the honesty.

With the tricky director, I had to practice polite, professional courage. I stopped debating vague definitions like “code-complete” versus “feature-complete” and started presenting clear evidence: milestones promised versus milestones missed.

When I stayed objective, leadership listened—and that changed the dynamic.

The complete Emotional Arc - Scapegoat to Secret Agent

Remember - I started this situation feeling like a scape goat - wondering who I could talk to, and worrying that, I or the engineers might become the scapegoats if the dates were wrong.”

And then when I escalated and brought the risks to visibility, I was able to get the support needed, although it still was not the solution, so I had to stay curious and change my approach. I had to go from angry TPM to a curious one.

Over time, I realized that I was using the same three moves again, and again. I was clearing the fog, asking better questions, and targeting the behavior that created credible action.”

These experiences also taught me that credible dates do not come from pushing people harder. They come from changing how we see, ask, and act. That is CAT.

CAT Framework

“That became my CAT framework.” C for Clear the fog, A for Asking the Questions and T for Targeting the right behavior.

A simple framework that I am calling “CAT”

Imagine a cheetah, a cat, that does not sprint all day, but when it moves, it moves with speed, focus and a

target aka purpose!

Lesson-1: Let’s begin with what the fog is?

There are lot of great people with good intentions, but we must pick our battles and narrow down our choices.

When there is a lot of information coming in, it is hard to process them fast enough. Facts get inter-twined with reassurances. This creates a fog in your brain preventing clarity.

From most of my career, I did not wake up thinking “I would love to become an expert in ambiguity”, because I thought, I was growing in program management.

Earlier in my career, when situation felt unclear, my instinct was often to work harder by sending emails, setting meetings, building trackers, scheduling more meetings, sending more emails with actions and forcing ETAs, and escalating relentlessly.

Because clearly, if people didn’t agree with my emails, my emails were not colorful enough!

Lesson-2: How to clear the fog?

To clear the fog, we need to get the tools needed, like a headlamp!

Put your headlamp on, to identify the evidence.

Next is about collecting the evidence.

Based on the evidence, now you are ready to ask the questions.

Questions help you understand why. So, try working backwards from it.

You do not need perfect certainty but only need enough shared evidence to ask the next right question and take the next credible action.

Lesson-3: What to ask, and what NOT to ask?

Do not argue with optimism. Instead, ask what makes the Mr Optimism credible.

When asking I learned to do three things:

1.ask the questions others were avoiding,

2.questions that quickly help you realize the situation on the ground, and

3.focus the areas that require further deep dive.

A good question is not a trap. It is an invitation to replace a vague promise with a specific, usable answer.

Lesson-4: Target Behavior - We are reality Negotiators!

As PMs, our job is not to create comfort;

We are reality negotiators, not merely….schedulers.

We need to create enough clarity for a credible decision. How we “act” determines the target.

Also - stay calm, stay consistent, and do the due diligence to bring facts, data, and objective analysis into every meeting.

That shift—from hidden risk to shared reality, involving my leadership chain to escalate, and getting the help I needed —is what changed the outcome

Lesson-5: Target Behavior, Keep the Trust

We are NOT targeting people. We're targeting behavior.

Because if I get the date right but lose the team, I have created a new problem!

The lesson I took from these experiences is that credible delivery is not about catching people out. It is about using calm truth to shift the conversation, aligning on progress we can actually see, holding the work accountable without making enemies, and adjusting our own style before the room forces us to.

Ask for specific, observable action, and align with them on whether it is reasonable. This keeps it respectful.

Calm: Although it might seem like you the PM was not engaged or involved before the date change was made, stay calm and do not accuse, instead ask what work is remaining, what changed in the assumptions.

Credible progress: can you give a date of date if you cannot commit to a date?

Not making enemies: ask if you can help them in anyway? Do not assume it is personal, try to provide examples of what success looks like, share past experiences on how the stakeholders typically handle delays. Help them help you by equipping them with necessary tools.

Adjusting style: setting expectations, giving heads-up on the agenda, aligning if they would find it helpful to attend the meeting. Provide

If the team repeatedly says they're confident without evidence, the behavior I want to change isn't the team's attitude. It's how we define credible progress.

Accountability doesn't have to destroy the relationship. E.g. just to collect status if you set a meeting, then you are inviting engineers who already hate meetings to show up for the sake of the PM.

Because nobody wants to become that PM.

You know the one.

The PM who walks into the meeting and everybody suddenly checks their calendar to see if they can escape.”

Better option is to use direct messages with the engineers or leaders to procure the progress and compare with the plan. Identify what assumptions, dependencies, risks, and contingencies you had previously and assess if any of those have changed or if we are eating into the buffer or contingencies.

Take-away:

Here are some areas for you to ponder and be the Cheetah!

That brings us to the Monday-morning test.

This week, clear one foggy status, ask one question you have been avoiding, and target one behavior that will make the next update more credible.

You do not need to solve every uncertainty. You need to make the next credible move.”

Clear the fog by separating what we know from what we hope is true.”

Specific questions turn reassuring language into discussable reality.”

Measure persuasion by what people do differently after the meeting.”

The target is not blame. The target is credible action: clear owner, real date, visible dependency, and measurable follow-through.

You may not eliminate ambiguity. But you can stop allowing it to hide behind reassuring language.