We talk about productivity like it’s a vibe. It isn’t. It’s a system. After watching Jeff Su lay out his “Co-work” setup, my takeaway is simple: the winners won’t be the hardest workers. The winners will be the best system builders.
As someone who helps brands create superfans, I’ve learned that consistency drives trust. Jeff’s method makes consistency repeatable. It turns personal knowledge, taste, and routines into reusable rules. That’s the point: stop starting from zero every day.
What Jeff Su Gets Right
Jeff Su, a product marketer, shows how simple files can run your life like a calm operating system. He jokes, he demos, then he drops the line that matters:
“These are just simple text files.”
That’s the magic. No mystery. Just plain files with instructions and memory, read at the start of each session. One file teaches the AI how to act. Another remembers what happened last time. He stacks rules like laws: country, then state.
“The root file is the constitution that governs the entire workspace… and individual workstations stack on top.”
He also hammers a point I wish more leaders would adopt: context is not optional. He calls it “implied context”—the stuff you know but forget to explain. Voice, goals, current projects. Bake it in once. Stop repeating yourself.
“You need to start building a system like this today.”
I agree. Not because it’s trendy, but because every session without a system is waste.
The Case for a Personal OS
Here’s the argument: You don’t have a time problem. You have a context problem. People bleed hours rebuilding instructions, retyping preferences, and rethinking patterns. Jeff’s approach turns all of that into reusable assets.
His setup doesn’t worship tools. It worships structure. The top-level file tells the assistant what to do. A memory file tracks active projects and decisions. Workstations handle areas like Email HQ or Personal Finances with their own rules and memory. No fluff.
He shows real use cases: draft a client follow-up from a meeting transcript, spin up a Notion project with the right properties, route a screenshot of a framework to the correct folder. None of it is magic. It’s instructions, written once, used many times.
Receipts That Matter
Jeff backs it up with clear moments:
- Voice profiles built from sent emails, so drafts sound like you.
- Workstations that layer rules without duplication.
- Spending trackers generated from statements, corrected once, remembered next time.
The through-line is smart constraint. Keep the root file lean. Don’t repeat rules. Choose the cheaper model unless a task truly needs more.
But Is There a Catch?
Some will say this is overkill. It isn’t. The real risk is trying to automate chaos. If your calendar is a mess and your files live everywhere, no assistant can fix that. Start with a small, clean setup. Build only what you use.
Others worry about privacy. Fair. Share only what you’re comfortable sharing. The idea works with any vendor and any tool—it’s the structure that counts.
My Playbook for Superfan-Ready Systems
If you lead a team or a brand, this is more than productivity. It’s how you scale trust. Here’s how I’d start, focused on repeatable client and fan experiences.
- Create a root “constitution” file. Define voice rules, decision rules, and where to find deeper docs.
- Spin up two workstations only: Email HQ and a single core area (sales, support, or content).
- Build a voice profile from your best messages. Lock in tone, greeting, signoff, and “never do” rules.
- Set memory prompts: active projects, current priorities, VIP clients, banned phrases.
- Run a session audit after big threads or projects to save new preferences.
The goal is consistent delivery without constant handholding.
Where I Push Further
Jeff nails system design. I’d add a fan lens. Add rules for surprise-and-delight, feedback loops, and recovery plans when things go wrong. Build playbooks right into the workstation so any draft, reply, or recap carries your brand promise.
Example starter rules you can include:
- Always restate the customer’s goal in the first line.
- Offer one proactive next step, not three.
- When we miss, own it in the subject line and say what we’ll fix by when.
That’s how systems create loyalty, not just speed.
The Bottom Line
Stop winging it. Write your rules. Save your memory. Let the machine read before it writes. You’ll ship faster, sound like yourself, and show up the same way every time.
Start with one folder, two files, and a single workstation. Protect your energy. Put your brain on the hard stuff—ideas, empathy, strategy—and let your system carry the rest.
Build your personal OS this week. Your future self—and your fans—will thank you.
