Designing automated print publishing capabilities to support more than 400,000 products. The goal is to generate the right print piece with the right products for the right people at the right time. Scope includes publishing software and print products as well as integration with or changes to: Customer Information Management, Product Information Management, and Content Management.
Context
This project is a work in progress, currently in the research phase. The sampling of documentation below is in service of defining the problem space and developing a shared vocabulary. My process consisted of stakeholder and customer interviews, deep dives into Gamut's product data structure, SME interviews, and competitive analysis. Right now, I am focused on developing a flexible presentation that won't require heavy templating and prototyping changes to our internal software.
Print Output Archetypes
Publishing Flows Exploring Necessary DAM and CMS Functionality
Working within the Zachman Framework, we focused on the What, How, and When and broke the content creation, management, and publishing process into its most basic elements, cross referencing enterprise software archetypes that typically manage each part of the process. Designing a specialized system would require integrating each of these components into one piece of software. Because of the advantage of a unified system and disadvantage of the large scale, we had an opportunity to develop microservices that could be used and improved independently while connecting to each other at critical points in the workflow.
Customer Journey Map
Product Display Breakdown
Design Principles by Example
