How do we combine all the type of interview questions in one place seamlessly?
One of Jotmillâs core functionalities was to create different types of interview questions depending on which the interviewer selected. So far, we have designed for five interview types which are audio, video, texts, checkbox and multi-choice type of interviews by having an upcoming modal widget prompt users to select their interview type in order to create a new interview.
This way the user has a variety of question types to select from when curating questions for an upcoming interview.
To simplify the interview type creation process, we designed a widget to help users understand different interview type, this way they can quickly select any interview type they want to create by clicking on âADD NEW QUESTIONâ
After the first test on the interview screen with the stakeholders, we found that some stakeholders were finding it difficult to understand what to do. Next, we added a widget helper on the left hand to assist interviewers in navigating through the Jotmill tool.
How do we enable collaboration between teams?
One of the coolest features for Jotmill is the ability to collaborate with everyone in the interview flows, from interviewer to interviewee, editors, and collaborators. Sadly, all the tools we explored did not have this feature, so we had to look for a tool with a collaboration feature and implement it.
We decided to use the insights gotten from the research, especially the competitors research:
"Figma is the only one with instant collaboration and comments in one place, and it's a feature that's needed a lot."
We implemented the invite feature into Jotmill from a button at the top of the page and allowed the interviewer to add everyone to the file and give rights and permissions.
Interviewees can save questions they have answered to copy their committed answers and reuse them later. This is one of the main benefits of the knowledge base as it enables teams to refer back to important saved questions for later use.
How do we onboard interviewees on the app and make them register?
When an interview is created, a link is sent to the intervieweeâs mail which takes them to the interview. Beforehand, they had to register to take the interview.
But doing this wouldnât really drive more influence on the business aspect of people knowing the app more after they have answered their interview.

For this reason, we went with the opposite flow of allowing the interviewee to answer the interview first, store their session as cookies in the cache in case they close the page before registering their account.
This way we ended up giving them a walk through of the other things they can do on the app when their interviews have been submitted.

The interviewee answers each of the questions sent in by the interviewer on this screen. They can display all the questions on a single screen or show one question per screen.
Designing and Building landing page showing value propositon
After designing the app, we wanted to show customers what Jotmill does; some of its features and how they can sign up for beta release.
The teamâs goal was to spend less time on development of the landing pages design.

I proposed to using USMO to build the landing page so as to safe development time and money and get it out faster. Usmo is a landing page drag and drop page builder for building landing pages. I was familiar with building landing pages on Umso, so it was the perfect tool to get the landing page ready due to the time constraints, we needed the development team to focus more on the Jotmill web app.
I didnât build the designs on Umso myself, I had to delegated the task to a designer on the team because I was occupied working on the Jotmill web app platform, I needed to make sure we met up with the deadline without any defaults, so I urged him to learn how to use Umso a No-code platform which had a low learning curve of a few hours and anyone would be good to get started on Umso.
The design and development of the landing pages took us four days. It was a wonderful experience watching the designer on my team try his hands on Umso and getting experience building for No-code platforms, that was a spark that pushed him to building more websites on Umso and grew on him as a skill.