Understanding Business Insights to Grasp System Operations
We began by understanding the principles of the LNG business and its overall process, starting with a role-based analysis of users grounded in the industry value chain. This enabled us to grasp the fundamental nature of the energy business, understand the core business processes, and establish standards for workflow. The biggest starting point was determining how to deliver a user experience that considers the LNG value chain as a foundation and integrates seamlessly with system screens.
We focused on minimizing the gap between field personnel accustomed to existing work methods and the new system, seeking ways to create a natural transition. This led to redefining workflows centered around the value chain, considering the business processes. Adapting to a new system work structure from their familiar ways was a significant challenge and adventure for the users.
The expected benefits of the project are as follows:
• First, standardization of B2B information architecture: defining standard menu access based on common tasks and linked workflows.
• Second, defining work access structure scenarios based on user access permissions and activities.
• Third, providing a familiar work system environment while enhancing system usage efficiency.
Starting the Legacy System Analysis
Through analyzing the As-Is menu tree and program lists, the priority was to understand unit task functions by user permissions, classify the menu access system by overall user permissions, and establish a hierarchical structure based on users’ task units.
01. Menu Tree & Storyboard Analysis
By establishing the overall workflow linked to the system based on the existing menu’s value chain, we aimed to enable seamless task continuity within a timeline-based cycle and assist in setting standards for system processing.
02. Establishing a Value Chain–Centered Workflow
By establishing an overall workflow linked to the system based on the LNG value chain, we aimed to ensure seamless task continuity within a timeline-based cycle and support the establishment of standards for system processing.
Guiding User Behavior
By defining behaviors for various users involved in the work process and mapping service flows for each scenario, a foundation is established to design an information architecture linked to user actions.
This approach goes beyond simply listing menus; it exposes menus based on the user’s service scenario and defines a natural flow that guides their next steps.
01. Establishing Work Behavior Scenario Criteria by User Permission
Based on the workflow, by distinguishing tasks that can be collaboratively handled according to each user’s unique role from those that must be handled individually, we were able to identify and check for conflicting or unnecessarily overlapping areas.
Establishing Menu Display Criteria by User Permission Based on Customer Experience Journey Timeline
By defining user activities according to user permissions, we established criteria for menu visibility based on the customer experience journey timeline.
Accordingly, we provided options for information architecture design based on different perspectives.
We offered a dual-structured information architecture that includes workflow-based structures, user permission–based to-do task management, and operations-focused structures, which ultimately influenced the design of the most optimized work screens.
03. oviding Guidelines for Menu Composition and Display Principles
By distributing guidelines that are practical and applicable to actual menu composition without being overly detailed, we ensured that the CRUD-based menu structure could be effectively implemented. This allowed for grouping and prioritization of tasks that enhance work efficiency, resulting in a consistent and user-friendly architecture.
Through analysis of menu hierarchy by user work permissions, we were able to derive a menu activity index aimed at improving sequential structure design according to task order and enhancing the hierarchical organization of navigation elements (GNB, LNB, Utility).
Recognizing the Importance of Information Architecture
Diagnosing information architecture through this project was quite rare in domestic IT projects. Often, the importance of information architecture is perceived merely as a simple task within the overall project. Frequently, information architecture is constructed without understanding the industry business or interpreting it from the perspective of user work scenarios. Therefore, this project was significant in recognizing the importance of information architecture from the very beginning.
Especially, reviewing information architecture during the development phase was highly unusual but also rewarding. I would like to express my gratitude to the client and project team members who provided great support during this short period.
