For a long time, I told myself I was done with building and navigating entrepreneurship. I took a long break.

Years of relaxation, and I genuinely believed I was pivoting toward a quieter path as a content creator. Write, record, publish. Keep it simple. I was comfortable with that.

Then the itch came back.

It started with a note-taking app for language learners that didn’t go anywhere. (Because I started learning Mandarin) 

But failure has a way of pointing you somewhere better, and that experiment eventually led to Ryoka: a permanent capital company I now run as the umbrella for everything I build.

When I shipped my first real product with Claude AI and felt what it was like to be back, the comfortable path stopped making sense.

That was April 2026. Since then, the content creator has quietly become something harder to explain with a single label.

Why the Routine Had to Change

Before April, my days were loose. Write some content, record bedtime stories, experiment when the mood hit. It worked fine for what it was.

But when your output changes, your structure has to follow. You can’t run a software portfolio, a content operation, and a podcast on whatever’s left over after lunch. I learned that quickly.

What surprised me, though, was how much I could do without burning out. Not because I work longer hours, but because I’ve removed almost all the friction. B

Building my own Ryoka OS dashboard centralized everything. No tab chaos. No context switching between five different tools. One place for the whole workflow.

The lesson I keep coming back to is that most people don’t fail because they lack discipline. They fail because they make their routine unsustainable from day one.

They overload the schedule, skip recovery time, and optimize for looking busy rather than actually moving things forward. I’ve been there.

Now I plan a few short wins and one or two longer ones each day, and I stop. That’s it.

The New Routine

My sleep cycle was a mess for a while. That’s mostly fixed now. I’m consistently waking up at 4:30–5 AM, which has become the foundation everything else sits on.

5:00 AM — Wake up, coffee, ease in.

5:30–5:45 AM — Task planning. Not a long session. Just absorbing what the day needs from me.

6:00–7:30 AM — Writing. Blog content first, always. I noticed a long time ago that my writing gets worse as the day goes on, so I protect the morning for it.

7:30–8:30 AM — Breakfast and a proper break. I take my time here. This isn’t wasted time for me. It’s the reset between the two most demanding parts of the day.

8:30–9:30 AM — Recording. Either a bedtime story episode, a Study Brew episode, or an entry for my personal journal podcast.

10:00 AM – Lunch — Building. Improving existing projects, working through recaps I keep with Claude per project, picking up exactly where I left off.

After lunch, the structure loosens.

I research, write more if something’s there, organize, experiment in Claude, or keep pushing on whatever project needs it. It’s not unstructured. It just doesn’t need to be scheduled the same way. The heavy lifting is already done.

With this rhythm, I’m running at four to five hours of focused output a day, and it doesn’t feel like effort. It feels like cruising.

Digital Minimalism Did a Lot of the Work

Years ago I got deep into digital minimalism. The idea is that your tools should serve a specific purpose, and everything else is noise.

I stripped back my iPhone, iPad, and Mac to only what I use. No notification creep. No app clutter. 

No software I’m not actively choosing to have. (I really have less than 20 apps on my iPhone)

It sounds trivial until you realize how much low-grade friction those things create. When your environment is clean, your thinking gets cleaner too. I’ll expand on this properly in a future post, because it deserves its own space.

A few other things that helped, without overcomplicating it: eating well, drinking more water, and making actual attempts to move my body. Running mostly.

Nothing extreme. But the output difference when I’m physically consistent versus when I’m not is noticeable enough that I can’t ignore it anymore.

The Longer View

I don’t think I need to scale this dramatically for it to work. The workflow is built for the long run. A decade, maybe more. If the load ever gets genuinely unsustainable, I’ll bring in outside help.

But the goal has always been a system I can maintain without needing to extract maximum effort every day.

Sustainable beats ambitious, almost every time.