Admin Portal for Operations

01 — Context

Summary

This project changed a workflow where even a simple announcement required an IT request and a deployment cycle. Built to give business teams direct control over their content — and architected so well from the start that three years later, it ran a completely different service without modification.

02 — Challenge

Problem

Non-technical teams — Marketing, HR, Security — had no way to update content independently. Every popup, announcement, or terms change went through IT and waited on a deployment. Requirements arrived fast through a planner, quickly pushing scope well beyond the initial brief — meaning the architecture had to absorb growth I couldn't fully predict at the start.

03 — Approach

What I Did

• Designed a modular architecture from day one, enabling continuous scope expansion without structural rework. What started as 4 main menus and 10 sub-menus has grown to 9 main menus and 26 sub-menus.
• Extracted recurring elements (CKEditor, image upload, form components) into shared components, handling scope growth through variant expansion rather than new builds.
• Prioritized intuitive, minimal UI for non-technical operators — reducing the learning curve for business team users.
• Challenged the 1920px min-width spec after observing colleagues using the portal on laptops during remote work and meetings. Proposed and implemented a 1280px responsive layout. Feedback afterward: "So much easier to use on a laptop."

04 — Outcome

Result

Multiple business teams — Security, Marketing, SCM, HR, AI Operations — gained the ability to manage content independently, without IT involvement or deployment cycles. The architecture, originally scoped for SKT Portal, was adopted three years later for T Switch Plus with no structural changes required — one admin platform, two production services.