Turns out, enterprise asset management is a real page-turner — if you know where the story is. IBM needed a writer who could take subjects most people actively avoid (maintenance software, ISO compliance, IT asset recovery) and make them readable enough to hold a plant manager's attention and rigorous enough to survive a fact-check from the engineer standing behind him.
I wrote pieces, one beat, built to rank, built to hold up under scrutiny, and built to not read like a glossary entry. Here are some of the high.
IBM Think —Enterprise content
Agency/Client
IBM
Work
B2B Thought leadership content
Role
Author
This is the piece I'm proudest of on the maintenance beat. Prescriptive maintenance is the industry's next step past predictive — not just "this will fail" but "here's exactly what to do about it" — and almost nobody outside the field can explain the difference.
I mapped the five-phase process end to end and grounded every claim in numbers I fact-checked back to their original source, not just whatever a vendor blog was recycling. The result reads less like a glossary entry and more like a case for why bad data quietly kills good AI investments.
This is the piece I'm proudest of on the maintenance beat. Prescriptive maintenance is the industry's next step past predictive — not just "this will fail" but "here's exactly what to do about it" — and almost nobody outside the field can explain the difference.
I mapped the five-phase process end to end and grounded every claim in numbers I fact-checked back to their original source, not just whatever a vendor blog was recycling. The result reads less like a glossary entry and more like a case for why bad data quietly kills good AI investments.
IBM needed a foundational explainer on computerized maintenance management systems that could rank on Google, hold the attention of a plant manager who's never heard the acronym, and still satisfy an engineer who's run one for fifteen years.
So I built it in layers — plain-English definition up top, real industry use cases (manufacturing, healthcare, government) further down — and let the reader choose how deep to go. It's since become one of IBM's most durable asset-management pages, updated and re-ranking years after publish.
Everyone confuses predictive maintenance with the preventive kind, and vendors are happy to let them. My job was to draw the line clearly enough that a reader could tell the difference in one paragraph, then make the case for why it matters — down to the five specific ways technicians actually detect a problem (vibration, oil, thermal, acoustic, motor current) before it becomes a shutdown.
Heavy on research, sourced against industry cost data I chased down and verified myself rather than recycling secondhand stats.
Decommissioning is the part of the asset lifecycle nobody thinks about until a laptop full of sensitive data turns up in a landfill or a lawsuit. The closest normal people ever get to it is the printer/baseball-bat scene from Office Space… But I don’t write for normal people.
I mapped the full seven-step process — identification through certification, including chain of custody, data sanitization and physical destruction. All the boring stuff that unfortunately can get you sued if you half-ass it. I worked until the piece made the reader feel like they were standing in the room where the shredding was happening. For better or worse.