Structural App

Creating and improving data visualizations with in the Structural app
The Client: 

Structural is a Saint Paul startup that provides a tool to mid-to-large sized businesses to increase enterprise productivity. They have raised over $5 million dollars from investors and are used by local businesses like Sunrise Bank and Ecolab. Structural exists to provide a tool through which businesses can leverage their employee’s data for employee development, to build better teams, and find the person for each task or project.

The User:

The primary users in view for our project were team managers who want to improve their teams, and team members who want to find knowledge within their organization. Organizations which find the most value in a tool like Structural are large companies with over 500 employees and distributed companies with many locations.

Challenge

Structural is addressing challenges of communication and knowledge that large and distributed organizations face. Structural wants to solve these problems by giving its users valuable and actionable data within the app. Our challenge was to create new features to surface the information users need in order to make important connections and improve their productivity.

Solution

To provide a solution which would enhance the Structural app to be more useful and engaging for Structural customers, we wanted to increase clarity and decrease confusion in the app by surfacing forgotten knowledge within the organization, eliminate missed opportunities by making timely connections, and improving communication among the users.

Role and Tasks:

I worked with three other UX designers on this project. We began by vocalizing our areas of strength and interest. Two team members loved to do research and two other members loved to ideate and design. My role throughout the project varied, but I supported the team through script and survey preparation, presentation design, and gathering and organizing client handoff documents.

Next Steps:

The client was thrilled with our work and took our recommendations seriously. The next steps on the project will be to strategize about the implementation of each feature and to continue to research with Structural users to understand what additional features will be most useful.

Project Takeaways:

I really enjoyed this project. It came together slowly and at one point we struggled to get in front of Structural users. However, each phase was challenging and rewarding. Our team was well balanced, from the business minded and mathematical to the creative and detailed. If I could repeat this project, I would like to be more involved in the designing and prototyping work. Since there were two team members who love to prototype, my creativity and love for detail got channeled toward our presentation keynote instead.

Client Kickoff Meeting

Our team met with Structural at the kickoff meeting to get the details necessary for us to begin work on the project. Ron, the CTO, and Haranshvir, the UX lead, came to brief us on Structural as a company, the SaaS application, and the challenge they were giving us.

Our task was to work within the existing Structural UI and with their existing data fields to create meaningful and actionable data for users of the app.

Client Kickoff Meeting

Our team met with Structural at the kickoff meeting to get the details necessary for us to begin work on the project. Ron, the CTO, and Haranshvir, the UX lead, came to brief us on Structural as a company, the SaaS application, and the challenge they were giving us.

Our task was to work within the existing Structural UI and with their existing data fields to create meaningful and actionable data for users of the app.

Initial Research

In order to research deep and wide, our team divided research categories and began digging to learn more about actionable data, meaningful visualizations, the kind of information managers find useful when building teams, and more. Between the four team members we interviewed numerous target users, completed a competitive audit, and discovered creative data visualization ideas.

Card Sort

While interviewing users at Clear Night, we did a card sort activity to learn what sort of data users found most important when viewing another employee’s profile. Most of the information users wanted to see related to their current role, skills, and qualifications. This was the most helpful component of our research.

On-Site Research

I wrote a script for us to use as we interviewed Structural users at Clear Night, a strong Structural customer. Each interview was insightful and helped us gain a better understanding of the sorts of information users go to the app to find.

Feature Cards / Sketches

From our card sort and interview data the team developed 12 features we thought would best serve Structural users. We sketched each feature on a card and added a description to help users grasp the concept.

View Sketches

Google Survey, Kano Survey, & Analysis

We added these feature cards to two lengthy Google surveys (1/3 kano analysis), one which we sent to outside participants, and the other to existing Structural users. We received over 40 results and distilled the kano analysis data into a spreadsheet understand which features users rated highest.

The org chart, project tracker, and role history features gained the greatest support.

High-Fidelity Prototypes

With research supporting the decision, half the team designed two prototypes, one for the project tracker, and one for the org chart and role history. These were created to exist within the existing Structural app.

View Wireframes

Presentation and Client Handoff Meeting

While the prototypes were being finalized, myself and another team member created the script and presentation slides for our final presentation and client handoff meeting. The team presented our process, findings, and prototype to Prime instructors, students, and visitors.

Afterwards, we met with the client to hand off our deliverables and answer any questions they had.

Presentation and Client Handoff Meeting

While the prototypes were being finalized, myself and another team member created the script and presentation slides for our final presentation and client handoff meeting. The team presented our process, findings, and prototype to Prime instructors, students, and visitors.

Afterwards, we met with the client to hand off our deliverables and answer any questions they had.

View KeyNote

Methods

Deep Dive  •  Contextual Research  •  Secondary Research Interviews  •  User Interviews  •  Card Sort  •  Survey  •  Kano Analysis  •  Sketches/Wireframes  •  Low-Fidelity Prototypes  •  High-Fidelity Prototypes  •  Client Kickoff Meeting and Final Delivery

Tools

Sketch  •  Keynote  •  Google Forms (survey)  •  Kanban Board  •  Google sheets  •  Adobe XD  •  InVision