A posting schedule that suits a team of one or two

Published social media schedules are generally written from the perspective of someone whose job is social media. They assume a working day with room in it, a supply of material, and no competing responsibilities that arrive without warning.

A business with one or two people has none of those. Social media is one item on a list that also contains serving customers, doing the work, chasing payments and everything else, and it is the item with no immediate consequence for being skipped — which is exactly why it gets skipped first and why an ambitious schedule fails.

The useful design goal is therefore not the best schedule but the most demanding one that still runs in a bad week. Those are different objectives and they produce different plans. A schedule that works only when things are calm will produce a few good weeks followed by a gap, and the gap costs more than the extra posts gained.

What follows is a concrete week built for that constraint.

Three feed posts, two Story days, a short daily window for replies, and one production session. That is the whole plan, and each part is doing a specific job.

Three feed posts, spread rather than clustered — say Monday, Wednesday and Friday. Spacing matters more than the specific days, because clustered posts compete with each other for the same audience and then leave a long silence.

Two Story days, which cost very little because Stories can be captured from work that is happening anyway rather than produced. They keep the account present on the days it does not post.

Fifteen minutes daily for comments and messages, at a fixed time. This is the part that most directly affects whether the account produces customers, and it is the first thing dropped when the plan is too full.

One production session of about two hours, once a week, to make the three posts. One session rather than three, because the overhead of starting is most of the cost.

The reason a weekly session works is that it separates tasks that use different kinds of attention, and doing each once is markedly faster than doing all of them three times.

Run it in four phases. First, choose the three subjects from your running list, and do not write anything yet. Second, gather every image or clip needed for all three. Third, write all three captions in sequence. Fourth, load them into a scheduler with their dates.

The phase people skip is the first, arriving at the session without a list and spending the best part of an hour deciding what to talk about. The fix is not discipline during the session; it is keeping a note through the week. Ideas occur while doing the work — a customer asks something, a job goes unusually well, a mistake gets made — and they do not occur when sitting down to think of content.

Two hours is realistic once the list exists. Without it, the same three posts can absorb an afternoon and feel like a much larger commitment than they are.

A plan with no slack breaks completely the first time a week goes wrong, and then usually stays broken, because restarting requires motivation that the failure has just consumed.

Three pieces of slack, all cheap. Schedule at least a week ahead, so a lost afternoon costs nothing — the queue keeps publishing while you deal with whatever happened. Keep two or three finished posts unpublished as a buffer, and use them for exactly this rather than posting them because they are ready. And decide now what gets dropped when time is short.

That last decision matters most and should be made while calm. The order that works for most businesses is: keep the replies, drop a feed post, drop the Stories, and only then miss a production session. Replies come first because a person who asked a question is a real prospect and an unanswered one is a lost customer, while a missed post is invisible to everyone.

Writing that order down means the decision is not made under pressure, which is when people drop the wrong thing.

With two people, the temptation is to split social media in half. It usually works better to split it by kind of task.

The division that works is one person owning production — subjects, images, captions, scheduling — and the other owning conversation, the daily replies. These need different things: production benefits from a consistent voice and a single person's judgement about what the account sounds like, while replies benefit from whoever is closest to customers and can answer accurately.

Splitting by day, alternately, tends to produce an account with two voices and no clear standard, plus a recurring gap where each person assumed the other was handling something.

Whatever the split, one thing needs to be explicit: who approves a post before it goes out. Two people posting independently to the same account, without a review step, is how a claim about a price or a delivery time reaches customers without anyone having checked it. Tools including Socie can hold a draft for approval before publishing, which turns that from a house rule into part of the process.

This schedule is a starting point, not a target, and the signals for changing it are specific.

Raise the cadence when two things are true at once: the current plan is running without effort, and the subject list is growing faster than the slots can absorb it. Then add one post a week and hold it for a month before adding more. What does not justify a raise is reading that more is better, or a good week.

Lower it when the production session is regularly being missed, or when posts are going out that you would not defend. Both mean the plan exceeds the available capacity, and continuing produces filler plus guilt. Dropping to two posts a week and keeping them good is a real improvement, not a retreat.

And review the shape occasionally rather than only the volume. If Stories consistently produce more enquiries than feed posts, the sensible response is to move effort towards Stories rather than to keep the ratio because the plan said so. The schedule exists to remove decisions, not to survive contact with evidence.