Hi everyone. I've been lurking for a while, trying to absorb everything, but I'm feeling pretty overwhelmed. My role is technically in procurement, but I've been tasked with evaluating and improving our content marketing workflows. We're a small SaaS team, and right now our "workflow" is basically: someone has an idea, writes a draft in Google Docs, sends it around for comments (which get lost), and then it eventually gets published after a lot of back-and-forth.
I understand the concepts of briefs, reviews, and stages in theory, but I'm stuck on where to actually begin building a repeatable process. I don't want to over-engineer it and scare the team, but I also know our current way is costing us time and quality.
Given my background in SaaS evaluation and TCO, I'm looking for a "recipe" that has clear, measurable steps. Something with defined inputs and outputs. I think starting with a single, common content type would be best.
Could you recommend a good first workflow to try? I was thinking maybe something around:
* **A standard blog post** (since we do a lot of those), or
* **A product update announcement** (which has a more defined scope).
What I think I need most is:
* A simple brief template to fill out before writing starts.
* A basic checklist for the first review (to catch the big issues).
* A clear handoff step for final edits/publishing.
Basically, the most foundational "pipeline" that proves the value of having a process, without being intimidating. Any examples or pointers to existing recipes in this forum that are known to be good entry points would be incredibly appreciated. I learn best from concrete examples I can adapt.
Start with the product update announcement, not the blog post. You already have the constraints - a defined scope, specific features to mention, and a known audience. That's half the battle.
Your recipe is staring you in the face. Take your current chaotic process and make one tiny improvement: force all feedback into a single Google Doc using the comment feature, and establish a rule that the draft doesn't move forward until all comments are resolved. The "brief" is just the Jira ticket or Slack thread where the product manager lists what changed. Input: ticket with feature list. Output: published announcement. Measure the time from ticket creation to publish. That's your baseline.
Most teams try to implement a full-blown CMS with approval stages and automations before they've proven they can handle a simple, linear process. Don't buy software until you've wrung every drop of efficiency from what you already own. Your procurement background will serve you well when you eventually do need a tool - you'll know exactly what problem you're paying to solve.
keep it simple