top of page

ScoutAsia - Radar

From the exploration & ideation of ScoutAsia Transformation

MVP launched

Radar is a unique feature to ScoutAsia, one that was created to help our customers curate news and the information they need based on the seeds they planted. Once that has been cultivated, our customers can keep up to date with their needs and wants of their customers, suppliers, competitors etc., and even get a clear overview of the landscape they are monitoring.

 

 It is a USP for us, because no other competitor does it like we do, combining news and corporate data into 1 single monitoring board - the radar.

Radar.png

Motivation

Part I of this project was ScoutAsia Transformation, and Radar is newborn from our discovery and exploration for ScoutAsia's new direction. With all our 3 persona, the Dealmaker, the Researcher and the Strategist, all have a need for using the Radar in their own ways. 

Fun fact: we(designers) initially called it 'Boards', and had a long few weeks before we decide on the actual name so that it is unique to ScoutAsia yet understandable.

Define

Much of the discovery work has been done before we choose to delve into Radar. We even had wireframes that look absolutely nothing like our final, just to pitch the idea to our management and the wider team of ScoutAsia.

 

Over here, I would like to highlight the immense amount of mind work my team did, before we dived into the actual wire framing.

 

Radar is a complicated feature made to be simple. There were plenty of mind work and mapping done before we could delve into the actual UI design, a nd even with that said, we did work on the design in parallel (timeline in reality is tight and we are on tight schedule).

Bitmap.jpg

Mindmap of customer needs to what we can provide

Board works.jpg

Level 1 Outputs, Level 2 Outputs, Level 3 Outputs, what are they? 

Level Outputs are easily obtained from the 'seeds' we plant, when our customers manually choose the 1st level of filter. We give them the direct results. But this isn't going to be of high value, so what can we do? Level 2 outputs, are insights and signals derived from the level 1s, giving them more information that they cannot get themselves. We find links and correlations of their Level 1s to produce these co-companies and recommendations. This makes Radar valuable.

Group 13.jpg
Group 14.jpg
Customer Journey Mapping

We had to map our 3 different persona's journey using the Radar, to know for sure what other outputs we may require, other features and steps we might have missed. Below is an example of a persona's journey map, where his focus is to study the market landscape of his industry.

Persona Board 1.jpg

Design

The design process runs through a long time, right from the initial ideation stage, POC, to the wires and hairs and then to the final design; final design for internal and beta user testings. Also what we call as MVP. To get this MVP out, it also took a painstaking 2 months because of the many considerations and new experiences we are building which sprung surprises to our teams. That said, everyone turn around quickly after we settled our 'Live' site maintenance. we were not running on neww temas, we were just 1 team for the entire Handshakes and ScoutAsia (Transformation or BAU).

Concept and Wireframes

Wireframes were made pretty high fidelity, for the fact that it was not only for the working project team to visualise, but also for the higher management and non-product teams to buy-in. Afterall, IT IS an overhaul of the current ScoutAsia.

Initial Conceptual wireframes for ScoutAsia Transformation

Free hand sketches during define phase for Radar

Wireframes after defining

Final Design

As an MVP design, we have to integrate it into the current ScoutAsia, the current UI, with the current infrastructure and user experience and whatnot. Here, you see the entire flow from how a customer plant the seeds, to the inflow of 'outputs' into their Radar, with a few different types of input.

As an MVP design, we have to integrate it into the current ScoutAsia, the current UI, with the current infrastructure and user experience and whatnot. Here, you see the entire flow from how a customer plant the seeds, to the inflow of 'outputs' into their Radar, with a few different types of input.

On Your Radar

Bringing alerts of Radar upfront to the customer so that they stay well-informed on their monitoring radars.

Create your Radar

The Radar homepage to house all your different Radar profiles, and the place to create new ones.

A short-term flow to integrate the creation of a Radar with this old Search bar and feature. If the MVP is successful and the Transformation is proven to be effective with the Internal and Beta users, we will move along to Phase 2 to decommission this Side Searchbar and Save Searches feature, and replace with 3 new features.

To bridge the old interface to the new Radar this was a necessary not-so-elegant solution.