Primary Role: UX Designer
Responsibilities: Research and design, user story writing, documentation
Tools: Adobe XD, Sketch, Frontify, Jira, LucidChart
For the next version of CineNet, there was a lot of decision-making regarding the direction of where the product would head. One of the projects that would have to be undertaken in order to support this direction is redoing the UI. The state of the UI currently presents basic usability challenges and isn't scalable for the direction that the product is going.
This became an opportunity to design an interface that closes a variety of usability gaps as well as introduce the design system framework and the process improvements that come along with it.
Because of my experience with supporting CineNet 3.4 and 3.5 when I first onboarded with the company, I have already been thinking about how the product can be improved. This was further supported with some of the research activities that were done
- identifying types of users
- interviewing stakeholders and users
- evaluating the current product and identifying basic usability gaps (whether from workflow or UI)

Ideating on the paradigm of how users interact with the product.

Inclusive Design
During this time, I had also put together a proposal for considering 508 compliance. Because the company has a lot of government clients and the increase of noise in this arena even in the private sector, it was an opportunity to introduce this as part of the new design system.
While I was able to gain support from marketing in this endeavor, in the end, I couldn't convince the decision-maker to its value. Despite this failure, because I was making design decisions for the new design system, there were still low hanging fruit in the WCAG 2.0 guidelines that I am able to implement myself without overstepping boundaries (color contrast, typography, basic usability principles, etc.) because in the end, it will improve the usability of the product and leave the door a bit open if this is a topic to be revisited in the future.

Slide from my presentation on accessibility and section 508.

Ensuring Current Feature Coverage
As part of the redesign, it was important that all the features that are currently available in the product be also available post design system implementation. To help with this, I produced user stories and a site map to keep functionality in check. Because we don't have a product manager/owner, having a log of user stories and acceptance criteria would prove useful in making sure that features don't get left out as well as being a resource for a product manager/owner when one would eventually get onboarded.
The site map was used to help keep track of high level progress of the UI redesign. This also helped make information architecture decisions from a navigation standpoint.

Snippet from Jira, where I kept track of existing features to ensure design coverage for the UI redesign.

Content Strategy
Another effort that has been folded into the design system is defining terminology relevant to the context of CineNet. This started with defining terms for concepts that will be new in the 4.0 version of CineNet. It has been observed that there has been confusion among the use of current terminology that it necessitated this effort. The idea would be that the living document of terms and concepts could be used to help standardize how the CineNet product is being communicated (training, marketing, development, etc.)
With the introduction of the design system brings also process improvements that's meant to maintain communication between different teams and the discipline of having the design system being used in conversations to help keep each other honest and focused.
Ongoing Progress
This project is still ongoing and will be for some time. A lot of work has been done in terms of design, but the final product may vary based on product decisions and priorities that are made.
Back to Top