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: Node Sets

  • Creation and manipulation of Node Sets is the foundation on which the product operates
  • A node set describes a hosting environment. It is a collection of one or more virtual and/or physical instances, scaling up or down as necessary based on need. We need a way in the UI to create and modify the parameters
  • Users will be easily able to create them in an intutive manner
  • User will not have to do this without entering a command line

Project Constraints

  • Node sets, once we came up with the name, were very similar to workloads in the fact that they needed a lot of data to be added by the user, therefore we used a form field, data entry model for this feature as well pretty much from the beginning
  • Taking existing framework be built earlier in the process (see workload creation) and adapting its general principles of design to use in this instance in order to keep consistency in the UI
  • We believe that the dashboard users will easily be able to build node sets from this platform by building an intuitive interface that address all current needs in an extensible manner for future growth

Scytale Enterprise: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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: Node Sets

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. More so we built goals for the entire product launch. This includes how many active customers we would get within a certain timeline (which is not disclosable information)
  • Using the terminology node was after a lot of back and forth with the product and content teams. The assumptions we made, based on looking at other similar technology models, is that the node is the correct terminology, but this has not been confirmed with user testing
  • We felt that post-launch was the best time to formalize our research and test our assumptions since we'd have a concrete site to work with
  • Coming up with appropriate terminology that worked for our stated need was the hardest thing about this part of the product development. We went back and forth for days on the proper term for this and waffled between cluster, node set and a couple other phrases
  • We made comparisons in terminology from other products, and came to the conclusion this was the right terminology
  • Not that I didn't know this already but this completely reiterated that words really do matter more than a lot of people realize when building out online products.
  • The fact that we went back and forth on one term for multiple days reminded me to be very thoughtful when content is my responsibility
  • This full product was launched 19 June 2019