Background 🖼

Omni's priorities are performance and reliability. Omni helps talent managers in Collab Asia to access and use Omni every day for critical business operations such as payment info keeping and contract record keeping. Hence, navigation, loading, and data modification need to be swift and intuitive. Data should be reliably kept with absolutely no data errors and failures allowed.

Why is the team devoting time to this project?

• Collab Asia's data systems are heavily fragmented across offices with different formatting, models, etc., which makes it difficult and unreliable to perform many data tasks across offices
• The practice of using spreadsheets for data keeping has spawned various inconveniences, inconsistencies, and errors that can be fixed with a proper database system
• The momentum from projects such as Stats by Office, Revenue by Managers, and Talent Pipeline makes this a perfect time to implement such a system and yield high values
• An "Omni" database would adhere to the best practice in the business IT system of Single Source of Truth. It will simplify business and data processes as well as reduce costs and improve new project potentials across all offices.

Goals 🎯

• Be able to reliably use data with better standardization across offices
• Have a reliable and official data source for any operational or analytical needs
• Faster, more convenient, more centralized, more intuitive workflow
• Avoid confusion stemming from the inconvenience of the US Dashboard
• Make it easier for the data and product team to produce consistent and reliable analyses
• Make it easy for analytics and operations across offices to be carried out
• Fill in the hole of accessibility currently present in the US Dashboard
• Make it easier, convenient, fast, reliable, and centralized for talent managers to update information about master sheets
• Make the data system of Collab sustainable in the future

Omni Progress 📊

We have build OMNI from scratch with the help and cooperation of everyone in Product Team. In this progress you may see the changes that we have done from version 1.0 to version 2.0 (latest update January 2023).

Through this progression we have manage to create a sole research community within the product and came back with results that satisfy both stakeholders and users.

‍

Project Owner: Kamilia Fauzi

People working on the project : 4 People

Workflow:

• We started by gathering all the database and doing research, understanding what and why the users do and don't during their workflow progression.
• Defining problems out of the research and with all the material sources that we had gather.
• Brainstorming and problem solving with teammates and in the same time ensuring product team's mission and vision are align with stakeholders' request.
• Having a plan for Back End Development, Front end development, UI, UX and product experience before starting the project.
• Making sure timeline set up are within the goals set. Most of the features we launch are based on scrum technique.
• Wireframing, designed, implemented and monitored prototypes and sites for continuous improvement and created eye catching and functional design concepts.
• Follow Up with the team for every work progress that have been made. Creative thinking and quick decision making during every calls to solve any sudden issue occur.
• Product testing - to measure the properties or performance of products
• Planning product launch - requires visual update, emails send, slack and follow up after launching.
• Intervention - Review lessons learned and areas of improvement.
• Plan features and improvement for the next version while maintaining follow up with stakeholders, users and bug fixes.

‍

All project are monitored and documented in every aspect from head to toe.

Please contact me to get to know more.

‍