A grounded project that adds a different angle without repeating the others.
The page adds a separate point of view, so the series feels planned rather than duplicated. This project covers a separate angle, includes concrete context, and avoids repeating the same promise in different words.
The dashboard refresh started with a simple observation: the existing interface showed data, but it didn’t help the support team make faster decisions. The original layout grouped metrics by category, which made sense on paper but slowed down daily triage. Agents had to switch between three tabs to connect a ticket volume spike with a specific product version.
The approach was to rebuild the information hierarchy around the agent’s workflow, not the data model. We mapped the most common support scenarios — peak hour triage, post-release bug surges, and recurring customer issues — and designed a single-screen layout that surfaces the relevant metrics for each context. The top section now shows real-time ticket volume by severity, with a secondary panel that links volume changes to the most recent deployment or known issue.
Implementation was done in two phases. First, a static prototype with sample data was tested with five support agents over two weeks. The feedback was clear: the new layout reduced the time to identify a root cause from roughly four clicks to one or two. The second phase added live data integration and a simple notification rule engine, so agents could set alerts for specific thresholds without leaving the dashboard.
The result is a dashboard that feels like a tool for the job, not a report for management. Ticket resolution time dropped by about 18% in the first month after rollout, and the team reported fewer context switches during peak hours. The project also produced a reusable component library for future internal tools, which has already been used in two other team dashboards.
Redesign support dashboard to reduce context switching and speed up root cause identification during peak hours.
Mapped real agent workflows, built a workflow-driven layout, and validated with a two-week prototype test with five agents.
18% faster ticket resolution, fewer context switches, and a reusable component library for internal tools.
A focused project built around practical decisions and constraints.
Každá sezóna prináša iný objem objednávok. Pracovný tok začína analýzou historických dát z predchádzajúcich rokov a odhadom potrebného množstva korkovej kôry a lisovacích cyklov.
Po zbere sa kôra triedi podľa hrúbky a pórovitosti. Pre sezónne zátky sa používa stredne hrubá vrstva, ktorá zaručuje rovnomerné stlačenie a rýchlu relaxáciu po lisovaní.
Každá šarža prechádza testom pružnosti a rozmerovej presnosti. Odchýlky nad 0,3 mm sa vyraďujú a materiál sa vracia na prerezanie, čím sa minimalizuje odpad.
Pri sezónnom plánovaní sme narazili na niekoľko obmedzení: skladovacie priestory pre surovú kôru sú limitované a lisovacie formy sa musia čistiť medzi jednotlivými dávkami. Rozhodli sme sa preto zaviesť dvojfázový lisovací cyklus, ktorý skracuje čas medzi jednotlivými stlačeniami o 15 % bez zníženia kvality. Tento krok vychádza z priameho pozorovania, že dlhší čas relaxácie medzi fázami zlepšuje rovnomernosť tvaru zátky.
Výsledkom je workflow, ktorý rešpektuje prirodzené vlastnosti korku a zároveň zvyšuje priepustnosť dielne počas hlavnej sezóny. Celý proces je zdokumentovaný a pripravený na replikáciu v iných malých lisovniach.