GTOX Share Redesign

Redesigned the share functionality on CGI's internal platform (GTOXperience) to increase feature adoption among consultants by addressing critical usability barriers.

Client

CGI Inc.

Role

Designer

Team

1 Product Owner, 1 Designer, 1 Developer

Timeline

3 weeks — Shipped Q4 FY2025

Skills

User Research | Design Systems | Prototyping | Figma

Outcome

Transformed an unused feature into a daily-use tool for consulting teams

(001)

— What's GTOXperience?

GTOXperience is an internal platform for CGI consultants to learn about IT services offered by the Global Technology Operations (GTO) business unit and easily access sales enablement materials.

A one-stop shop for service learning and sales enablement materials.

Some numbers for context:

35+

Services Featured

200+

Documents, Materials and Tools

3,000+

Visits Per Month

(001)

— What's GTOXperience?

GTOXperience is an internal platform for CGI consultants to learn about IT services offered by the Global Technology Operations (GTO) business unit and easily access sales enablement materials.

A one-stop shop for service learning and sales enablement materials.

Some numbers for context:

35+

Services Featured

200+

Documents, Materials and Tools

3,000+

Visits Per Month

(002)

— Problem Identification:

(002)

— Problem Identification:

"We had a built-in share functionality on the platform, but no one was actually using it. Everyone is sharing content manually."

Problem:

Usage data revealed the share feature had minimal adoption even though consultants were sharing content regularly, which indicates a clear usability issue.

Design goal:

Redesign the share features to improve usability, clarify sharing options and increase feature adoption among consultants.

(003)

— Research Insights.

(003)

— Research Insights.

Through interviews and observational research with senior leadership, I identified three issues with the initial share functionality.

#1

Lack of Microsoft Teams integration:

CGI consultants preferred sharing through Teams, but the feature lacked this option, forcing them to manually copy URLs from the address bar instead.

#2

Lack of context:

Consultants couldn't preview what they were sharing before sending, making them feel uncertain about what content would be distributed to clients or colleagues.

#3

UI inconcistencies:

Visual elements were misaligned, some buttons were hidden, and inconsistent colour and typography made the layout look unpolished and uninviting.

(004)

— Brainstorming & Ideation.

(004)

— Brainstorming & Ideation.

To map out the redesigned experience, I created a user flow that illustrates how users would navigate the system step by step. This helped identify key decision points and ensure my redesigned version supported all 3 sharing options.

(1) Share with clients | (2) Share with CGI colleagues | (3) Share this page

(1) Share with clients | (2) Share with CGI colleagues |
(3) Share this page

(005)

— Testing & Iterations.

(005)

— Testing & Iterations.

After creating high-fidelity prototypes using CGI's design system, I tested them with users and the developer. We discovered Outlook had file size restrictions, so sharing multiple documents at once wouldn't go through. To fix this, I suggested that we switch from square buttons to radio buttons for the "share with colleagues" option, making it clear users could only share one document at a time.

After creating high-fidelity prototypes using CGI's design system, I tested them with users and the developer.

We discovered Outlook had file size restrictions, so sharing multiple documents at once wouldn't go through. To fix this, I suggested that we switch from square buttons to radio buttons for the "share with colleagues" option, making it clear users could only share one document at a time.

(006)

— Final Design.

#1

Share with clients:

Send brochures to clients via Outlook with clear delivery confirmation.

My design rationale:

Refined popup layout: I cleaned up the card with consistent alignment, spacing and styling in accordance to CGI design systems.

Interactive feedback: I added input states (purple on focus, red on error) for immediate feedback.

Confirmation flow: The popup now closes automatically after sharing, with a success or error alert in the top-right corner.

#2

Share with CGI colleagues:

Select specific documents to share with CGI colleagues via email with clear visibility into what's being sent.

My design rationale:

Document selection: I added the option allowing users to select which documents they want to send to colleagues, giving them control over what gets shared.

#3

Share this page:

Generate and share a link to the current page via Teams, email or manual copy for maximum flexibility.

(The website is internal and only accessible to CGI employees.)

My design rationale:

Expanded sharing options: The original feature only let users email a page link. I added Teams integration and a "Copy URL" option so users could share through whatever platform works best for them.

(006)

— Final Design.

#1

Share with clients:

Send brochures to clients via Outlook with clear delivery confirmation.

My design rationale:

Refined popup layout: I cleaned up the card with consistent alignment, spacing and styling in accordance to CGI design systems.

Interactive feedback: I added input states (purple on focus, red on error) for immediate feedback.

Confirmation flow: The popup now closes automatically after sharing, with a success or error alert in the top-right corner.

#2

Share with CGI colleagues:

Select specific documents to share with CGI colleagues via email with clear visibility into what's being sent.

My design rationale:

Document selection: I added the option allowing users to select which documents they want to send to colleagues, giving them control over what gets shared.

#3

Share this page:

Generate and share a link to the current page via Teams, email or manual copy for maximum flexibility.

(The website is internal and only accessible to CGI employees.)

My design rationale:

Expanded sharing options: The original feature only let users email a page link. I added Teams integration and a "Copy URL" option so users could share through whatever platform works best for them.

(007)

— Reflection.

(007)

— Reflection.

What I learned:

Testing early with developers and users helps catch technical constraints and usability issues before they become problems. The simplest solution is often the right one.

Looking ahead:

While this redesign addressed the main usability issues, I believe there's always opportunity to gather usage data post-launch and continue refining based on how people actually use the feature.

No heading elements found. Showing placeholder content.