V-CONNECT LEARNING PLATFORM REDESIGN

Turning an internal B2B tool into a market-ready product for launch

ROLE

UX Design, User Research

TIMELINE

3 months

STATUS

Live Site

CONTEXT

V-Connect began as an internal learning tool used to host and manage company-led employee enrichment courses. It functioned as a service layer rather than a standalone product.

PROBLEM

The platform was not designed for external clients.
Workflows, language, and assumptions reflected internal use, limiting its viability as a customer-facing offering.

CHALLENGE

Transform an internal tool into a market-ready B2B learning platform without losing the operational efficiency that made it valuable internally. This required validating real user needs, clarifying the product’s value proposition, and redesigning the experience for scale.

OUTCOME

Led the redesign end-to-end, grounding decisions in user research and close collaboration with engineering to deliver a standalone, customer-ready learning platform.

SCOPE & RESPONSIBILTY

Research

Working with existing users’ insights

Design

Developing while coordinating with product owners

Iteration

Implementing feedback from leadership up to the CEO

Delivery

Ensuring proper handoff to engineering and development

REAL-WORLD CONSTRAINTS

Legacy Internal Workflows

Tight Engineering and financial limitations

Balancing internal user needs with market expectations

Fixed timeline set for product launch

UNDERSTANDING USERS

Research focused on existing users of the tool inside the company. Research questions focused on what the points of frustration with the current experience were? What are internal legacy processes and shortcuts that you would not expect a new user to know?

1. Batch creation was cognitively demanding and error prone

Facilitators had no clear structure or guidance through the multi step batch creation process, leading to confusion, incomplete setups, and reliance on institutional knowledge.

2. Large, unstructured input forms overwhelmed users

Forms lacked hierarchy and clarity around required versus optional inputs, causing users to stall or miss critical fields.

3. Dense, inconsistent interfaces made it hard to scan and trust the system

Long, text heavy tables combined with inconsistent visual styles made it difficult to get an overview of batches and activities, increasing cognitive load and reducing confidence in the product

FROM INTERNAL TOOL → MARKET PRODUCT .

SIMPLIFYING COMPLEX WORKFLOWS

Problem

Batch creation lacked structure and feedback, forcing facilitators to rely on prior knowledge and trial and error.

Design Tension

Adding structure reduced errors, but too much rigidity limited facilitator flexibility during setup.

Design Decision

Introduce a guided batch creation workflow that provides clarity for new users while preserving flexibility for experienced facilitators.

The Market Ready Outcome

The workflow no longer depends on internal training, enabling external customers to configure batches independently.

1

Step-by-step guided flow

2

Optional shortcuts for experienced users

2

1

3

Progression indicators and save and exit states

3

4

Continued guidance throughout batch creation process

4

REDUCING

COGNITIVE LOAD IN COMPLEX FORMS

Problem

Long, unstructured forms overwhelmed users and led to missed fields or stalled progress.

Design Decision

Reduce visible complexity by clarifying hierarchy and progressively revealing optional inputs.

The Market Ready Outcome

The interface supports confident decision making, reducing setup errors and time for first time users.

1

Suggested defaults and contextual guidance

1

2

Clear distinction between required and optional fields

3

Collapsible functionality to streamline process

3

2

4

Explicit guidance about content while exploring

4

CREATING A READABLE AND CONSISTENT INTERFACE

Problem

Dense tables and inconsistent UI patterns made it difficult to scan information and undermined trust in the product

Design Decision

Standardize interaction patterns and introduce visual hierarchy to improve readability and consistency

The Market Ready Outcome

A consistent, scannable interface supports scale, improves usability, and reinforces product credibility.

1

Filters, sorting, and horizontal tabs for large data sets

2

Iconography and color replacing text heavy indicators

1

2

3

Consistent type scale, icon set, color system and UI components

OUTCOME AND IMPACT

Product shipped to production

Now offered as a standalone solution

1800 participants, 30 + clients

REFLECTION

Research focused on existing users of the tool inside the company. Research questions focused on what the points of frustration with the current experience were? What are internal legacy processes and shortcuts that you would not expect a new user to know?

V-CONNECT LEARNING PLATFORM REDESIGN

Turning an internal B2B tool into a market-ready product for launch

ROLE

UX Design & Research

TIMELINE

3 months

STATUS

Live Site

CONTEXT

V-Connect began as an internal learning tool used to host and manage company-led employee enrichment courses. It functioned as a service layer rather than a standalone product.

PROBLEM

The platform was not designed for external clients.
Workflows, language, and assumptions reflected internal use, limiting its viability as a customer-facing offering.

CHALLENGE

Transform an internal tool into a market-ready B2B learning platform without losing the operational efficiency that made it valuable internally. This required validating real user needs, clarifying the product’s value proposition, and redesigning the experience for scale.

OUTCOME

Led the redesign end-to-end, grounding decisions in user research and close collaboration with engineering to deliver a standalone, customer-ready learning platform.

SCOPE & RESPONSIBILTY

Research

Working with existing users’ insights

Design

Developing while coordinating with product owners

Iteration

Implementing feedback from leadership up to the CEO

Delivery

Ensuring proper handoff to engineering and development

REAL-WORLD CONSTRAINTS

Legacy Internal Workflows

Tight Engineering and financial limitations

Balancing internal user needs with market expectations

Fixed timeline set for product launch

UNDERSTANDING USERS

Research focused on existing users of the tool inside the company. Research questions focused on what the points of frustration with the current experience were? What are internal legacy processes and shortcuts that you would not expect a new user to know?

1.

Batch creation was cognitively demanding and error prone

Facilitators had no clear structure or guidance through the multi step batch creation process, leading to confusion, incomplete setups, and reliance on institutional knowledge.

2.

Large, unstructured input forms overwhelmed users

Forms lacked hierarchy and clarity around required versus optional inputs, causing users to stall or miss critical fields.

3.

Dense, inconsistent interfaces made it hard to scan and trust the system

Long, text heavy tables combined with inconsistent visual styles made it difficult to get an overview of batches and activities, increasing cognitive load and reducing confidence in the product

FROM INTERNAL TOOL → MARKET PRODUCT .

SIMPLIFYING COMPLEX WORKFLOWS

Problem

Batch creation lacked structure and feedback, forcing facilitators to rely on prior knowledge and trial and error.

Design Tension

Adding structure reduced errors, but too much rigidity limited facilitator flexibility during setup.

Design Decision

Introduce a guided batch creation workflow that provides clarity for new users while preserving flexibility for experienced facilitators.

The Market Ready Outcome

The workflow no longer depends on internal training, enabling external customers to configure batches independently.

1

2

1

2

2

Optional Shortcuts for experienced users

1

Step-by-step guided flow

3

3

3

Progression indicators and save and exit states

4

4

4

Continued guidance throughout batch creation process

REDUCING COGNITIVE

LOAD IN COMPLEX FORMS

Problem

Long, unstructured forms overwhelmed users and led to missed fields or stalled progress.

Design Decision

Reduce visible complexity by clarifying hierarchy and progressively revealing optional inputs.

The Market Ready Outcome

The interface supports confident decision making, reducing setup errors and time for first time users.

1

1

1

Suggested defaults and contextual guidance

2

3

2

3

3

2

Clear distinction between required and optional fields

3

Collapsed functionality to streamline process

4

4

Explicit guidance on content while exploring

CREATING A READABLE AND CONSISTENT INTERFACE

Problem

Dense tables and inconsistent UI patterns made it difficult to scan information and undermined trust in the product

Design Decision

Standardize interaction patterns and introduce visual hierarchy to improve readability and consistency

The Market Ready Outcome

A consistent, scannable interface supports scale, improves usability, and reinforces product credibility.

1

2

1

Filters, sorting, and horizontal tabs for large data sets

2

Iconography and color replacing text heavy indicators

3

Consistent type scale, icon set, color system and UI components

REFLECTION

Research focused on existing users of the tool inside the company. Research questions focused on what the points of frustration with the current experience were? What are internal legacy processes and shortcuts that you would not expect a new user to know?

OUTCOME AND IMPACT

Product shipped to production

Now offered as a standalone solution

1800 participants, 30 + clients