How to Map a Process Before You Write the Procedure
A procedure written from memory records what people believe happens. A process map records what does, and the handoffs it exposes are where the savings are found.
Read
Blog
Field notes from the desk.
Writing, ghostwriting, editing, and what I'm learning along the way.
When a Checklist Beats a Procedure
A checklist protects trained people from skipping steps in familiar work; a procedure teaches the work. Here is how to tell which one your floor needs and how to write a list people use.
ReadDocumentation for Small Manufacturers Without a Quality Department
A small shop doesn't need a quality department's paperwork, only five controlled documents that one busy person can keep true.
ReadWhat to Do With 200 Outdated SOPs
Sort outdated procedures into retire, rewrite, and leave-alone piles by risk before you write anything, and most of a two-hundred-document backlog shrinks to a short first batch.
ReadWill SOP Software Fix Your Documentation Problem?
SOP software solves storage and version control, and it writes nothing, so the useful question is whether your documents are unreliable or merely scattered before you buy.
ReadHow to Write Safety Procedures People Follow When Nobody Is Watching
Safety procedures fail when they're written for the auditor instead of the operator, so this covers placement, step wording, and how to test a procedure on the real machine.
ReadTraining Materials vs. SOPs: Why One Document Can't Do Both
Merging a training document and an SOP into one file produces something too thin to teach a new hire and too padded to serve as a fast reference once they know the job, and splitting the two is usually a sorting exercise, not a rewrite.
ReadHow to Write Work Instructions for the Floor, Not the Office
A work instruction covers one task at one station on one page, written at about an eighth-grade level and mounted within arm's reach of the work, because the most common reason good documentation fails on a factory floor is placement rather than writing.
ReadDocument Control Without Buying Software
Document control needs four things regardless of budget: a version number that changes with every revision, a named owner, a printed effective date, and one official location everyone checks before trusting a copy; most small manufacturers can run that on a shared drive and a changelog.
ReadHow to Write a Quality Manual That Isn't a Copy of the Standard
ISO 9001:2015 no longer requires a quality manual, and most of the ones still being written restate the clauses instead of describing the company; a useful manual is fifteen to twenty-five pages built around a process map, an ownership table, and honest exclusions.
ReadWhat ISO 9001 Actually Requires You to Document
ISO 9001:2015 requires a short list of maintained documents and roughly twenty records, most of which a working company already produces; the forty-procedure binder is sold, not required.
ReadThe Cognitive Science of Clear Documentation
Documentation that reads well in a review fails at the machine, and working memory research explains why: the person following a procedure is spending the same attention the sentence is taking.
ReadHow to Write Equipment and Product Manuals People Don't Ignore
Most manuals fail because they're written to be complete instead of usable, and the fix is to organize them around the task in front of the reader rather than the structure of the product.
ReadWhat Is Process Design, and How Is It Different From Writing It Down?
Documenting a process records what happens today. Designing it decides what should happen, and the two belong in the same project.
ReadHow to Capture Institutional Knowledge Before It Walks Out the Door
How to get what your most experienced people know onto paper before a retirement, a resignation, or a medical leave takes it out the door.
ReadWhy Onboarding Time Never Goes Down, and How Documentation Fixes It
Why new hires take as long to get productive as they did five years ago, and which documents actually move the number.
ReadHow to Build a Knowledge Base Your Team Will Actually Read
How to build an internal knowledge base people actually use: what to write first, how to organize it around the reader's task, who owns it, and why most go stale within a year.
ReadWill Your SOPs Hold Up to an Audit?
What an auditor is actually checking when they ask for your procedures, and how to write SOPs that pass on the first read instead of triggering a scramble.
ReadHow to Document a Process Before You Write It Down
The step most documentation projects skip is looking at the process first, where it breaks, where it repeats itself, and where a step survives only because it always has.
ReadWhat Goes in an Employee Handbook (and What Doesn't)
The difference between a handbook that protects you and one that collects dust: what belongs in it, what belongs in policy, and how to structure both.
ReadHow to Write an Operations Manual People Actually Use
How to organize an operations manual so a reader finds the one thing they need without reading the other forty pages.
ReadWhy Your Best Employee Writes the Worst Documentation
The person who understands a process best usually explains it worst, and the reason is cognitive rather than personal.
ReadFamous Books That Were Secretly Ghostwritten (Part 1)
A look at the well-documented cases of ghostwriting hiding behind famous names, from Alexandre Dumas's collaborator to JFK's Pulitzer-winning book.
ReadWhen Should You Hire a Technical Writer Instead of Doing It Yourself?
The honest arithmetic on your hours against a writer's, and the signals that quietly tell you writing your own documentation has stopped working.
ReadHow Much Does It Cost to Document Your Processes?
Honest market ranges for SOPs, operations manuals, and full documentation systems, plus the cost of the questions, errors, and training time that undocumented process quietly charges you.
ReadSOPs vs. Work Instructions vs. Policies: What's the Difference?
A breakdown of how policies, SOPs, and work instructions differ, and how to tell which one a piece of documentation should actually be.
ReadHow to Write an SOP a New Hire Can Actually Follow
A step-by-step method for writing procedures a new person can follow alone, from someone who wrote them on a manufacturing floor before writing them for clients.
ReadWhat Is a Standard Operating Procedure, and Why Do Most SOPs Fail?
What a standard operating procedure actually is, why most of them end up in a binder no one opens, and what it costs when the person doing the work cannot follow the page.
ReadAI-Generated Writing, Humanizers, and AI Detectors: How They're Reshaping the Rules for Publishers, Schools, and Platforms
What counts as AI-generated writing, why humanizer tools mostly fail, how unreliable AI detectors really are, what Amazon's KDP disclosure policy requires, and what to do if your work gets flagged.
ReadKeeping Your Book Confidential When You Use a Ghostwriter
How confidentiality works when you hire a ghostwriter — NDAs, credit, ownership, and how your private material is protected from first interview to finished book.
ReadWhat to Ask Before You Hire a Book Editor
The questions to ask a prospective book editor about editing level, experience, process, cost, and deliverables so you hire the right partner for your manuscript.
ReadSelf-Publishing vs. Traditional: Which Is Right for Your Book?
An honest comparison of self-publishing and traditional publishing: what each path offers, what each costs you, and how to choose based on the job your book is doing.
ReadHow to Write a Business Book That Generates Leads
How a business book actually produces leads, what separates the books that work from the ones that only look impressive, and whether to write it yourself or with a ghostwriter.
ReadSEO Content That Doesn't Read Like SEO Content
Why most SEO content reads like a machine wrote it, and how to write pages that get found without ever sounding optimized.
ReadWhat Is Content Strategy and Does Your Brand Actually Need One?
What content strategy actually is, how it differs from simply making content, and how to tell whether your brand needs one or only thinks it should.
ReadDo You Need an Editor or a Ghostwriter? How to Tell
How to tell whether your book needs an editor or a ghostwriter, how the two differ in cost and process, and how to choose with confidence.
ReadMemoir Ghostwriting: Turning Your Life Into a Book
What memoir ghostwriting actually involves, from the interview process to who owns the story, and how a ghostwriter turns a life into a book told in your own voice.
ReadHow Long Does It Take to Write a Book?
A realistic look at how long a book actually takes to write, from business books to memoirs, and why working with a ghostwriter usually shortens the timeline.
ReadHow Much Does It Cost to Hire a Ghostwriter in 2026?
Honest market ranges for 2026, what actually drives the price, and how to read a ghostwriting quote without guessing.
ReadWhat Is a Ghostwriter, Exactly? (And What They Don't Do)
What a ghostwriter actually does, where the material comes from, who owns the book, and the things no honest ghostwriter will ever promise.
ReadHow to Hire the Right Ghostwriter: A Buyer's Checklist
A practical buyer's checklist for choosing a ghostwriter you can trust with your voice, your name, and your book.
ReadGhostwriter vs. AI: What Actually Happens to Your Book
AI can draft fast. Whether it can write the book with your name on it is a different question entirely.
ReadDevelopmental Editing vs. Line Editing vs. Copyediting: Which Do You Need?
Three kinds of editing, three different jobs. Here is what each one does, the order they happen in, and how to tell which your draft actually needs.
ReadHow Business Owners Write Books Without Writing Them
Surprisingly few business books are written by their authors at the keyboard. Here's how busy founders get a real book done, without becoming writers.
Read"Sometimes the fluffy bunny of incredulity zooms round the bend so rapidly that the greyhound of language is left, agog, in the starting cage."David Mitchell