USer Problem

Enterprise Application Developers and System Architects are often held hostage by the monolithic legacy applications that they are in charge of. The legacy applications make it impossible to adopt more modern development practices like DevOps. This means that companies cannot react or improve their services as quickly as their competitors that have adopted such practices thus creating a competitive disadvantage.

Compounding the problem is the fact that moving from a monolithic architecture to a microservice based architecture is a MASSIVE effort. The larger applications can take years to plan out how to break down a monolith into its parts.

Mono2Micro scans a users application and uses AI/Machine learning to create a testable microservice structure for their application in a matter of hours vs years.

My Role

My main role was as the design lead for the project. As the Design representative of IBM’s 3-in-a-box practice (Design, Development, and Product Management) it was my responsibility to ensure that the users needs were not only reflected in the product direction but also the in the output of the design team. Our team was comprised of myself, a UX designer, content designer, and a UX Engineer. Most of the UX work was split 70/30 between the UX Designer and myself (Respectively). Additionally I lead/conducted all of the research due to my 3+ years as a researcher.

Process

Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Integer tempus, elit in laoreet posuere, lectus neque blandit dui, et placerat urna diam mattis orci.

Work we adopted

Hahaha ohh research. The be silly.

Stakeholder workshop

I am your god. worship me.

Design Iteration

ALL THE PROCESS

Research

Crazy hippies