Slogan or Decision?

Slogan or Decision?

In almost every board meeting, one sentence gets said: “We need to develop the business.” Everyone agrees. It goes into the minutes. Then a year passes, the same meeting is held, the same sentence is said, and everyone agrees again.

What actually happened during that year? Usually nothing. Because what was said was never a decision — it was a slogan.

A slogan expresses an intention. A decision creates an obligation: a named owner, a budget, a date, and a metric that will judge it a success or a failure.

The difference isn't semantic. A slogan costs no one anything, which is why it passes so easily. A decision costs something, which is why it gets postponed.

Across more than 16 years in internal audit and control system reviews, I've worked inside dozens of businesses — contracting and roads, real estate investment, manufacturing, trading. What struck me most was never the size of the errors. It was what happened to the recommendations: detailed reports explaining the gap and proposing the fix, read carefully, the author thanked — and then filed in a drawer. Two years later, the exact loss the report warned about shows up on the income statement.

This series was born out of that gap: the distance between what we know is right and what we decide to do.

What the series covers

Five themes, each running across several articles:

One — The difference between a business development slogan and an executable decision. What turns a statement into a real decision, and the four elements that — if any one is missing — reduce it to a good intention.

Two — Signs your development plan is just meeting talk. Indicators you can check yourself within an hour: does the plan have a single owner? Does anything move in the budget? Does delay carry a consequence?

Three — Turning vision into measurable steps within 90 days. Why five-year plans fail where 90-day cycles work, and how to build one in practice.

Four — Companies that made a real development decision, and what it produced. Cases from the Egyptian market, with before-and-after numbers, including the setbacks that success stories usually leave out.

Five — How financial data turns a development decision from instinct into calculation. Reading the statements to tell you where exactly to invest, instead of reading them for compliance alone.

How it will be published

One article per week, in Arabic and English, each with a visual summary for readers who prefer the short version. You won't find imported management theory here — only what I've seen work, and what I've seen fail, inside businesses operating under Egyptian market conditions specifically: constrained financing, volatile costs, and a team asked to develop the business without being relieved of a single day of running it.

Before we begin

A question for you: what was the last “development decision” taken in your company? Can you name its owner, its deadline, and the metric that measures it?

If you hesitated on any one of the three — this series was written for you.