Due to the various skillsets needed per department, my manager and I conducted daily SCRUM meetings until all interfaces were up and running in their entirety.

To detail, this process helped us devise a code that we could use to apply to different types of projects to provide specific KPI to quotes, for stakeholders to make essential business decisions. This led to Reporting such as depicted below:

Thanks to Open Creative Sessions we designed a code system that ultimately served upper management, in addition to appropriate microcopies to use when sending quotes and creating calendar entries.

Managers valued the code system as it would aid in directing sales team members to clients who focus on these types of buildings or compare what types of projects to focus on getting quotes for. We also thought of all cases where anyone who had access to our calendars and databases may have trouble navigating and finding updated quotes due to the serial number difference per quote, and contractors, new architects, and new engineers calling the same project different names or code names per quote request.

This led to another issue revealed during our brainstorm which was naming conventions and hierarchies to keep all these projects organized in an intuitive way that would be inclusive to everyone involved with the project.  

Example:
‍
###### for the Original Quote
###### for the Original Quote update
######-1 For a Rebid
######-1a For a Rebid update


During this session, I also learned that Salesmen work with a vast variety of companies who all have their own management structure they use from Waterfall, Agile to "Mom and Pop", many still have processes that are decades old. This meant that I had to adopt a filing system that kept all the essential details front and center, along with being as accessible as physical copies of the documents they were used to taking on the road with them.

Ultimately implementing Open Creative Sessions to generate ideas led me to narrow down software that would be essential to daily operations:
‍
SharePoint
Google Drive
Localendar
Access
Excel

*It is important to note that I had the range to apply any necessary software however, due to the various skill levels, I understood that these 5 would be sufficient to the company's goals and save them much more money than creating an interface from the ground up.

(This would have cost hours from the IT department along with several lengthy phone calls and meetings daily when my department should be heads-down quoting bids for clients.)

‍

Language developed when sending communication outside of the department:

(Though well known, and largescale, Murray Supply is generally personable, direct, and to the point, we couldn't make the language in our correspondence too technical, or we could risk loosing the bid entirely.)

A major hurdle which came up during the calendar development process was language and color palate.

How would we see a Total of Jobs without cluttering data with other entries?

What color could be used to signify department-specific tasks and employee updates?

Would there be enough range in color choices to signify when a job was complete, in progress, or needed to be started?

Below are my notes and iterations to final version for the calendar:

Due to the limited color selection on the calendar design system we used, we had to figure out which color would be used per entry and any other potential scenarios or hinderances which would arise during the workday:

I enjoyed my time at Murray Supply very much and left with a deep adoration for the industry.

I learned how society functions at a depth that most people are not exposed to regularly. I came across many insights about urban development and operational design which I apply to personal and professional life today.

The impact I left is felt through the positive relationships and network I built through strong teamwork and effective communication.

Below are some excerpts from reviews I received from my managers throughout my time at Murray Supply: