Skip to content
← All work

Rebrandt · 2022 · 3 min read

Leading a usability overhaul with the CEO in the room

Eleven severity-ranked issues, negotiated with the founder down to four deliverables inside a 40-hour scope and shipped to Rebrandt's production site, with the CEO singling out brand consistency and ease of use.

11 → 4
issues audited, negotiated to deliverables
40 hr
fixed scope
3
designers led
The full deck is available on request ↓The client appears under a pseudonym, and the team is listed by role.
Role

Design Lead — 3-designer team

Timeline

2022

4 weeks (40-hour scope)

Team

CEO & Founder

Design Lead (me)

UX Designer

UI Designer

Deliverables

Usability audit

Competitive analysis

Sitemap

Icon library

Wireframes

Handoff documentation

Problem

Forty hours of scope, a three-designer team, and the CEO as the direct stakeholder. Rebrandt's platform had more usability problems than the budget could fix, so the real work was prioritization: we audited 11 severity-ranked issues and negotiated them down to four deliverables with the founder. Rebrandt shipped the result to production.

Original Rebrandt dashboard before the redesignFinalized dashboard shipped to production
Before and after: the dashboard as we found it, and the version Rebrandt shipped to production.

Scope

Each designer audited the platform independently. We merged our findings and ranked every issue on Nielsen's severity scale, from cosmetic to catastrophe, so the prioritization conversation with the client would rest on evidence instead of opinions. We walked the CEO through all 11 issues and prioritized them together. That conversation produced four agreed deliverables:

  1. Enhance the information architecture
  2. Redesign the main dashboard
  3. Update the icon library
  4. Refine the secondary dashboards' UI and preview layout

Architecture

The platform's core job is creating and publishing a social post. I mapped the existing flows and found the same task reachable through two or three different navigation paths, each in a different menu. The redesigned flows consolidated them into one.

Two paths to the same task, consolidated into one
Two paths to the same task, consolidated into one

For the sitemap, my proposal and my teammate's shared some moves but disagreed on fundamentals. Rather than force a premature merge, I submitted both versions to the client with the reasoning behind each, and the CEO returned a finalized version that combined elements of both. The documented stakeholder changes became the contract for the design phase.

My proposal next to the stakeholder-finalized architecture
My proposal next to the stakeholder-finalized architecture

Design

Each designer produced a dashboard variation on a UI style our UI designer standardized: three genuinely different layouts, one decision for the client. We also rebuilt the icon library on Feather Icons, and I aligned the secondary dashboards with the new main-dashboard language.

Three dashboard variations, annotated for the client
Three dashboard variations, annotated for the client
A secondary dashboard with a consistent create button and tabbed pending and approved views
A secondary dashboard with a consistent create button and tabbed pending and approved views

Outcome

The client picked a final dashboard during our progress call and shipped the changes to their production site. Their feedback singled out brand consistency and ease of use. Beyond scope, we left them a moderated-testing script so their team could validate the designs with real users once they had them.

Appendix

How the work fit a 40-hour budget: six time-boxed phases, hours budgeted per task, and a rationale behind each choice. The platform had no user base to test with, so direct client-feedback sessions replaced testing and pulled the CEO into design decisions early (the full phase plan lives in the deck).

Competitive teardowns of Uberflip and Paperflite grounded the recommendations: brand consistency and a simpler IA from one, a cleaner UI bar and harder-working dashboard real estate from the other.

The audit document: severity-ranked issues, each paired with a proposed solution
The audit document: severity-ranked issues, each paired with a proposed solution

The full story

Every artifact, decision, and iteration lives in the deck.

The deck is available on request. The password is included in my job applications, or you can request it via the contact form.

© 2026 Tamir Said-AhmedMentorshipSenior Product Designer @ FISBuilt from scratch, pixel by pixel ✦