Business Processes which should be Considered before Building a BPO System

What is BPO? (Business Process Outsourcing)

It is, basically, 'to outsource' the so-called indirect business. Or, in some business conversation, it often refers to "a contracting service in response to the commission". Anyway, the company entrusts the duties such as general affairs, human resources, accounting and welfare and telephone correspondence to the trustee. These outsourced duties are essential, even though they do not produce any profit directly.

BPO in Japan, there are three major businesses which are "Customer service" "Order Management", and "ICT systems management".

The following workflow is "antivirus operations" which is the most costly in the "ICT systems management". Most notably point is that it admits use of personal belongings as an information terminal device, in order to ensure the convenience of employees. These are cases of companies in the so-called "BYOD" (Bring Your Own Device) framework, that are judged to be conducive to business improvement (quality / delivery / cost) in the core business even in light of the information leakage risk.

(However, "anytime email confirmation" has been realized in many companies nowadays. In that sense, I probably should not note it as "special mention".)

In this outsourcing operation, it has been devised to reduce the overall cost by the cooperation of commissioning side and the trustee side. To be specific, each user him/herself to actively report "security status" of the devices which have been registered in advance. For example, users can attach a screen capture of virus scan history, or describe the inconvenience and worries on the utilization. On the Trustee side, as well as checking the overview report of all employees, they would perform investigation and correspondence individually, if necessary. Really, it's sophisticated.

[Device Security Report flow]

Free Trial of a Workflow, What Do You Run on It? (Suggestion Box)

* Series; Can be used immediately, part 1.

Considering the introduction of the workflow system... I want to evaluate Workflow products by running data that is even a little significative.

However, even how much you look for, there is no business sample that fits completely in the business of your organization. I mean, the "Business Process To Be" will differ greatly because it depends on the company size, the business industry and the department in the company. So you will download a Business Process Definition sample (Workflow Sample) that is too simple, and you activate in the Workflow system, and end up inputting something nonsense like 'test' or 'foo bar'.

I would like to present you "Suggestion Box Workflow" in the following, which is very convenient as a workflow to be run during a trial period of Workflow product. The Flow diagram is simple enough, and you can start using it (if you wish) in any organization of a small team to large company. More than anything, it is good that you can start it smaller without affecting the main business.

[Suggestion Box flow]

Business Manual within Workflow!

You need
(A)'a Manual to accelerate each processing (each step)' (micro-spective) as well as
(B)'a Manual that grows understanding about the entire business' (macro-spective).

Looking at the operating screen of the Workflow, it is possible to handle allocated tasks even for non-experience personnel. "Vacation Request", "Approve the Request", "Confirm Absence", etc. All they have to do is to input along the indicated form screen. (There may be 'a Manual to accelerate each processing'(A).)

* Sample for (A) Embed Manual to Operating Screen of Workflow with Google Drive

However...
They are not few cases that you want solutions to the questions in entire-business-spective or entire-system-spective such as ,

• Will my salary be reduced?
• First of all, how the leave system is defined?

The following Workflow-sample contains "The overview of the leave system" (a business manual). That is, apart from the "manual to handle each step"(A), "Manual for the entire business flow"(B) is given to see in the workflow. (New feature of Questetra [Version 9.7!!)

[Leave Request Flow-w/Manual]

Recruiting Process Improvement meets Recruitment Ethic

"Recruiting and Job hunting", the way it should be have been discussed for decades.
Especially in Japan, it seems like 'a social problem that cannot be resolved forever'.

That is, companies want better talent as possible, so they start recruiting earlier than the officially agreed date. While students spend quite a lot of time searching for their future employment after their graduation rather than studying. Both of their interest matches, even though both of them think that is not the way it should be.

Companies and colleges have tried something so far.
In Japan, there was a gentleman's agreement which was called 'Agreement for Recruitment'. It is enacted in 1952, but the rule has never been complied until it is abolished in 1996. Even in the 21th century, A variety of approaches have been made such as 'Charter of Ethics' by companies, or arrangement between colleges. However, those were not enough to achieve the self-control of both them as well. I must say, it could not limit the activities of "companies that want to ensure new graduates at an early stage" and the "college student Look for employment desperately" as if "men and women who fall in love with love".

Spring of 2013, Prime Minister Abe summoned the economic organizations and requested a "further delay" on the recruitment period, said "it cannot be overlooked that students losing the opportunity to extend their capacity". Speaking short, ' those company explanatory sessions be held later than spring break (March, which is the end of the school year in Japan) of the third grade.' A " New Charter of Ethics" will be established by the economic organization soon, and will be determined "Spring Break of 3 graders (March)" which is three months later than currently "winter break of the third grade (December)".

It is necessary for companies that no choice but to (formally) comply with the gentlemen's agreement, to change more smoothly in the "recruitment work flow".

[Recruitment workflow]

With Cloud, Leave Request at Any Time from Smartphone!

There are many types of "off".
What is "Vacation"?
What is "Leave"?

Request for "leave" is an important application that concerns to salary, but in the other hand it is troublesome that you have to read-back "the work rules" or to look for the format of the "application". You want to make it smoother.

The following Workflow is "Leave Request flow" which can be used by a lot of companies.
You do not have to care such as "difference between annual leave and special leave" or "difference between compensatory day off and Substitute holiday". Except the "obvious holidays" like Saturday and Sunday, you can freely request for leave of vacation. Furthermore, every time you see the screen of application, you can learn that "Oh yeah, I can also make request from here when I request parental leave".

[Leave Request flow]