arrow_back Back
CMS Internal Tool

iQor CMS

A dedicated content management system built to power every announcement, update, and editorial piece published across iQor's internal digital ecosystem. Built for speed, structure, and scale.

View live demo ↗

Try it yourself

Demo with fictional data. Your changes are only saved in your browser.

Role

Senior UX/UI Designer

Year

2026

Duration

8 weeks

Deliverables

UI Design, Components, HandOff Specs

Tools

Replit AI, Claude AI

01 Context and problem

iQor is a global company with a lot of people who need to hear the same thing at the same time: announcements, articles, surveys, forms and courses. All of that lives in the HUB, the app employees use. But someone has to create it, review it and publish it, and that part didn't have a place of its own.

In practice, content was scattered across loose documents and several separate apps that weren't built for this. To see each piece, people had to open a different app and go through many steps.

The problem was building that place: a CMS where the people who produce content can write, approve and publish without friction, with consistent templates and visual themes, and where content reaches the HUB with the right structure. It had to be clear for people using it every day and flexible enough for so many different content types.

02 My role and the team

I was the Senior UX/UI Designer on the project. I designed the interface, the components and the handoff specs, and I used Replit AI and Claude AI to turn those designs into a working product. It took about eight weeks.

I worked with the product director, the Lead Product Owner, the DevOps director and the people who use the app, iQor's call center agents, who helped me understand what they needed day to day.

03 From Replit to a real product

[PENDING: Santiago will fill this in]

Screenshot pending

04 Design decisions

[PENDING: Santiago will fill this in]

The hardest part wasn't on the screen, it was judgment. Several user stories, as they were written, didn't give a good experience or a clear logic for the people who would use the app. When that happened, I questioned them, talked it through with product and changed them so navigation was simpler. A user story is a starting point, not a contract.

Screenshot pending

05 AI inside the product

[PENDING: Santiago will fill this in]

Screenshot pending

06 The demo

[PENDING: Santiago will fill this in]

Screenshot pending

07 What I learned

Outcome

Today the product remains stable in use globally at iQor, and it hasn't needed to be redesigned to iterate on it.

[PENDING: Santiago will fill this in]

  • Changing a decision early is cheaper than defending it: if the experience doesn't work, say so with reasons and adjust it.