Cohesive Data Strategy: Connecting Siloed Business Units

A core requirement for the EMBA program is an international resident project where we consult directly for a client. Our client was based in Seoul, South Korea and the team traveled to Seoul to present the final presentation. The initial goal for this project was to provide a big data strategy for our client. I am not sharing the name of the client for privacy. After a couple of months of conference calls, our team realized that the real issue that needed to be addressed was organizational structure.

It turns out that our client had tons of data but however because of process and policies we unearthed that the Marketing and the IT department were not collaborating with each other and instead operated as separate business units. This lack of information sharing from units reflected in the underperformance of the overall company in profits. We worked with both the teams separately to first identify existing practices and then recommended a more cohesive data strategy. One of our deliverables for this project was a very detailed map of how the two units could work together and also given that we had a data scientist on the team we also demonstrated with actual data the implications of how a cohesive strategy could be beneficial.

Initially, I served as the technical expert in this project to research existing solutions for the client. After the pivot in the scope of the project, I served as a the technical expert and as a solutions architect mapping exactly how they could implement a system modeled after the strategy we recommended.