iTranslated by AI
What I Did as a Corporate Engineer in 2024
2024 was a year of changes in both organization and stance, but each time, I internally developed the necessary tools. Here is a look back at those development projects.
Developed an inquiry ticketing system
First, partly due to organizational changes, I decided to manage inquiries collectively. Previously, inquiries were received via Slack and weren't managed with any specific ticketing system. Since we had introduced Notion, I set it up so that reacting to a message in Slack would store it in Notion.
After that, I added properties to that Notion database such as:
- Priority
- Status (Unprocessed, In progress...)
And attached items to the content section like: - Slack links
- Investigation materials
While this had the side effect of many inquiries appearing in Notion searches, I believe the impact is minor since I include text at the beginning to identify them as inquiries.
Most importantly, I previously managed inquiries using Slack drafts, which often led to frequent follow-ups. While the response speed itself might not have changed much, the number of follow-up messages decreased significantly. It was an unexpected benefit, possibly related to the concept of "Responsibility = Response" (Respons-ability) argued in the following book.
As of December 27, 2024, I have handled 484 inquiries (since the system started in mid-March, so about 8.5 months). It's great to be able to visualize these numbers.
Developed a permission management table to re-envision people and departments as teams
Managing permissions—who has what access and how teams are structured—had become complicated. So, I developed a tool to re-envision individuals and departments as teams.
- Create a team table from SmartHR information
- Set SaaS permissions based on the teams
Regarding permission updates, I am also using this:
This has gradually started showing its value. During alignment meetings, we now share this tool's team management table, and stakeholders discuss based on it. I feel the "fog in the workplace" that was previously vague has cleared up a bit.
Additionally, I set up Slack alerts for improper permissions (including cases where accounts haven't been created).
Developed a quasi-password manager in kintone
It would have been ideal if we could have introduced a dedicated password manager, but I decided to make do with kintone for now. It's certainly better than using spreadsheets or Slack DMs. The users' feedback seems positive.
Developed a complex workflow using JavaScript in kintone
There was an extremely complex workflow, and while I considered splitting the app, I ended up implementing the workflow using JavaScript. I had the JavaScript generate fixed-length keywords and set up the approval process based on those keywords.
Maximizing the utilization of the account management SaaS "bundle"
While we had already introduced bundle last year, I decided to fully utilize it.
- Cleaning up accounts
- Setting up automations
- Importing apps under the Corporate IT jurisdiction that bundle cannot automatically import into bundle via CSV.
I carried these out, and for item 3, I created a CSV conversion sheet.
Also, by distributing bundle accounts to other departments, I was able to simplify the process for inventory auditing purposes.
I really like bundle.
Development of a backup tool for CloudSign contracts
I created a backup tool to address the need for backing up CloudSign information.
Donated PCs
I donated PCs. I'm really glad I did this. I feel like I did something positive for society.
Organizing Notion page structure
Since various departments were using Notion in a trial-and-error manner, I consolidated the common pages.
I also added app icons to the top page. It was a quick-and-dirty job, but I think it's actually quite useful.
Developed an internal announcement delivery tool with Notion
I developed a tool to notify Slack of announcements posted in Notion. Choosing Notion was the right call as it supports Markdown and images.
I used the following article as a reference for the announcement style, adopting this layout:
- What is happening?
- Who is the target audience?
- What must they do?
- FAQ
It is very convenient to be able to add to the FAQ section after an announcement has been delivered. Additionally, I set it up so that once a user clicks a checkbox, the announcement record disappears from their top page—serving as a "check this once confirmed" mechanism.
Summary
It was a year where I realized many things could be managed within the scope of existing SaaS or free tiers. That said, I do feel I could have come up with these ideas back in 2023. I want to continue improving my ability to use SaaS in more advanced and creative ways.
Zenn Recap
My Zenn Recap showed 30 articles. I want to keep writing technical blogs consistently next year as well.
Qiita Review
And here is the 2023 version:
LAPRAS
log
Discussion