Redesigning an Enterprise Product Experience Through Iteration
Exploring multiple design directions, collaborating with stakeholders, and building a more consistent product experience.
Final redesigned product direction, used as the visual foundation across the wider experience.
Project at a glance
Lead / Senior UI/UX Designer
Enterprise Product Redesign — Binary Republik
Product Manager + CEO + development team
UX/UI redesign, visual consistency, responsive experience and reusable components
End-to-end UI/UX design, exploration, iteration, component creation and responsive validation
Figma and relevant AI-assisted design/development tools
Starting with a direction, not with individual screens.
The project started with an existing enterprise product that needed a more cohesive and scalable interface. Instead of redesigning individual screens in isolation, I focused on establishing a strong homepage direction first and then using that direction as the foundation for the wider product.
- Creating a clearer visual hierarchy across dense product pages.
- Establishing consistency in typography, spacing and layout patterns.
- Improving the overall interface quality without rebuilding the product.
- Creating reusable patterns that could be applied repeatedly.
- Making the experience scalable across existing pages.
- Ensuring responsive behaviour across different screen sizes.
Understanding what was already there
I first reviewed the existing experience to understand its structure, visual language, page patterns and inconsistencies.
Pages followed different layout logic, which made the product feel assembled rather than designed as one system.
Primary and secondary content often carried similar visual weight, making pages harder to scan.
Similar elements — cards, buttons, lists — appeared in slightly different forms across pages.
Navigation and page entry points needed a clearer, more predictable structure.
Spacing varied between sections and pages, affecting rhythm and readability.
Type sizes and weights were applied inconsistently, weakening hierarchy.
Learning from other platforms
I reviewed patterns from comparable enterprise and productivity platforms to understand familiar navigation models, content hierarchy, dashboard structures, component patterns and interaction approaches.
I used these observations as references to evaluate what could work for this product's context — not as templates to copy.
Exploring the right direction
Rather than committing to the first concept, I explored 10+ homepage variations to test different approaches to layout, hierarchy, navigation, content organisation and visual style.
Broad layout tests — different content orders, navigation placements and density levels, kept intentionally rough to compare directions quickly.
The strongest layouts were developed further with clearer hierarchy, consistent spacing and a more defined type scale.
One direction was finalised and treated as the visual foundation for the rest of the product.
The final homepage direction that emerged from the explorations.
What changed between iterations was mostly structural: how much content the page led with, how navigation and key actions were surfaced, how sections were separated, and how much visual weight each block carried.
Iterating with stakeholders
The homepage direction evolved through multiple review and feedback cycles with the Product Manager and CEO. Each iteration helped clarify the information hierarchy, visual direction and overall experience.
Multiple homepage directions presented side by side.
Review with the Product Manager and CEO.
Hierarchy, layout and visual details adjusted.
One direction agreed and taken forward.
Key design decisions
Content and navigation were structured so that primary information leads, supporting content follows, and each page has an obvious entry point.
Typography, spacing, cards, buttons and UI patterns were standardised so pages read as part of the same product.
Recurring elements were designed once as reusable patterns, which kept the redesign consistent as more pages were updated.
The approved homepage became a structural template — its grid, rhythm and section patterns were reapplied across other pages.
Layouts were considered across screen sizes so components reflow predictably rather than breaking at smaller widths.
From homepage to the rest of the product
Once the homepage direction was finalised, I extended the visual language and component patterns across the existing pages.
Approved direction — grid, hierarchy and visual language.
Reviewed for structure, spacing and component differences.
Rebuilt using the shared patterns and page rhythm.
- Reused components instead of designing new variants per page.
- Standardised spacing so sections shared the same rhythm.
- Aligned typography to one consistent scale.
- Improved page-level hierarchy so each page had a clear focus.
- Created consistent interaction patterns across similar elements.
- Suggested alternative page layouts where a different structure worked better.
Reusable component patterns
I created reusable components and patterns so that the redesigned experience could remain consistent as additional pages were updated.
These were reusable component patterns rather than a fully documented design system — the goal was consistency across the redesign work, not a standalone deliverable.
Validating the experience
After extending the redesign across the product, I tested layouts across different screen sizes and browsers to identify alignment, spacing and responsive behaviour issues.
- Responsive layout behaviour across screen sizes.
- Alignment of content, components and page sections.
- Spacing consistency between and within sections.
- Component behaviour when content length or width changed.
- Visual consistency across redesigned pages.
Preparing the designs for implementation
I worked with the development team to communicate the final UI direction, reusable patterns and page layouts for implementation.
I also used AI-assisted tools during parts of the design and implementation workflow to accelerate exploration and communication, while validating the resulting layouts and interactions manually.
A cohesive, reusable foundation
The redesign established a more cohesive visual direction for the product and provided a reusable foundation for updating the wider experience.
- A clearer visual direction agreed with stakeholders.
- A more consistent page-to-page experience.
- Reusable components and patterns.
- A scalable design foundation for future pages.
- Responsive behaviour reviewed across screen sizes.
- Implementation-ready designs handed to development.
What I learned
- Exploring multiple directions early helped align stakeholders before scaling the design.
- A strong homepage direction can become a useful foundation for redesigning a larger product.
- Reusable components matter most when an enterprise product already has many existing pages.
- Validating the design after implementation is as important as the initial visual design.
Final reflection
This project reinforced that enterprise redesign is not only about making screens look better. The real challenge is creating a direction that stakeholders can align around, that designers can scale, and that developers can implement consistently.
The final redesigned product experience.