BDC BW Calculator
Business Data Cloud - Business Warehouse Calculator
[Description]
During the sales cycles, Capacity Unit calculations for BDC were done via Excel spreadsheet, requiring manual input and copy-pasting, leading to inefficiencies and potential errors.
[Business Goals]
Integrate an automated calculator into existing financial tools to speed up workflow, reduce errors, and eliminate manual effort.
[Organization]
SAP Labs Bulgaria - Order to Cash
[Date]
02.2025 - 06.2025
[Type]
Web Component,
PDF File template
Product Highlights
-
Reduced human error risk during the process
-
Improved data accuracy by automatic transfer
-
Based and validated decisions with end-users and process experts
-
Complex UX-driven experience backed-up with real data from interviews and usability testings
-
A single source of truth that eliminates the need for multiple draft versions of Excel documentation
-
Internally awarded project, and recognised end-to-end UX process
“This will make AE's life easier for sure.”
– Account Executive's feedback from the Usability Testing Session
Collected KPIs & UX Metrics
100%
Users completed all tasks independently
9.0/10
Net Promoter Score
5.7/7
Average SEQ
[Single Ease Question)
Scope of Work
[Methodology]
-
Scrum, 2-week sprint cycle
-
2 UX Designers collaboration
The project started with a Kick-Off Workshop, involving all necessary stakeholders (Business, Process and Technical Experts).
The goal of the session was to define project's scop, feature requirements and any other key information.
This time, the aim was to replace an Excel document, so understanding how the configuration and sales process look like was crucial to start work.
As-is Journey and To-be Journey Mapping
Next step was to map the 'As-Is' and 'To-Be' user journey maps.
Mapping was done in parallel with talking to the process experts and users.
The outcome visualises the process that users go through to accomplish a goal, and contains the following elements:
-
Stages
-
Involved Users
-
Actions
-
Touchpoints
This helped to identify pain points, potential improvement opportunities, and to envision how the new process will look like with our solution.
Low-Fidelity Wireframes
The initial deadline, which was about a month, set strict time frames for all UX activities. Therefore, we quickly brainstormed initial concepts and experimented with different approaches or layouts. Direct access to the solution architect and product owner allowed us to effectively reiterate draft ideas. The goal was to have 2 proposals ready to gather feedback from the process experts and the actual end-users.
The approaches were:
Phase by Phase vs. Step by Step
User & Expert interviews
Simultaneously to working on the wireframes, we were preparing and conducting user interviews.
Engaging end-users and cross-team process experts provided first-hand process insights, details and contextual understanding.
Due to being such a big and widely distributed target group, it was challenging to find participants who hold Account Executive roles, but we ultimately succeeded in finding 5 end-user representatives.
This stage was extremely important for the whole team, as we learnt about product rules and constraints that weren’t mentioned in the original Excel file or any available guidebook. Collected insights also began to shape the design, and initial stand-alone application concept evolved into flexible and scalable web component approach.
User interface & Prototyping
High-Fidelity Mockups were crafted using the UI5 (SAP Fiori) component library to guarantee experience consistency and alignment with the design system guidelines.
Each mockup illustrates a distinct step in the user journey, ensuring the entire end-to-end process is planned with clarity and precision.
To enable usability testing, the designs were converted into an interactive prototype using Figma.
Validating concept with real end-user before UI development has began, allowed the final solution to be refined and data-driven.
As part of the new ways of working, all decisions were documented together with the Front-End solution, and meant to be reviewed by the required approvers. This step was quite time-consuming, as the potential approvers weren’t initially our stakeholders, so they weren’t named in any repository. This activity involved some detective-like work, email communication, and network help, but the rest of the team benefited from the gathered contacts and the clear structure.
Each reviewer provided their opinion during the solution presentation, which was later communicated to the team and helped the discussions around the requirements scope.
Usability Testing
This round of recruiting end-users took much less time due to already established direct connections.
For the UX-related deliverables
-
Interactive Prototype in Figma
-
Moderator Script and Tasks
-
Personalised privacy policy
-
Mural board for results and synthesis
Because of the access to the UX Research practice within the UX & Design Standards team, we could double-check our writing materials and discuss what metrics were best to include for this research.
The most impactful task feedback allowed the implementation of an additional feature, which significantly improved the overall usability and was appreciated the stakeholders.
Cross-Team collaboration and
Developer Hand-Over
As one of the last activities that involved UX input was integration and legal topics clarifications. Our input was the solution presentation and support during the meetings.
After all adjustments were completed, we organised an official hand-off call for the developers to go screen by screen, and make sure we’re aligned in every technical and design aspect. Despite our daily updates and open communication, this was still an important step to ensure every scenario was covered, and answer any remaining questions.
The development stage and MVP product launch were concluded with the final UX-Check, which collected all needed minor fixes that has happened during the regression.