If Conway’s Law is the problem, Service Blueprints are the answer.
*Conway’s Law state that organizations design & deliver systems that mirror their own communication structure.
This case study is focused on how I introduced the concepts of Service Blueprints to become the standard format of understanding both End to End problem space as well as a double and triple click into a smaller sub-system. Through Service Blueprint format and designing a workshop from a true end user perspective by bringing together all the moving pieces - User flows, Internal business processes, tech/digital products, communication & data
Leading with Why
The real problem companies working (often times unknowingly) as per the Conway’s law is, surprise, surprise, creation of product silos. Tech companies take pride in moving fast & breaking things. No matter how many different programs like ‘Single Threaded Initiatives’ or ‘Guilds’ etc exist, these fast moving product silo teams will end up running into the same problems of
Ensure Consistent User Experience
Reduce Redundancies
Understand Dependencies
Central infrastructural teams help with these problems but it is not nearly enough. Often times, beyond carrying that our focus is on the end customer, in our hearts there is not systematic, repeatable approach to a true system understanding from the end user’s lens.
