Blog / Digital growth /

An editorial calendar that follows customer decisions

The editorial calendar is full. Every slot has a date, a keyword and a format. And it still doesn’t help anyone, because it never asks what a customer needs to understand before choosing, buying, setting up or coming back. It’s a schedule of output, not a map of useful answers.

A better calendar follows customer decisions. That doesn’t mean forcing every subject into a neat funnel. It means finding the real choices people face, the information that helps with each one, and where a well-maintained page can answer the question better than a new article.

Begin with decisions, not keywords

List the decisions a customer must make in the real order they encounter them. A person may first need to decide whether a category fits their situation, then compare options, understand compatibility, arrange delivery, use the product, and resolve a problem. The sequence differs by business and product, and I wouldn’t copy a generic diagram and assume it describes your audience.

For each decision, write the question in plain language. “Which option fits my room?” is more revealing than a broad label such as “product research”. “Can I use this with the equipment I already own?” may expose a content gap that a keyword list does not show. Keep a distinction between questions customers actually raise and questions the team merely assumes they ask.

Use the evidence you have: support enquiries, sales conversations, search queries, onsite search, returns reasons, reviews and feedback from people who deal with customers. Every source has limits. Search data shows what people type, not always why, and a support log overrepresents difficult cases. Note the source and your confidence for each insight.

Map the answer to its best home

Once the decision is clear, decide where the answer belongs. It might belong on a product page, a category page, a delivery or returns page, a help article, a comparison guide, or an existing editorial post. A new article isn’t automatically the right fix, and I’d rather improve an existing page than add another one. If a shopper needs a compatibility detail before selecting a variant, burying it in a blog post makes the journey harder.

Look at existing pages before adding a calendar slot. Search the site and ask whether one can be improved. Consolidating overlapping pages, or adding a missing explanation to a high-intent page, often helps more than another article with similar wording. Record where the answer will live and why.

A useful calendar can include maintenance work. Updating a page when product details change, checking links after a site release, or reviewing an outdated explanation may be more valuable than publishing on a predetermined cadence. Treat editorial care as part of the plan rather than as spare work to do only when new writing is finished.

Build a sequence that respects uncertainty

Some decisions depend on information the team does not yet have. Mark assumptions and assign a way to check them. A small review of search queries or a conversation with customer-facing staff may reveal whether a proposed topic is distinct enough to warrant a page. I don’t turn a weak signal into a confident brief just because a date is free.

Set a priority using practical criteria: customer importance, evidence that the question occurs, consequences of a poor answer, effort to produce or maintain the answer, and whether the answer can be supported accurately. This is a discussion aid, not a mathematical score that creates certainty. If a topic contains regulated or technical claims, involve the appropriate reviewer early.

Then schedule dependencies. Product information may need approval before copy is drafted. A translated page needs language review and URL planning. A guide that depends on new imagery should not be assigned the same deadline as a text-only update. A calendar that includes these steps is more useful than one that records only publication day.

Give each item an owner and a useful finish line

For every entry, record the customer decision, evidence source, page destination, editor, subject-matter reviewer if needed, and maintenance trigger. Define “done” in terms of a usable answer: the page is accurate, links to the next relevant step, works on mobile, and has been checked in its live context. Publication alone is not a quality measure.

After release, observe the signals that match the purpose. A comparison guide may be judged by whether customers can find the information and whether it reduces repeated questions; a category update may need an organic landing-page review and an internal usability check. Avoid promising a traffic outcome that no one can guarantee. Set a review date and record what would make the page need another edit.

Keep the calendar revisable

Customer questions and products change. Hold a regular review to close items that no longer matter, revise assumptions, and add newly evidenced needs. Preserve the reasoning behind important decisions so that a future editor understands why the page exists. A calendar should support judgment, not remove it.

Test the calendar by following one customer question across the planned entries. Can the person find an answer before purchase, get help after it and reach the next step without wading through unrelated articles? If there’s a gap, add the missing answer or change the destination.

If your calendar is already crowded, pick one planned article. Which customer decision does it serve, where should that answer live, and what evidence supports the need? What would you change before giving it a publication date?