We are using a combination of a small number of people + software + servers and robots.
We are promoting a new era of company management.
I hope to share some of the process in this section.
We are familiar with the term "landscape" in urban planning, landscape architecture, and geography, but we don't hear it very often.
In layman's terms, landscape is "an organic connection between people, nature and artifacts". (It seems that the actual definition of the term "landscape" is different in each field.
The reason why I bring up the idea of landscape when creating IT services is because IT development tends to be created in a point-by-point fashion, and I think it is necessary to have an idea to cover that.
For example, the functions to be used are summarized as requirements definition, usability is created as web design, and a place to store information is created as a database, which is then combined into a single system.
We also work on ranking high on search engines, post on social media, and send out press releases to let people know about it.
At first glance, all of these things seem important, but if we compare this to the construction of public facilities, we start to feel that something is missing.
The first step is to put together a list of possible uses by local residents, decide on the exterior and interior of the building, and create a multi-purpose room management office.
In order to inform the community about the new facility, we give priority to posting it on bulletin boards, telling people we know, and putting it on circulars.
Is that enough to really see the "view" that people enjoy and use?
I feel like I'm missing something.
Perhaps it seems to lack "something fun" that would make the people living there feel richer in their lives.
I believe that one of the most important things when creating an IT service is how you build that part of the service.
Well, in IT, it's not so much a landscape as it is a cloudscape.