Going the Extra Mile for Go Where
While the development of MaskGoWhere was not extremely technically demanding, Eyung notes that the team nevertheless took extra pride and effort in making sure the platform was easy to use, bug-free and enhanced according to user needs.
Technology, he says, was not the only factor in the mission’s success. “Working closely with PA allowed for optimal OpsTech (operations-technology) integration, where we could use real-time feedback to learn about user needs, and the Agile approach to deliver continuous improvements,” he explains.
And though the mission lasted some 48 hours from conception to launch, the team continued to monitor, enhance and stabilise the platform. The team also proactively stepped up to make up for the lack of manpower and volunteered their time on public holidays and the weekends to take on extra duties such as replying to enquiries from citizens.
Importantly, the development of Go Where has underscored the meaning of serving users and citizens in a time of need. Looking ahead, Eyung and his team are thinking about how the design and functions of the Go Where tech stack can apply to other contexts, such as for national events or emergencies. “This is what makes our jobs meaningful,” he added.