Embedded Files
PortProjectDashboardPort Project
The Port Project was a look at telephone numbers that were ported in (taken from another company) and ported out (taken by another company) over the period of months. We split them out in wins and losses.
In the 412 area code we actually lost more VOIP lines then Gained over the time period I looked at. The charts show how you can breakdown by area code and map them on an actual map.
The next set shows > 50 lines (large business) > 50 times (count of wins and losses). With the amount of data I looked at I had to use a quantity but as the data shows one specific customer, Level 3 Communications, was focusing and winning our large business users. At that point we focused on what they were doing to win them and marketing focused on creating a strategy to stop that attrition
The next set shows the quantity based on the individual months and area code. What this does is gives us a good map of the companies hitting our areas the hardest either by a call campaign or door to door campaign. Marketing then focused on a door to door during those months to change those losses to wins.
The last shows something our company knows but needed to be stated in this type of format. It shows that losses are relative to Tenure in Months. We lose the higher tenured companies/customers and win the lower tenured companies/customers. The problem we can see though is the quantity of loss is greater than the quantity of gain.
The Port Project was a look at telephone numbers that were ported in (taken from another company) and ported out (taken by another company) over the period of months. We split them out in wins and losses.
In the 412 area code we actually lost more VOIP lines then Gained over the time period I looked at. The charts show how you can breakdown by area code and map them on an actual map.
The next set shows > 50 lines (large business) > 50 times (count of wins and losses). With the amount of data I looked at I had to use a quantity but as the data shows one specific customer, Level 3 Communications, was focusing and winning our large business users. At that point we focused on what they were doing to win them and marketing focused on creating a strategy to stop that attrition
The next set shows the quantity based on the individual months and area code. What this does is gives us a good map of the companies hitting our areas the hardest either by a call campaign or door to door campaign. Marketing then focused on a door to door during those months to change those losses to wins.
The last shows something our company knows but needed to be stated in this type of format. It shows that losses are relative to Tenure in Months. We lose the higher tenured companies/customers and win the lower tenured companies/customers. The problem we can see though is the quantity of loss is greater than the quantity of gain.
ExceptionsDashboardExceptions Dashboard
The exceptions dashboard has 4 simple charts on it but all are very intuitive
Total Records – Just shows total records by day to find peaks and if we are more proactive moving forward
AHT by week by workgroup – Our Average Handling Time for tickets by internal and external teams
AHT as compared to Total Rejections – This gives us an insight as to, based off total submissions, with more rejected tickets the AHT should go down as the tickets should be completed quicker
ISOC entry showing predictive analysis – An ISOC is an individual code that can cause an issue. For instance, P6545 was entered multiple times in August. This showed us that there was an actual system issue. We alerted dev in the same month and they had a fix in a week after finding the root cause. If it were not for this predictive model they wouldn’t have been aware until much later
The exceptions dashboard has 4 simple charts on it but all are very intuitive
Total Records – Just shows total records by day to find peaks and if we are more proactive moving forward
AHT by week by workgroup – Our Average Handling Time for tickets by internal and external teams
AHT as compared to Total Rejections – This gives us an insight as to, based off total submissions, with more rejected tickets the AHT should go down as the tickets should be completed quicker
ISOC entry showing predictive analysis – An ISOC is an individual code that can cause an issue. For instance, P6545 was entered multiple times in August. This showed us that there was an actual system issue. We alerted dev in the same month and they had a fix in a week after finding the root cause. If it were not for this predictive model they wouldn’t have been aware until much later
DSGDashboardsviewDSG Dashboard
Our Desktop Dashboard showed the projects we are currently working on. We can call it a streamlined PM tool which I designed. We could keep notes, dates, dollars, etc. The Dashboards are what truly put us in touch with the work we were doing however.
Dashboard by Status – This gave an over view of the space and the status each project had. I also added the ability to click thru and pull up the exact reports that went into the specific count as well as clicking thru that to bring you to the specific item in question
Dashboard by Benefit – Same info, different breakdown. Gave us the insight into which benefits we were affecting
Portfolio Report – Showed the projects and the “lanes” they were in. Frontline, Key Projects, Marketing
Capacity – This was a concept I came up with that based off an 8 hour work day and estimate of project time we wanted to show the quantity of work our team was producing. I feel this gave our end users a good idea as to why we had to reject some projects and focused our work on the projects that would give us the most savings or produce the most revenue.
Optix JIRA Dashboard – This is a JIRA dashboard for our individual project. I pulled the dashboard into the window and reports are fully accessible at hand in our workspace without leaving the system.
Our Desktop Dashboard showed the projects we are currently working on. We can call it a streamlined PM tool which I designed. We could keep notes, dates, dollars, etc. The Dashboards are what truly put us in touch with the work we were doing however.
Dashboard by Status – This gave an over view of the space and the status each project had. I also added the ability to click thru and pull up the exact reports that went into the specific count as well as clicking thru that to bring you to the specific item in question
Dashboard by Benefit – Same info, different breakdown. Gave us the insight into which benefits we were affecting
Portfolio Report – Showed the projects and the “lanes” they were in. Frontline, Key Projects, Marketing
Capacity – This was a concept I came up with that based off an 8 hour work day and estimate of project time we wanted to show the quantity of work our team was producing. I feel this gave our end users a good idea as to why we had to reject some projects and focused our work on the projects that would give us the most savings or produce the most revenue.
Optix JIRA Dashboard – This is a JIRA dashboard for our individual project. I pulled the dashboard into the window and reports are fully accessible at hand in our workspace without leaving the system.
InteractiveWordCloudInteractive Word Cloud
Surveys are a big part of your clients feedback. With Tableau we can quickly create word clouds and pinpoint the issues we are currently facing with a system. This is imperative in moving in a fast, agile atmosphere. Quickly diagnosing the heaviest issues that a user faces and caring for them quickly and efficiently.
Surveys are a big part of your clients feedback. With Tableau we can quickly create word clouds and pinpoint the issues we are currently facing with a system. This is imperative in moving in a fast, agile atmosphere. Quickly diagnosing the heaviest issues that a user faces and caring for them quickly and efficiently.
Google Sites
Report abuse