We will dive deeper into the different use cases for forms shortly. Firstly, think about your business and whether you collect data from employees or clients. Can this be streamlined by collecting that data using web forms? Or, do you need a way to educate users through different types of content (eg. text, video, quizzes)? For the majority of businesses, the answer to one of these questions will be yes.
The MyLeap application is an online learning and behavioural change platform. The scope of the work was to provide content digitally in an easy to digest manner. It also needed to be highly customisable so future content could be created and released to users.
What we created for customers was a form with slide logic that could be completed while notes were taken. It was setup to share content on a specific topic. If a user wants to learn about the best way to approach difficult conversations then they select that subject as their learning focus - engaging with the content through text, images, videos and tasks.
While the front end is important for engaging your users, the real power of the forms behaviour comes in the administrators ability to customise. The process of configuring a form is shown in the video below. A new version could be created with updated content or previous/current versions of a form could be downloaded as a PDF. As the number of learning areas grows MyLeap is not forced to re-engage with a software developer every time (which significantly reduces the long term costs of the software). There was a complex hierarchy structure that was developed as part of this project which saw relevant material grouped together. This custom business logic was solved using custom code, written by a WorkingMouse developer that understood the purpose of the application.
It's clear to see the flexibility and power of the forms behaviour. Highly customisable and configurable at run time means that you don't need to re-engage your software developer every time you need to update something. Consider your digitalisation strategy and whether the forms behaviour can help you better engage with clients or improve your internal process.
The process of implementing forms in your application is simple. During WorkingMouse’s Scoping process, one of the artefacts produced is a built out initial model of your application, identifying behaviours that may be used. In the interest of transparency, we will step through the process.
In order to proceed to step 2, the requirements of the application must be detailed. This is done during the discovery phase of WorkingMouse's scoping process. We recommend firstly breaking the requirements into high level epics before going into more detail through user stories. These requirements can be stored on the Codebots library or other tools like Jira/Confluence.