schedule meetings with experts!

while the platforms MVP is event booking, we also aimed to make room for solopreneurs, teachers, and mentors (overall labelled as Experts) to make use of our booking features - to do so, I designed a scheduling feature, where users can request a certain meeting time that can then be accepted or rejected by the expert

check this out, it's a checkout page

paying sounds like the simplest part of a user flow, but it turned out to be quite a challenge and lesson in balancing back-end requirements with front-end simplicity. in an older iteration of this page, emails needed to be collected, users had to log in to proceed but none ever did, a users were skipping back and forth between sections and therefore missing out required fields, or accidentally resetting other already filled ones.with that, i introduced a progress stepper up to, and used some nifty accordion sections to prevent users from trying to escape filling in their email and scrolling straight to the payment form.

The operations team suggested a process similar to buying things on typical e-commerce platforms, but with added functionality that suits them such as segmenting orders into different rooms within a unit, and the option to reserve an item before receiving confirmation from clients.This is designed for desktop so that the designers can easily see everything on one page, and also go back and forth between other files they may have open while ordering such as cost estimation documents. All usable inventory be it stored with the company warehouse or with the vendors will be viewable in a marketplace format, and can be ordered for the individual client projects based on pre-set lists of items needed.

The issue being tackled is not as simple as providing a solution to the internal team, but also required an accompanying platform for the vendors where the inventory was being ordered from to completely streamline the process. We decided to design this for mobile instead of for desktop, keeping in mind that vendors may need to process orders and requests on the go and potentially while they are in warehouses or storage locations.For some vendors, the company would make agreements for them to set aside a set number of inventory, but this is typically just a verbal agreement. So, we added these stock commitments into the app to have a more concrete view of what has been reserved.

Last but not least, the bridge to connect the marketplace, vendor app, and a third party stock count tool. This platform is intended for the procurement team to be able to manage the stock commitments with each vendor and place orders for more, view stock numbers for inventory, and create the user accounts in order for vendors to access the vendor app in the first place.

From the dashboard page I designed, recruiters would be able to view all applicants at a glance, then click on a name from the list to view the applicant profile and resume, then either assign the applicant to another recruiter, or screen the applicant immediately.Applicants can be selected for interview or rejected via the buttons displayed beneath the profile - the Schedule Interview opens up a second drawer where the recruiter can select date and time slot options for the interview session that the applicant can choose from. Here, a templatised invitation email is also displayed and can be edited if needed, while not necessary. Then, the recruiter can click the Send Invitation button for the email containing the invitation and slot selection to the applicant.I chose to use sidebar drawers for each step as a recruiter might be reviewing many applicants in a single sitting, and would need speed and efficiency to go through all of the steps above - putting these into a popup or a separate page might be perceived as a lot more back-and-forth.

I sort of took a chicken-before-egg approach to this project unintentionally, and only worked on the flow of creating job listings for people to apply to after working on the dashboard of applicants. I broke this up into a few pages:
1. An overview of existing job listings
2. The form for users to create new job listings
3. An expanded view of a job listing , where the user can see all the input they added in 2., and also a filtered view of profiles of those who applied to this job in particularUnlike the dashboard page, this flow is something that a recruiter may not need to access as frequently nor do the steps necessitate speed and efficiency as screening candidates would. So, I broke this up into pages for each task and context. 1 being an overview, 2 being a form that may require time and scrutiny over the input details in order to convey clarity to those who wish to apply, and 3 serving as a more focused version of the hiring dashboard.