[GAS Development for Non-Engineers] How I Reduced a 20-Minute Manual Task Forced by the Parent Company to 30 Seconds
Prologue: An Unreasonable Demand from the Parent Company
“With the introduction of the new system, you will be required to manually convert data via CSV every month.”
——The moment I saw the message from the parent company, the words “Excel Hell” flashed through my mind.
Why are we being forced to use such a tedious method in 2025...?
“The manual is over a dozen pages long, and it takes about 20 minutes to complete.”
The instructor smiles brightly. But I can’t bring myself to smile back.
“Are we really going to do this every month...?”
Yamada from our systems department lets out a groan.
Chapter 1: Aota-san Appears—The Guardian of Accounting Entry
Here, our new force (though she’s already a celebrity within the company), Aota-san makes her entrance.
She is known as the “Guardian of Accounting Entry,” with a reputation for being second to none when it comes to mastering spreadsheet importrange and Excel functions.
“Could you handle this manual task for me?”
I asked Aota-san. I had hoped that with her professional eye, she might be able to manage it, but...
“Copy column A... then use this function... and then apply the filter...”
We try a special training session with the manual in hand, but the steps are bizarrely numerous.
I never expected Aota-san, who usually breezes through her work, to be this confused...
“They say it takes about 15 minutes once you get used to it, but every month? Honestly, this is exhausting.”
Fatigue seeps into Aota-san’s voice.
Even though she’s known for her Excel skills, she’s struggling with this “crap Excel” task that takes 20 minutes no matter how many times she tries.
Watching her, I felt something I couldn't quite put into words.
“Such heavy labor should be done by a machine...”
I finally decided to take action.
Chapter 2: The 6-Hour Mojibake Hell and the Light of Blog Searches
First, I ask AI, “How can I automatically convert CSV files?”
“Please specify the character code as SHIFT-JIS!”—the AI replies, but when I actually open it in Excel, the screen is filled with mysterious characters.
\{l
No matter how many times I ask, the AI just repeats,
“Let’s try it with SHIFT-JIS (firmly).”
“No, that’s exactly what isn’t working...!”
“If it comes to this, I’ll try searching blogs.”
When I perform a web search—the “ancient wisdom”—a certain article hits.
“If it’s a Japanese-specific character code, specify 'MS932'!”
This is it...!
function convertToCSV(data) {
// MS932で文字化け撲滅
const csv = Utilities.parseCsv(data, 'MS932');
return csv.join('\n');
}
When I tried it, the mojibake disappeared as if by magic.
The development time it took to output the correct CSV was 6 hours.
“Don’t act like you knew that from the start, AI...” I thought to myself, but I had somehow cleared the first hurdle.
Chapter 3: A Progress Bar is a Sign of Peace of Mind
Having solved the mojibake issue, the conversion itself started working.
Aota-san was also happy, saying, “That’s amazing, Manager! This will make the work overwhelmingly easier...”
However, that peace was short-lived. The next wall appeared.
“Manager, I can’t tell from the screen if it’s running or just waiting...”
Yes, people don’t feel at ease unless they have a sense that things are “moving.”
I tried the AI’s sample code, but the progress bar just hit 100% in an instant and finished.
“This isn’t progress, it’s just a slideshow.”
In the end, I incorporated progress management using a cache service.
(Previously, when I fed the AI some code that happened to work well, it understood it in seconds.)
After some back and forth, including the time to polish the UI, it took about 3 additional hours.
function updateProgress(current, total) {
const progress = Math.round((current / total) * 100);
CacheService.getScriptCache().put('progress', progress, 300);
// 画面に反映するHTMLを返す
return HtmlService.createHtmlOutput(
`<div class="progress-bar" style="width:${progress}%;background-color:green;">
${progress}%
</div>`
);
}
Watching the elapsed time display I implemented to visualize the time saved, and the green bar sliding smoothly across the screen, Aota-san smiles with a sense of relief.
"Humans really do find comfort in even such simple things, don't they..."
Chapter 4: Manuals Need to Look Good, Too!
Once the system was running stably, we held an internal demo.
Aota-san operated the screen herself, and when everyone saw the task finish in 30 seconds with a single click, their eyes lit up.
However, that was when the "How do I use this?" problem arose.
I decided then and there that I would create a manual.
"I have to think from the perspective of the person using it."
Actually, I put a lot of care into this manual as well.
/* マニュアルのデザインテーマ */
:root {
--primary: #4a90e2; /* 優しい青 */
--success: #2ecc71; /* 爽やかな緑 */
--background: #f5f6fa; /* 柔らかな背景色 */I also made sure to cover how to handle errors thoroughly in an FAQ.
<div class="important-note">
<i class="fas fa-info-circle icon"></i>
<!-- やさしい言葉で解説 -->
エラーが出ても慌てないでください。
ほとんどの場合、以下の確認で解決できます：
・ファイルは正しいフォルダに入っていますか？
・文字化けしていませんか？
・データの形式は合っていますか？
</div>With a feeling of, "If you're in trouble, look here!"
The results:
Simple, bulleted procedures
Important warnings highlighted in eye-catching boxes
Visual clarity using icons
Focus on readability with a gentle color scheme
Aota-san gave me feedback like
"Even a new employee wouldn't get lost with this,"
"The color scheme is cute and it's fun to look at!"
A manual isn't just an instruction book.
It's an important communication tool that shows empathy for the user.
...That said, this might just be my own speculation.
"Is the 'cute' that an old guy thinks of just pushy?"
I felt anxious, but I finished it anyway.
Since Aota-san said, "It's so easy to use!", well, I guess it's fine.
After the demo, Aota-san says,
"Manager, couldn't we sell this to the parent company?"
—Her eyes were sparkling.
I grin and sip my coffee.
"But you know, this is our own secret weapon."
Yes, the manual work forced on us by the parent company is being sped up behind the scenes with this tool, and that's our little secret.
Epilogue: Is Inventory Management the Next Battle?
After implementation, the 20-minute ordeal Aota-san had been struggling with plummeted to 30 seconds.
Yamada from the Systems Department is also thrilled, saying, "I can't go back to manual work anymore!"
However, it is not over yet.
"The methods for aggregating inventory management data are all over the place..."
Starting with that one remark from the Sales Executive, I have a feeling that a further battle is about to begin—.
Summary of Lessons Learned
Even if AI is convenient, what ultimately saves you is human wisdom (blog searches)
Know the value of MS932: Japan's unique legacy specifications are not straightforward
Progress bars are a symbol of peace of mind: Humans feel anxious if they don't get a sense that things are "moving"
Manuals are the ultimate weapon to save your future self and your colleagues
Don't overlook Aota-san's struggles: Someone else's trouble is the perfect timing to decide to develop a solution
Next Episode Preview
"The Legendary Accounting Manager Conquers the Chaos of Inventory Management!"
"I leave the creation of inventory documents to each manager, but... can't we standardize it somehow?"
The Sales Executive's words were light—but there was deep darkness hidden within them.
Disparate formats, different aggregation rules, and inefficient work hours.
I have no choice but to create a magic tool that unifies the documents that four sales managers each spend four hours creating with just a single click!
A data hell challenged alongside AI, a death match with a progress bar whose progress couldn't be seen, and finally... a tool was born that made every manager say, "Isn't this a bit too convenient?"
Stay tuned for the next episode, "Conquering Chaos with One Click!"