Case Study

Internal Resource Portal

A centralized platform designed to help multi-location teams access resources, receive announcements, and submit support requests from one place.

Preview

Dashboard

Number of Logins Per Week

Announcements

Open Tickets

Resolved

This preview is a simplified, anonymized representation of the internal tool. It recreates the structure and functionality without using real data.

Role

Front-End / Product UI

Stack

Next.js, React, Tailwind

Focus

Internal tools, RBAC, UX

The Challenge

Company resources, announcements, and internal requests were spread across multiple systems, including email, shared drives, and informal communication channels. This made it difficult for employees to locate information, stay informed, and submit requests consistently.

My Role

As part of the portal development team, I contributed to front-end development, UX improvements, stakeholder feedback gathering, and workflow design. My work focused on making information easier to find, simplifying user interactions, and helping translate operational processes into intuitive interfaces.

Key Contributions

Resource Library

Contributed to the design and implementation of a centralized resource library that organized content using categories, tags, and search functionality.

This reduced reliance on scattered files and improved access to important company resources.

Announcements

Helped create a structured announcement system that allowed updates to be shared consistently across the organization.

The goal was to reduce dependency on manual communication and improve visibility of important information.

Support Requests

Contributed to the interface for submitting and tracking internal requests, helping replace informal processes with a more consistent workflow.

User Experience & Navigation

Improved navigation patterns, content organization, and information architecture to help users locate resources and complete tasks more efficiently.

Design Decisions

I kept the interface simple and task-focused so users could quickly find resources, read announcements, and submit requests without needing extra training.

The portal was designed around role-based visibility, meaning different users could access information relevant to their responsibilities.

I used card-based layouts, tags, and clear status labels to make the system easier to scan and navigate.

What I Focused On

I focused on simplifying complex workflows and making the interface easy to navigate for users with different roles and responsibilities. The goal was to reduce friction, improve clarity, and make key actions accessible without requiring additional training.

To support development and testing, I used Docker to run a local database and simulate a production-like environment. This helped surface issues early and ensured more reliable behavior during development.

I also created simple onboarding materials to help users understand how to navigate the system, reducing friction and improving adoption across teams.

What I Would Improve Next

• Improve the resource library UI to make navigation, filtering, and content discovery more intuitive
• Refine the support ticket interface to improve clarity, reduce friction, and make key actions more intuitive
• Gather additional user feedback after rollout to identify usability improvements and prioritize future enhancements based on real-world usage.

What I Learned

This project helped me understand how front-end decisions directly impact real operational workflows. Designing for multiple user roles required careful consideration of visibility, usability, and structure, especially in a system used by both technical and non-technical users.