The Meeting Started Before the Work Was Ready.

When governance forums receive coloured status instead of decision-ready evidence, senior people spend scarce time reconstructing reality and defer the judgment the meeting exists to make.

The Meeting Started Before the Work Was Ready.

The Meeting Started Before the Work Was Ready — FLM4 article by Imad Lodhi

Poor preparation turns executive time into live data collection

A customer delivery review opened with a familiar slide: one account was red.

That was all the meeting knew.

The deck did not show when the risk first appeared, which milestone had slipped, what dependency was blocking recovery, what the customer had been told, or what decision the delivery manager needed. It simply showed a red circle beside the account name.

So eight experienced people spent the next thirty minutes collecting facts in real time.

Someone searched an email. Someone else opened the project plan. Finance checked an invoice. Sales explained the customer’s mood. Delivery tried to reconstruct the sequence. By the time everyone understood the problem, the meeting was nearly over.

The decision was deferred.

We often call this a meeting problem. It is usually a preparation problem.

A governance meeting should not be the place where the organization first assembles reality. It should be where prepared evidence is interpreted, trade-offs are surfaced and decisions are made.

That distinction matters because executive time is expensive. More importantly, it is scarce. When leaders spend it asking for basic facts, there is less time left for judgment.

A coloured status is not a decision-ready input.

“Red” may attract attention, but it does not explain what changed, why it matters, what has already been tried, what choices remain, or who has the authority to choose among them. Without that structure, the meeting becomes an investigation conducted by committee.

The answer is not a longer deck. In fact, long decks often hide the same weakness behind more pages.

The answer is an admission standard for the conversation.

Before an issue enters a decision forum, the owner should be able to frame the outcome at risk, the evidence, the cause as currently understood, the available options, the recommended action and the decision required from the room. Uncertainty is acceptable. Unpreparedness should not be routine.

This changes the manager’s role. Instead of presenting a status and waiting for senior people to interrogate it, the manager brings a management case. The room can then challenge assumptions, test trade-offs and make a commitment.

It also changes the meeting owner’s role. If the required evidence is missing, the owner does not reward poor preparation by turning ten attendees into researchers. The issue is either prepared quickly, assigned for completion, or moved to the appropriate forum.

There will always be genuine surprises. Operations do not wait politely for the next agenda. But recurring reviews should not behave like every known risk has just been discovered.

A useful question before the next governance meeting is simple:

If the people in the room understood this slide exactly as written, could they make the required decision?

If the answer is no, the meeting has started before the work is ready.

That is not efficiency theatre. It is management-system design: protecting decision time by making the inputs worthy of it.

If this tension feels familiar, my book, The 7 Essential First-Line Management Systems, goes deeper into the practical systems that turn information into action. You can explore it at imadlodhi.com/flm1.

Read more...

Loved it? Follow me.

About the Author

Imad Lodhi

Founder IMADLODHI.COM | Partner | Global Sales & Delivery Executive | Strategy & Innovation Leader | Delivery Excellence/Analytics Leader | DWS Leader | Author

ABOUT IMAD

Imad Lodhi

Sales & Delivery Transformation Executive focused on the management systems, mindsets and behaviours that turn strategy into measurable outcomes.

Continue the conversation

Stay in the conversation.

Awesome sauce!

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form :(