The Repository is a capability where users can store Decision Assets and Runtime Entities, view the list of assets stored, see asset version history and more that can be reused across multiple solutions.

Repository

Currently internal and external users of FICO applications do not have a central location to exchange and store assets for re-use. They have to manually email assets as attachments or use external storage services such as box or github.

Although it has always been deemed a valuable platform need, it’s priority was very low mainly due to not enough resources available to figure out a way to integrate and unify all of the different product libraries without breaking all of the solution architectures in existing products.

Each product owner had slightly different visions for it depending on their target line of businesses.

Problem Statement

Personas

This concept is for managing all the different type of assets that is used within FICO decisioning applications in one location.

Currently users do nothave a central area to exchange and store assets. They have to manually email assets as attachments or use external storage services such as box or github.

  • Central location to store assets created by Capabilities

  • Versioning & branching

  • Standard metadata for consistency

Goals

Research and Analysis

Evaluated current internal FICO applications, as well as previous concepts in parallel with how other companies organize and arrange their assets during the research phase.

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.

Final User Flow

Screen Flow

UI Evolution

The UI concepts also evolved over time as a new Design System was created and implemented to unify the look and feel across all applications.

We also had to make sure that the UI was flexible as the Repository needed to be scalable in the event that more features, or more asset types could be introduced over time.

Conclusion

The Repository ended up getting developed before I departed FICO and is currently being used by internal teams as part of the company’s future.