Welcome back to The Missing Manual with your hosts, Julia Levy and Jenny Cotie Kangas (JCK). In this episode, we are right in the middle of a multi-part series detailing the real, unvarnished work it takes to build a content engine and operationalize AI for daily work.

Too often, people get frustrated with AI because they expect it to read their minds. Today, we demonstrate a core truth: you cannot automate what you cannot see. We share our personal back-and-forth building a comprehensive Markdown instructions file for our Claude Projects. We discuss the transition from tactical execution (acting as a production assistant) to strategic advisory (acting as an operational Chief of Staff).

Whether you are looking to scale an internal talent function, smooth out cross-functional handoffs, clean up your Canva asset pipelines, or just fix your messy workflows, this episode provides a strategy-first framework for learning out loud.

Inside the Episode:

• The Split Path: How we navigated different ideas for our next steps by letting AI evaluate the best operational path forward.

• The Dual-Mode Prompt: Designing system instructions that govern both administrative task delivery and high-level decision tracking.

• The Crucial Prerequisite: Spotting gaps in your operational process (like missing template locks) before pushing a workflow live.

• The Handoff Habit: Why generating a clean handoff document at every natural pause is the secret weapon to preventing context drift and saving your sanity.

Don't forget to look out for our upcoming episodes where we operationalize this live and push our first episodes through the new engine to see where it breaks—and how we fix it.

If you enjoyed this strategy-first look into practical AI application, please remember to like, subscribe, and share this episode with someone trying to streamline their daily operations!

Documenting the Mess Before You Automate

"Automating a broken process just breaks things faster."

In this episode of The Missing Manual, JCK and Julia take you behind the scenes of their own operational chaos. This is part 3 of our ongoing series on operationalizing AI for a specific, real-world use case: running this exact podcast.

Julia does a complete verbal download of the current, highly manual production workflow, from editing in Riverside and wrestling with inconsistent thumbnail creation in Canva/Google, to manual file renaming on her Mac downloads folder and navigating the LinkedIn algorithm.

Before touching a single automation line, the team uses Claude to map out the current state. JCK steps onto her soapbox to explain why HR, TA, and business leaders must document every shadow process and departmental variation before trying to automate. If you don't map the friction, you simply bake the friction directly into your AI system.

Tune in to hear: • The critical difference between automating a process and optimizing it first. • How to use your least favorite manual tasks as a bullseye for AI opportunities. • The debate: Do you fix the gaps before you write the project instructions, or solve them inside the system?

Stay tuned for the next episode as we dive into defining the rules of the road and building out the actual project instructions!

Two Brand Voices, One Show: How We Train AI to Speak for Both of Us

When two distinct creators collaborate, how do you ensure the content speaks with a unified voice—without losing the hard-earned, earned beliefs of either host?

In this episode of The Missing Manual, Julia Levy and Jenny Cotie Kangas dive deep into the mechanics of operationalizing their show using AI. This isn't about quick hacks or shortcuts; it's a strategic, behind-the-scenes look at how to merge individual "Brand Voice Bibles" into a singular, cohesive AI grounding document.

Tune in as we discuss how we are training our AI to step into the role of our virtual Production Assistant and Chief of Staff. You’ll learn how to establish unified guardrails (like our shared, yet distinct, hatred of the em-dash), how to handle stylistic friction, and why the secret to scaling your workflow lies in defining a clear "blueprint for good."

Key Takeaways for Your Work:

• Don't get stuck on the tool: The foundational strategy applies whether you are using Claude Projects, Gemini Gems, or Custom GPTs.

• Why your AI needs to know what "bad" looks like just as much as it knows what "good" looks like.

• The workflow pipeline: How to collaborate with the tool to get a draft 85% of the way there, and how to feed your final 100% version back in to train it for the future.

Have you built a grounding document for your own business operations yet? Let us know your thoughts on LinkedIn at The Missing Manual page!