When I started reading up on User Experience (UX), the field I wanted to pursue, I noticed that a bunch of the articles I read mentioned networking.

Set up coffee chats with UX professionals, the articles said.

No thanks, I thought.

Until I joined Seattle’s Ladies that UX chapter, where I connected with an amazing mentor. She gave me advice about the industry, my internship search, and, or course, networking. She talked to me a lot about networking.

I was terrified. But I didn’t want to disappoint my mentor, so every couple of weeks I found myself cold emailing or messaging a UXer on LinkedIn to set up virtual coffee chats on Zoom.

The first year of networking, I think I talked to about 8 UX professionals. They were awesome, but I felt awful. The whole day before the conversation, and sometimes even after, I had so much anxiety I found it hard to focus. I nervously fumbled through those 30 minute conversations (thank you to everyone who spoke with me, I’m grateful for your patience :)) and I felt insecure about my abilities and felt unqualified to talk to UX professionals; I didn’t know what I was doing — what if I was wasting their time?

But each conversation I had with a UXer taught me something. I got to hear about someone’s journey from retail to travel design; a conversation with a UX Researcher made me realize that I actually wanted to be a designer; a Product Designer working at a hospital inspired me to explore career opportunities in the health tech industry. I even got my first UX internship by networking with a professor. Sure, there were 1 or 2 awkward virtual coffee chats, but for the most part, I got to have some thoughtful and impactful conversations.

With time, my anxiety surrounding networking began to fade. This past summer, I just wrapped up an internship and had between 1–5 virtual coffee chats with design professionals per week. My anxiety about networking has decreased a ton since the first time, and I’ve genuinely had so much fun meeting other designers and hearing their stories. I’ve even kept in touch with some of the people I’ve had virtual coffee chats with, which has been really meaningful.

I feel a lot more confident now, and it’s really helped me come face-to-face with and squash some of my imposter syndrome. However, networking still can be challenging, especially when you start out. Here are some practicals on how to make networking easier.

1. Join a design community. Ladies that UX, Hexagon UX, there are so many ways to join a UX community. and once you do. The people in those communities are generally excited to connect and meet, and there’s a lot of people within who are happy to talk.
2. Find a mentor. If you’re like me and you need some external pressure to make you do something, a mentor can really help you out. My mentor provided a lot of accountability and encouragement for me as I began networking.
3. Reach out to people who are doing things you’re interested in. LinkedIn and Twitter are great ways to do this. Sometimes it’ll take 5–10 cold messages to get a response, but there are so many people who genuinely want to help you and are happy to share their advice and stories.
4. Be clear about why you want to talk to someone. People don’t know how to help you unless you know what you need help with. Are you curious about what working in a certain industry or company is like? Are you trying to decide if you should go into UX Research or Design?
5. Go into a conversation with questions. No, you don’t have to verbatim follow a script (it’s still important to leave room for a natural flow of a conversation — small talk at the beginning always helps to ease into a conversation). But, I’ve found that questions have always helped me feel more prepared and safe going into conversations.
6. Remember that the virtual world can make networking easier in a lot of ways. You get to talk to people from the comfort of your home, you don’t have to commute to meet…it’s quite convenient. Plus, I always have my questions pulled up on my screen so if I blank, conversation topics are always top of mind.
7. Follow up and thank people for their time. It’s generous for professionals to take time to talk to someone they may not even know; a simple, thoughtful message can be really kind and can go a long way.
8. Have fun. Yeah, yeah, I know this sounds cheesy. But honestly, think about it: When you network, you get to meet people who are doing super interesting, cool things. You get to hear about their journeys and ask them questions and be inspired by them, and that’s honestly pretty exciting.

Lastly, I know that I often struggled with feeling guilty about asking people for their time — one thing that helped me with this was the realization that everybody had to have some help to get to where they are now. And by receiving help and advice, we’re setting ourselves up to be able to offer that same help and advice to others later.

Happy networking :)

I’m just wrapping up taking a class called Physical Prototyping, which is where a bunch of HCDE (Human Centered Design & Engineering) undergrads and I learn how to do some Electrical Engineering kind of stuff. To be completely transparent, I definitely lean more into the design aspect of my major than the engineering aspect, so this class was one of the hardest I’ve ever taken. Nevertheless, thanks to hours of work and the generous help of my TA, professor, and the kind students in my class, I was able to bring to life an idea I had — a night light.

Concept

There’s this staircase that leads to my apartment gets that gets really dark at night that leads to my apartment, so I wanted to use an LED strip that functioned as a night light to light up the staircase.

Implementation

I started out by sketching out a couple schematics that indicated how the components I was using would work. To create this project, I used a photoresistor (which took in light values) and IR remote receiver (which allowed me to turn the LED strip on and off) as inputs and used a pin connecting to a transistor (which allowed me to control the LED strip via my computer) as an output.

I connected all of the components to on my breadboard(which is pictured below), and began coding via Arduino.

Some of the biggest challenges I had with the technical aspect of the nightlight included:

• Calibration: I had initially set up my transistor to turn the LED on and off based on how much light the photoresistor took in. However, during office hours, my TA and I found that the LED strip was so bright that when it turned on, the photoresistor would start reading the LED strip’s brightness as well, and thus the transistor would switch the LED strip off, leading to a blinking effect. To respond to this, I used Arduino’s callibration example code to automatically identify maximum and minimum sensor values and turn the LED strip on and off accordingly.
• Breadboard issues: One of the other issues I made a lot of little mistakes like with the IR remote, when I was sometimes connecting the wrong wire to ground. Another time, I didn’t have my claw clamps properly connected on the dots of the LED strip, so the LED strip wasn’t turning on.

After getting the code figured out, I went on to create the enclosure for my circuit board, so it wasn’t out in the open. I started with an empty yogurt container, then went on to cut a few openings in the front and sides that allowed for my power wires and photoresistor to peek out. Then, I went on to cut holes in the top of the yogurt container that allowed for the LED strip to come out of. I topped it off with a fun little mushroom hat :)

Final Video and Reflection

While I made sure this project was feasible, there are a couple things I would iterate on if I were to continue on this project:

• I would provide multiple brightness and light color options for the LED strip to make it more interactive and customizable for users.
• I also include a strong motion sensor so that users wouldn’t need to use the remote to turn it on or off.

Overall, this project was definitely challenging for me. It took awhile to troubleshoot and debug, since both the code and the physical wiring both had potential to have issues (the Arduino code is linked here, in case you’d like to take a look!). I’m super grateful for the experience though, and it was really exciting to share the final product with my roommates and peers. (Also, shout out to my roommates for being the best actors ever :))

Our prototype, CloudZzz, is a speculative sleep technology that helps people develop healthy sleep habits via a through a pillow and a Cloud AI system. We used a variety of prototyping techniques, including a video prototype to communicate the products capability to measure sleep, set alarms, and track REM cycles. We also have a digital mobile app component that links to the data to display analytics visually to the user.

Goals

We were motivated by the UN Sustainable Development Goal #3: Good health and wellbeing. Through the different prototyping techniques we use, we evaluate desirability and usability, exploring whether this product concept is something that users would want and if it could actually improve sleeping habits.

Implementation

We used a total of 4 prototyping techniques for our project.

Cardboard: We constructed a cardboard prototype to serve as a low fidelity version of our Cloud AI, which is a voice-assisted technology. This cardboard prototype helped define sizing and shape for the 3D prototype.

3D prototype: Based on the cardboard prototype, we 3D printed a higher fidelity version of the cardboard prototype. The 3D prototype of the user can speak with the Cloud AI to set alarms, play sleep sounds & music, and communicate about sleep data. This prototype is voice activated to help users reduce blue light exposure.

Soft Goods: We gathered a cloud-patterned fabric and stitched it together to create the pillow case that accompanies our Cloud AI model. The pillow fabric has the technology to track the user’s REM and sleep cycle, as well as determine when the user is awake and asleep.

Video: In addition, we filmed and edited a video prototype that showcases the Cloud AI + pillowcase in use. In our video prototype, we also showcase a digital aspect of our product which is a few screens of an accompanying app. These screens showcase more detailed data on the users sleep cycle and options for setting alarms, etc. This video prototype was then shown to some user participants in order to gather feedback.

Evaluation

One of the first parts of our evaluation process was during our critique session, where we got much feedback referencing project scope. We had initially set out to evaluate usability, feasibility, and desirability, but because we didn’t have the technological means to do feasibility, we decided to limit scope to usability and desirability.

Moreover, our product initially had the capability to do aromatherapy and was able to record dream-tracking, but our peers pointed out that these capabilities were over-the-top and had several privacy concerns if the device was recording every sleep sound. Thus, we decided not to include these capabilities in our final product.

Outside of critique, we evaluated the effectiveness of our prototypes by asking three potential users to watch our video prototype (which demonstrates use cases for our prototype) and conducted a user interview with them.

We found that:

• 3/3 users would use our product
• ⅔ users expressed concerns with the visual design and cohesion of our product (they couldn’t tell that the pillow and Cloud AI went together
• 3/3 users were able to identify use cases for the product

Analysis

Based on our evidence, here are a couple things that went well:

• We found that our product was desirable; our feedback sessions indicated that users would use the product based on the concept.
• The fact that our product was not heavily related to screens; users appreciated that they did not need blue light exposure before bed to use this product.

Meanwhile, we also received a couple bits of feedback that would influence what we might to differently next time:

• Our users pointed out that our 3D prototype and sewing prototype did not look cohesive, which hindered the visual appeal of the product. In the future, we would try to make the prototype look more cohesive by using more similar colors and shapes between the fabric for the pillow and the Cloud AI.
• During our ritual dissent critique, our peers brought up concerns about the feasibility of how well the pillow would measure sleep, especially for users who moved a lot in their sleep. In future iterations, we might try to consider other forms of sleep tracking outside of the pillow.

Overall, our prototype definitely has room for further iteration, but the product itself is desirable and holds promise. Based on our prototyping and evaluation, we believe our product has the potential to help further the UN’s goal of good health and well-being.

Last week, my classmates and I were tasked with building a Wizard-of-Oz prototype: one that functioned like an actual product, but actually did not work. The intention of this was to explore and test out ideas without being constrained by production costs and feasibility of building.

Designing a Wizard-of-Oz game

My group and I chose to build a voice AI prototype. We created a game called “Word World”, where the user would get to choose one out of four categories (Food, Movies, Countries, and Animals). They would then select a mode (Alphabetical or Single Letter), and based on their selection, they would have 5 seconds to come up with a word for the category they chose. For instance, if they picked Food and Alphabetical, they might say, “Apple, Banana, Cantaloupe, etc.”

The game included a training mode, in which we walked our users through how to play. It then went on to play the game with the users (giving them positive or negative sound effects based on their answer), and included a portion at the end when the user had the option to make the game harder or easier.

Testing a Wizard-of-Oz prototype

To test out the prototype, we put a phone in a black box, and connected that phone to our Wizard (Ryan) through Zoom. Then, we asked a super kind student who we found outside our classroom if he would like to test it out. I acted as a facilitator while our user tested out the game with Ryan (who he thought was actually programmed AI!). Han also acted as a Wizard and produced sound effects (a “ding” and an error sound) per answer our user gave. I can’t attach the video here because we don’t have consent for that, but here’s a picture of what our set up looked like.

We went into user testing to find these measures:

• The number of times our participant had to ask the facilitator (me) a question because something was unclear: 3
• Learnability of game: rated 5 on a scale of 1–5 (with 1 being difficult and 5 being easy)
• Enjoyment of game (likeliness of playing game again): rated 4 on a scale of 1–5 (with 1 being not at all and 5 being extremely likely)

Analysis

I learned quite a few things about behavioral prototyping from this.

1. Some of our questions were really confusing. Our user visibly looked confused and had to ask me to clarify how to answer some questions. For instance, we asked our user how easy the game was, which he found difficult to answer (he changed his mind and went back and forth). We could’ve asked him to pick a mode “easy/moderate/difficult” instead.
2. In terms of facilitating, in the beginning I didn’t clarify that the user could end the game at any point. So when our Wizard asked him “Would you like to play again”, our participant said “Yes” three times. I had to tell him that it was okay to end the game, which he promptly did after I explained that he was welcome to say “No.”
3. In the future, I would’ve liked to explore more ways to measure how much a user liked a game. I know we asked a question about if they would play it again at the end, but people lie sometimes. I wish we could’ve gotten more feedback on if the user found our AI to be too repetitive, etc.

Overall, behavioral prototyping, especially for voice, was super helpful because it allowed for us to explore different responses and use cases for how participants would interact with our game; I would be curious to see what another users experience might look like.

Design

Last week, I was tasked with creating a video prototype for a health/wellness type product. I decided to focus on the nutrition space, on a product called Nutri-Scanner. Nutri-Scanner is a device that scans all the items in your fridge, then generates a list of recipes that are sent to your phone to give you cooking inspiration and options.

Storyboards

Before getting started, I storyboarded what I envisioned and talked to my classmates for feedback. I got a lot of good critique about the angles and framing, which I ended up incorporating into the final video.

For the final prototype, I got my sister to act as the main character. Her motivation is to cook something. However, she has many ingredients and she doesn’t know how to use all of them to make a meal. That’s where the Nutri-Scanner comes in. She scans all her items with the Nutri-Scanner, and then is sent a list of recipe ideas to her phone. She is able to use the recipes to make a meal. You can watch the full video here:

Google Photos

Analysis

I think the prototype helped me see how the product worked and ways it could be more efficient. I think I could’ve spent a little more time getting feedback on the product itself in the ideation phase, because after doing the video prototype, I’m realizing that I could’ve made the product more simple by making the Nutri-Scanner a phone app instead of its own product. I also think that instead of a leaf, I probably should’ve used a lo-fi prototype that was a little more believable because it may have been hard for the audience to know what it was.

After getting feedback during critique, I learned that the most unclear part was realizing that the Nutri-Scanner would send users a recipe at the end. If I could film again, I would incorporate a clip that showed the actress looking through an actual recipe. I would also spend more time storyboarding and coming up with more unique angles. However, given the week-long timeframe and the 90 second limit, I’m pretty happy with how the final video turned out and have come out of this experience with clear ideas for iteration!

Design

I started out by sketching a couple ideas for the design. My levels of understanding with CAD software and with 3D printing were — like with the other projects — very minimal. However, 3D printing is very time consuming so I wanted to create something very simple. I sketched out a couple ideas, ranging from a pencil box to a jewelry holder.

I ended up settling on a sticky note holder because of its utility (I had a couple sticky notes that I wanted to organize.) I left the top open to account for any height of sticky notes and I left the front open to allow for easy access.

The next challenge was using Rhino, a type of CAD software. I had a steep learning curve with this one — I know the box below looks pretty simple, but that itself took a couple hours for me to get used to the software and go through enough test designs to make it work. I tried adding decorative element, but with time constraints and my lack of expertise, that ended up not being feasible so I settled for functionality.

The final product ended up taking 34 hours to print, but I came out with this:

Reflection

I learned a couple things from this process. This was more challenging than the other projects because for laser cutting, I already had experience with Illustrator. However, I lacked a lot of technical skill with Rhino, which was pretty frustrating and limiting. If I had more time, I probably would have tried something more complex.

Also, I skipped the lo-fidelity prototyping, thinking it would be simple enough. I really wish I’d low-fidelity prototyped this box with proper measurements because my 3D object ended up being too big. I also think it would have been better if I’d done some background research on sticky note holders because there were some other effective designs I could’ve drawn inspiration from.

As I brought my product to class for critique, I got some feedback I would use in future iterations including:

• Rounded edges for safety
• Thicker base to prevent the bottom of the sticky note holder from peeling off
• A smaller size to take up less space

All in all, I found this project to be challenging but have several takeaways I would implement in future projects.

Last week I was tasked with learning how to operate the laser cutter and piecing together a phone stand. After a couple hours with Illustrator and the laser cutter, I ended up with a final product — here’s how it happened.

Design

Here were my design requirements:

• Must be cut from not more than two sheets of 11 x 17" chipboard, and/or 11 x 14" flute (total of 4 sheets)
• Must not use any glue, tape, or other fastening materials to assemble and use
• Must be able to be dissembled into pieces that can be stored flat and transported (as in a backpack)
• No downloaded designs. The structure and design must be of your own conception.

I started off by researching some phone stands. I began sketching out ideas and ended up going on to prototype two.

I prioritized prototyping ideas that were simple and durable because I wanted to create something easy to assemble but also sturdy enough to hold my phone. To add to the aesthetic appeal, I also drew a lily and decided that I would laser cut it onto my design.

Prototype

I started with a paper prototype that looked like this:

The design was sturdy enough, but as I researched other designs, I realized there were options that might be simpler — both for creation and for assembly. Moreover, the design didn’t allow for users to hold their phones horizontally.

I went on to research more options and discovered a simpler way. However, as seen in the picture below, the prototype ended up being so weak that I had to hold it up for it to support himself. With the material I was using, I realized this might not be a feasible alternative.

I ended up going back to the drawing board, this time looking for a design that was both simple and durable. I settled on a triangular design that afforded for stability but also had only 3 pieces, making it relatively simple to put together.

Analysis

I went to class to get some feedback at a critique session. Here were some major takeaways:

The Good:

• The flower design brought in minimalistic, aesthetic appeal.
• Stable and sturdy design that supported phones horizontally and vertically.

What I would do differently:

• The design didn’t afford for phone chargers (some of my peers included a divot at the base that allowed for a phone charger to go through).
• The design was built for my iPhone mini, which meant that height-wise it didn’t afford for larger phones, especially because of the connecting flap on the top. In the future, I would make the phone holder taller to account for this.

Overall, this project meant a lot of prototyping (I made three designs total and over 7 prototypes) as I learned how to use the laser cutter and identify what the most durable design would look like. Sketching and conducting product research were two skills that came in very useful throughout this process, and these are ones I will continue to work on as I develop my design process.

Design

My design requirements were as follows:

• must be made of some kind of flexible fabric or material
• must use a sewing machine to connect and assemble the component parts of your design
• must use some sort of fastening mechanism as part of the design (velcro, drawstring, zipper, etc.)

I started out by sketching a couple ideas: exploring buttons & zippers, different types of front pockets, strap designs, etc.

I ended up settling on a front pocket that spanned the surface area of the tote bag for quick accessibility. I decided to include velcro with the front to make sure things like keys and smaller items would be secure in the tote while still being in an easily accessible spot.

I went on to start sewing. I made this quick, low-fidelity prototype with the muslin (a cheap fabric). It looks pretty wonky because my measurements were off, and the seams are pretty messy because I was just learning how to keep the seams straight.

My prototype was sloppy and the rounded corners were measured improperly. As I moved on to work with stronger fabric, I thought deeply about color choice and making neat seams.

I chose 3 kinds of fabric: sunflowers (for the front pocket), black (for the body), and yellow (for the tote handles).

As I started sewing, I encountered a couple roadblocks. I had some issues with the seams (I named this iteration of my tote “Harry” because of how the seams looked after the sewing machine). I had to pull out those seams and start over.

The total process took a couple hours, broken up across a couple days. But the finished product looked like this.

Analysis

There were a couple things that worked well about my prototype. I think one of the strongest parts was the aesthetic: the colors and the fabric patterns all complemented each other nicely. The tote bag was functioning; it could hold items and the pocket was secure.

However, there are some things I would do differently for next time.

1. Make the handles shorter! They were way too long, especially for shorter people.
2. Make the front pocket taller — it would be nice to hold more things in it.
3. Use stronger fabric — I used cheap black fabric, which was good for my wallet but not good for durability of the tote itself.

Overall, I actually really enjoyed sewing and would love to make a tote bag again. But next time, I’ll be sure to keep in mind the learnings I mentioned above :)

Design Requirements

For the purpose of the assignment, I had the following constraints:

• Valves
• 4 x 4 inches
• Water volume adjuster
• Physical affordances and controls for when visibility and dexterity are challenged by soapy hands, steamy showers, and absence of corrective lenses

Design

With these design requirements in mind, I began sketching out a couple ideas.

I played around with the idea of an in-device Spotify connection that would all. However, I kept thinking back to OXO’s vision of making something simple. So I ended up limiting the design features to 4 controls: valves, temperature, water volume, and a timer.

User Testing Video Link

When it came time for user testing, however, I ran into some confusion from the user; she didn’t know which button would actually start the shower (the valve button).

In an effort to make the interface more intuitive, I placed the temperature knob first, then the valves (since this was the order the user interacted with the prototype in). I also played around with the idea of a bluetooth integration to give the user some flexibility and user delight with the interface. The next iteration looked like this:

Analysis

After bringing my second iteration of the project to class for a design critique, I got a sense of what was working and what wasn’t. I realized that the most confusing part of the interface was that there wasn’t a clear indication of how to actually start the shower; some users thought the “Set” button was how to turn the shower on whereas another user pressed on the temperature dial.

I also realized that logistically, it would be difficult to make the music portion work. A built in Spotify integration would take up too much of the already tight space, and the Bluetooth integration meant people might need to access their devices while being in the shower which would be inconvenient (as not all people may have waterproof devices). A big part of OXO’s mission is to make products simple, and as I reflect, I’m coming to see that the music component just complicates the product.

Though there were some difficulties with the prototype, there were some components that worked; all my users understood the dial, and it was apparent to them which functions were buttons and they understood what each of the components did on their own. The components of the design (buttons, a dial, and a slider) where all large enough to be visible for people with visual impairments and were interactive enough for the soapy/watery environment. If I were to build this prototype again, I’d include a power button and a “Start” button that would make it clear to users when in the process the shower should turn on.

Reflection

One of my takeaways from this project was to make a user flow and make it clear where a process begins and ends. My users understood how each of the components functioned independently, but they were confused on when the product was turned “on”.

Another major learning was to keep things simple. In the end, I tried to add too many functionalities onto a size-constrained prototype which made it overwhelming to use. In the future, I’m going to map out a user flow and have someone read the copy to make sure it’s understandable before prototyping.

I’m looking forward to focusing on clarity and simplicity for the next prototype I work on!

My first year of college, I had no idea what I was doing with my life.

So when corona-cation rolled around, I found myself with ample time to really think about it. I researched careers and even took up an Accounting course (to my parents’ excitement) and then promptly decided I hated it and quit (to my parents’ disappointment).

Fueled by my desire to avoid Accounting at all costs (no offense to Accountants — I appreciate the work you’re doing) I scoured through LinkedIn for career inspiration. That’s where I learned about UX, a field where I could combine my interests in psychology and design. I became so intrigued that I enrolled in a free course and started working on a few UX projects.

I loved UX much more than Accounting and I knew this was a career I wanted to pursue. Through a family friend, I learned about Human Centered Design & Engineering — a major UX professionals loved — which was offered at the University of Washington, about a thirty-minute drive from my hometown.

The only problem? It was a competitive major with a low acceptance rate, which would likely be even lower for me since I would be applying as an out-of-state transfer. At the time, I was attending university at a small town in Ohio.

I debated over if I should apply or not. It would take me a year to complete the prerequisite courses required to apply, and what if I didn’t get in? I would’ve wasted a year of university taking the extra coursework. If I didn’t apply, I would be able to graduate with a bachelor’s in Psychology in three years; perhaps it would be better to try for a Master’s or certificate program after?

But I also knew I didn’t feel fulfilled academically. I was tired of balancing all the school work with trying to self-learn UX on the side. I was going to school to learn; shouldn’t I be learning about something that I actually wanted to do?

Though the chances were slim, I decided to go all in for it. I went full force into the STEM classes I needed to take to apply. I did side projects to hone in on UX skills. I networked with UX professionals to understand the field. I reached out to multiple people for feedback on my application.

It was challenging at times. I loved the university I was at, and it was hard to imagine leaving. I remember praying about my decision often, wondering if the work I was putting in would even be worth it.

But when I finally got the email on a Monday afternoon in May, I felt nothing but relief and excitement. I was going back to Washington to pursue the career I wanted in my dream major.

I’m currently finishing up my first quarter in HCDE. Looking back, I’m so grateful that I took that step to apply, even when it felt like it would be impossible to get in. I’m so thankful for the many people who encouraged and helped me along the way.

To any students that are unhappy and unfulfilled in the majors they’re in — I want you to know it’s possible to find a career path that’s fulfilling. I started college feeling unfulfilled academically, and I’m now in a program where I often find myself getting excited about doing my homework (I know; it’s crazy).

If I could go back to my freshman self and give her any piece of advice, I would say: Trust yourself.

Through my years in college, I noticed when certain topics or ideas made me excited. I also noticed when things didn’t feel right. And then based on what I learned about myself and my interests, I made a couple changes to my life that snowballed into bigger things.

Two years ago, I never would’ve predicted the path I’m on, but I’m glad I’m here now. I’m sure there will be lots more changes in my life soon, but I’m learning to just do things and see what happens; step-by-step, one day at a time.

And to anyone planning to transfer or switch majors, I just want to offer some encouragement. It’s hard to make changes to your career or life plan, but you owe it to yourself to figure out what you feel called to do. Trust yourself — you got this. And please, send me a link to your Medium post when you’re ready to tell your story; I’m excited to hear about it!