Expressing convenience as a promise everyone can understand.
In 1975, the development policy for TA-Q-BIN was announced, and a team including young people worked to put it into practice. When it started on January 20, 1976, it targeted the Kanto region, and had conditions such as being within 1 meter in length, width, and height, weighing up to 10 kg, and paying 500 yen. These are inception terms and are not current terms of service.[1]
Azchael ／ Wikimedia Commons ／ CC BY 2.0
Narrowing down the conditions has the effect of making the decision between the acceptor and the requester easier. Under a system where all packages are accepted through individual negotiations, it takes more time to get a quote, and some people give up before using the service. By clarifying the range of items to be handled, the act of ordering one item will become easier to become a part of daily life.
The 2016 annual report lists TA-Q-BIN's development policies as thinking from the user's perspective, targeting a wide range of customers, and achieving both uniform service and cost reduction.[3] The design made it impossible to leave politeness and efficiency to separate departments.
According to the company's history, the nationwide network at the prefecture level was completed in 1991.[2] It didn't reach all over the country at once from the start. For a user, being able to send something depends not only on the place where it is accepted, but also on the system on the recipient's side.
Here lies the difficulty in quality in the service industry. Even if the first point of contact is kind, if the promise is lost during sorting, transportation, or delivery, the customer experience will not be good. The job of cultivating a network is not just to increase the number of bases, but also to enable people in different locations to keep the same promise.
伝Interpreting YAMATO DENSHI
Consistent service promises make a service easier to use.
Services that have different fees, targets, and requests each time are more difficult to use for first-time users. While creating standards that can be standardized, it is also necessary to decide who will decide on exceptions. This is a way to ensure that convenience does not depend solely on the goodwill of those on site.