Understanding Process‑Oriented Organizational Construction: Business Flow, Process, IT, Data, Quality, and Operations

The company has set a clear goal of building a process‑oriented organization, which means creating efficient value‑creation processes, matching organization to processes, integrating management systems, achieving operational excellence, and fostering a culture of continuous improvement and contractual delivery.

To reach this goal, the company emphasizes a correct understanding of basic concepts—business, process, IT, quality, and operations—and their interrelationships, providing a compiled speech from a business management workshop for reference.

1. Business Flow is an objective, end‑to‑end (E2E) process that starts with customer requirements and ends with product or service delivery, driving customer satisfaction and corporate value. Every strategic choice defines a business flow, and all activities should align with it.

Recognizing the business flow is crucial because it is the origin of all work: process describes the flow, IT enables it, data moves within it, quality requirements attach to it, and operations execute it.

2. Process is a concrete representation of the business flow, capturing best practices to ensure repeatable success. The article cites two case studies: an online issue‑handling process (ITR) that shifted from internal grading to customer‑impact grading, and a delivery process that was redesigned from the telecom operator’s perspective.

Both examples illustrate that processes must reflect the true business flow; otherwise they become redundant or overly complex.

3. Data is the information that flows within processes. Proper data management is essential because inaccurate or missing data undermines downstream activities and overall business reporting.

The IPD transformation highlighted the lack of data architecture, leading to fragmented tools and poor integration. The lesson is that data mapping must precede process and IT design.

4. Quality is defined as “conformance to requirements” and must be embedded in processes. Quality management includes planning, control, and improvement, with standards and checklists guiding each work step.

Internal control, information security, and network security are specific forms of quality requirements that also need to be process‑based.

5. Operations involve continuous, cyclical activities that execute processes to achieve business goals. Effective operation management optimizes quality, cost, efficiency, speed, flexibility, and customer satisfaction, and it spans from enterprise‑wide strategic planning (DSTE) down to project‑level execution.

Operations must follow processes; only then can issues be identified and optimized.

6. Organization‑Process Alignment – Processes define roles, and organizations must embody those roles. Designing organization and process together starts from strategy, identifies key capabilities, and matches them to process and role structures.

All functional units should participate in cross‑functional projects that execute the main business flow, ensuring end‑to‑end responsibility.

7. Responsibility – Business supervisors own the processes; process‑IT teams and consultants provide expertise but do not own the processes. Clear ownership enables effective problem resolution and continuous improvement.

The article concludes by urging readers to ask whether they are slaves to processes or masters of them, emphasizing that true mastery comes from understanding and actively shaping business flow, process, IT, quality, and operations.