a content system, not a calendar.
formats, a production day, one approver and two weeks banked — the parts that survive a busy month.
the work usually exists already. what is missing is someone empowered to release it.
most dubai brands do not have a content problem, they have a decisions problem. the work stalls because nobody agreed what gets made, who approves it, or when.
— 01deciding once, not weekly.
aim for repeatability — a system, not a one-off calendar that resets each month. a system exists to make those decisions once.
so write those three down and stop revisiting them. the churn that kills content programmes is almost always a decision being remade rather than work not being done.
then decide the output honestly — how many finished pieces a month you can produce through a busy period, not an ideal one. a calendar sized for a quiet month collapses in the first busy fortnight.
and pick one platform to be genuinely good at. a system spread across five channels in dubai is one channel's worth of effort divided five ways, and it produces five accounts nobody would follow.
— 02formats, a production day, an approver.
pillars, formats, a batch-production rhythm and a clear approval flow. a system means you never start from a blank page — pillars, formats and a calendar a busy team can actually keep.
the working shape is a small number of repeatable formats rather than a list of post ideas. formats survive a busy month because nobody has to invent anything; ideas do not.
batch production into one day a month and bank two weeks before publishing. an account producing this week's content this week is permanently reactive, and it shows within a month.
name one owner and one approver with a 48-hour turnaround. most content systems in dubai fail on approvals rather than production — the work exists and nobody is empowered to release it.
and keep an archive that is actually navigable. labelled projects, marked selects, saved grades. material you cannot find again is material you will pay to produce twice.
— 03the number the system answers to.
track output consistency and the outcomes it drives — both should climb. vanity metrics feel good and tell you nothing. track the numbers that connect the feed to revenue, and adjust monthly.
pick one number and record its current value before anything changes. enquiries a month, bookings, cost per acquisition — one figure both sides judge the system by.
review quarterly rather than monthly. one month of social data in dubai is noise, particularly around ramadan and the summer, and monthly judgement produces constant changes and no compounding.
and cull each quarter. drop the format that consistently underperforms rather than adding another — subtraction is the fastest improvement available to most calendars.
— 04what makes a system survive a year.
it has to work when the founder is travelling, the shoot gets cancelled and the month is busy. any system that depends on enthusiasm has a two-month lifespan.
the practical tests are simple: two weeks banked at all times, one named approver, and a monthly production day already in the calendar. a system with those three holds; one without them restarts every quarter.