logo

TEL:(+81)050-7117-8096※Phone support in Japanese only.
We will call back if unavailable.

Language: 🇯🇵 日本語 🇰🇷 한국어 🇺🇸 English
Back to Column List

Business System Consultation Center - Our Business System ColumnVol.62 2016.02.01 Takahashi Minoru

The trap of feature-rich package systems

Thank you for your interest and continued support.
This is Takahashi from the Marketing Plan Research Laboratory.


For the continued smooth operation of a system,
the presence of employees serving as system administrators is indispensable.


People who are suited to be system administrators
"all business operations covered by the system"
“all the functions provided by the system”
and have a general understanding of both.


System administrators serve as a bridge between the CEO, the front-line staff, and the IT team,
organizing diverse requests into a single coherent path
and plays a key role in clearly defining the exact system requirements.


In the systems we provide,
the person in charge is generally the president.
(This means the president also serves as the system manager.)


This is because the scope of the systems we provide is often narrow,
and it is relatively easy for the president alone to grasp the entire picture
and make optimal requests to us.


However, when the system’s scope of functionality expands, this approach no longer works.
For example, it’s only natural for the president to think, “I’ll ask the accounting department about accounting matters.”
(Large systems usually come with a wealth of accounting and financial functions.)


Operating a system that cannot be fully understood by a single person or a small team
"Including unused functions in updates, resulting in the continued payment of unnecessary update fees"
"Entering data into functions that don’t generate necessary outputs (wasting labor costs)"
“Cases where necessary data entry is frequently omitted (reducing the reliability of reports)”
These issues—collectively known as “system-induced corporate strain”—occur frequently,
and ultimately carries the risk that
This carries the risk of leading to such a situation.


If you are presented with a proposal for a system with too many features,
it might be a good idea to start by requesting a customization
"Please identify the unnecessary features and remove them from the menu."


That's all, Thank you for reading.

------------------------------

■ Previous / Next Column ■

<<< Next Column Vol.63 - Business owners who buy systems without knowledge and get deceived 2016.03.01

>>> Previous Column Vol.61 - It's no surprise when systematizing an Excel-based workflow fails 2016.01.01

Back to Column List

Contact Us

Feel free to reach out to us anytime

Please fill in the form below and click "Send".
Fields marked with * are required.
Company / Name*
Email Address*
Topic (optional)
Message*

Sending your message. Please wait...

Thank you very much for your inquiry.
Your message has been received.
One of our team members will be in touch with you shortly.
Please allow some time for our response.