1. The Problem
The business problem involved the need for a centralized and streamlined pricing portal for AWS fintech services. There were challenges with disparate pricing models across different regions that led to confusion and inefficiencies for users trying to access consistent pricing information.
2. The Users
The primary users included AWS sales teams, fintech partners, and customers looking for pricing details on AWS services. Additionally, internal stakeholders such as product managers and marketing teams needed access to accurate pricing information for strategy development and sales support.
3. Discovery
I learned about the problem through user interviews, market research, and analysis of existing pricing discrepancies. Feedback from sales teams indicated significant challenges in providing accurate pricing to clients, which highlighted the need for a unified solution.
4. Constraints
Key constraints included the complexity of existing pricing structures, the need to comply with regional regulations, and the requirement to integrate with various backend systems. Additionally, there was a need to ensure that the portal was user-friendly and accessible to a diverse user base.
5. Design Process
Solutions were explored through collaborative design sprints and brainstorming sessions with cross-functional teams. This included mapping user journeys, creating wireframes, and developing prototypes that were iteratively tested with users to gather feedback and refine the design.
6. Prototype
Ideas were validated through usability testing of both low-fidelity and high-fidelity prototypes. Continuous user feedback was collected during testing phases, allowing for adjustments that ensured the portal met user needs and provided a seamless experience.
7. Outcome
The project resulted in a comprehensive global pricing portal that improved access to consistent pricing information for AWS fintech services. Key outcomes included increased user satisfaction, enhanced sales efficiency, and a reduction in time spent on pricing inquiries.
8. Lessons Learned
One key lesson learned was the necessity of maintaining open lines of communication with all stakeholders throughout the project. Future initiatives would benefit from a more iterative approach, allowing for continuous improvements and adaptations based on user feedback and changing market conditions.
