Build a 90-day execution plan around your team’s capacity

Start with a choice the business can explain

“Improve performance” is a direction, not a decision. Write the commercial question first: protect cash before expanding, improve reliability before adding a product line, or test one customer segment before committing to another market. State what you are choosing to do and what you are deferring.

A quarterly plan translates part of that choice into work. It does not establish that the strategy is sound. Check the customer evidence, the economics and the alternatives separately. Do not rank a mandatory deadline against an optional improvement using a weighted score that makes the two look interchangeable.

For a business working across GCC markets, put actual country, customer and supplier dependencies into the brief. Contract approvals, holidays, specialist availability and local requirements can change the sequence. This guide does not prescribe a regional working calendar or legal requirements.

Describe the evidence of a useful result

Give each initiative one accountable owner and a result someone can inspect. “Build a dashboard” is an output. “The operations meeting uses a reconciled margin view to decide which exceptions need action” describes intended use. Specify the current baseline, the measure, the evidence source and the review date without promising a benefit that has not been tested.

Use three questions in the brief: what business decision should improve, what will exist or work differently, and what evidence would cause us to stop or change course? A completed task list does not prove a commercial benefit. Record whether a measure is an early indicator, a final outcome or merely a convenient proxy.

The example below is original and fictional. It is not a Mizwala client engagement, an estimate of typical results or an endorsed planning method.

Reserve the hours that are genuinely available

Count hours available for change after recurring operations, payroll and close, customer service, agreed leave and known commitments. Do not use total contracted hours as spare project capacity. Ask the people doing the work to challenge the assumption.

Use mutually exclusive resource groups. If the same finance manager appears in two groups, divide that person’s available hours between them; do not count the same hours twice. Separate scarce approval or specialist time where it controls delivery. A team-level total can hide a bottleneck in one person.

The free planner uses three user-named resource groups, a constant weekly capacity for each, and up to eight initiatives. Each initiative has a start week, a whole-week duration and demand on all three groups in every active week. It covers 13 whole planning weeks, or 91 days, as a quarterly approximation—not an exact 90-day calendar. It does not adjust capacities for holidays, absences, partial weeks, dependencies or different skills. Use more detailed planning when those differences matter.

Three reasonable initiatives, one shared bottleneck

Consider a fictional Omani distributor. After routine work, its finance group has 8 change-hours a week, operations 10 and commercial 6. Managers propose the following work; hours are required each active week, not totals for the initiative.

Finance needs 12 hours in weeks 1–2 and 14 in weeks 3–4, against 8 available. Operations needs 12 in weeks 3–4, against 10 available. That is six overloaded resource-weeks: four finance weeks plus two operations weeks. It is not six different calendar weeks. The largest single resource-week gap is 6 hours.

The first three initiatives require 155 scheduled change-hours in total: 40 + 60 + 55. That total is insufficient on its own to identify the conflict; the timing and the resource group expose it. The fourth initiative is an explicit deferral, not silently treated as delivered or cancelled.

Zero numerical overload does not prove feasibility, benefits or the right strategic choice. Check the assumptions and dependencies described in the guide.

Change sequence before hiding the conflict

One option is to start the reporting pilot in week 5 instead of week 1, keeping its six-week duration. It then runs in weeks 5–10. Collection work still runs in weeks 1–4; the stock test remains in weeks 3–7. The same 155 hours are scheduled, with no overload against the entered capacities.

This is a capacity illustration, not a recommendation that reporting should always wait. If the report is needed to diagnose stock decisions, the dependency could invalidate this sequence. If the finance owner is absent in week 5, the constant-capacity assumption could invalidate it too. A deadline, cash constraint or customer commitment may require a different scope or additional confirmed capacity.

Compare four explicit responses: defer work, reduce its scope, change its sequence, or obtain agreed extra capacity. Overtime is not a free balancing item. Record what was authorised and what outcome or commitment changed. Use the planner’s “Compare sequenced example” button to reproduce the arithmetic; it replaces the example inputs rather than optimising your own plan.

Review decisions, not only completion percentages

Use a short weekly review: compare planned and actual progress, identify new evidence, name the next decision and assign an owner with a date. Check whether routine workload has consumed the capacity reserved for change. A favourable colour or a task marked complete should not conceal an unresolved exception.

At a meaningful checkpoint, review the original choice as well as delivery. Did the tested customer assumption hold? Was the stock issue a purchasing parameter problem or unreliable demand data? Did the performance pack change a decision? Decide whether to continue, re-scope, defer or stop, and record the evidence behind that decision.

Keep the stop and defer list visible. Restoring every deferred initiative during weekly meetings recreates the original capacity problem. Agree who may change the portfolio and require the consequence for another commitment to be visible.