Case study
Enjin.world
Rebuilding a career platform for bilingual students and professionals in Tokyo. Sole designer on the 2023 revamp.

Overview
Summary
- Background
- A career platform in Tokyo for bilingual students and professionals, running three services (Career, Forum, Community) under one product. About 2,600 registered users, roughly 390 active in a typical month.
- Problem
- People signed up but did not come back to apply, post or take part. Of those who started a job application, only about half finished it, and nothing in the product said why.
- Approach
- Twenty interviews and a focus group. Two candidate approaches, one chosen. The architecture split into three service contexts, each with its own messaging.
- Outcome
- All five usability participants completed the tasks, one with a hint to find the service switcher, and all preferred the redesign. Seven-day application completion rose from about 49% to about 64% in the first full month after release.
Context
Context
Enjin was a Tokyo startup building a career platform for bilingual students and professionals in Japan. The product, enjin.world, ran three services: a job board (Career), a Q+A space (Forum), and a networking feed (Community).
I joined in 2020 while still moving from graphic design into UI/UX, and co-designed the first interface with another designer. By 2023, with more practice and fresh research, I owned the full revamp. This case study is about that second version, and follows the mobile experience.
I partnered with the CTO, who also acted as product manager, on prioritization and scoping. Two design interns supported earlier phases. The dev team reported to the CTO.
The objective was to help users move from browsing to taking part: applying for a job, asking a question or joining a community, without removing any of the three services.
Problem definition
Problem
The site had users. It did not have habits. People signed up and did not come back to apply, post or take part. We had no behavioral analytics to show where people dropped off or why. What we did have was the application table: in the month before release, roughly 390 users were active, about 84 started a job application, and about 49% of them finished within seven days.
The brief was to find out why, with interviews as the only research tool available.
Research
Research
I ran twenty 1:1 semi-structured interviews with active and lapsed Enjin users, recruited across the three services, plus one focus group session with five users and two non-users for comparison. Sessions were roughly 45 minutes, recorded with consent, and synthesized via affinity mapping into themes.
Three themes consistently emerged:
Architectural confusion. Users felt overwhelmed and didn't know where to start. The flat tab strip put Forum, Career, Community, and Messages at equal weight, with no anchor or primary purpose. Most couldn't tell what Enjin was primarily for, so most didn't form a habit around it.
The clearest expression of this was the unified Messages inbox. Career replies from recruiters, Forum responses from strangers, and Community DMs from friends all stacked into one stream. A job rejection could land directly beneath a casual ping about coffee. A filter could narrow the inbox by relationship type, but users still had to interpret and sort those relationships within the same surface on every visit, and high-stakes recruiter messages drowned in social noise.
Familiarity gravity. When asked which sites they actually used for job hunting, LinkedIn and GaijinPot dominated. For social, Facebook and Instagram. Their habits set the interface expectations we were not meeting.
Visual fatigue. The original orange-green palette was the most-cited surface complaint, signaling "early stage" in a market where Indeed Japan and LinkedIn set the polish baseline.
Research made it clear what was broken, not how to fix it. With no budget for separate IA studies, I reasoned from how LinkedIn, Facebook and Reddit handle similar problems, weighed two approaches, and tested the integrated redesign with users at the end.
Design development · Approaches
Two ways to clarify the product
The research pointed to confusion between services and conversations. We considered whether clearer labels within the existing structure would be enough, or whether the services needed more distinct boundaries.
Keep the navigation, improve the labels
Keep Home, Forum, Career, Community and Messages as the main destinations, and make their labels clearer. This preserved a familiar structure for existing users, but left the inbox problem intact: recruiter conversations, Forum follow-ups and Community messages would still share one surface.
Give the three services a shared entry pointSelected
Bring Career, Forum and Community together in a service switcher. Users open the burger menu, choose a service, and enter its navigation and conversations. This kept all three services within Enjin while giving each a clearer boundary.
Keep the breadth, clarify the boundaries
We chose the second approach because it addressed both navigation and messaging. The cost was lower visibility of the other services: switching now required opening a menu. That made finding the switcher an important question for usability testing.
Design development · Decisions
Decisions
Borrow patterns users already knew
I borrowed interface patterns from the two sites users habitually relied on: LinkedIn for the job browsing and profile flows, Facebook for the community feed. Attention went to the content instead of to working out the interface.
Cut the visual noise
I replaced the orange-green palette with teal and off-black, added whitespace, and gave each service its own mark: a staircase for Career, an infinity loop with speech bubbles for Forum, a speech-bubble cube for Community. The sub-brand marks did the wayfinding work on every screen.


Design development · Architecture
Architecture
Career, Forum and Community became distinct contexts within the same product. The burger menu opens a shared switcher with all three options. Selecting one takes users into its relevant navigation and messaging, while keeping the same interface patterns across services.
One unified inbox became three contextual Messages surfaces. Career carried recruiter threads. Forum carried follow-ups from people who answered users' public questions. Community carried friend DMs.
The trade-off. Someone active in all three services now has three inboxes to check, and nothing on the screen totals them. Two of five test participants asked whether Messages was shared before opening it.



Deliverables
Three distinct service experiences for Career, Forum, and Community, connected by a burger-menu switcher for cross-service moves. Mobile-first responsive layouts across all three. Three sub-brand marks and a unified type and color system. A component library covering every repeated pattern, from button states to data tables. On the side: a product explainer animation (After Effects, own voiceover) and bilingual B2B brochures and event standees for the recruiting circuit.


Validation
Validation
One week before release I ran a moderated, task-based usability test with five users who had used the original platform, drawn from the interview pool and current users, followed by a short interview. Roughly 40 minutes each.
- Task 1
- Find a job in Career and start an application. 5 of 5 completed.
- Task 2
- Switch to Forum and find a question about working visas. 5 of 5 completed; one needed a hint to find the service switcher.
- Task 3
- Reply to a recruiter message. 5 of 5 completed.
- Task 4
- Find and join a community. 5 of 5 completed.
- Task 5
- Return to Career from Community. 5 of 5 completed.
All five preferred the redesign in the closing interview. Most named the colored header with the service lockup as how they knew which service they were in. Two asked whether Messages was shared across services before opening it. The participant who needed a hint on task 2 found the switcher unprompted on task 5.
Recognizing the current service and discovering how to leave it were different problems. Participants used the service identity to orient themselves, but one needed help finding the switcher. Questions about whether Messages was shared also showed that the inbox boundaries were not immediately clear to everyone.
Five returning users, not first-time users. The test shows the integrated redesign was usable and preferred by people who knew the original. It does not separate the effect of the architecture, the messaging split or the visual change, and it says nothing about newcomers.
Outcome
Outcome
The redesign shipped in 2023 with all three services intact, service-specific navigation and messaging, and one shared visual foundation. Application completion gave us one way to examine whether users were following through on a core task.
of starters finished within seven days
of starters · about +15 pts
Monthly active users also increased, from roughly 390 to about 450, and application starters from about 84 to about 97.
What it shows. A larger proportion of application starters submitted within seven days. For a recruitment service, submission is a meaningful step beyond browsing: it turns interest in an opportunity into an application. The increase was encouraging, although it did not establish which design changes contributed to it.
What it does not show. Completion is one step in one service. It says nothing about whether people found Forum or Community easier to reach, and nothing about anyone arriving for the first time. Those were the questions the usability test could only partly answer.
Counted from the application table: users who created an application draft in the month, and how many of them submitted within seven days. The last full month before release against the first full month after it. Staff and employer accounts excluded. I defined what counted; the CTO ran the queries. Enjin has since closed, so the figures here are from my records of those results, checked with a former Enjin engineer. Treat them as close rather than exact.
A before-and-after comparison, not a controlled test. Job supply, recruiting season and who happened to sign up also changed between the two months. The number is consistent with the design argument; it does not prove it.
Reflection
Reflection
The central decision at Enjin was to keep the product's breadth while making its boundaries clearer. Labels alone would have left the shared inbox intact. Separate service contexts fixed that, and raised a new question: where do I switch, and which conversations live where? Testing showed where the structure was understood and where it still needed explaining. Next time: a tree test before committing to the IA, first-time users in the usability test, and switching and messaging tested together, since they were really one question.





