Finesse Mobi

Prototyping, Information Architecture & Product Management
Project Overview
In 2015, I worked on  Finesse Mobi, a mobile application designed for iOS and Android. The purpose of this application was to allow customers of the Finesse MBS (Misc. Billing Solution) software, which was one of Accelya's key SAAS billing product for airlines, to be able to process high value invoices.


Note: I am unable to provide any images associated to this project due to confidentiality reasons.
My Contributions
Role
Technical Manager (Product)

Duration
1 4 months

Team
2 Developers
2 UX Designers
2 QA Engineers
1 Tech. Manager
1 Software Architect
1 VP of Product (Part-time)
A web-based SaaS suite of products catering to the Cost Accounting requirements of top global Airline companies developed by Accelya Group. It includes solutions such as FinesseMBS, FinesseCost, Finesse Mobi etc.
What is Finesse?
In early 2015, I undertook the challenging responsibility of overseeing the development of the Finesse Mobi mobile app, which was a critical deliverable for our organization. This project came with two distinct and paramount objectives that needed to be fulfilled in order to ensure its success:
Collaboration with the Software Architect:
My first task was to work closely with our seasoned software architect. Together, we embarked on the intricate journey of designing the essential components that would form the backbone of the Finesse Mobi app. This involved in-depth discussions, brainstorming sessions, and rigorous planning to ensure that the app's architecture would be robust, scalable, and aligned with our organization's broader technology roadmap.

Coordination with UX Designers and Developers:
Simultaneously, I had the privilege of collaborating with our talented UX designers and dedicated developers. Our primary goal was to bring the vision of the Finesse Mobi app to life, starting with its release on the iOS platform. This phase demanded close coordination, effective communication, and a shared commitment to delivering a product that not only met user expectations but also adhered to the highest quality standards.

My initial step in this journey was to engage with our UX team members. I recognized the importance of grasping the nuances of what was being built and understanding how it would seamlessly integrate into our existing technical infrastructure. To achieve this, I initiated numerous meetings with the UX team, aiming to clarify the details and refine the initial concepts presented in the high-fidelity mockups they had meticulously crafted.

Given that I was not directly involved in the Research and Definition phase of the project, I faced the task of quickly ramping up on certain critical topics. This was particularly vital as I needed to provide essential knowledge to team members, including our junior colleagues who were eager to contribute to the project's success.
My commitment to knowledge acquisition and sharing became an integral part of the project's success, ensuring that everyone involved was equipped with the insights and information needed to make informed decisions and execute their tasks effectively.
Conceptualization
I worked closely with the software architect and the database administrator to figure out a way where we could abstract the information related to invoices that was already stored in the web application. This part involved not only utilizing my skills in object oriented design  but also database design best practices.
I used my time to brainstorm on possible approaches that can be taken for designing the following a) a REST API library that would directly support the UI as well as
b) how user access for the mobile app was to be facilitated to balance out the security constraints and
c) making sure the Information Architecture was presented intuitively.
As me and the team continued to refine our ideas it was clear that there were basically two user personas that would be the focus of app (provided in the image below).
Abstraction
Designing a solution that works
This phase of the project involved setting up processes for the development work and also delegating the tasks around what was to be built. I worked with developers and the QA team to iteratively build the initial parts of the mobile app including the REST APIs and modifications that needed to be made to the product service layer.
As our team was relatively small and everyone was on-site, I decided that we would have a daily stand-up meeting for the duration of the development tasks and supplementary ad-hoc meetings to discuss any roadblocks or technical challenges.
We started integrating the changes in the backend with the UI changes early which helped the acceptance testing for various components. This was followed by developing a working prototype that we updated and installed on a few test phones for the team to test frequently.
We also met regularly with the VP of Product and other stakeholders to provide status updates and get their feedback.
Development
Getting into the nitty-gritty
I worked closely with the QA team to ensure that we were testing the app for three things in particular:
1. Consistency in Design
2. Acceptable response times
3. Supporting the different use cases

Multiple issues came up during this part of the project but working together as a team helped resolved most of the issues. After about  10 months ( v.16) into the project we finally had something that we felt confident that we could launch on the app stores.
Testing
Is it ready yet?
Working on this initiative was an incredibly rewarding experience, and it not only bolstered my confidence but also imparted some invaluable lessons that I believe are worth sharing. Here are some specific takeaways from my journey:

Teamwork is Key
Collaboration within a team is the cornerstone of successful project execution. Team work plays a pivotal role in the success of any project. A well-structured, motivated team can overcome challenges and drive innovation.

Clear Communication is Essential
Effective communication is the foundation upon which a project's success is built. Clear, concise, and regular communication is crucial to ensure that everyone is on the same page. Transparent communication minimizes ambiguity and reduces the likelihood of misunderstandings or misinterpretations, saving time and effort in the long run.

Adaptability is a Strength
Adaptability is a crucial skill in project management. Being open to change and receptive to new ideas can lead to more effective problem-solving. The ability to pivot when necessary and adjust strategies based on evolving circumstances can greatly enhance a project's chances of success.

In conclusion, my experience with this initiative underscored the importance of teamwork, clear communication, and iterative development.
Moreover, the experience instilled in me the confidence to take on complex problems with a proactive and solution-oriented mindset, recognizing that success often lies in the collaborative effort of a well-informed team.
Insights
What I learned along the way