Somos.tech is a nonprofit organization dedicated to building a thriving community in the tech industry. It provides networking opportunities, essential resources, mentorship, and a strong sense of belonging.

Discover | Problem

It's tough out there for a lot of Latin and Hispanic folks when it comes to finding a job. One big reason is that they often don't have a strong network or community to lean on for support. Without those connections, it's a real challenge to land opportunities and get ahead in their careers.

My Role

Activities

Tools

Duration

User Research | Competitive Analysis | Affinity Mapping | User Personas | User Flows | Task Flows | Sketching | Wireframing | Prototyping | UI design | Usability Testing

Overview

12 weeks to present | Part-time

Figma | MS Teams | MS Loop | MS Clarity

Work process

Product designer. Collaborative work with cross functional disciplines.
Software engineers, product managers, CEO.

Starting the job search in tech without a supportive community is tough. As a Hispanic/Latinx, I feel alone, knowing there are plenty of people like me out there facing the same challenge.

Research | Competitive analysis

3 popular tech sites were involved in my analysis: Designlab | Woman in Tech | ADA

Strengths

  • Clear mission statement.

  • Hierarchy of information architecture.

  • Build community through real projects and events.

  • Showcase real outcomes through metrics.

Findings

Although they offer similar features and tools for skill development and career advancement, none of the platforms provide opportunities for users to engage closely with the community. Additionally, none of them have integrated AI tools to enhance the user experience throughout the job hunt journey.

This presents an opportunity for Somos.tech to stand out by incorporating AI-driven resources to better serve its audience and gain a competitive edge while fostering community engagement.

Research

Research

At the start of the design process, I received guidelines from the board members of Somos. As we progressed, we either confirmed those needs or set some aside for later consideration. Unlike previous times when interviews were conducted early on, we did not conduct interviews this time.

  • Discover Disciplines

  • Plan the career development

  • Get connected with our recruiter

Screenshot website

  • Help with job search

  • Use our Network

Then I started to familiarize myself with the web page and its resources to effectively leverage them for the new section 'Starting in Tech'.

Actual information architecture

I wanted to make it easier for people to find what they're looking for on the website. Right now, it's hard to find things quickly, so adding a new section would make it even harder. That's why I worked on organizing the website better to help users navigate more easily.

  • Too much text

  • Hard to understand how to proceed

  • Not engaging

Rethinking a new information architecture for the whole website

But things didn't go as planned. The team reminded me that I wasn't supposed to revamp the entire site. My job was just to handle the new section, 'Starting in Tech'.

This experience taught me an important lesson: sometimes, you can't fix everything at once. Instead, you have to make the best of what you have. “Do your best with the resources you have”

So, I dove straight into the Starting Tech section, and here's what we have


To ensure the user remains at the core of our ideation process, I've formulated point of view statements and how might we questions.

Research | User Persona

After gathering all the research, I synthesized the data and defined the problem. To clarify my target and empathize with them, I created a user persona, Sofia Ramirez.

Define

Story board

Define | Feature Set

I prioritized the features based on what users need, what we found in our research, and what Somos.tech wants to achieve.

Define | User Flows

I've created flowcharts for our persona, Sofia, and key features.

* Flow chart link

I created a storyboard that shows the user's emotional journey while interacting with the product or service, from frustration to satisfaction.

These flows aided in defining the wireframes necessary for prototyping.

Design

Building upon research and the defined user flow, I will start the design stage. This phase will begin with the development of low-fidelity wireframes, allowing for rapid iteration. Subsequently, I will progress to mid-fidelity and high-fidelity designs, aligning closely with user requirements.

Wireframes

Considering my persona's goals and user flows I created low-fidelity wireframes to truly grasp how the system should function.

Low fidelity

I started with low-fidelity wireframes to explore how design patterns could be replicated for a cohesive and streamlined website.

After receiving feedback from both the team and users, I modified and incorporated their suggestions to create a user-centered design.

Low-fidelity V2.

During the usability testing of the low-fidelity prototype, participants provided valuable feedback, emphasizing the importance of essential features like the 'submit resume' function. Additionally, they suggested incorporating 'add skills' and 'interview preparation with AI' to enhance the user experience. However, after discussing with the project manager, it became clear that adding these features was not feasible at the current stage of development.

Due to privacy concerns, storing private data such as skills information was not permitted for the nonprofit project at this time. While I agreed with the users' feedback and recognized the potential benefits of these features, I had to prioritize adhering to project constraints and ensuring compliance with data protection regulations.

High fidelity

For this phase, I opted to skip the mid-fidelity stage and transition directly to high-fidelity designs. This decision was driven by the need to align the program's design with the existing style of the page. With minimal exploration required at the mid-fidelity stage, I focused on refining the design elements and ensuring consistency with the current aesthetic.

Test

Deliver | Usability testing

I conducted five remote usability tests to gain insights into users' experiences with the site. I got valuable feedback on usability, navigation, and overall user satisfaction, informing iterative improvements to enhance the user experience

Findings

Iterations

I'm a bit confused about what should come next. I am not sure to press the finish button”

Through further refinement and enhancement, I aim to create a more polished and user-centric experience that addresses the needs and preferences of our target audience effectively.

Launched product

Feedback included

  • Included an arrow in the step bar to allow users to continue without needing to scroll down.

  • Included brief introduction.

  • Ask more tailored questions to provide a unique roadmap and appropriate job search results.

Launched product

Feedback included

  • Included an arrow in the step bar to allow users to continue without needing to scroll down.

  • Included a clear option to see the group information before joining.

Launched product

Feedback included

  • Introduced a brief, user-friendly introduction to guide users through the process.

  • Established a dedicated space for users to input location information, streamlining the experience.

  • Enhanced the design of the job search link by increasing padding and switching to a complementary secondary color for improved visibility and usability.

Latest iterations

Launched Product

Feedback included

  • Implemented clear sections to organize the content of the page, distinguishing each section from the other for improved navigation.

  • Designed clear calls-to-action (CTAs) to establish hierarchy and streamline user navigation, ensuring users know where to go next.

  • Incorporated a feature to notify users upon completion of the Starting in Tech program, with an option to share their achievements on LinkedIn.

  • Enhanced user experience by providing clear guidance on what to expect after completing the program, ensuring better organization of information, and utilizing recognizable patterns for clickable elements.

  • Added a crucial feature allowing users to leave reviews, facilitating feedback collection and improving the program's effectiveness.

  • Missing some brief information in the first step

  • “I prefer not to scroll down to the bottom to continue or go backward.”

  • Confused about the position of the finish button.

  • Easy to follow steps

  • Useful tool

  • Innovative

  • Simple Design

View the latest deliverable which is still in progress

Key takeaways

  • Skipping the interviews phase due to time constraints was a mistake. Designing based on assumptions led to a large, disjointed product with unnecessary features. Testing revealed that users prioritize roles, network building, and resume creation over trendy features like roadmap planning and search functionality. Moving forward, we must prioritize user needs to ensure our product remains focused and effective.

  • Through my experience with the Starting in Tech project, I've come to appreciate the power of putting users first. You know, it's easy to get caught up in all the exciting ideas swirling around, but I've learned that focusing on what really matters to our users is key. Looking back, I realize I could've pushed even harder for a simpler, more user-friendly approach. After all, when we prioritize our users, we're not just building a product; we're crafting an experience that truly resonates with them.