Internal work-management system
We built the screens of an internal work-management system where staff at a national testing and certification body handle administrative and management work in one place. Staff use these screens every day, so any confusing flow or unsteady behavior turns into friction that piles up daily. Our part covered the screen structure that gathers many work functions into one system, the entry, search, list, and detail screens, and controls that work like a desktop application inside the web browser.
A screen structure for handling many kinds of work in one system
The internal work-management system was built so that the administrative and management functions an organization runs on are handled in one system. We laid out the structure of the main screens so that many different work functions could be used inside that single system. The rule for the structure was that, however many functions were added, staff should never lose track of which task they were looking at.
Work screens that flow from entry through to detail
Administrative and management work usually follows the same order: enter, search, pick from a list, check the details. While implementing the entry, search, list, and detail screens of the internal work-management system, we arranged them so the move from one screen to the next was always clear. Only when an item picked from a list carries straight into its detail, and the way back to the list is clear, does repeating the same work daily involve no wasted steps.
Stability measured against the person who uses it every day
Internal work screens are where the same staff repeat the same tasks every day. So we put a clear flow and steady behavior ahead of anything eye-catching. People who use a system daily stay fresh only when the order they learned once keeps working and every action gives the same result each time.
Controls that behave like a desktop application inside the browser
The internal work-management system opens in a web browser, yet it was built so complex work functions could be used like a desktop application. We developed the work screens and controls using reusable screen components and handling for user actions. Staff need no separate installation at each desk; any browser opens the same screens.
Highlights
A screen structure that gathers administrative and management functions into one system
Work screens that run from entry and search to lists and detail views
Controls that work like a desktop application in the web browser
Insights
GA4 client_storage: 'none'은 정말 쿠키를 막을까?
두 달 전 이 블로그에 「GA4 쿠키 없이 쓰기」라는 글을 썼습니다. clientstorage: 'none' 으로 쿠키 저장을 끄고, 자체 분석이 쓰던 익명 ID 를 clientid 로 넘기면 쿠키 0개로 GA4 를 쓸 수 있다는 내…
GA4 Measurement Protocol: gtag.js 없이 서버에서 이벤트 보내기
랜딩 페이지의 전송량을 파일 단위로 쪼개 보다가, 가장 큰 파일이 우리 코드가 아니라는 것을 알았습니다. Google Analytics 의 gtag.js 였고, 방문 한 번에 176KB 를 받고 있었습니다. 페이지 전체가 1,094K…
중소 제조업 AI 도입 순서: DX를 먼저 끝내야 할까?
공장을 가진 중소·중견 제조기업 16만여 곳 가운데 스마트공장을 도입한 곳은 19.5%입니다. 회사가 작을수록 이 비율은 더 떨어집니다. 중소벤처기업부가 2025년 4월에 낸 제1차 스마트제조혁신 실태조사 결과입니다. 그림: 기업 규…
Next.js loading.tsx와 404: 버튼이 화면보다 먼저 살아나게 하기
관리 화면 왼쪽 위에 사이드바를 접고 펴는 ☰ 버튼이 있습니다. 폭 하나 바꾸는 버튼인데, 대시보드에서 누르면 2초 넘게 아무 반응이 없었습니다. 레이아웃만 바꾸는 일이 왜 이렇게 오래 걸리는지부터 들여다봤습니다. Next.js 16…