From our initial meeting with the team, I collected vital information, which helped to determine the intended users directly involved in building the Control Center product. In later years, the Style Guide became a valuable resource for cross-functional teams. Outlined here are example personas of our users describing the estimated percentage of use for this product tool.

An integral factor in creating the Style Guide is deciding which platform to use. I received suggestions from the team of various platform products to investigate and conduct research. I outlined each product’s benefits and disadvantages in a report similar to a SWOT list. After gathering all the needed data, I reviewed my findings with the team. After careful review, we determined that Confluence was the most feasible choice due to security, control of data, and ease of use and access.

After creating buy-in for our choice platform, I needed to improve the current deliverable process to ensure quality and consistency for each new component request. Outlining the current workflow helped to identify areas to improve. I proposed adding another step to the process before releasing the final approved mock-ups for development. The improvements to the flow required that any new or updated components be captured through the Style Guide to prevent duplications or discrepancies.