Case Study 03 · Technical Content Publishing at Scale

Content programs for engineers

Engineers are the hardest audience I’ve worked for. They check every spec, and they leave the moment a piece wastes their time. At EETech, a B2B electronics and automation publisher, I lead the video and written teams that make content for them, every week, for the brands they buy from.

Role
Director of Content and Video
Audience
Design and controls engineers
Formats
Video series, product video, whitepapers, articles, webinars
Team
10 staff, plus a 20-plus bench
Since
October 2022
80%
Video revenue growth in two years
88%
Of revenue from repeat clients
120,000
Hours watched, two shows and live webinars
~200
Weekly show episodes since 2023
200+
DigiKey product videos a year, and growing
40+
Enterprise accounts

MediaTek: one data center story, told in every format

MediaTek was moving into AI data centers and needed engineers to take it seriously every month, not once. So instead of a list of one-off pieces, I built one connected, year-long program with my team: executive-bylined Tek Talk blogs, whitepapers that carry the technical depth, a hosted data center video series, and 25-plus keynote videos localized in a single month.

The rule that holds it together is simple. Each blog topic becomes the outline for a video episode, and every piece points to the next one. The result is live on MediaTek’s own data center page, where the hero video and the articles sit side by side.

MediaTek data center page
mediatek.com/products/data-center · produced for MediaTek

My role: I ran the program. My team produced the video and the articles, which carry MediaTek’s own bylines.

DigiKey: a program a global distributor trusts

The Product Information Overview line started as a template pitch and four trial videos in early 2024. I scoped it, priced it and built it. The hard part was never the video. It was building a way of working that two companies, and every supplier in the program, could trust.

That trust compounded. Weekly check-ins became monthly, and by year three DigiKey handed script and video review over to my team. The line now runs 13 to 18 videos a month against an original plan of 10, and about a third of viewers in the 2026 campaigns watched to the end. Production is now largely automated: a product page goes in, a client-ready video comes out, and a person still signs off on every one before it publishes.

DigiKey Product Information Overview library
DigiKey’s Product Information Overview library

My role: Scoped and launched the program. I run production, cadence and the client relationship.

The shows: a weekly habit for engineers

Automator’s Edge on Control.com and AAC Spotlight on All About Circuits cover robotics, automation and new hardware. They’re written by editors, shot in our studio and published every week. Together that’s about 200 episodes, 4.7 million views delivered for the sponsor, about 6,500 new subscribers and 114,000 hours watched. Automator’s Edge holds about 22,000 views an episode even without paid promotion.

A weekly show only works if it shows up every week. These have, as sponsored content, for close to three years.
Automator's Edge episode thumbnail
Automator’s Edge, “Can Drones Save Civilization?”

My role: Producer. My team makes them every week.

Writing and demos engineers actually finish

In a typical year my team publishes about 55 blogs, 30 whitepapers and 24 technical articles under client bylines, on the clients’ own sites and on All About Circuits and Control.com. Every piece opens on the engineer’s real design problem, every spec is checked against the datasheet, and the client’s engineers approve it before it goes live.

Inductive Automation article on Control.com
Control.com · Inductive Automation series, part 1

My role: I ran each from brief to publish, and shot and produced the SICK and TestEquity video.

What This Demonstrates

A content program for engineers is a publishing business in miniature: a format, a cadence, a quality bar and a client who comes back. The film work taught me the bar. Running these programs taught me how to hold it at scale, with machines doing the repetitive part and people owning every claim.

← All case studies