Genba First AI Weekly Report | WK23 | Thinking about the meaning of receiving 'small voices' while writing a novel

This week, I spent more time writing a novel than on the actual development of the Genba First AI app.

At first glance, this might seem a bit removed from site improvement or AI utilization.

However, what I felt while actually writing was quite the opposite.

Writing a novel is also the work of picking up the 'things that couldn't be said' within people.

The discomfort that couldn't be put into words. The dissatisfaction that was swallowed at the time. The regrets that couldn't be told to anyone. The things that one actually wanted help with but couldn't voice.

I am gradually giving shape to such things within the story.

While doing that work this week, I was thinking again about the meaning of creating a 'box to receive small voices'.

Previously, I created a box to collect the 'small voices' of people working in the community.

It is not a large consultation desk or a formal proposal document, but a small entrance to receive voices before they become words, at a stage even earlier than that.

On the front lines, even if there are people in trouble, it does not necessarily mean they can raise their voices immediately.

'Is it okay to say something like this?' 'Maybe I'm the only one who cares.' 'Maybe it won't change anyway.'

While thinking such things, voices often remain unsaid, and only fatigue accumulates.

That is precisely why I believe that before suddenly creating a large system, we first need a place where things can be put into words in a small way.

While writing the novel this week, that thought became even stronger.

When people talk about AI utilization, it tends to inevitably become a conversation about efficiency and automation.

Of course, that is also important.

But what I want to do with Genba First AI is not just to speed up work.

It is to make the small discomforts and troubles that people are carrying visible, even if only a little.

It is to make it possible to receive voices that are easily overlooked on the front lines as a system.

And, it is to connect them to the next improvement or proposal without ending it at just collecting voices.

As small tools for that purpose, I use Google Forms, spreadsheets, Apps Script, and small web apps.

Not large-scale DX, but tools to make current problems a little easier to handle.

I call this 'instant operational improvement'.

This week, there might have been little visible progress on the apps.

However, while writing my novel, it was a week where I rethought 'why it is necessary to receive small voices'.

Operational improvement and writing novels are somewhat similar at their roots.

Not letting what someone couldn't say go unacknowledged.

Making things that are hard to see slightly more visible.

That is an important axis of Genba-First AI for me right now.

Next week, while organizing the 'boxes for collecting small voices' I have created so far and the flow of these weekly reports, I would like to gradually arrange the lead lines that connect to pinned articles and free reports.

Rather than producing big results immediately, I will leave a record of what I practiced, where I stumbled, and what I thought about.

I would be happy if that accumulation eventually leads to someone thinking, 'Maybe I can do it too'.

In the previous article, I summarized how I made the 'box for collecting small voices'.

Genba-First AI Weekly Report | WK22 | This is how I made the box for collecting small voices

Also, here is the first article I wrote.

🍀I made a box to collect 'small voices' from people working in the community🍀
https://note.com/genba_daiichi/n/n23f858b6a86b

At Genba-First AI, I share information on AI utilization, operational improvement, and small web app creation in a way that is easy for beginners to understand.

I would be happy if you could read future weekly reports as well.

P.S.

I continue to share information about AI utilization and operational improvement myself, but I am still in the trial-and-error phase regarding how to deliver that information.

If there is anyone who is knowledgeable in the same field or is practicing this, I would be very happy to exchange opinions with you.

Waste in the field, turnover, training costs, and reliance on specific individuals.

I want to improve these structural issues even a little.

That sentiment will not change in the future.