Scribd
Upload
25 views3 pages

CXO Dashboard Documentation

The document provides documentation on a CXO dashboard. It describes the intended personas of IT department heads and CXOs who would want a high-level view of application health, issues, and availability. It outlines what information and customizations should be included in the dashboard such as the top applications and transactions to monitor and discuss deep dive functionality.

Uploaded by

vilazviji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views3 pages

CXO Dashboard Documentation

The document provides documentation on a CXO dashboard. It describes the intended personas of IT department heads and CXOs who would want a high-level view of application health, issues, and availability. It outlines what information and customizations should be included in the dashboard such as the top applications and transactions to monitor and discuss deep dive functionality.

Uploaded by

vilazviji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

CXO Dashboard documentation:

Persona:

Primary persona: With CXO dashboard the primary personas we are targeting: IT Dept
heads, and CXO, CIO level persona..

Secondary persona: Any client application owners can also make good sense of this
dashboard and can find it useful.

Underlying assumptions:

The above persona has general awareness of APM product, and any terminologies used in
the dashboard like workload, transactions, response time, Digital experience monitoring,
service, host and application availability.

What all these persona want to see in the dashboard:

CXO, CIO level would want to see, for all their application monitored (there could be 100s of
them) are they all running healthy, if not, where’s the degradations/issues happening?

Dept heads, Application owners, their scope is little limited.. lets say, Payments dept head..
he would be interested in all applications related to Payments.. Application owner for UPI
payments, he would be interested in particular application health summary data.

What can be customised and why is it needed?

The default number of applications we are going to show in CXO dashboard, lets say 10...
there will be an option to select which 10 the users want to see.

The same should be possible for top 5 transactions, where users can select among 100s of
transactions, the top 5 they want to view.

Because we don't know which applications or which application transactions are important
for users of CXO dashboard.

What’s the key takeaway of CXO dashboard:

Ultimately, CXO or Dept heads, they would want to have a bird's eye view of what's
happening at application level. " which could impact their business or which is impacting
their customers and customer experience badly.. . What is the availability? What are the top
transactions, how many are slow/error etc... how many end users are using that
applications (along with versions), how many of those version has error? ...
CXO Dashboard Application summary pod:

Shows 3 key data such as number of problems reported in the application by HEAL number
of Early warning reported in the application by HEAL and overall application availability in
percentage.

CXO Dashboard Application summary:

Once any application is selected, we will be showing 8 different pods which displays key
insights on what’s happening to that application.

Deep dive screens from CXO dashboard:

For CXO, CIO or Dept head kind of person, do we think he/she will click and go to our deep
dive screens? May be not!

So for such personas, or users when added in the CC, we have to have a selection, whether
does he need access to Deep dive screen or not can be selected, so that, based on the
selection, the clickable thing in pods will be enabled or disabled for such a user.

Our primary persona discussed may not be technical enough to understand our deep dive
screens, but may our secondary personas would be, it would makes sense to enable and
allow to go deep dive with CXO dashboard for such users.

POD1: It’s the Signals POD.

Shows number of problems reported by HEAL.

Shows number of early warnings reported by HEAL

Shows number of changes reported by HEAL for any configuration changes that has
happened for that application.

Shows number of changes reported by HEAL for any file changes that has happened for that
application.

Why is this data important?

Number of issues reported for an application is good indicator of application health, and a
good starting point to check the issues and do a deep dive.

Deep dive screen: Upon click of this POD, the user will be landed to our Signal page.

Pod 2 and 3:

We show the workload

You might also like