About

Why this site exists, who it's for, and how to read it.

What this is

The Executive OS is a media site about externalizing your work intelligence with AI. The thesis is simple: most of what executives do every day — remembering context, deciding tradeoffs, drafting communication, structuring decisions — can be offloaded to AI, but only if you build the right system around it.

This is a site for people who want to do that without writing code. Most "AI for productivity" content is written by engineers, for engineers. We're filling the other side — people who lead businesses, run sales operations, advise companies, or build solo. The audience is non-technical operators who care about leverage, not implementation details.

Who writes this

I'm Fukken. Two decades operating in enterprise IT, the last several years building AI workflows that run alongside the day job. I'm not an engineer — I read code, but I don't write production software. That's the constraint that shapes everything published here: every workflow on this site has to work without an engineering team behind it.

I run a parallel Japanese-language site, FukkenLab, where the same experiments are documented in Japanese. The Executive OS is not a translation — it's a separate brand for an English-speaking audience, with content adapted to a different cultural and business context.

How this site is organized

Four sections, each with a specific job:

  • Workflow OS — Long-form pieces about the architecture of an AI-driven personal operating system. The why and the how, at a system level.
  • Stack — Tool reviews. What we use, what we tried and dropped, and what we'd recommend to a friend running a similar business.
  • Playbooks — Reusable templates, SOPs, and prompt packs. Ready to drop into your own work.
  • Field Notes — Shorter pieces. Single experiments, mistakes, in-between observations.

The newsletter pulls the best of all four into your inbox, weekly.

Editorial standards

Every published piece comes from real use, not theory. If we recommend a tool, we've used it for at least a month in actual operations. If we publish a workflow, we run it ourselves. We document failures with the same rigor as wins, because the failures are what tell you whether something is real.

Some links on this site are affiliate links. We disclose this on every article, and we only link to tools we'd recommend to someone we know personally. We never accept payment to cover a tool, and we never publish reviews we haven't lived with.

Get in touch

The fastest way to reach me is the contact form. The newsletter (launching shortly) will be the best way to follow along — sign up notice will appear on the homepage when it goes live.