CASE STUDY
Staff Directory
Project Overview
In November 2020, I undertook the development of a Staff Directory application to solve a recurring problem in my daily work. My role within the organization fluctuated between Developer, Webmaster, and Database Administrator, and a common task involved managing user access to applications. However, retrieving the necessary user information required querying multiple databases, which was both time-consuming and inefficient.
To streamline this process, I decided to build an internal tool that would consolidate user information into one easily accessible interface. This project was a significant step in improving internal workflows and optimizing my time.
My role in the project was that of a UX UI Designer and Developer.
| Tech Stack | .NET Core |
|---|---|
| Project Type | Internal tool |
| Role | UX/UI Designer, Developer |
| Completion Date | Nov 2020 |
Key Features
- Design: Something I can host on a Development server that will be easy to pull up and use.
- Secure: I made sure to pull information which wouldn't create any security concerns.
- Work Efficiently: So much easier than hunting down all that information.
Project Gallery
Design and Development Insights
As the sole designer and developer, I built this to solve a problem I ran into constantly myself — the main design goal was speed and simplicity.
User Research
The pain points of the existing process were clear from my own experience:
- Slow and Inefficient: Gathering bits of information from multiple databases was a slow and laborious task.
- Tedious: Connecting to 2-3 different databases just to locate and verify user information added unnecessary complexity to the process.
- Uncertainty: Verifying user information with different departments added further delays before I could proceed with access management tasks.
Recognizing these issues, I set out to create a secure and efficient application that could be hosted on a development server for quick reference.
Pain Points
- Slow: It was an inefficient use of my time to piece together bits of information from several sources.
- Tedious: I'd have to connect to 2-3 database to find bits of information that would lead to the actual information I need.
- Unsure: I'd then have to verify the person with the department before proceeding.
Address Issues
- Design: Something I can host on a Development server that will be easy to pull up and use.
- Secure: I made sure to pull information which wouldn't create any security concerns.
- Work Efficiently: So much easier than hunting down all that information.
Design and Development Process
The design goal was to create a web-based application that would be simple, efficient, and secure. The application did not require a backend database, as it only pulled information from existing sources without storing any data. This approach not only simplified the development process but also reduced potential security concerns.
The interface was designed to be intuitive, allowing developers to quickly access the necessary user information without needing to manually query multiple databases.
The application was developed using .NET Core, marking my first experience with this technology. As part of the development process, we also configured our development servers for .NET Core, which opened up new opportunities for future projects.
Key Performance Indicators
- 70% reduction in Information Retrieval Time: The Staff Directory reduced the time spent gathering user information by 70%, cutting down the process from several minutes to just a few seconds.
- 50% increase in Efficiency: By consolidating information into one tool, I was able to increase my efficiency by 50%, allowing more time to be spent on higher-priority tasks.
- 30% decrease in Errors: With a streamlined, centralized source of information, the tool decreased the likelihood of human error by 30%, leading to fewer misidentifications and incorrect access permissions.
Launch
I successfully published the Staff Directory to our development server, where it was used by myself and other developers. Due to its ease of use and the time savings it provided, a few key staff members were granted access to the site. It became so popular that senior executives requested that it be shared with all permanent staff.
The application did not store any information, which made it secure and lightweight, and it required no additional database infrastructure, which further simplified maintenance.
Lessons Learned & Future Improvements
Impact
This project not only enhanced internal processes by streamlining user access management but also introduced the organization to .NET Core development. It allowed me to spend my time more efficiently and demonstrated the importance of creating tools that cater directly to internal needs.
The Staff Directory application had a noticeable impact on my workflow and that of other developers. By centralizing access to user information, the application significantly improved our ability to manage user access efficiently. Senior executives who saw the tool’s potential requested that it be shared with all permanent staff, further expanding its impact across the organization.
The project also demonstrated the benefits of .NET Core in our environment, paving the way for future development projects using this framework.
What I Learned
Building the Staff Directory was my first foray into .NET Core, and it gave me valuable experience in setting up and deploying applications on our development servers. The project also reinforced the importance of creating secure, efficient solutions that directly address recurring internal challenges. It showcased the power of internal tools to improve workflows and overall productivity.
EXPLORE MORE
Continue through the portfolio.
Browse the complete project collection, or reach out if you would like to discuss the engineering and design decisions behind this work.