Why I’m simplifying my AI workflow

Sepia engraving of a man in a baseball cap relaxing at a desk with a blank notebook and WordPress coffee mug as elaborate machinery fades into the background.

I’m starting to “un-ui” my daily work. I spun my wheels multiple times trying to build a sophisticated dashboard. The flashy pictures of people creating these work stations and hubs to display and track all of their work was so attractive.

Maybe I was getting too clever and trying to do too much. Specifically, I was really pushing to see what I could do with WordPress as this OS layer for all of my work and connecting AI. I might have gotten a little too clever sometimes even.

I actually built something really cool, and I do like it. I even figured out with AI how to build an in-place editing experience with Gutenberg that saves directly back to the markdown files on my laptop. Heck, I made a task manager, all in WordPress, and I have designs for an interactive graph. My goal was to make Obsidian and Notion with WordPress Studio. It worked, and I have a memory layer and LLM wiki that is growing.

It’s all in the background now. I don’t do any daily work in that system. Why do I even need to? The more intricate I started to make the OS and ui, the more I have started reverting back to low-fi task management and work. Everything is getting tracked, saved, and updated all in that background layer, but I’m literally spending my days chatting and checking items off in a Claude Doc (you can do it with GPT’s pages too).

My ui is starting to disappear. I am inside of the Claude and GPT desktop apps, so there is that harness I’m working within, but that’s a bit different. My actual work is just happening in conversations.

This process might evolve again. I’m sure it will. In fact, that’s actually exciting to me. The fun part is testing and iterating on processes. The outcome is better workflows for me no matter what.

All this is to say, you don’t need to have an overhyped, flashy Jarvis or command center, unless you want it.

Do what works for you. All the power is at our fingertips to create anything that helps us individually. Share it with others, but go make something cool, for yourself.


One response

  1. John Smith Avatar
    John Smith

    This matches what I’ve seen: the memory layer and saved markdown keep their value, while the dashboard on top gets used less over time. Keeping everything tracked in the background and doing the actual work in conversation seems like a sensible split. The Gutenberg editor that writes back to local markdown sounds like a nice build, even if it isn’t your daily tool.

Leave a Reply

Your email address will not be published. Required fields are marked *

Your post must include a link to this post.

How does this work?
Write a response on your own website and include a link to this post. Then submit your response’s URL here. Your response may appear here after moderation. To update or remove it, edit or delete your original post and submit the same URL again. Learn more about Webmentions.