Overcoming Brand Restrictions and Introducing Dynamic Prototyping in a Corporate Portal

How transitioning from static screens to functional Axure RP prototypes unlocked C-level approvals and overcame validation challenges in a multinational portal.

01 Overview

The Context: Development of a large-scale portal for a highly hierarchical multinational company, dealing with an extremely restrictive brand book (only two colors allowed) and an impending global rebranding scenario that would impact the project midway through.

My Role: UI/UX and Prototyping, working in close collaboration with technical leadership (tech lead reporting daily to the business lead) and the project team.

The Impact: Overcoming severe visual barriers, successful transition from static deliverables (Photoshop) to dynamic functional prototypes (Axure RP), facilitating client C-level validation, and securing a new contract to build a second portal.

02 The Challenge and Initial Scenario

At the time this project was carried out, functional prototyping tools like Axure RP were still relatively uncommon in the market, making the creation and validation of static layouts in Photoshop the dominant standard.

The project kicked off under heavy corporate pressure and complex constraints:

Corporate Rigor: A large multinational enterprise featuring rigid hierarchical structures and formal, serious processes.

The Brand Book Restriction: The greatest visual challenge was a severe palette limitation: only two colors were allowed, with zero room for flexibility, supporting tones, or point accent colors for specific actions.

The Rebranding Clock: The multinational was undergoing a global rebranding process that would affect operations within a few months, requiring development to proceed concurrently with shifting future guidelines.

03 The Turning Point: From Photoshop Statics to Agile Prototyping

Initially, layouts were delivered the traditional way through static screens generated in Photoshop (the standard of the era, prior to the widespread adoption of Figma and Adobe XD). However, the client company's rigid workflow took its toll:

The Validation Bottleneck: The client's business lead needed to present new screens and last-minute requested features to their superiors (C-level). Static screens failed to demonstrate real product behavior and created communication gaps among executives.

The Proactive Solution: Recognizing the time constraint and the need to test ideas and workflows quickly, I decided to introduce interactive low-fidelity wireframes using Axure RP.

Internal Impact: The shift was a success. The business lead gained a powerful persuasion tool: functional prototypes allowed leadership to accurately understand feature workflows, drastically accelerating internal approvals and shielding the project from endless revisions.

04 The Outcome and Contract Expansion

Despite the uncompromising brand book restrictions, the upcoming rebranding, and heavy corporate bureaucracy:

• Successful Delivery: The portal was delivered meeting all technical and business expectations.
• Commercial Value: The smooth workflow adopted for the client's internal validation built so much trust that it led to signing a new contract for a second portal.
• Value Lesson (Soft Skills): This case proves that a senior designer's role goes far beyond drawing screens within a brand manual; it involves understanding the client's political/corporate context and providing the right artifacts to unblock decision bottlenecks.