Average Task Time
User Feedbacks
Assisted The Dev Team
To understand the problems, I conducted user interviews and usability audits.
Since this is an internal system, I talked to colleagues who had experience in relational operations.
“Buttons always change, which really confused me (block, approve, reject).”
“After completing an operation on the detail page, returning to the list immediately feels quite strange.”
“Currently, it’s post-review, and after a job is posted, it should directly be in the Open status (currently, the status is Pending). Additionally, at this point, the ‘Approve’ button’s actual function should be ‘Review.'”
“There are two menus for company management.”
“Job statuses need to be organized.”
“Block->Block2->Block3->…, ->Unblock, generates one record. Can this process be simplified to generate only one record for each operation?”
“It’s too complex. I think tabs (processed, unprocessed) and charts can be removed. Another drawback is that the processing button should be closer to the list of reported items.”
“The words in the history section look awkward and are arranged unevenly.”
“There are too many columns for reported objects, making it unclear. Would consolidating them into a single column be better?”
Based on feedback from colleagues, I analyzed the existing system to identify specific usability issues in terms of user experience.
The list of companies with an “Approved” status in the “Company Applications” is the same as the list of “Companies” in “Management”.
Actions for internships with different statuses are inconsistent. Normal internships have the same actions as those that require review.
Upon login, administrators can’t quickly identify urgent tasks. They must navigate various modules to individually check for tasks, causing inefficiency in task handling.
In the Reports section, administrator actions impact stable data, including accounts and existing internships. This section comprises lists of reported company accounts and reported internships, some of which partially overlap with the lists under the Management section.
Note: As the Reports section hasn't been developed, there are no images available for presentation.
Reviewing company applications
Managing existing accounts and internships
Viewing site analytics
Addressing user reports
Managing content shown on Hiintern websites
Based on information gathered from user interviews and usability audits, I sketched various structural concepts and key screens to explore possible solutions. You can experience the original concept through the Notion page below. However, this prototype still has the issue of repeated lists. 😅
To iterate on the design, I conducted 4 review sessions with stakeholders. Finally, we arrived at a more intuitive solution, emphasizing the importance of user engagement and better adaptation to real-world workflows.
Raise the hierarchy for core content types—company accounts, internships, employer accounts, user accounts—enabling easier access to these essential functions.
Define clear states for company accounts, internships, employer accounts, and user accounts. Align these states with appropriate actions to reduce confusion.
| Status | Actions |
|---|---|
| Active | Block |
| Blocked | Unblock |
| Awaiting | Approve, Reject |
| Status | Actions |
|---|---|
| Hiring | Block |
| Ended | Block |
| Blocked | Unblock |
| Awaiting | Approve, Reject |
| Status | Actions |
|---|---|
| Normal | Block |
| Blocked | Unblock |
| Status | Actions |
|---|---|
| Normal | Block |
| Blocked | Unblock |
Create a centralized dashboard that aggregates data and pending tasks, providing an overview for operations staff to manage their workload more efficiently.
Simplify the structure by placing company applications (‘Entry Requests’) and ‘Admitted Companies’ under the ‘Company’ module. Convert ‘Approved’ company applications into operation records, no longer using duplicate tables.
Note: The data in this video were fabricated.
Separate the process of addressing reports from managing accounts and reviewing internships.
Note: The data in this video were fabricated.
If you focus solely on functional logic, upcoming tasks may lead to logic decoupling.
Some code overcoupling may result from the requirements side originally, so never only think within the design scope.
It's really hard to break free from the former logic once you've delved deep into it.
Hi, I’m Zoe Zhou! 👋 A UX/UI designer with 3 years of experience in web and mobile design. I’m currently seeking a full-time UX/UI position where I can bring user-friendly, clear, and delightful designs to life. Let’s collaborate to make your projects shine!
