Covision

Redesigned an event management CMS so planners can build branded, mobile-ready attendee experiences, on top of the existing system instead of a rebuild.

Role
Senior Product Designer
Timeline
4 months
2025
Scope
Research, IA
UX prototyping

Visual design
Worked with
CEO
Product

Developers

(handoff & support)
Industry
Event management
B2B SaaS
Powerful CMS to manage live events: the redesigned Covision event overview, page builder with its Insert Content menu, and the attendee app on a phone
The redesigned CMS, from event overview to the page builder and the attendee app it produces.

Overview

A CMS built without a design team

Covision is a platform for planning in-person, virtual, and hybrid events. Event teams use its CMS to build agendas, manage speakers and attendees, and share content with interactive tools.

The CMS was built without a design team. Developers made most decisions, which led to a clunky, hard-to-use tool. Event teams couldn't deliver modern experiences: mobile-friendly, personalized, and interactive events.

Key issues

What was getting in the way

Important tools were hard to find

Key features were buried deep in a cluttered side menu, making them hard to access and slowing down workflows. It increased cognitive load and made core tasks feel hidden or less important.

Before: event details page with a long side menu of expanding sections such as Attendees, Agenda, Materials, Engagement Tools, Setup, Data Import, Custom Fields, Sessions and App Designer
Before: a cluttered side menu with multiple expanding sections.

Flat tables with no visual hierarchy

Every page used the same plain layout, whether editing the homepage, managing attendees, or updating speakers. Nothing stood out, so planners couldn't tell what mattered, where they were, or what they were editing.

Before: sessions shown in a dense plain table with columns for name, description, speakers, date, collection, status, access control, time slot and location
Before: sessions shown in a plain table with no visual cues.

An outdated page builder with no attendee preview

Modules were basic links with limited layout control, no visual preview, and no styling options. Planners couldn't create engaging, on-brand experiences, only rigid, outdated pages.

Before: the page designer as a plain list of modules such as Main Banner, Agenda, Q&A, Logistics and Knowledge Base, with no preview
Before: the page builder had very limited layout controls and no styling options.

Every improvement was designed to fit the existing system, making it quick to build and simple to scale.

With developers in mind The approach behind every change

/01. Page builder

The page builder became the core of the attendee experience

I redesigned the page builder so planners can create branded, mobile-ready pages that match exactly what attendees will see. It's simple but flexible: text, images, videos, links, agendas, speaker lists, carousels and more, all from one menu.

The live preview updates in real time and works on any device. Planners can switch between desktop and mobile views and fine-tune each layout, so experiences work across screens.

Page builder: page navigation and content list on the left, the Insert Content menu, a live mobile preview of a Quick Guide link collection, and its style, design and options settings on the right
Building a page with a live mobile preview.

/02. Components

A library of components for every kind of event

I expanded the component library with agendas, speaker lists and link collections, on top of text and media. Planners mix and match modules to build pages that fit their event.

Each component has built-in settings for layout, colors, visibility and behavior. Changes show up instantly in the live preview.

Desktop preview of an event home page with a featured Next Session agenda card and Meet Our Speakers, with the agenda component's style, content and card settings
A featured agenda component in the desktop preview.
Component settings panels for image, text, link collection, people and agenda, next to the components they produce: slideshows, grids, carousels, featured speakers, video, up next and pills
Component settings and the attendee-facing components they produce.

/03. Audience targeting

Personalized content without duplicate pages

Planners can now control who sees what, down to specific components on a page. Dynamic labels based on attendee data, such as role, department or session attendance, personalize content for different groups.

For example, a resource list can show only for attendees in the marketing team who joined a specific session, or a welcome message can change based on someone's role. Planners get more control without creating separate pages for every variation, and attendees get the relevant, personalized experience they expect.

/04. Brand style

Brand controls keep everything on-brand

Planners set logos, colors and fonts in one place. The styles apply automatically across all pages and components, so buttons, backgrounds and text always follow the brand, with no manual edits.

Brand Style settings: event logo, light, dark or auto color theme, core and state colors, and typography, with the mobile preview updating to match
Brand settings apply across every page and component.

/05. Event overview

A clear starting point for planners

A new overview page shows key event information at a glance: registrations, session attendance and recent signups. It highlights today's sessions and offers quick links to common actions.

Planners no longer dig through menus. They start with a clear view of what's happening and act with fewer clicks.

Event overview for the Annual Company Summit: quick actions, when and where, today's sessions with RSVPs, recent registrations, and charts of event registrations and session attendance
The event overview page.

/06. Product architecture

Improving the architecture without breaking what worked

I didn't try to rebuild the platform from scratch. Instead, I worked closely with developers to make it easier to use, maintain and improve over time. Most existing pages stayed as they were at first, reorganized into a clearer structure that reflects how event teams actually work.

New information architecture: an Event with Manage Pages for marketing and in-event pages, and sections for Overview, Agenda, Attendees, Content, Communication, Engagement and More
The new structure, organized around how event teams work.

This made it possible to add new features, refresh old ones and improve the experience step by step, without slowing down development or creating extra work. It also gave developers a cleaner, more scalable foundation to build on.

The Content section in the new navigation, with an existing assets page embedded inside it and a note: existing pages are embedded in the new structure until developers prioritize them
Existing pages are embedded in the new structure until developers prioritize them.

Key takeaways

Beyond screens: structure, systems, and how teams really work

This project was a deep dive into untangling messy workflows and making a CMS actually feel usable. It touched many parts of the product.

  1. Building on top, not starting over

    The biggest challenge was designing for something that already existed. I had to respect the system, clean it up, and build on top of it without breaking things for planners or developers.

  2. Clarity drives confidence

    The more I simplified, the more everything clicked. Clear navigation, consistent components and previews that work aren't flashy, but they help planners move faster and trust what they build.

Tell me what you're building, and I'll ask a few questions to understand it.

← Back to Selected Works
Ask Elisey anything…AI chat

Go to

Selected WorksPage
Work ExperiencePage

Case studies

CiteMedAI-assisted clinical-evidence platform • 2026Case study
Health VisionAI-powered clinical intelligence platform • 2026Case study
CovisionEvent management SaaS • 2025Case study

Contact

Email Eliseyhello@eliseykolev.comCopy
Visit LinkedIn ProfileLink
Elisey Kolev
Ask Elisey TabAsk Elisey ↵