The organization needed a centralized platform to manage and host internal projects without relying on external CMS solutions. Unlike most projects that begin with detailed requirements, this initiative started with only a list of core pages and high-level feature requests. There were no established workflows, user journeys, or functional specifications. This created an opportunity to contribute beyond interface design. I became responsible for uncovering requirements, defining user experiences, creating scalable design patterns, and helping transform a collection of ideas into a cohesive product.

The challenge wasn't simply designing screens. The challenge was defining how the platform should work before design and development could begin. Without established workflows, several questions needed to be answered:

Before solving usability problems, I first needed to identify them.

One of the most important decisions was investing early in a design system. Although creating a design system requires additional upfront effort, it became the foundation that supported the entire platform. The design system included:

As the platform expanded, the system significantly improved consistency and efficiency.

Designing the product before designing the interface. One of the most important realizations early in the project was that the biggest challenge wasn't visual design—it was product definition. Before creating screens, I spent time understanding how features related to one another, identifying workflow dependencies, and uncovering missing requirements that had not yet been documented. Instead of treating design as a downstream activity, I approached the project from a product perspective, helping define how the platform should work before determining how it should look.

Creating structure through flows. User flows became one of the most valuable tools throughout the project. By mapping workflows and feature relationships, I was able to identify gaps, edge cases, and opportunities to simplify complex administrative processes before development began.

Building systems early. Because CMS platforms naturally grow over time, I invested early in creating a scalable design system. This allowed new features to be designed and implemented more efficiently while maintaining consistency across the platform.

As the sole UI/UX Designer and Front-End Developer, I:

Starting without detailed requirements. Working within project timelines meant balancing thoughtful problem-solving with the need to move quickly. Rather than exploring every possible direction, I focused on defining strong foundations and iterating as requirements matured.

Designing a large CMS solo. CMS platforms are inherently broad—many screens, states, workflows, and permissions. Carrying discovery, UX, UI, component creation, documentation, and development support independently meant constantly balancing depth against deadlines without letting quality or consistency slip.

Designing without direct user observation. Without direct access to user behavior, decisions were informed through research, CMS best practices, stakeholder collaboration, and continuous evaluation of workflow risks.

While business metrics cannot be disclosed, the project established a strong foundation for the platform's continued growth. The creation of a design system improved consistency across the product while supporting faster feature development. Reusable components and shared patterns strengthened alignment between design and development, reducing duplication and improving maintainability. Beyond interface design, the project transformed a collection of loosely defined requirements into a structured product experience, providing a scalable framework for future enhancements and expansion.

The biggest lesson from this project was that successful product design often begins long before screens are created. Requirements are rarely complete. A large part of the work was actively identifying gaps, asking the right questions, and anticipating future needs rather than waiting for a finished brief.

It also deepened how I think about design systems—not as a collection of UI components, but as a shared foundation that connects design and development. Working across UX, UI, QA, and front-end strengthened my ability to think beyond individual screens and treat the product as a complete system. Most of all, it reinforced the value of ownership, adaptability, and proactive problem-solving when building a product from the ground up.

The Internal CMS Platform was more than a design project—it was an opportunity to help define a product from the ground up. By combining product thinking, UX design, design systems, and front-end development, I helped transform broad business requirements into a scalable platform foundation. The experience strengthened my ability to navigate ambiguity, create systems that scale, and contribute across the full product development lifecycle.

My involvement with the platform continues today. As new business requirements emerge, I remain responsible for designing new features, refining existing workflows, expanding the design system, and supporting front-end implementation.