Chipcon 2.0 Proposal

Chipcon 2.0 Proposal

Chipcon 2.0 Proposal

Leveraging UI/UX design to enhance the usability of Chipcon, there by driving business success by securing the proposal.

Disclaimer: Due to a non-disclosure agreement with the client, all content, UI elements, and confidential data have been replaced with placeholders and dummy data.

Role

UI/UX Designer

Industry

Semiconductor

Duration

3 Weeks

Business Goal

Business Goal

—> To secure a considerable budget through this proposal.

—> To secure a considerable budget through this proposal.

—> Help increase sales for client.

—> Help increase sales for client.

Project Goal

Project Goal

—> Improve the system architecture and user experience.

—> Improve the system architecture and user experience.

—> Make application scalable for future.

—> Make application scalable for future.

Discovery.

Discovery.

Discovery.

What is currently happening ?

The main users of the application are test engineers who work in various other organisations. Since we worked as service partner, we were not able to do an extensive research as we had minimal exposure to the users. But we were able to meet a handful of users and also got help from various stakeholders to gather more insights.

Define.

Define.

Define.

What do we need for the proposal?

From the discussions with users and stakeholders, conducting usability testings, we were able to uncover a list of problems and pain points. Working sessions were conducted with the stakeholders to organise the problems, helping us prioritise our efforts.

Problem Definition.

Problem Definition.

Problem Definition.

1.Onboarding

1.Onboarding

1.Onboarding

  • 3 to 5 hours of training

Onboarding and getting started with the application is difficult and takes more time and effort.

Onboarding and getting started with the application is difficult and takes more time and effort.

Onboarding and getting started with the application is difficult and takes more time and effort.

2.Information Architecture

2.Information Architecture

2.Information Architecture

  • Unconventional Workflows

  • Unrelated configuration in single page

  • Not intuitive

Information is spread randomly and making things confusing.

Information is spread randomly and making things confusing.

Information is spread randomly and making things confusing.

3.UX Writing

3.UX Writing

3.UX Writing

Headings and labels are not clear enough for the user to understand what is or will happen.

Headings and labels are not clear enough for the user to understand what is or will happen.

Headings and labels are not clear enough for the user to understand what is or will happen.

Ideation.

Ideation.

Ideation.

How are we going to do it?

From the discussions with users and stakeholders, conducting usability testings, we were able to uncover a list of problems and pain points. Working sessions were conducted with the stakeholder to group the problems, helping us prioritise our efforts.

1.Onboarding

1.Onboarding

Onboarding and getting started with the application is difficult and takes more time and effort

There’s no dedicated onboarding flow, so a client representative currently has to demo the application to every new user. Adding an onboarding flow with GIFs or videos in a carousel to showcase features and usage can eliminate the need for manual training.


The application lacks empty states. When a new project launches, it opens with default configurations, leaving users confused about where to start and how to navigate the app. To address this, empty states with intuitive messages and clear CTAs were introduced, guiding users on where to start and how to navigate.

2.Information Architecture

2.Information Architecture

Information is spread randomly and making things confusing

Information was scattered across various pages, making it difficult to navigate. A proper information architecture was implemented, grouping global operations together, adding a new page for DIO configuration, and moving the protocol register map to the register map page, among other improvements.

3.UX Writing

Headings and labels are not clear enough for the user to understand what is or will happen.tion is spread randomly and making things confusing

The application had popups with misleading headings, unclear error messages, and vague CTA labels.

Headings, CTA labels, error messages, and other content were refined for clarity, improving the overall intuitiveness of the application.

Delivery.

Delivery.

Delivery.

How did the proposal go?

We presented our approach to enhancing the UX and system design, supported by compelling data. The proposal was successful, resulting in budget approval. The improvements made to the UX were crucial in securing the proposal.

What Next?

What Next?

What Next?

There is always scope for improvement. As the primary focus was on the proposal, some solutions have not been fully validated for optimal usability. Conducting usability testing presents an opportunity to refine the design further, and these enhancements will be addressed in the Chipcon 2.0 delivery phase.

There is always scope for improvement. As the primary focus was on the proposal, some solutions have not been fully validated for optimal usability. Conducting usability testing presents an opportunity to refine the design further, and these enhancements will be addressed in the Chipcon 2.0 delivery phase.

Predicted Impact

Predicted Impact

Predicted Impact

Reduced onboarding time from 3 to 5 hours to a matter of minutes.

Reduced onboarding time from 3 to 5 hours to a matter of minutes.

Reduced onboarding time from 3 to 5 hours to a matter of minutes.

No need for a person to teach the application.

No need for a person to teach the application.

No need for a person to teach the application.

Better UX writing providing clarity for the user.

Better UX writing providing clarity for the user.

Better UX writing providing clarity for the user.

Revenue for the company.

Revenue for the company.

Revenue for the company.

The clients recognised the importance of UI/UX design and the profound impact a designer can have on the success of a project.

The clients recognised the importance of UI/UX design and the profound impact a designer can have on the success of a project.

The clients recognised the importance of UI/UX design and the profound impact a designer can have on the success of a project.

Learnings.

Learnings.

Learnings.

Working effectively with stakeholders

Working effectively with stakeholders

Working effectively with stakeholders

Working effectively with stakeholders is essential to designing a successful software solution, especially when dealing with B2B clients, where numerous constraints often come into play.

Working effectively with stakeholders is essential to designing a successful software solution, especially when dealing with B2B clients, where numerous constraints often come into play.

Working effectively with stakeholders is essential to designing a successful software solution, especially when dealing with B2B clients, where numerous constraints often come into play.

Enterprise and Consumer UX are not too different

Enterprise and Consumer UX are not too different

Enterprise and Consumer UX are not too different

Consumer UX is deeply ingrained in everyone's mental model. Don't shy away from using some of it's best practices in Enterprise too!

Consumer UX is deeply ingrained in everyone's mental model. Don't shy away from using some of it's best practices in Enterprise too!

Consumer UX is deeply ingrained in everyone's mental model. Don't shy away from using some of it's best practices in Enterprise too!

MAIL ME

kabilyogeshtamilselvan@gmail.com

©2025 Kabilyogesh. Crafted personally with Framer.