Why I Picked Up a CAD Mouse

The assignment was simple. We needed parts manuals.

What I got was a hard drive. Two hundred and fifty gigabytes of it. CAD files, exports, scanned blueprints, supplier PDFs, vendor catalogs, photos of whiteboards, photos of photos, files named Final_v2, Final_v2_REAL, Final_v2_USE_THIS_ONE. Years of work, dumped onto a single drive with no map, no index, no naming standard, no source of truth. Just artifacts.

I had never opened a CAD file in my life.

But we needed parts manuals. So I picked up a CAD mouse and started clicking.

---

What I Actually Did for Months

I sorted. I opened files. I tried to figure out what a part was, what was a revision of a part, what was a one-off prototype, what was the current version of any of it. I built folders. I built naming conventions in my head and then on paper and then in the folders. I taught myself enough CAD to open the files, take views, and screenshot what I needed.

I was building a manual by archaeology. Digging through layers of artifacts to figure out what the company actually made.

And it worked, eventually. Manuals got built. People used them. Nobody asked how the sausage was made.

---

The Frame on the Shop Floor

A few weeks in, I had a working theory of the product. A catalog forming in my head — this part goes with that one, this revision supersedes that one, this assembly belongs on this model.

So I went and pulled a mower frame off the line, rolled it onto the shop floor outside my office, and started checking my theory against the actual thing we were shipping.

The drive said one thing. The mower said another.

Not catastrophically — a fastener here, a bracket version there, a routing detail that didn't match. But enough to be sure of one thing: the files I was working from couldn't be trusted as the source of truth. The product was the source of truth. The hard drive was a record of what people had drawn at various points along the way. The mower was what the company actually built.

That's when the feeling clicked. I'd been doing the work in the wrong order. Parts manuals weren't supposed to be reverse-engineered from a hard drive and a physical unit on the floor. They were supposed to be the natural end of something the company already had, and we didn't have it.

I couldn't have explained it that cleanly at the time. But the suspicion was set. The CAD mouse made it worse, not better — the deeper I got into the files, the clearer it became: the manual was a finished output. It was supposed to fall out the end of a working setup. I was the working setup. I was a person doing the job of infrastructure that didn't exist.

Knowing it was backwards didn't help. I still had a deadline. I still had to ship the manuals.

What it did do — and this is what mattered later — is plant a suspicion I'd carry into every job after.

---

What It Shaped, Quietly

I started noticing the same shape everywhere I went, in every building I worked in after.

Somebody manually pulling reports because the system couldn't generate them. Somebody re-keying customer data because nobody knew where the answer lived. Somebody making a deck from scratch every quarter because the data didn't roll up anywhere.

Every one of those was a person producing a finished output by hand because the company didn't have anything underneath that could produce it in context. Same shape as my hard drive. Different room.

The chaos isn't the problem. The chaos is the symptom. The problem is that the thing underneath — the system that should be generating the order — doesn't exist.

Once you can see that, you can't unsee it.

---

Why This Matters Now

I walk into manufacturers today and I see it in the first hour.

Engineering departments running on heroics because nobody upstream knows what's real. Quote builders held together by one person's spreadsheet. Customer information living in three CRMs, four email accounts, and one guy's head. Reports getting built manually every week because nothing aggregates the underlying data.

And look — this is how most businesses work. Gaps don't get noticed until somebody trips over them. Then someone gets handed the gap and told to fix it, and they do, and the fix becomes the job, and the underlying absence never gets addressed because the fix is now load-bearing. That hard drive job was a gap that got exposed. The fix was me. I just happened to be a kid who'd remember the shape of it for the next twenty years.

It's not laziness. It's not bad people. It's an absence — the system that should be there and isn't. Everyone's working around the gap, and most of them don't even know it's a gap.

That's why I started Kre8ive Studio. Most of what I do for clients now is name what's missing, then build it.

The 250-gig hard drive — and the mower frame on the shop floor that argued with it — was where that muscle started. I just didn't know it was a muscle yet. I thought I was figuring out CAD.

---

If I'd Had AI…

Today I could throw that 250-gig drive at a few well-built tools and get a draft inventory of every file, every part number variant, every revision conflict in an afternoon. The labor would compress from months to hours.

But here's the part that matters: the AI does the labor. It doesn't do the noticing. It would happily produce a beautifully organized set of parts manuals on top of the same missing system, and we'd be right back where we started six months later.

And it still wouldn't know the mower frame on the shop floor disagreed with the file.

The diagnostic — what should be generating this, and why doesn't it exist? — is still human work. That's the muscle. AI just makes the muscle ten times more useful once you have it.

---

The Question

What's the report, the spreadsheet, the deck, the manual in your shop that somebody is producing by hand every week — that should be falling out of a system you don't have yet?

That's where I'd start.

---