Blog Publishing Workflow With Claude AI: Cutting Time by 36%

How to turn a manual blog publishing process into an AI-assisted workflow without losing your voice? Explore how I learned to prompt with Claude in real time, implemented what works, refined what doesn’t, and mapped out the next steps that unveils work habits, new needs, and evaluate synergies with current tools so that we can keep our content operations sustainable as we grow.

This workflow describes the process of transferring the final draft of the blog post from Google Drive (the writing platform) to WordPress (the publishing platform).

This process includes the following substeps: formatting, final edits, internal/external linking, and identifying key highlights.

It’s the first iteration of integrating AI to optimize workflow and reduce content production time from a previously manual workflow.

The Goals of this Workflow Revamp

The goal of this blog’s publish workflow refinement is three-fold:

  1. Workflow Refinement (Primary): Turn a habit-tested but manual workflow into an AI-assisted but human-controlled workflow to reduce the blog publish workflow completion time from 3+ hours to less than an hour.
  2. Hands-on Learning in AI Creative Operations: Learn how to use Claude AI (free plan) effectively, identify its strong suits/limitations, and test the synergy between Claude and built-in AIs within my existing blog management tools (Google Drive —> Gemini, Notion—> Notion AI, Elementor —> Elementor AI)
  3. Mental Offloading for Business Growth: Make space to begin social media marketing initiatives to increase subscriber count.

Why Revamp the Blog Publish Workflow?

  • Established Consistency of Habit —> The blog publishing workflow has been well established and laid out, primed for AI prompting and automation that requires detailed step-by-step instructions to ensure efficiency.
  • Highly Repetitive —> Easy to be taught via Claude skills and replicated via AI prompting with easy-to-measure outcomes
  • Non-Strategic —> Won’t replace long-term strategic direction and ownership
  • Immediate Impact —> One of the biggest bottlenecks right now, and easy to validate the level of satisfaction.

Why Claude AI?

  • Teachable Tool with Structured Organization: I can teach Claude skills by providing process instructions in plain language, written as AI prompts that are easily retrievable and editable, to ensure my responses are consistent and more predictable.
  • Advocated by Thought Leaders: Ali Abdaal, one of the most influential self-help influencers, mentioned Claude as a key contributor to the upscaling of his business’s creative operations.
  • Tool Scalability:
    • All-in-one work hub with native connectors to existing management tools I already use for seamless API integration with intuitive ways to scale as business operations grow.
    • Business-friendly features such as data visualization, document artifacts, and custom dashboards (future expansion into Claude Code and CoWork).
  • Audience Interest & Searchability: Claude AI is a trendy topic with high amounts of search volume.

Step 1 was conducted on Friday, May 15, 2026.

I’ve connected Claude to Notion and Google Drive for this case study.

From: Anthropic Getting started with Claude.ai

Anthropic knows best how to approach its own product. I refined my AI prompting approach by following Anthropic’s guidelines for crafting effective AI prompts.

AI Prompt Formula: [Setting the Stage – What is your Role & What are Your Objectives?] + [Define the Task] + [Specify the Rules] + [Add Context Files]

I’ve given Claude access to my Google Drive and Notion, so Claude can read the referenced documents and directly add pages.

Claude AI auto-generates a new Notion page that shows the

[Proposed] Iteration 2 Process — Claude Workflow Analysis & Implementation Guide

  • Full process evaluation of my current blog publishing workflow and
  • Instructions on how to approach the next iteration of the workflow.

See Claude’s Sequential Steps Taken After AI Prompt Initiation (B):

Claude is advertised as a “thinking partner” by Anthropic, so I should talk with Claude in an effort to collaborate and encourage Claude to ask me questions. The back-and-forth interaction will give me a better idea of the true extent to which it could do.

My AI prompting approach is more conversational and gives Claude a broader scope of context for how this workflow revamp is a part of a bigger initiative.

AI Prompt Formula: [What I plan to do?] + [List of goals] + [The process] + [How the results should be presented?] + [Future collaboration expectations]

Claude auto-generated the

  • [Public] Nivationist Link Library on Notion as an expandable, single-truth links hub and
  • A Google Docs artifact on the step-by-step instructions on how to implement and use the workflow with tailored AI prompts. ****
  • Shows the full process evaluation of my current workflow within the chat (not as a Notion page compared to Method 1) for the coherence of current/future communication

See the Type of Responses Claude Gave After AI Prompt Initiation (B):

Claude proactively asks for specific contexts, allows me to pick what I want to do with a given list of recommendations, and gives me multiple-choice responses where I can put in my own alternative option for further processing, refinement, and human-driven operational control.

  • The more context you give to Claude and how this context is linked to your overall goal of completing the task that you requested Claude to do, the more helpful its responses will be to you in your use case.

  • When you collaborate with Claude as opposed to giving Claude a task, you’re given more flexibility and control over how Claude approaches your request. You also partake in refining their thought process before they take action.

  • Anthropic’s definition of how to create a good prompt is still relevant. The reason it yields a less varied response depends more on the level and amount of context provided. Although the Collaborative Approach doesn’t follow Anthropic’s structure for AI prompting, all the elements are still present (just with a different naming convention and more conversationally structured).
    • It’s best to combine the level of context and communication style from the Collaborative Approach + easy-to-use AI prompt structure from the Persona Approach.

  • Although it may be helpful for Claude to conduct its own context search within a connected tool you’ve given access to, it’s a privacy, security, and control issue.

[Action] Ask Claude to limit their search only to the files and links you explicitly referenced and shared in the prompt. Be aware of the information stored and be honest about your level of exposure before connecting your applications to any AI. Protect sensitive information behind a password to restrict access or transfer sensitive information to another place, if necessary.

Step 2 was conducted on Friday, May 15, 2026.

Why is human review necessary?

AI responses have a tendency to hallucinate, which means they will produce responses that sound like accurate answers but are made up. That’s where I would have to review the Claude artifacts to ensure their accuracy and intuitiveness of use for my use case.

This step is great for testing the synergy between Claude and other built-in AIs within my existing blog management tools (i.e., Google Drive —> Gemini, Notion—> Notion AI, Elementor —> Elementor AI)

The Human Review Process

The human review workflow diagram below was made by

  1. Audio transcribing the process (via Google Keep) of how I conduct the human review process, and then
  2. Generated via ChatGPT.

This step requires the testing of the Newsletter Publishing workflow revamp, which was completed on Tuesday, May 26, 2026.

Methodology

I am incorporating Claude into two workflow revamps simultaneously: blog publishing (this case study) and newsletter idea curation + publishing case study.

Currently, my newsletter creation + publishing schedule and my blog publishing schedule are on an alternating weekly basis.

Since Step 2 of this blog publishing revamp was in closer alignment with the newsletter schedule (week of May 18th), the workflow testing of the newsletter idea curation + publishing was done first.

This arrangement resolves several operational concerns:

  • Reduce Operational Redundancy and Conflicts: By aligning the revamp test with its respective publishing schedule, I was able to get two deliverables while doing the test. A newsletter that’s published on schedule, and this case study.
    • This approach ensures that the experimentation required for this case study will have the least impact/conflict on the deadlines for more established deliverables (blogs/newsletters).
    • There is no need to wait until the week of May 25th (the next blog publish schedule) to start the workflow revamp. Proxy-based information could be gathered via another similar workflow revamp to anticipate friction, apprehend results, and increase the probability of succeeding the “under an hour” goal when the next blog publish schedule rolls around.

  • Enriched Case-Study and Process Improvement by Building from the Previous: Since the approach and level of Claude-generated revamps for both workflows are about the same, redundant results and the lack of new findings could be resolved by feeding in post-process recommendations in the newsletter revamp test to improve the overall workflow revamp process and audience interest in this case study.

What was incorporated into this workflow from the previous?

The following two objectives from the newsletter idea curation and publishing workflow revamp will be incorporated into the workflow refinement/testing process in this case study.


Source: [See where the following tasks were derived from to get the full context.]

  • “Build a consolidated, single-truth work execution system by teaching Claude skills and organizing context files into different projects. Use ChatGPT as a fallback when the Claude free limit is reached. Test Claude’s ease of use before paying for the premium.”
  • “Experiment with Task Mining to have AI document my current workflows and auto-detect bottlenecks for future iterations, and save time writing down the workflow steps that help update skills in Claude.”

This sub-step was conducted on Tuesday, May 26, 2026.

Defining the Scope of Task-Mining for This Case Study

The long-term goal of incorporating task mining into the overall content management system is to remove a major friction point: having to document each workflow by memory and relying on my sole ability to explain the workflow steps in detail as the single point of truth and context for Claude to refine/suggest future iterative refinements.

With task-mining, I’m able to share my workflow either as a Loom/screen recording or have a dedicated task-mining software that can monitor what I do passively, record every click, keystroke, application switch, and mouse movement in real-time, which then automatically generates process maps and identifies bottlenecks/solutions from raw data for my review.

Because the Nivationist’s core philosophy and content are based on iterative case studies, incorporating task mining is crucial for process efficiency and scaling.


The purpose of this research/preparation substep isn’t to incorporate a fully operable task-mining workflow.

Because it is a part of a long-term initiative,

The incorporation of AI applications into the workflows isn’t yet fully established (still in the testing phase).

Instead,

The immediate goal/purpose of this substep is to

Research the type of tools I can use for task mining (get a sense of the learning curve, free-trial duration, after-trial pricing, pros/cons),

Set up a minimal task-mining application and gather process data whilst doing this case study to accumulate data to experiment with in a consistent learning schedule, and

Ensure this substep doesn’t affect the blog publish schedule for this week.

How do I approach task mining?

3 Task Mining Methods

Microsoft Power Automate: I’ve set up a free account to get a preview of the application and learn from its tutorials on task mining within its 90-day trial. It has a task-mining feature built in, but the synergy/intuitiveness between the current tools I use (Notion, Google Drive, Google Keep, Notebook LM, etc) and the enterprise-level functionality of Power Automate needs to be further explored.

Activity Tracker + n8n: n8n offers better synergy with the content management tools I currently use, but it lacks a built-in task-mining feature. Instead, n8n needs to pull raw data from an activity tracker application to generate results akin to native task mining. I’ve downloaded the Activity Tracker app so it can monitor my processes in the background and upload the raw data into Power Automate or n8n for process experimentation and business synergy to help decide which task mining platform to go with after the free trial ends.

Screen recording of my previous workflow (not the Claude-suggested workflow): There was an issue opening the Activity Tracker app. It also takes time for the app to load the activity data, and most of the data is uncategorized. Thus, I screen record my blog publish workflow as a precaution if Activity Tracker fails, and as additional context to close data gaps prior to Activity Tracker troubleshooting to ensure data coherence.

This sub-step was conducted on Wednesday, May 27, 2026.

Below are the summarized instructions and AI prompts within the Google Doc artifact that Claude generated. The instructions are composed of three parts:

  • Part 1: Proofread the final draft of the blog post, identify key highlights of the blog post, search engine optimization, and external/internal links suggestions to include in the blog post.
  • Part 2: WordPress post formatting reference sheet, featured image generation with ChatGPT, and pre-publish checklist.
  • Part 3: After-publish checklist.

Want a refresher on how I got the instructions + AI prompts? —> Navigate to Step 1

Copy your Link Library snapshot

Open your Nivationist Link Library in Notion. Copy the full Internal Links table + any Outbound sections relevant to today’s post topic. You’ll paste this into every Claude prompt below.

Run the Proofreading + Highlights prompt

AI Prompt Formula: [Role + Brand Voice Context] + [Specific Task] + [Structural Constraints] + [Post Content]

Run the SEO prompt

AI Prompt Formula: [Role + Brand Voice Context] + [AIOSEO Field Constraints] + [Post Content]

Run the Link Suggestion prompt

AI Prompt Formula: [Role] + [Task + Link Format] + [Link Library Snapshot] + [Post Content]

[In-Process Friction Points / Solutions] Part 1: Post Proofreading, Identify Key Highlights, SEO, and Suggest External/Internal Links

Previous Workflow Time: 140 minutes

Claude’s Target Time: 22 minutes

Current Workflow Time (Actual Time): 10 minutes + Human-Review (~60 minutes) = 70 minutes


In-Process Friction Points / Solutions

Information Consolidation: Relaying the “next steps” proposed in the newsletter workflow, I took the initiative to create a new Claude project, feed all of the AI prompts into Claude’s project instructions, upload a copy of the full post for context reference, and include the Nivationist link library Notion page as a reference link instead of pasting each prompt one at a time in Claude in the general chat.

Human Review to Reduce AI Hallucinations + Errors: Because of the screen-recording countermeasure for task-mining, the blog post has been published ahead of schedule using my previous workflow (no AI). I can then use Claude to compare the no-AI-assisted published blog post workflow vs. the Claude-assisted blog post workflow.

  1. I asked Claude to explain the differences between the human-revised blog post (I gave Claude the URL of the published blog post) and the Claude-revised blog post.
  2. Claude has trouble detecting the actual highlighted sentences (with background in #FFD37A) on the actual published blog post after matching Claude’s conclusions with my own review.
  3. I asked Claude to generate an error report, which led to the following errors in Claude’s response to my request in step a.
    • Matched sections = the same highlights that both the published blog post and the Claude-assisted blog post selected. Not used sections: the highlights that Claude suggested but were not highlighted in the published post. Human-added section: the highlights that I highlighted in my published blog post, but not recommended by Claude.
    • Claude is bad at detecting highlights in my published blog post. I found that the highlights Claude thought were highlighted insights are within a paragraph distance away from the actual highlights. Claude may be having trouble detecting the background hex code color used to identify the published highlights.

Claude provided flawed reasoning for the errors made. The root cause given by Claude for why these errors exist is also incorrect, as the published blog post is included in the initial request for a comparison report in step a.

Claude is great at refining grammar without changing the original post drastically. The Claude-assisted blog post is similar to my published blog post, with only minor word changes and sentence restructuring.

Claude’s SEO Title suggestion is too generic but SEO-safe.

[ACTION]: Claude needs to increase the number of external links. It suggested only two external links for an 18-page blog post.

[ACTION] Add a criterion to the external/internal linking AI prompt to increase the number of recommended external links.

[ACTION] Use Claude’s SEO suggestions as a starting point. I will revise it further to emphasize how my blog post compares with other blogs on a similar topic, and I will use ChatGPT to generate additional suggestions to avoid hitting the Claude free plan limit.

[ACTION] Use Claude to proofread the entire post and identify key highlights. Then, I do a final review of the suggestions before publishing the post.

This sub-step was conducted on Wednesday, May 27, 2026.

  1. Format using your Reference Card

Use the formatting rules below — you no longer need a published post open in another tab.

ElementRule
Heading hierarchyH2 for main sections, H3 for sub-points
Highlight color[ADD YOUR EXACT HEX CODE — pending screenshot of live post]
Highlighted textColored background highlight — max 1 per paragraph
Paragraph spacing[ADD: e.g. “20px bottom margin”]
Featured imageFull width, top of post, above title
Internal linksOpen in the same tab
External linksOpen in new tab
CTA at the end of the postLink to newsletter signup + 1 related post

First time using this: open a published post, fill in the [ADD] fields above, then never open a reference post again.

  • Add links

Using accepted link suggestions from Step 4, add them to the WordPress editor.

  • All internal links open in the same tab
  • All external links open in a new tab
  • Newsletter signup CTA is at the end of the post
  • Upload featured image

Generate in ChatGPT using this prompt:

AI Prompt Formula: [Task] + [Image Description] + [Brand Colors] + [Art Style Reference] + [Dos/Don’ts]

Tip: Save your image style description after your first post — copy-paste it each time so the series stays visually consistent.

  • Final pre-publish check
    • Title matches SEO title (or intentionally different for readability)
    • Meta description filled in AIOSEO
    • Slug confirmed
    • Featured image uploaded + alt text added
    • All highlights applied
    • All links checked (internal same tab, external new tab)
    • Newsletter CTA at the end
    • Category and tags set
    • Scheduled for Friday, 10:00 AM EST
    • Read the post one final time, top to bottom

[In-Process Friction Points / Solutions] Part 2: WordPress Post Formatting, Featured Image Generation, and Pre-Publish Checklist

Previous Workflow Time: 57 minutes

Claude’s Target Time: 45 minutes

Current Workflow Time (Actual Time): 52 minutes


There are no in-process friction points, as the workflow revamp suggested by Claude moves all references and, previously, a mental checklist into a consolidated location. The time improvement is small, but it frees up mental space and ensures future consistency/accuracy.

[ACTION] Full Scale Automation: This workflow is highly repetitive, has an established structure, and requires minimal human thought, which makes this process great for full automation using APIs to have the post saved as a draft in WordPress before being scheduled for publication after simple human review.

This sub-step was conducted on Wednesday, May 27, 2026.

Update your Link Library

  • Add the newly published post to the Notion Link Library internal links table
  • Note which series it belongs to and its post number
  • Add any new outbound resources used to the relevant topic section

Previous Workflow Time: N/A

Claude’s Target Time: 5 minutes

Current Workflow Time (Actual Time): 5 minutes


There are no in-process friction points, as the workflow revamp suggested by Claude is to update newly made internal links into a consolidated location for future ease of processing.

[ACTION] Full Scale Automation: This workflow is highly repetitive, has an established structure, and requires minimal human thought, which makes this process great for full automation using Zapier or Make to create a trigger/result process node or custom APIs to auto-update the links library.

Previous Workflow TimeClaude’s Target TimeCurrent Workflow Time (Actual Time)
Part 1140 minutes22 minutes70 minutes (10 minutes + human review 60 minutes)
Part 257 minutes45 minutes52 minutes
Part 3N/A5 minutes5 minutes
Total197 minutes72 minutes127 minutes

It takes 50% less time to complete Part 1 of the workflow after factoring in human review.

Due to setting up a Claude project, uploading all relevant context files, and consolidating all AI prompts into a single skill, the actual Part 1 workflow took 10 minutes, but due to the human-review time that’s needed to double-check the accuracy of the AI responses, an additional hour is added to the total time spent in Part 1.

Calculation Method (exclude human review): % Change Between Part 1 Previous Workflow Time and Part 1 Current Workflow Time (Actual): (140-10)/140 100 = 92.9%

Calculation Method (total): % Change Between Part 1 Previous Workflow Time and Part 1 Current Workflow Time (Actual): (140-70)/140 100 = 50%

It takes ~93% less time to complete Part 1 of the workflow (post editing, highlight identification, link suggestion, and SEO).

The current process reduced the gap to the ideal goal of 1 hour from 137 minutes to 67 minutes, eliminating ~51% of the original gap.

Calculation Method: Gap Difference Between the Goal time of an hour and Previous Workflow Time: (197-60=137) – Gap Difference Between Claude’s Target Time (ideal) and Current Workflow Time (Actual): (127-60=67) = 70 —> % Improvement Towards Ideal Goal (70/137) 100 = 51.1%

It takes ~36% less time to complete the blog publishing process.

Calculation Method: % Change Between Total Previous Workflow Time and Total Current Workflow Time (Actual): (197-127)/197 100 = 35.5%

The % improvement is non-applicable for parts 2-3, but is foundational for full automation.

The 3 Nivationist Principles are what turn this philosophy into what we can take action on and feel the tangible effects of our progress from the inside out, despite feeling “not enough.”

Because ultimately, the number of great solutions available to us is endless, and the person working behind the plan isn’t a stone-cold robot but a living human with real needs and deserves a plan that works with them in mind.

The essence of Nivationist is “taking care of the human in us.” Rather than separating the emotional personal growth from the outcomes we bring, we should use our human tendencies (current work habits, reflexes, etc.) revealed within the process of our work to create a well-rounded plan on what to do next.

The results of this process revamp attempt do not meet the 1-hour time limit goal. But it does improve my previous workflow time by an overall of ~36% but close to a reserved estimate of 60-70% if the human-review process is better refined and full automation is integrated for parts 2-3.

Mindset Shifts:

  • Shifts in Perfectionism: From following processes for the sake of completion to using what was learned from previous processes to improve the current approach.
  • Reimagined Perfectionism: Using the desire to improve as an iterative process and publishing case studies to report the process, regardless of whether the ideal goal was met or not. Using the results to build a better approach for the next attempt.
  • Mindset Snapshot: “The approach may not align with the original instructions, but it’s at times necessary to have messy efficiency rather than inefficient completeness.”

Next Steps:

  • Continue to iterate with AI-assisted tools to meet the 1-hour workflow completion limit consistently.
  • Continue to publish case studies to showcase results to the public, regardless of whether the ideal goal was met or not.

Work Habits / Friction Revealed:

  • I like to retain my voice and the entirety of my ideas (letting AI only change the grammar, wording, sentence structure, formatting, etc.)
  • I prefer to review the AI-generated results before publishing.

Next Steps:

[ACTION] Build a consolidated, single-truth knowledge hub on Notion. Readwise is already connected with Notion. Still needs to connect Google Keep, ChatGPT chats, and Snipd.

[ACTION] Add more criteria to the AI prompts to better align with task expectations.

  • The variety of external media suggested should also be specified (including videos, podcasts, articles, etc., rather than just a certain category of media).
  • The number of suggested external links must be proportional to the length of the blog post.
  • The suggestions for grammar, wording, sentence structure, etc. must be shown as highlighted suggestions for easier review to eliminate the time it takes to identify what was changed.

[ACTION] Automate the Google Doc draft to WordPress draft post (include formatting, brand color incorporation, custom elements, etc.), automatically update the links library, and send me a Todoist task to review the post before scheduling to publish.

[ACTION] Experiment with the Task Mining methods (Power Automate, n8n + Activity Tracker by using both video screen recording and activity data from the tracker.

[ACTION] Research tools to support my human review process and cut down workflow completion time.

N/A: This principle isn’t relevant in this case study.

Share This Post!

Leave a Reply

Your email address will not be published. Required fields are marked *

Here’s more!

Illustration of a male blogger connecting layered puzzle pieces into a unified structure, symbolizing evaluating and refining a blog purpose so ideas work together instead of competing.

Refine Your Blog Purpose: 7 Factors to Maximize Feasibility

How can you realistically blend your ideas into a single blog purpose that is clear, cohesive, and unique? Without a feasibility check, your ideas compete instead of feeding into each other, and you might abandon ideas that could’ve given you a unique edge. Refine your blog purpose with 7 factors to maximize feasibility and give your ideas a full chance.

Read More

Sign Up for the Nivationist Newsletter

As a subscriber, you have a say in how Nivationist grows and takes shape! 

Plus, get pre-release insights, behind-the-scenes builds, and proofs that it’s okay to start even if you feel “not enough.”