Gremlin Mid-fi Prototype

View Attack Creation Prototype

I focused on 3 things

  1. Too much eye and mouse movement while creating attack and navigating between attacks to see what has already been created
  2. Too many clicks to get to the point and see whats needed in each step to reveal the next
  3. Once steps mostly complete, overwhelming amount of information to review or see has been completed versus walking you through step by step and going ability to review and edit

I prioritized ? Why that?

  1. Amount of clicks from “attack creation” to “acknowledgement of completion”; less clicks, less effort, more productivity creating a daily/weekly/monthly habit that’s intuitive.
  2. One step at a time while seeing where user is in the flow to focus them on task and accelerate their responses without distraction of prior or future content to fill.
  3. Minimal mouse and eye movement to next step interaction while seeing the whole picture of the attack. Most of user interaction with sites/products is scrolling, mousing and looking around for the next thing to do and why.

My process:

  1. Research chaos engineer principles
  2. Research technical limitations base on my product and site research
  3. Research existing UI to learn what it does and how; step by step attack creation, deletion, monitoring etc,; the whole picture
  4. Start identifying places with over-info or incorrect step flow, duplicate info, similarities in content between actions
  5. review each function; impact, container labels, schedule, etc of “creating attack” and evaluate places to optimize, minimize, maximize etc.
  6. start sketching very lean ideas capturing placement of primary elements like nav, CTA, data viz, and steps
  7. start brand placement ideation while identifying ui difference and ux flow
  8. Mobile first. Not because thats your target audience, but because it help find the crux of the biscuit, the most import thing for the user to focus on. Put together a few possible scenarios from existing ui for user path to successful attack creation; involves mapping out current flow with amount of clicks
  9. test content step by step with live or online users
  10. test features with live or online users
  11. Iterate at least 3 various ux flow with minimal ui change focusing on most prominent CTA for the user
  12. pick one iteration to clean and polish and produce prototype in either InVision, Figma or better yet html, css js.

What would you discuss?

with engineers:

  1. time constrains on updating CTA on step to auto-update headline dynamically upon completion
  2. what additional data metrics can we scrape from the current data we have and if it’s relevant, how do we serve it up?
  3. what are the “real” success factors of an attack?
  4. Which parts of the product are old tech v new tech?
  5. which products or features lend themselves to other products or upselling and why?

with Customers:

  1. what are the key details in identifying if your gremlin was successful?
  2. what else do you want to see you gremlin do?
  3. Do you find yourself creating small variations of exiting attacks? why?
  4. How do you know you set up the attack correctly?
  5. Can you explain what you do to others in a quick elevator spiel?

If I had more time….

  1. Sxplore segmenting the gremlins based on maybe type of experiment you want to perform/li>
  2. I would get a better understanding of the success factors of an attack.
  3. Create some data viz around the attack
  4. change both fonts to one and have more weights that are a bit more legible
  5. edit headlines/CTAs to match more cleverly
  6. edit spacing in between elements more methodically
  7. give the individual gremlins personality, the personality will be a mix of tutorial cleverness to help user champion tool
  8. I would add animations for a few elements that seem like they could use the benefit of an animated confirmation of completion