This is my current project.

Which I’ve been involved in since April 2024.

🧭 Context

I’m currently working on an internal platform under development at Electronic Arts. The platform aims to centralize key back-office operations that were previously managed across separate tools — including permissions, access management, data handling, and asset distribution for internal teams involved in game development and testing.

While it isn’t public-facing, the platform plays a critical role in streamlining workflows for dozens of internal teams. I join the effort at a pivotal stage: helping transition the platform from dev to production by improving its usability, visual clarity, and overall consistency — all essential for adoption at scale.

🎯 Tasks

I serve as an external design consultant with a technical focus. I’m the first designer embedded in a team of senior engineers, and my responsibilities evolve constantly:

• Evaluating and improving the platform’s visual hierarchy, interface clarity, and usability.

• Working directly within the codebase — editing HTML, SASS, and contributing to Angular-based micro-frontends.

• Styling and customizing key components in production, including navigation bars, form elements, data tables, and an internal low-code builder.

• Creating internal documentation by turning test pages and component demos into practical references.

• Bringing visual consistency to components built using a third-party UI library and laying the groundwork for future design documentation.

🛠️ Actions

Despite having over a decade of experience in UX/UI design, this project pushes me to rethink my approach and operate inside a development environment. I actively learn new tools, workflows, and ways of thinking to contribute meaningfully in a deeply technical setting.

• I take ownership of the platform’s navigation components, redesigning them for clarity and scalability as engineers add new features.

• I reorganize the interface of a complex internal builder — refining button hierarchies, clarifying configuration flows, and aligning the structure with patterns found in modern design tools.

• I document as I go, turning exploratory tests into live, contextual guides — covering component behavior, configuration logic, and advanced use cases involving dynamic expressions.

• Rather than relying on mockups, I ship improvements directly in code, which earns me trust and autonomy within the team.

✅ Results

I help bring visual harmony, structural clarity, and consistency to a complex product — all crucial for user adoption, which remains a key success metric for the team.

By owning front-end improvements, I reduce the burden on engineers, allowing them to focus on backend architecture and functionality.

My hands-on documentation has become a living resource for onboarding and ongoing internal education, supporting both technical and non-technical users.

I gain technical confidence, autonomy, and a stronger ability to reason through design decisions based on implementation realities — not just visual intent.

🔁 Reflections

This project pulls me out of autopilot and reconnects me with the core of what it means to build. Wearing the developer hat — without losing my design perspective — expands how I think, work, and collaborate.

I now design with deeper awareness of how things are made, and I carry that mindset into every conversation, decision, and contribution I make.