カテゴリ 古民家暮らしモカとの記録セキュリティの記録副業の記録

The record with MokaNovember 18, 2026

The First Role to Add Is a Researcher — The Morning My AI Assistant Got Faster

The First Role to Add Is a Researcher — The Morning My AI Assistant Got Faster

The result, first

This morning I reorganized the team that works around Moka, my AI assistant (Muse). By the afternoon of the same day, the replies to my requests were visibly faster.

My own words, as they came out: “Your replies got faster.” “That is quite fast.” And then, without thinking: “This is another great discovery.”

What changed was not effort, and not headcount for its own sake. Two bottlenecks were removed. Here is what I did, and why it worked.

What I changed this morning

First, I created a headquarters for all the blog work. Twenty departments — the makers, the language teams, and the people who run each site — now sit under one “Blog Headquarters.” It has three leaders instead of one, a checking team of seven inside it, a copywriting team of seven, and an images team of three. (The setup itself is recorded in a separate article.)

Second, I grew the research desk of Sebastian, my vice-butler, from one seat to three, split by subject:

Checking was split into two lines as well, and I added a new “progress” role whose job is to move work that is waiting, not just record it.

Third, I gave the research desk one rule: before researching anything, check whether we already have that knowledge in the house. If we have it, do not research it again. Collect only what is missing. The check goes list first, then summary, then the full text — the same three steps we use for everything.

I also gave the role-holders knowledge

A role is a name tag. A name tag alone does not do the work; the knowledge inside it does. Moka and Sebastian were both given a butler’s knowledge base to work from. The people in charge of each department needed the same.

So this morning we reviewed what each leader needs to know, and shared it: 26 places across the departments, plus the three new research seats — 29 in total.

Why it got faster

The reason was not the number of people. It was that two narrow entrances were widened.

Before today, research had one entrance. I ask about all sorts of things — departments, systems, the world — and every question queued at the same door. Checking was the same: everything passed through one point at the end.

This morning, research and checking were split so they can run side by side. The one door I kept single is the deciding door: publishing and other outward decisions still come to me alone.

It is like a shop with one cash register and a long line. Adding more shop staff does not move the line. Adding a register does. This morning’s reorganization was the register.

The takeaway

If you bring in Muse, add a researcher first — before the roles that make things.

When the research entrance is fixed, each new question starts by checking what is already on hand, instead of starting from zero. Making and checking then line up behind it and move in parallel.

The numbers are still being prepared

Honestly: I do not yet have figures for how much faster it became.

This morning we prepared the way to measure it — four rulers: from handing over material to a finished draft; from draft to publication, with my approval time counted separately; how many articles finish per day; and how long the language versions take to line up. Moka will keep the record from here, and I will add the numbers to this article when there are enough of them. I will not write “several times faster” on a feeling alone.

Record of this article

Record of this article
  • November 18, 2026 ― Draft created (ledger No.179). English version written results-first, from the same morning's record as the Japanese version No.178(3,416 characters)
  • November 18, 2026 ― Published with the user's approval (all five confirmation points answered OK; Japanese and English published together)(3,416 characters)

#AI #Muse #Moka #Organization #Beginner

← Back to the article list / ← Back to the English top page