Workview is a flexible and powerful web-based database management and collaboration platform that can solve several Business challenges. It enables teams to share data and develop customizable applications, fostering collaboration and cooperation Throughout the entire organization.
Role
UX/UI Designer · End-to-End Design
Scope:
Full-cycle product design: discovery, UX strategy, system architecture, interface design, 300+ screens
Stage:
Early-stage startup under NDA - 0→1 product definition
Timeline:
2022-2023
Overview
Workview is designed to be installed seamlessly as an infrastructure solution for businesses of all sizes. Opens up opportunities for enhanced business interaction, as it allows users to use both our applications and create their own, integrating them into our platform, for process flexibility and solving various kinds of problems. The uniqueness of our project was that each participant in our product could customize the platform for their personal needs. The infrastructure of the project is intended for companies that need a sale host and want to close various business niches. Some businesses need some kind of back office. These are the back offices that we designed. As an open-source code, we can give the developer instructions on how to write such applications. Thus, they can implement their own applications on one platform, building their business in one place.
Context
I worked on a scalable B2B platform for communication, data management, and process automation.
The product included:
• Video calls and chats

• Data management

• Workflow automation

• Custom forms

• Permission-based collaboration

• Built-in applications

The solution was designed as a universal system for various industries, from banking to healthcare. The project is under NDA, so some details are restricted.
Problem
Businesses were using disconnected tools for communication, data management, and automation, which led to:
• Fragmented workflows
• Manual operations
• Errors
• Dependence on the engineering team
We built a platform that unifies data, communication, and automation within a single logical system. User needs were understood based on data and tasks provided by the client.
Product Vision
The vision was to give business teams a flexible workspace to manage data, automate workflows, communicate, and create custom applications without relying on developers for every change.

My Role
I was responsible for:
• Product structure and information architecture (IA)
• UX architecture
• Workflow design
• Design system and component library
• Permission logic UX
• Product visual direction
Worked closely with business analysts and the development team.


Constraints / Trade-offs
• Startup without an active user base
• Limited resources
• No quantitative research or usability testing — the client was conserving resources
• Project at the MVP stage
Decisions were made based on client interviews, analysis of the provided data, and product thinking.

Research & Insights
We relied on data and feedback from the client. Key insights:
• Businesses need flexibility without involving developers
• Different roles require different access levels
• Automation must be built into the core of the system
• Table-based logic is familiar to users
• Communication should happen within the context of the data
These insights shaped the product architecture.




Core Product Architecture
The system was built on tables, which serve as:
• A data repository
• The workflow hub
• The foundation for automation
• The collaboration point Data + Communication + Automation are unified within a single logic.

Key Design Decision
1. Table-driven system
Decision: the whole product is built on tables.
Why: client interviews showed that business teams need flexibility without involving developers, and that table logic is familiar to users. Tables also scale easily.
2. Granular permission configurator
Decision: a role-based system where access is set per role and user type.
Why: different roles need different access levels.
3. Built-in automation flow
Decision: trigger-based automation inside the database.
Why: automation had to be part of the core of the system. It saves users time on repeated work.
4. Modular view system
Decision: the same data can be shown as a table, a form, an overview or a built-in application.
Why: different teams need to see the same data in different ways.
5. Integrated communication
Decision: chats and video calls sit inside the work data.
Why: communication should happen in the context of the data.
6. Option sets from other projects
Problem: users can create option sets for multiple-select columns from scratch or pull a set from another project. What happens if the source project is deleted?
Options: add a search (lookup) inside the set table, or leave search for a later version.
Decision: show an error in the affected set. Search is not in the first version.
Why: a quick start for v1. Search helps navigation, but the product works without it.
Trade-off: in v1 users find a set by scrolling the list.

Design System
I created a scalable design system that included:
• A tokenized color system
• A typographic hierarchy
• A state system
• Permission-based UI patterns
• Adaptive components
• A structured component library
The system ensured consistency, accelerated development, and enabled easy scalability.



Collaboration
I was the only designer. I worked with business analysts and the development team. Decisions were informed by client interviews and client-provided data.
Product Outcome
The platform is:
• Scalable and flexible
• Adaptable to different industries
• Supportive of digital transformation
Delivered: the full MVP design, 300+ screens, a tokenised design system and a component library, handed over to the development team.
Status: the project is ongoing.
Not measured: the client chose not to fund user research, usability testing or analytics at this stage, so I have no usage data.
What I would track next: time for a new user to create the first table, and the share of users who set up permissions without help.

Key Learnings

Designing complex systems requires architectural thinking

Permission logic is a key element of enterprise UX

Strategic thinking is critical under limited resources

Automation should be designed at the core level





