Case Study

Deka Pro

Unifying Enterprise Fragments into a Single Workspace

Deka Pro was built for UAB NEVDA to solve workflow fragmentation across tasks, time tracking, and document systems.

Within a broader NEVDA product landscape (roughly 10 active products), Deka Pro became the execution layer where teams plan, communicate, and move work forward. The objective was to transform scattered information into one actionable workspace.

Executive Summary

Teams were losing time to context switching across multiple tools for tasks, time, and documents.

I designed Deka Pro as a unified execution workspace with synchronized views, task-level communication, and direct integration with Kontora data.

The result was less workflow fragmentation, higher daily usage, and a clearer source of truth for cross-team delivery.

Role & Scope

Role: Lead Product Designer

Scope: Workspace architecture, information hierarchy, multi-view interaction model, and contextual collaboration patterns.

Collaboration: Worked with product and engineering teams to align interface decisions with live backend workflows and cross-tool synchronization constraints.

01. Main Workspace: Dashboard Views

The workspace evolved into multiple coordinated views — list, calendar, communication, Kanban board, and status — so teams can track the same work in whatever layout fits the moment, without losing context.

Deka Pro — Kanban board view — 05 Kanban board

02. Context: The Fragmentation Tax

Users were switching between three tools for one project: one for tasks, one for time tracking, and Kontora for documents.

This context switching caused lost information and lower productivity because work status was fragmented across systems.

Ecosystem Relationship Map

System Context

Kontora-Centered Ecosystem Diagram

Diagram framing Kontora as the data engine and Deka Pro as the execution interface connecting tasks, time tracking, and communication flows.

03. Design Strategy: Contextual Interoperability

We did not build only a task list. We built a live-sync environment where every action in Deka Pro reflects across the broader NEVDA product ecosystem.

A flexible toggle between Kanban and list views allowed users to work in the mental model that fits them best, without losing context.

Communication was embedded directly into tasks so updates and decisions remain attached to the work itself, not scattered in separate chat tools.

View Flexibility: Kanban and List

Interaction Model

Kanban vs List Split Screen

Split representation of board and list modes, highlighting the toggle that preserves user preference without losing task context.

Drag across the comparison to see how the same workspace shifts between list and Kanban without disrupting task continuity.

Deka Pro Kanban-priority split-screen variant

Deka Pro list-priority split-screen variant

List-first Kanban-first

Contextual Collaboration Inside Tasks

Embedded Communication

Task Detail Sidebar with Chat/Activity

Task detail structure where activity updates and conversation remain attached to the work item, reducing communication drift across tools.

Deka Pro contextual collaboration view showing environment conversations attached to task context — 01 Environment

Deka Pro status communication interactions embedded in task details — 02 Status

Deka Pro sub-task communication stream tied to the active work item — 03 Sub-task

Deka Pro task communication panel where activity and chat remain attached to the task — 04 Task

04. Discovery: Workflow Audit

User interviews showed that "Done" means more than checking a task box. It often requires updating linked documents in Kontora, which made cross-tool fragmentation especially costly.

Journey Compression: Before and After

Workflow Evidence

Before vs After Journey

Workflow comparison from a multi-app sequence to an in-platform flow, demonstrating reduced steps and lower execution overhead.

05. Impact: Measuring the Shift

30%

Increase in daily active usage after migration to Deka Pro

Unified source of truth through direct sync with Kontora data

8px

Grid system used to keep dense interfaces breathable and consistent

Less

Context switching and double-entry overhead for teams

06. Final Reflection

Deka Pro proved that the best interface often disappears into workflow clarity. By creating a seamless bridge to Deka Office backend systems, teams could focus on outcomes instead of software coordination overhead.