Improving workflows across Accedo One
Accedo One is a customer-facing streaming platform used to create, configure, build, and manage mobile, web, and TV streaming applications. This case study highlights selected workflow improvements across the platform, including navigation, build management, and guided content-configuration flows.
- Role
- Senior Product Designer
- Focus
- Platform UX · App workflows · Design systems
- Users
- Non-technical and semi-technical operators
- Product
- Streaming platform / app builder
Overview
Accedo One supports teams building and managing streaming applications across mobile, web, and TV. My work spanned both the Admin platform and app experiences within the broader ecosystem, with this case study focusing on selected improvements that made complex capabilities easier to understand, configure, and use for non-technical and semi-technical operators.
My role
I worked hands-on across UX, UI, interaction design, design-system components, implementation reviews, and design QA, collaborating closely with product and engineering. My work spanned both the Accedo One Admin platform and app experiences across mobile, web, and TV, supporting customers building and managing streaming applications.
Design challenge
Accedo One gives customers flexibility to configure and manage streaming products across multiple platforms. The design challenge was to make powerful configuration and delivery tools clearer, more accessible, and easier to act on without hiding the complexity customers needed.
Selected improvements
Rather than one single large project, this case highlights three focused improvements that supported the same product goal: making Accedo One easier to navigate, configure, and operate.
- Page header and navigation system
- Build view improvements
- New content container flow
Page header and navigation system
I redesigned page headers across the Accedo One Admin app to improve readability, accessibility, visual hierarchy, and navigation clarity. The headers acted as key entry points into different Admin sections, so the work focused on making them clearer, more consistent, and easier to scan across the platform.
What changed
- Improved contrast, readability, and visual hierarchy across Admin section headers.
- Created a more consistent header system across product areas.
- Refined colors, styling, and header layouts to better support accessibility and scanning.
- Iterated with the team on colour choices, using AI-assisted contrast checks to improve readability and meet accessibility requirements.
- Designed sticky and minimized states to keep section navigation available while scrolling.
- Created supporting left-navigation icons as part of the broader Admin navigation update.
- Added responsive overflow behaviour for sections with many navigation items.
Readability and hierarchy detail
The redesign improved contrast, spacing, and hierarchy so section titles and navigation items were easier to scan across Admin and met accessibility requirements.
For sections with many navigation items, I also defined responsive overflow behaviour so lower-priority items could move into a ‘More…’ menu when space became limited.
Build view improvements
I improved the Build view, where customers manage app builds, trigger new builds, publish builds, download build artefacts, and investigate failed builds.
Rather than showing every state in the flow, this section focuses on the moments where the redesign made the workflow clearer: managing builds, triggering actions, and understanding failed states.
What changed
- Added a contextual header with app/platform information, logo placement, and clearer navigation between related configuration areas.
- Clarified build status and available actions on build cards.
- Improved the trigger-build flow and modal experience.
- Made failed build states and log access easier to find and understand.
- Supported publishing, downloading, and related delivery actions.
- Made the workflow easier for semi-technical users managing app delivery.
Build list clarity
Earlier
Build information was shown in a compact card layout, making status, version details, and available actions harder to scan at a glance.
Redesigned
The redesigned view added clearer app context and configuration navigation, then moved builds into a table structure so status, version, build time, and actions were easier to compare and act on.
Triggering a build
Earlier
The trigger build action sat within the page flow, with limited guidance around the selected version and next step.
Redesigned
A focused modal clarified the selected build version and gave the user a clear primary action before starting a new build.
Failed build handling
Earlier
Error information was present, but it was harder to scan and understand what needed attention or where to find more detail.
Redesigned
The failed state made the problem more visible and provided clearer access to logs or supporting information for troubleshooting.
New content container flow
I streamlined the flow for adding a new content container by introducing a guided wizard. The goal was to help customers move through layout, naming, playlist type, and content selection step by step, reducing uncertainty during setup.
The wizard broke the setup process into clearer decisions, making it easier for users to understand what they needed to choose before creating a new content container.
Guided wizard sequence
1. Choose container layout type
2. Name the container
3. Choose container feed type
4. Configure manual feed
5. Review and create selected playlist
From less guided setup to a guided wizard
Less guided setup
The earlier flow placed container setup inside the Editor app preview, with limited guidance around the order of configuration decisions.
Choose layout type
The wizard introduced a clear first step, helping users begin with layout before moving through the rest of the setup sequence.
Clearer separation of setup decisions
Combined configuration choices
Layout, naming, and feed choices were less clearly separated, making it harder to understand what to decide next.
Choose feed type
The wizard separated feed type selection into its own step, helping users choose between manual, dynamic, and playlist feeds before continuing.
Clearer review before creating the container
Harder to review before creating
The earlier final step made it harder to review selected content and confirm the create action before finishing.
Review selected items and create
The wizard ended with a dedicated review step for the selected manual feed, making selected items and the final create action clearer before completing setup.
Customer design reviews
Alongside product design work, I held design review sessions with customers. I reviewed applications they had built using Accedo One, discussed areas for improvement, and highlighted Admin capabilities they could use to improve layout, navigation, and content presentation.
Outcome
Across these improvements, the work made Accedo One easier to navigate, configure, and operate. The redesigned header system improved orientation and readability across Admin, the Build view made technical build states and actions easier to scan, and the guided container wizard helped users move through setup one decision at a time.
- Clearer navigation and visual hierarchy across Admin sections
- More scannable build status, actions, and configuration context
- A guided container creation flow that reduced uncertainty during setup
Other cases
Read more of my case studies
Deutsche Telekom - Magenta TV
Long-term product design across mobile, tablet, and TV, shaping clearer ways to browse, watch, and return to content while adapting shared product logic across devices.
Deutsche Telekom XR Sports
Designed a complex XR sports product for Meta Quest 3 and Apple Vision Pro, combining live and post-match content, real-time data, replays, and multi-camera viewing within a tight delivery timeline.
LEGO TV
Sole designer for a child-friendly Smart TV product, leading discovery, UX/UI design, and usability testing with children to simplify navigation and content discovery.