DNS Reports

DNS Reports

Project Details

During my co-op at BlueCat Networks, I got the opportunity to partake in a research project regarding DNS Reports. The purpose of this research was to determine the value proposition of adding reports to BlueCat's Edge product and to determine the content and format of the report.

Team

  • 2 Technical Project Managers
  • 3 UX Designers

My role

  • Notetaking during user interviews
  • Analyzing the user feedback
  • Presenting findings with my Team

Duration

8 months

The Process

1

Understood the Environmental Space

As another designer and I were new to the company, we first started by understanding the problem space. It was important to understand the space we were designing before starting. We:

  • Talked to a developer to determine what is feasible
  • Explored current functionalities of Edge

2

Exploratory Session

With our design team and the Edge Product Managers, we conducted five exploratory sessions to gain an understanding of what would be useful to the customers. We asked questions such as:

  • Would users find reports valuable?
  • Which type of reports would they like to see?
  • What kind of reports are they currently using?
  • How would they use the information?

Results

In Miro, we grouped topics together to find similarities and made a list of quotes and key takeaways. Reorganizing the information on Miro helped us analyze the results. With this info, we created a presentation and presented the findings to executives.

MiroBoard:

Miro Board

We found that customers did feel these reports were useful. We also found that customizability and notifications were important. This was decided that it would be included in a phrase two, as it was not possible with the resources we currently had allocated.

3

Wireframe Validation

From the results of the exploratory session, wireframes were made by my teammate. We wanted to confirm our idea, so we took the wireframes and conducted wireframe validation from 3 customers.

During the session we asked questions about:

  • The location
  • The timeframe
  • Data visualizations
  • Content
  • Layout
Link to the mocks

Results

Similar to the last feedback session, we documented and analyzed the findings.

MiroBoard:

Miro Board
4

Feature Review

The wireframes were then transformed into high fidelity mocks by my teammate and a feature review with developers was conducted to begin the implementation. During the feature review, the design was handed off to the developers.


5

Implementation

As the feature was being built, a demo was conducted to show the company what they had so far. During the demo, we found differences between what we had designed and what developers had produced. As a result, meetings were held to discuss the difference and also understand why the changes were made. We made changes to our design based on the meetings. We also held an additional call with internal Solution Architects to verify that the changes would still meet the needs of the customers.