SBEP Certification Portal

The SBEP Certification Portal was designed to improve how professionals apply for and progress through certification within the Blue Economy. At the time, the process was functioning operationally, but it was held together through manual workarounds, spreadsheet logic, and disconnected evaluation steps.

This project was not simply about designing a cleaner interface. It was about translating a complex certification workflow into a structured digital experience that could support applicants, reviewers, and administrators with more clarity, consistency, and trust.

This project focused on rethinking that experience end-to-end — not just as an interface, but as a complete system that balances complexity, usability, and trust.

Role: Product Designer
Timeline: 2025 – 2025
Scope: End-to-end product design 

A multi-sided platform for musicians and organizers built to reduce fragmented discovery, communication, and self-promotion.

The Problem

The certification process worked, but only because people behind the scenes were doing a significant amount of manual coordination.

Eligibility was being managed through Excel sheets with macros, where conditional logic helped determine whether an applicant qualified for the next stage. While this made the process operationally possible, it also meant that much of the system’s logic lived in a place users could not see or understand. For applicants, decisions could feel opaque. For administrators, maintaining and scaling the process required continuous manual effort.

 

“Put an image of excel sheet here”

 

On the applicant side, the experience was even more fragmented.

The self-assessment process consisted of hundreds of questions, scattered across different documents and categories, often presented without clear structure or progression. Depending on the application type, users were required to:

  • Navigate large volumes of ungrouped questions
  • Interpret requirements on their own
  • Track their own progress manually

 

That combination created a poor experience on both sides. Applicants felt overwhelmed, progress was hard to track, and administrators had to spend additional time clarifying requirements, validating responses, and managing workflow transitions. The issue was not that the certification process was rigorous. The issue was that the rigor had not been translated into a guided experience.


Understanding the System

Once I started looking more closely at the workflow, it became clear that this was not a typical UI cleanup. The challenge was systemic.

What existed was a collection of steps:

  • Eligibility checks handled through spreadsheet logic
  • Self-assessments spread across large question sets
  • Peer reviews conducted without standardized structure
  • Exam readiness determined with limited visibility

Each step functioned independently, but there was no unified experience connecting them.

From a user’s perspective, this meant:

  • No clear starting point
  • No sense of progression
  • No visibility into what comes next

The challenge, then, was to redesign not just individual interactions, but the entire flow as a connected system.


Key Insights

1. The biggest source of friction was not the amount of work, but the way it was structured

The certification process was inherently detailed, and that was not something to remove. The real issue was how that detail was presented. When users are faced with a large volume of questions without clear grouping, sequencing, or progress visibility, the task feels heavier than it actually is.

Users weren’t overwhelmed by the work itself —
they were overwhelmed by the lack of structure around the work.

2. Hidden logic weakens trust

The Excel-and-macro setup handled real decision-making, but from a user experience standpoint it acted like a black box. Applicants could be told whether they qualified, but the reasoning behind that outcome was not clearly surfaced in the experience.

In certification systems, transparency matters because people are not just completing a form. They are investing effort into something that affects their professional credibility. If the rules and transitions are unclear, trust starts to erode.

3. Long processes need visible momentum

The portal was not a one-screen interaction. It was a multi-stage journey that required sustained effort over time. In that kind of process, progress visibility becomes part of the experience itself.

Users needed to understand where they were, what had been completed, and what remained. Without that, the system could feel endless, even when the path was defined internally.

4. Operational inefficiency becomes user-facing friction

Many of the problems visible to applicants were actually symptoms of backend inefficiency. Manual validation, scattered question sets, and unclear stage definitions all increased the workload for administrators, which in turn created delays, ambiguity, and inconsistency for users.

This reinforced that improving the internal structure of the process was inseparable from improving the front-end experience.

5. The solution was not simplification. It was guided complexity

This project required resisting the temptation to flatten everything into a “simple” flow. Certification is supposed to be thorough. The design opportunity was to take that unavoidable complexity and make it navigable through structure, hierarchy, and clear transitions.


Design Approach

The approach shifted from designing screens to designing a structured journey.

Instead of asking:
“How can we simplify this?”

The focus became:
“How can we make this process navigable?”

This led to a few key principles:

  • Break large tasks into logical sections
  • Introduce clear system states at every stage
  • Make progress visible and measurable
  • Align backend logic with front-end transparency
  • Design for both applicants and administrators simultaneously

 

The goal was to create a system where users never have to ask:
“What do I do next?”


The Solution

The final experience transformed the certification process into a structured, end-to-end journey:

Entry → Eligibility → Approval → Self-Assessment → Peer Review → Exam → Certification → Membership

Each stage is:

  • Clearly defined
  • Sequentially connected
  • Supported by system feedback

Centralized Dashboard

A centralized dashboard gave applicants a stable starting point and a clearer picture of their progress.

Instead of scattered interactions, users now have:

  • A single entry point
  • Clear visibility into their current stage
  • Defined next steps

This removes ambiguity and anchors the entire journey in one place.


Replacing Excel Logic with Structured Eligibility

The eligibility flow translated backend conditions into a more understandable front-end experience.

Instead of relying on hidden spreadsheet logic, the portal began surfacing requirements in a structured way so users could better understand how qualification was determined.

Users now know:

  • What qualifies them
  • Why they qualify (or don’t)

Re-architecting Self-Assessment

The self-assessment was the most significant redesign area. Because applicants could face a very high number of questions depending on application type, the experience needed stronger hierarchy.

The scattered question sets were redesigned into:

  • Categorized sections based on specialization
  • Progressive disclosure of questions
  • Clear progress indicators

 

Instead of facing hundreds of questions at once, users now:

  • Move through focused sections
  • Track completion in real time
  • Maintain a sense of momentum

 

The experience shifts from overwhelming → manageable.


Standardizing Peer Review

The review process was structured to align with the new system:

  • Evaluation criteria are clearly defined
  • Reviews follow a consistent format
  • Outcomes are easier to interpret

This improves:

  • Fairness
  • Consistency
  • Trust in the certification process

Defining Transitions Between Stages

One of the key improvements was introducing clear transitions.

Users are no longer left guessing:

  • When they move to the next stage
  • What qualifies them for progression
  • What is expected at each step

Every stage now has:

  • Entry conditions
  • Completion states
  • Next-step guidance

For the organization, these changes created a stronger foundation for consistency. For applicants, they transformed a process that once felt obscure and overwhelming into one that felt structured and legible.


Impact

The redesigned system introduced clarity at both the user and operational level.

Applicants experienced:

  • Reduced cognitive overload
  • Clear understanding of their progress
  • Increased confidence in completing the process

Administrators benefited from:

  • More structured data
  • Reduced manual intervention
  • Improved scalability of the certification process

 

Most importantly, the experience began to feel more trustworthy. That matters in a certification context, where usability is only one part of the equation. The system also needs to communicate rigor, fairness, and credibility.


Reflection

This project reinforced that not every UX problem should be solved by simplification. In complex systems, the better question is often how to make the complexity understandable.

The SBEP Certification Portal was valuable because it sat at the intersection of workflow design, information architecture, and trust. It required turning hidden logic into a visible experience, reorganizing dense content without weakening it, and shaping a process that worked better for both applicants and the organization behind it.

That is what made the project meaningful: the challenge was not designing a few better screens, but designing a clearer system.