Overview of the product
Many Tempus products contain numerous need-driven configurations that can be customized to any merchant's desire. Even before my time, there has been a desire to offer a standardized SaaS solution that makes use of the different technologies in the diverse product suite. PaymentMate Portal exists as an administrative tool that interfaces with Tempus's PaymentMate POS experience.
Planning and Strategy
- We started by comparing Tempus’s current solutions with the proposed minimally viable product requirements. This resulted in planning and research sessions with our developers and stakeholders to determine which solutions feasibly fit within the MVP requirements.
- We also researched successful products and experiences in the the payments space today (Square, Stripe, Adyen) for competitive analysis.
- We wrote personas, user stories, and started working on user journeys and low fidelity artifacts.



In Practice
- Due to unique processes and an aggressive timeline, the designers were engaged in a consulting capacity while software architects defined the technical scope of the product.
- We used our research and low fidelity artifacts to start incrementally producing screens for the product.
- This product is still being designed and developed today.



Retrospective
- When solving problems for a target user, it is of the utmost importance to speak to that user to understand the problems from their perspective. I think this would have greatly improved the quality and precision of our designs.
- Business requirements, user needs, and product goals should be harmonious. In absence of that, the balancing act is very challenging.
- Analyzing competitors at a very granular level pulls back the curtain on how these other product teams were solving their own unique problems. Comparing our problems with theirs helps understand which decisions were made for similar reasons.
