Now recruiting for a Senior UX Design Freelancer! Click here for more information →

Learning UX with Real Products & Beta Communities: Tips for Success

May 30, 2023
Written By:
No items found.

We talk a lot about how to grow as a UX designer, develop your skills, and expand your knowledge. We’re all for going down rabbit holes, whether about technical concepts, data tables, or UX heuristics, to name a few of our favourite things. But sometimes it’s best to step away from the textbooks, lectures, and courses, and get your hands dirty (metaphorically speaking) by testing out new products for yourself in the real world.

Using real products and talking to users is one of the best ways to learn as a UX designer. In this article, we shake things up and go deeper into learning by using. First, we’ll share how to stay in the loop with what new products the kids are using these days, then we’ll walk through how to analyze the UX of a new product. Finally, we’ll outline what’s to be gained by participating in the beta versions of your favourite apps.

You’ll come away with creative ways to learn about the user experience in the real world so you can apply new nuggets of wisdom in your work.

Sound good? Let’s dive straight into how to train yourself by using real products and betas.

Watch the live event recording where we share our best design tips, tricks, and exercises for learning by examining real products and participating in beta communities.

How to stay up to date with new products

Before you start using betas and new products, you first need to find those products. Here’s how to keep up with what the kids are doing these days.

Check Product Hunt

If a product isn’t on Product Hunt, does it really exist? Product Hunt is a popular website that allows users to share and discover new tech products. Regularly checking this curated list of new products is a safe bet if you want to stay in the loop and keep up with trends. Check it once a month or so, or whenever you need to procrastinate productively 😉.

You can check out the launch archive, pick a month, and look for the most popular products—that means there’s something there.

Focus your search on enterprise UX products if you want to develop further in this area. The UI for more complex enterprise products needs to be especially efficient.

When browsing through products, check the taglines and aim to understand the problem they’re trying to solve. You want to look at products that are trying to fix a real problem, not just add a new flavour of something (cough *CHECKLIST APPS* cough). What’s their story? What are they trying to convey? Also check the comments to see if people are actually using the product.

Comments on Product Hunt for Softr for Google Sheets.

Next, grab a cup of coffee (or two), and sign up for a product you’re actually interested in and have use cases around. Then get ready to start dissecting the UX 🤓(more on that in the next section).

⚡️Quick tip: Once you’ve found some interesting products to follow, read the release notes to get a sense of the product’s foundation and how it was built. Product news releases might also have some great details. We keep an eye on Figma’s release notes, for example, as they’re always up to something crazy.

How to analyze and dissect the UX of a new product

So you’ve found some interesting new enterprise products. Now what? Here’s how to analyze them to improve your design skills and get a better grasp of design principles.  

Come up with a real use case for the product

Instead of browsing through a product’s website and reading about their top features for hours, use the product for yourself as soon as possible. Jump in the pool and see how the product solves a real problem.

Testing the product yourself will also keep you interested and engaged (we at least have a hard time focusing on things we’re not actually interested in 🥱).

Record the onboarding process

The best way to learn about onboarding in the real world is by signing up for new products. (Just be sure to reserve time to clean out your inbox in a week or two after signing up! 📬…marketers be emailin’)

Record the onboarding process by taking plenty of screenshots or screen recordings since you won’t be able to see it again afterwards. Capture any interesting or new UIs to refer back to later. Note the flow and the places where the makers prioritized and didn’t prioritize—make any notes you think are interesting.

⚡️Quick tip: Evernote can be a good tool for taking screenshots, as it saves the sources of your screenshots. CleanShot is another good option. You can of course just save screenshots to your computer, but you might want to change the default save location to keep things organized.

Aim to understand the user flow

While going through the onboarding process and playing around with the product, aim to understand the user flow. Document the series of steps you took to get things done.

For example, if you’re documenting the user flow for Softr for Google Sheets, it could look like this:

1) Sign up, then answer a few questions before using the product.

Note: Were you frustrated by having to answer these questions before getting to use the product? (we were a bit 😖)

2) Choose a template to create your first application.

Note: How did you find this UI? Was it easy to pick the most relevant use case?

3) Choose where to store your data.

4) Authenticate with Google.

5) Choose what pre-built pages you want in your application (note: these options were all pre-selected).

6) And you’re in! Note the UI here, and see how the onboarding continues with mini tutorials for different tasks.

As you continue exploring the product, keep taking notes about the user flow and jot down anything that bugs you, piques your interest, or makes your design-loving heart sing.

Break down why you liked the UX

When a product’s UX design is a hot mess, our patience dwindles and we yell out “But whyyyy?!?” in frustration. But to be a better designer, also ask “Why?” about the good stuff. If you liked the experience, consider what was actually good about it. What worked well, and why? How was it smooth?

Look back at your screenshots and analyze every microstep of the user flow, piece by piece. What were the default selections? What were the tiny behaviours that made the UX a bit smoother? You can then apply these tactics to your own interaction or visual design work.

To get UX inspiration from real products, you have to notice things. And the more you know, the more you notice. To cultivate awareness when dissecting the UX of a product, you might want to zone in on something you’re curious about, or something you’ve been trying to figure out. You can also pay attention to novelty—what about the UX is new to you? Why do you think the UX designer built it that way?

⚡️Quick tip: When applying anything new you’ve learned, just be clear on the reason why you’re doing it. If you can’t articulate why, leave it out. #reasonwhyoritdidn’thappen.

Prompts to guide your UX analysis

To guide your analysis of a product’s UX, ask yourself the following questions. This will make for delicious research and analysis. *chefs kiss* 🤌

  • Is the product really solving the problem they brought up? Give them a score accordingly.  
  • How many UX best practices are they following?
  • Are they trying to break UX patterns just to be clever, or are they really improving things? Since it’s especially important for enterprise products to scale fast and focus on outcomes, they should be applying common UX patterns.  
  • How does the product connect different patterns and behaviours to improve the UX?
  • How much time do you think people took to build the app? Was it rushed as they had to publish something quickly, or did they iterate several times before launching it publicly?
  • What do you think influenced the designer’s choices? (e.g. a framework, a specific design system, something trendy, etc.) Note: Startups often love copying what their competitors do without knowing if that even works for them.

The benefits of participating in beta communities

By joining private betas (when a product isn’t actually a product yet), you get a behind-the-scenes look at the product team’s UX work and learn all about product design and strategy, which is pure gold for UX designers.

Here are a couple key advantages of taking part in app beta tests, plus some tips for how to provide useful feedback.

Follow the product team’s decision-making process

Joining a beta at an infancy stage and sticking with it is a great way to learn about the company’s history, learn from their mistakes, understand the decision-making process, and gain insights into the product’s future direction.

Every product team gets to choose where they put their energy. When you’re testing out new products or working on redesign projects, you have to infer why designers made the choices they did. But when you’re part of a beta, you get to the core of why they made certain choices, like which feature requests to prioritize. You get to see how a product team functions in a scrappy startup context.

📙Fanny’s Reader beta experience
Fanny from the Pencil & Paper team joined the Reader beta, which didn’t yet have an onboarding UI. For about a year, new beta testers would be onboarded by another beta tester, and then pass the baton by onboarding someone new. Reader’s community manager created resources like Loom videos and PDF checklists to help testers with the onboarding. But otherwise, beta testers—people really interested in the product—were in charge of making sure others had a good onboarding experience.

Fanny happily devoured the 4,000-word emails sent to beta testers because the updates were so technical and specific, covering the challenges the Reader product team faced and how they overcame them.

At this early stage, Reader leveraged the community’s built-in interest rather than investing in an onboarding UI that might have missed the mark. By getting user feedback from Twitter, Discord, the Reader app, and email replies—actual data from actual users—it was easy for Reader to decide what to prioritize. After all, the success of a product isn’t just based on having a good idea, but about solving the right problem in the right way.

Reader saved time and strengthened the community early on. This choice wouldn’t be right for every product or industry, but it made sense for Reader’s product team.

Even if you join a beta and the company ends up spending time and resources on stuff that doesn’t matter, you’ll better understand why they went out of business.

Engage with the community

When you’re part of a beta, you get to be a sponge, soak up all the juicy UX knowledge, and engage with the community. You get to talk to real users and design with other people.

You can also influence the software’s future by providing feedback and logging bugs.

Communicating with developers and other stakeholders and thinking critically about the product will help you feel more involved in the project and give you a better understanding of how software is created.

Here are some tips for sharing useful feedback as a beta tester or user testing participant:

  • Give the kind of feedback the product team specifically asked for. Also be specific about the UX aspects that you found confusing or particularly smooth.
  • Offer suggestions and ideas for solutions when pointing out issues so the team can take actionable steps to make improvements. But don’t be too annoying with your solutions—have humility.
  • Share screenshots and screen recordings to give the team clear reference points and avoid confusion.
  • Join different communication channels and participate in discussions in a useful way. Ask good questions, share your thoughts, collaborate with other testers, and respond to comments across different channels like Discord and Twitter, or wherever the product team is asking for feedback.

Delving further, product market fit is a critical concept for startups to understand, as it means being in the right market with a product that can satisfy customer needs. In an ideal situation, in a great market, there are lots of potential customers who will be eager to purchase your product. This creates a situation where the demand from the market is so strong that it almost pulls the product out of the hands of those offering it, thereby creating success and growth.

Wrapping up

By testing out new products for yourself in the real world, you’ll strengthen your UX muscles and be better able to identify what works well and what needs improvement. You’ll grow a lot faster as a UX designer and get fresh ideas for your work. Remember, “Good designers copy, great designers steal.” All those screenshots and notes you save will form a handy collection that you can always use to practice your UX analysis skills.  

UX is ever evolving, so testing one product one time isn’t enough. Embrace your curiosity and regularly check Product Hunt and take new products for a test drive. The connections, insights, and inspiration you gain through beta communities will also go a long way to keep fueling your UX growth.

UX Heuristic Report Template Kit

Spend your time and life force on capturing heuristics problems rather than endless visual fiddling. Meganne Ohata will guide you the whole way, so you can propel your work and become their most trusted advisor.

Learn more
ux heuristics series

Download our Table UX Audit Checklist

Do a mini UX audit on your table views & find your trouble spots with this free guide.

Available in a printable version (pdf), plain text markdown, Apple Keynote or Microsoft Powerpoint.

Please fill in the form below and it will be in your inbox shortly after.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Want to dig deeper on flow diagrams?

Be the first to know about our upcoming release!

If you found this intro content useful and find yourself needing to express yourself more efficiently on your software team, this training is for you. Our new flowchart training includes real-life enterprise stories and examples for using flowcharts for UX. You’ll get tips on how to make your diagramming efforts successful, how to derive info for the flow charts, and how to get others to use and participate in the diagramming process.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Get to know us
“Your article made me realize our tables suck.”
Matthew S.
Previous Post
Conditional Logic in Forms
Next Post
N-N Relationships in Data Visualizations