First Time Sharing This: Grab My Private AI Writing Teaching Method + 8 Prompts (+ Demo)

It’s the universal problem. EVERYONE is drowning in AI docs slop.

I’ve written guides for Excel, and for Powerpoint.

Writing a really good guide for Word (docs) was the hardest for me.

That’s because the problem is SO big. We all spend DAYS a week in docs. Reviewing them. Writing them. Editing them.

And increasingly complaining about them because they’re AI slop.

And that has real consequences—almost every business I know is having issues with employees producing AI slop that impedes business decision-making.

Let me let you in on a secret: the problem is NOT the model. I get asked that all the time. It’s not the model—it’s the organization.

Specifically, organizations relied on talented employees to maintain a document bar for hundreds of years. That’s gone now.

We don’t have a new way to maintain a document bar. And we desperately need one.

That’s why I wrote this. To solve the biggest AI problem in business: how to scale good business writing.

After hundreds of hours teaching business writing and seeing what works and what doesn’t, I’m sharing a full writing kit for AI here. It’s not just for Word. It’s for Google Docs. For Slack. For anywhere you have a need for less AI slop and more business writing.

Here’s what you get:

• The nine principles of business writing with AI that eliminate slop

  • Every Document Exists to Change Someone’s Mind or Behavior

  • Structure Is a Forcing Function for Thought

  • Constraints Do More Work Than Instructions

  • Quality Scales Through Self-Evaluation, Not Human Review

  • Failure Modes Are More Predictable Than Success

  • You Can’t Prompt Your Way Around Bad Inputs

  • Every Organization’s Documents Sound the Same Unless You Fight It

  • Iteration Is About Diagnosis, Not Polishing

  • Documents Don’t Exist in Isolation—They Exist in Workflows

• Eight production-ready prompts built on these principles, plus a quality evaluator skill for Claude (or ChatGPT)

  • Meeting Notes (from transcript or raw notes)

  • Status Report (weekly/monthly updates)

  • Executive Brief (decision memo)

  • Project Proposal (resource allocation request)

  • PRD (Product Requirements Document)

  • Technical Documentation (user guide / how-to)

  • Post-Mortem / Incident Report

  • SOP / Process Document (standard operating procedure)

  • Business Evaluation Claude Skill (document quality evaluator you can run automatically—also works in ChatGPT)

• A video walking through exactly why generic prompts fail and how these principles fix the core problems—plus a demo of how you can modify these prompts for your business

• A framework for customizing these prompts to your organization’s standards, voice, and decision-making processes

• Real examples showing the difference between AI slop and documents that actually help teams execute

• And yes, a special note on how to adapt prompts and strategy for Microsoft Copilot (check out my full Copilot guide here)

This isn’t about finding better AI tools. Every company I work with already has access to models that can write production-quality docs. The problem is they don’t know how to prompt for it, and they don’t know how to scale quality evaluation across their teams.

If your organization is producing AI documents faster than you can evaluate them, if you’re drowning in meeting notes that capture nothing actionable, if your teams are converging on that bland default AI voice—this is the methodology that fixes it.

This is how you teach AI to write like your business actually thinks.

Let’s write better.