The Product team have been busy developing a new version of the Case Search. But while the coding started in September, the research, requirements gathering, design and feedback process started well before and needed input from around the company and our client community.
In this article Garry, our Product Owner, describes the process.
Why a New Version?
Like any product, Case Search has seen lots of changes and improvements since it was first released, but we knew there were important elements still to add.
From the outset we planned to have mapping and location based searching, a feature that was also requested by lots of users. User feedback is really important to us, and key to deciding what the team will work on next, and which features should be developed.
Before we could add mapping, the Platform team first had to add geographical data to the workflow search index. They also had to develop a new filter syntax for the Workflow worker API so that the location data could be queried.
Once we had the platform technology in place, work could start on the new version.
Design and Proof of Concept
The design review was lead by Sarah, head of our Creative team. Using our framework components Sarah was able to generate a mocked up search page.
The proof of concept was interactive, so during demonstrations you could switch between views, pick filters, and use the map. The mockup also included embedded documentation explaining how each element was configured.
The new version includes the ability to search by case subtype, a map view of results, results that can be displayed as a table or set of cards, plus performance improvements.
Sharing with the Community
We run fortnightly community catch-ups, and a meeting in August provided the perfect way to demonstrate the latest plans for Case Search.
As well as feedback on the proof of concept during the session, a questionnaire was sent out, with a link to the mockup. That meant the new version could be shared more widely and everyone had time to consider the design and make comments, rather than trying to do everything on the spot via a chat in Teams.
The Build
With all of the requirements written up as user stories in Jira, and acceptance criteria added using a Given/When/Then template, writing the template could start.
Unlike the current version, which was built using the platform's forms engine, the new Case Search uses the same technology as other website templates. This means the template can use existing components, will be easier to deploy and support, and will be more performant and robust.
Once the QA team sign it off, the plan is to release the new Case Search in October.
Next Steps
The new version of Case Search allowed us to formalise some of the steps in our design processes. You'll see members of the Product team popping up more regularly in the community catch-ups to share what we're working on, as well as the chance to get your hands on interactive mockups and to give feedback.
As for what we're working on next, we'll soon be publishing a product roadmap, probably on the documentation site, so you'll have to wait and see!
Further Reading
The Case Search article in the Case Management documentation has been updated with all of the features in the new case search.
Share this page
