Posting cadence for teams: the contract that survives a quarter

A team cadence is usually decided in one meeting, by the person most excited about it, for people who are not in the room. Six weeks later nobody remembers what they agreed to, and the person who set it is quietly annoyed. The rhythm was never the problem. The contract was.

This page is about setting a posting cadence for teams that survives a real quarter: who owns each goal, how to size it per person, what to do when someone misses, and when to raise it. It is written for founders and marketing leads running a program with three to ten people.

TL;DR

Why a single team target always fails

Twelve posts a month across the company sounds like a goal. It behaves like a shared inbox. Everyone assumes someone else is covering it, the number is only checked when it is already missed, and no individual ever feels late. Diffusion of responsibility is not a character flaw, it is what shared targets do.

Splitting the number per person fixes ownership. Splitting it per network fixes something else: a LinkedIn post and a short video are different tasks with different costs. Folded into one number, the expensive format is always the one silently dropped, and the total still looks fine.

One person, one network, one number, one period. Anything vaguer is a wish with a deadline.

Size the cadence per person, in a conversation

Do not assign cadences. Agree them, one person at a time, with one question: what can you publish in the week the quarter closes and you are travelling? The answer is almost always lower than what they would volunteer in a kickoff meeting, and it is the number that will actually hold.

Expect the founder to overcommit and the sales team to undercommit. Both are fine. A sales person publishing once a week for a year is a serious program. A founder publishing four times a week for three weeks is a burst.

For company pages, LinkedIn publishes its own floor of one update per day and a ceiling of three or four. Use it for the brand account only. Applying page guidance to people is the most common way a team cadence gets set too high on day one.

Weekly or monthly periods

Use weekly periods for short formats. The feedback loop stays tight and one missed day is recoverable inside the same week. Use monthly periods only for formats with real production cost, such as long form video, where a weekly target would force bad work or be ignored.

The failure case is a monthly target on a short format. Three quiet weeks, then a panic, then four posts in two days. Nothing about that shape builds a habit, and the numbers at the end of the month look identical to a team that published steadily.

Freeze the cadence, move the target

Once set, leave the period alone for at least two cycles. Switching from weekly to monthly mid quarter makes the history unreadable: you can no longer tell whether a good month came from a better team or an easier goal.

If the number is wrong, change the number, not the rhythm. Lower it after two consecutive misses, and raise it only after two clean periods in a row. Two is the threshold that separates a bad week from a wrong target.

What to do when someone misses

Do not send the reminder. It costs you something every week, it arrives when the period is already lost, and it turns a shared project into a task someone supervises. Teams that rely on reminders stop when the reminders stop, which is always sooner than anyone expects.

Let the board do it instead. A visible lane, a marker showing where the person should be today, and a streak that is about to end apply the same pressure without anyone playing manager. If somebody misses twice, that is a signal to have the sizing conversation again, not to chase harder.

Counting without asking

A cadence only exists if it is counted, and the counting cannot depend on the people being counted. A shared spreadsheet measures willingness to update a spreadsheet, and that willingness disappears in exactly the week the posting does. This is the mechanism explained in social media posting consistency.

Public profiles remove the dependency. A published post is visible to anyone, so it can be detected and counted with no account access, no password sharing and nothing to install on anyone's phone. The limits of that approach are in public social media metrics.

How to choose your setup

• Three to five people, one network. One goal each, weekly, one shared board. Nothing else is needed for the first quarter.
• Six to ten people, several networks. One goal per person and per network, plus one team objective above them, or the board becomes a list nobody reads.
• Agency running client programs. A separate space per client, and a read only view the client can open. See client reporting for personal branding.
• A team that already failed once. Halve every cadence from the previous attempt. The second failure costs far more credibility than a low target ever will.

The sizing conversation, in four questions

Have it one to one, never in a group. In a room, people commit to what sounds impressive. Alone, they tell you what is true.

1. What could you publish in your worst week this quarter? This is the number. Everything else is context.
2. Which network, and which format? A written post and a video are different jobs. Pick one to start with.
3. What would make you miss it? Usually travel, a launch or a deadline. Now you both know it is coming.
4. Do you want the team to see your lane? Almost everyone says yes, and the ones who hesitate are telling you the cadence is too high.

Write the answer into the goal itself, not into a document. A cadence that lives in a doc is a cadence nobody ever checks against reality.

What happens when someone leaves

In a founder led program the audience belongs to the person, and it walks out with them. That is a real cost, it is not a reason to avoid the model, and it should change two things about how you run it.

First, keep the history. Their lane stops, the record of what the program produced stays, and that record is what protects the budget in the next review. Second, never build the program on one person: three people publishing weekly survives a departure, one person publishing daily does not.

Bringing a new person into an existing cadence

Someone joins in month four, and the reflex is to hand them the team's rhythm on their first week. That is the fastest way to produce a person who has already failed at something before they understood it.

• Start them one step below the team. If everyone publishes twice a week, start at once, and raise it after a month they held.
• Do the sizing conversation properly. The same four questions everyone else answered, not an inherited number.
• Do not backfill their history. They started when they started, and a lane that opens empty is honest.
• Say the streak rules out loud. A new person who does not know that a missed period resets the count will discover it in the worst way.

Teams that get this right end up with different numbers next to different names, which looks untidy on a board and is the only version that lasts. The board is not comparing people, it is showing each person against the promise they made.

How Groowth handles this

A goal in Groowth is exactly this contract: one account, one content type, one cadence, one target. The cadence is frozen when the goal is created, the counter fills from posts detected on the public profile, and the streak counts periods hit in a row rather than days.

Above the lanes sits one crew objective, so the last person's week is everyone's business. Nobody checks in, nobody installs anything, and the free plan covers three accounts with no card.

Frequently asked questions