CentricMinds

Updating of CentricMinds Digital Workplace Solutions

For 15+ years, CentricMinds has offered a Digital Workplace Solution for organisations of all sizes. Joining the team, I started redesigning the outdated and complex backend CMS to improve user experience and functionality.

Objectives

  • Modernize the CMS Interface
  • Improve usability for admin and content creators.
  • Move features to the front-end workspace
  • Improved content authoring experience
  • Update the design and styles

Team

  • UI/UX Designer (me)
  • Business Owner
  • Developers
  • Project manager
  • Customer Experience Manager

Getting started

Reviewing & asking questions

I reviewed the CentricMinds CMS and documented the workflows, including screenshots. This allowed me to ask questions and identify opportunities to improve the UI and UX experience. Invision App was essential for adding comments to the screens, asking about CMS features, and getting clarification from the developer team.

Insights

Opportunities

Insights

Customer comments and my review:

  • I can’t find content that I need to edit
  • Difficult for non-technical users to navigate
  • Too many pop-up windows; I get lost in them
  • Training is needed to use the CMS admin
  • Poor contrast and colour affecting readability
  • Cluttered interfaces

Opportunities

Design

  • Consistent icons and file types
  • Update colours and typography for a cleaner look
  • Remove multiple overlays
  • Update form library with updated components
  • Move popular CMS features to the frontend workspace

Navigation, Accessibility & User Guidance

  • New primary and secondary navigations
  • Improve the site publishing flow
  • Increase text sizes, buttons and icons
  • Updated colours inline Web Accessibility

Redesign v’s Reskin

Pivoting from redesign to reskin

I initially suggested that we do a reskin before we started the project. I had timing concerns for the backend redesign, build, and testing. As we transitioned into the design phase, we decided to move forward with the reskin option.

Current CMS
New Design
Reskin

Re-skin of the CMS

The reskin involved replacing the old style and refreshing the CMS interface. This included updating colours, typography icons, and other interface styles.

Previous
Next

Overlay modal v’s fullscreen modal

I recommended using the fullscreen modal due to its better user experience. Fullscreens adapt to screens and reduce vertical scrolling. Unfortunately, the decision was made to stay with the current modal. I introduced the option for the user to expand the modal to fullscreen.

Lightbox style with background overlay
Fullscreen modal

Style guide and component library

It was essential to provide a style guide that would work for both CMS and front-end workspaces. I put together a component library with options for developers to use.

Opting for fewer color options made it more efficient for the developers to implement changes across the CMS and frontend workspace.

Updating the frontend

Part of the project involved updating the frontend workspace, which included a reskin and the redesign of various areas.

Moving admin features

The next step was moving admin features to the frontend workspace, such as setting up your styles and managing teams, tasks, and workflows.

I focused on user-friendly solutions that were accessible to the team without dealing with the complex CMS.

Add your logo and brand colours
Management of teams and users
Plan, organise and visualise your tasks from one dashboard
Automate requests and approvals with workflows
Previous
Next

Summary

Learnings

As much as I wanted to undertake a redesign, I recognised that this approach needed to be lean. That decision opened the next phase of moving critical features to the front-end build, allowing ongoing improvements and an updated user experience. 

Challenges

CentricMinds CMS is powerful but can be complex and confusing for non-technical administrators. I had to navigate the admin workflows and ask numerous questions to understand it better. However, collaboration was limited due to our small team and time constraints.