Catherine Hicks
User Experience and Product Design Professional

Scytale

Scytale was started in 2017 by seasoned engineers from Amazon Web Services, Google, Okta, PagerDuty, Splunk, and Duo Security who want to help enterprise engineers securely and easily build identity-driven, large-scale distributed software systems

Role & Project Summary

  • Scytale Enterprise: Event Logs

  • Viewing Event logs allows users to troubleshoot and have insight into their installation
  • Users need an audit stream in order to troubleshoot potential problems
  • Users will be able to see and filter all events on their servers 

Project Constraints

  • The idea of user management was the first piece of our administration tasks that were built for the platform. We looked at AWS, Okta and Google services for how they handle user management as concepts we could explore in our application
  • Users must be able to see all types of data in the logs and be able to filter it by type so they can pin down any potential trouble spots
  • We believe that putting together an efficient event log will allow users to quickly troubleshoot problems and be able to resolve them
  • Product requirements were fleshed out by the Product Manager that allowed me to know which events to design the 1.0 version of the event log for

Scytale Enterprise: Event Logs

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Scytale Enterprise: Event Logs

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Scytale Enterprise: Event Logs

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Summary

There is no specific goals for this feature. Moreso we built goals for the entire product launch. This includes how many active customers we would get within a certain timeline (which isnot disclosable information)

We made the assumption of what types of events people will need to see in order to troubleshoot their potential issues with Scytale Enterprise. We did this with some knowledge of errors currently showing up in logs and also some understanding of what the potential more common errors would be, however this was not confirmed at time of launch by any user validation

We felt that post-launch was the best time to formalize our research and test our assumptions since we'd have a concrete data to work with

This is on the roadmap in the near future, however we felt that in the initial concept phase, the feedback we got in less formal conversation, and a basic alpha of a platform that was used as a basis for enhancement, we felt we were not designing this platform completely blind without understanding the users in some capacity so we felt we could hold off on introducing formal research into the mix until we had something more concrete to get get feedback on

Did we want to have different log views for different types of events or one singular view for all events? We had differing opinions on the team when we started, and it was up to me to figure out a way to make everyone happy

I decided to work towards the singular view with filtering because I, as the UX professional, felt that was the overall best experience. While not validated by users, I looked at other event logs (ie google) and saw that most of the ones I audited did something similar, so I felt comfortable it would be something users were familiar and comfortable with

How to mitigate long drawn out disagreements by being firm in my opinion and being able to vocalize it, I found that my team reacted favorably to that.

While I knew I was hired as a SME, I often was erring on the side of being too collaborative instead of voicing my opinion and this part of the project really reminded me of what my role is

This full product was launched 19 June 2019