The Data Designer is the entry point to a collection of tools that users can access to create assets that can be used in other FICO decisioning applications or services.

Data Designer

Tenants need a tool to create and manage Data Definitions that consists of data elements such as entities, fields, calculated fields (variables), and enumerations that can be used across multiple solutions.

There are a number of FICO products that have different implementations and the design needs to incorporate all their needs.

Problem Statement

Personas

This application is meant to be used by Solution Developer and Business Analyst users.

The Data Definitions is a complete UI overhaul of an existing application where users can create and manage database schemas. This tool allows user to add properties to individual nodes of a selected schemas such as entities and fields.

Depending on the type of field, there are masking options and a field calculation feature that runs in design time.This is a long term project because multiple product teams were involved and a conflict of terminology stalled conversations.‍‍

  • Central location to store assets created by Capabilities

  • Versioning & branching

  • Standard metadata for consistency

Goals

Evaluating existing internal application UI’s

The current Library page has a block/card layout that is not very useful. Also no other information other than the Name is available or a search feature which is inconvenient when there are multiple Data Definitions.

The editing UI misleads the user that the Data Definition is a flat structure. It is actually multi levels deep and this is done through the Type column.

Another issue with this layout is if the Data Definition contains hundreds or thousands of nodes, then they system lags because it also loading all of the set properties at once.

There is a calculations feature that is hidden in the ellipse icons where users can perfom additional actions to enrich their data.

User Flow Evolution

The user flow changed over time as the product changed hands and more research from the architect was done.

We had to accomodate technological restrictions suce as assets being created and stored by other capability teams who owned a specific editing tool.

User Journey

Screen Flow

UI Evolution

The first concept iteration was deemed a "lite" version of the current product as the team that I was on only required the ability to create a schema/data definition to be used with an external database initiative.

The current product was tightly integrated with the platform at this time and because it was developed using a different technology stack, there was no way for my team to reuse their UI components without cog issues.

End Results

After evaluating the user flow from the current UI, PM requirements and from gathering feedback through the user studies; this is the end result.

The Data Designer was projected for development in Fall of 2022.