NovA content calendar needs reader situations, not just topics
Broad themes such as sales or AI do not tell a writer what to publish on Tuesday. Start with the moment in which the reader needs an answer.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
“Marketing, sales, AI, personal brand” is not a content calendar. It is a filing system.
The missing decision appears on Tuesday morning when somebody has to write. What, specifically, does the business need to say about sales today? A broad topic gives no answer because it contains no person, no moment and no problem.
I get much more useful briefs from reader situations. A founder has leads, but replies take a day. A creator has published for six months and cannot tell which posts lead to commercial conversations. A team wants automation but is afraid every customer message will sound synthetic. Those situations are narrow enough to produce an actual point of view.
Situations create useful boundaries
A topic such as “sales” invites the writer to cover everything: pipeline, scripts, pricing, follow-up, hiring, forecasting. A situation such as “the form converts, but nobody replies until tomorrow” immediately creates a boundary. The article can focus on handoff, response expectations, customer context and ownership.
That boundary is useful for the reader too. They can recognise themselves in a situation much faster than in a generic category. The material feels specific because it is specific, not because the writer has decorated the opening with a personal anecdote.
Situations also tell you what to leave out. Good expertise includes exclusion. The writer may know ten adjacent concepts, but only three change the reader’s decision at this moment.
The same problem can produce more than one article
Teams sometimes avoid a subject because “we already wrote about it”. That is too crude a test.
Choosing a customer management system and repairing one full of meaningless statuses are both CRM problems, but the reader is in a different place. The first needs selection criteria. The second needs a way to diagnose why the system stopped reflecting the real sales process.
The subject can repeat while the situation changes. That is not duplication. It becomes duplication when the new piece asks the same question, makes the same argument and reaches the same conclusion with a different headline.
This distinction reduces the pressure to invent endlessly novel topics. Most businesses do not need novelty for its own sake. They need useful coverage of recurring decisions at different stages.
Choose the format after the question
Calendars often begin with format slots: short video on Monday, carousel on Wednesday, long post on Friday. That can be operationally convenient and editorially dangerous.
Once the slot exists, the team starts compressing or stretching ideas to fill it. A complex question becomes five shallow bullets because Wednesday requires a carousel. A simple answer becomes a long article because Friday is “thought leadership day”.
I prefer to identify the reader’s question first. Sometimes the best answer is four sentences. Sometimes a comparison table is genuinely useful. Sometimes the topic needs a long explanation because the conclusion depends on several conditions. Format should carry the idea, not dictate it.
Recurring series can still help. They reduce production friction and create familiarity for readers. They stop helping when the series must be filled even though there is no worthwhile idea that week.
The best backlog already exists inside the business
Useful situations are rarely invented in a blank brainstorming document. They appear in sales calls, support requests, search terms, email replies, comments and the questions customers repeat before buying.
I like to preserve the context around those questions. Who asked it? At what stage? What did they already understand? Which decision were they trying to make? A note saying “write about analytics” is almost useless a month later. A note saying “founder cannot tell whether Telegram influences sales because customers convert later through search” is a real brief.
Not every question deserves a piece of content. Some can be answered directly. The point is to let observed uncertainty inform the calendar instead of relying entirely on internal brainstorming.
A calendar should show the role of each piece
A healthy content programme contains different jobs. One piece helps someone recognise a problem. Another compares two approaches. Another answers a serious objection. Another explains how the product works. Another helps an existing customer use it better.
If every post only tries to attract attention, the audience has nowhere to go after becoming interested. If every post assumes deep knowledge, new readers struggle to enter. Reader situations naturally create a mix because people arrive at different stages.
That is why I see a calendar as a map of moments, not a grid of dates. The publication date answers when something will go live. The reader situation answers the harder editorial question: why would this be useful to someone now?