Building Enterprise apps, in a whole new way.

BUILD is a no-code prototype suite housed within the SAP Cloud Platform. It empowers SAP customers, partners, and business analysts to craft enterprise applications and validate any design with their clients, all while familiarizing themselves with the design-led development process. I had the privilege of being the third designer on the team. My responsibilities encompassed the design of the UI shell and user interface controls. I also focused on enhancing the usability of the most frequently used UI5 controls within BUILD’s Prototyping Tool.

Role

  • User Research/
    Interviews
  • A/B Testing
  • UX/UI Design

Industry

  • Enterprise, B2B
  • ERP (Enterprise Resource Planning)

Timeline

  • Company: 3 years
  • Project: 6-7 months

Launch Site

Background Story

Nearly 3 years into my tenure as a Sr. UX Designer at SAP, my manager approached me with a unique opportunity. He asked if I was interested in working on a "special" project with Team 'X'. Eager for a fresh challenge and the chance to build something entirely from the ground up, I immediately seized the opportunity. At that time, the project consisted of only four individuals and some preliminary ideas illustrated by a few sketches on whiteboards. The project bore the codename 'Norman', and its details remained confidential until we could demonstrate its viability to our stakeholders.

Interestingly, although we had a clear understanding of the problem we aimed to solve and had validated our hypothesis, I discovered that the company had tried and failed to create this product nearly four times in the past. Another team based in Germany once came close to succeeding, but the product's direction shifted and it evolved into Web IDE (Integrated Development Environment). This tool facilitates users in quickly designing and extending applications for both browsers and mobile devices, streamlining the entire application lifecycle – from prototyping and development to packaging, deployment, and even customer extensions, specifically for SAP Fiori and SAPUI5 applications. This outcome was quite distinct from the original concept of BUILD.

To conclude, I was among the pioneer designers on the team. As the project gained momentum, the team expanded to over 100 members. The indelible impact we achieved as a cohesive unit is immeasurable. I'm immensely proud to have collaborated with such an outstanding team on this initiative.

Improving the Panel and web Application

The concept for Build was promising, but from an engineering perspective, it posed a nightmare. As I delved into the design phase, I encountered numerous usability issues. It became evident that the 'UI Shell' needed to be segmented into multiple components. Consequently, I introduced a new interaction model, as depicted in models: A1 and A2. Throughout this journey, our team also stumbled upon significant UI design challenges. This led us to the decision of overhauling the entire framework on multiple occasions.

Project Organization

As the capabilities of Build expanded and its complexity grew, the product team was tasked with facilitating the organization of content and files within projects. Build featured a tool called "Boards" for this purpose. However, its design was not intuitive, making it nearly unusable. The subsequent wireframes present a revamped design proposal.

Ideations

Having segmented the UI Shell into distinct components, I proceeded to investigate the integration of notifications, drawing inspiration from user feedback. I also experimented with various UI alternatives. This involved using the logo's color palette for reference, fine-tuning spec measurements, and ensuring a harmonious balance in the overall hierarchy of design elements, including the History Navigation, Submenu tools, and micro animations present in the sidebar.

Feature Automation

Having noticed users grappling with an abundance of options, I chose to magnify the most frequently used features and dynamically reorganize the toolbox based on user interactions over time. This transformed the panel into an adaptive interface, becoming smarter and more user-friendly as time progressed.

Takeaways

SAP Build is an exceptional tool for crafting high-fidelity Fiori UI5 prototypes. Here are the primary features and benefits I gleaned while designing my inaugural prototype app:

Low Cost of Changes: No need for programming, resulting in a much quicker turnaround time.
WYSIWYG: What you see is precisely what you get.
Interactive Prototype: Incorporates screens, processes, and real-time data integration.
Fiori Compatibility: Offers a head start on Fiori development.

Low Fidelity Prototype:

Process Map with Sticky Notes: Allows for a rapid visualization of processes. However, it lacks detailed screen information.Screen Mock-ups: Provides a visualization of screens, but offers limited insight into the process and data visibility.

Not all Prototypes are Created Equal

Mock-ups, as low-fidelity prototypes, have their limitations in enhancing the user experience. To truly excel, transitioning to a high-fidelity working prototype is crucial. It significantly mitigates the risk of presenting yet another subpar User Interface (UI) to your end-users.