Why We Are Building Byrdhouse - Combining Language Barriers and Building Relationships

Why We Are Building Byrdhouse - Combining Language Barriers and Building Relationships

The inability to express and defend oneself due to language barriers can be a painful experience. Snow Huo, the founder of Byrdhouse, was inspired by his own struggle with language barriers as an immigrant. He was determined to learn and master English so that his voice would no longer be silenced. However, as he went through school and started working, he realized that many immigrants, classmates, and co-workers faced the same obstacles.

The fear of being called upon by coworkers to chat, not knowing the appropriate way to respond, and the embarrassment of having to make up excuses to skip public speaking sessions in a different language are challenges that many immigrants face. Additionally, the nervousness of group conversations, not understanding the content, or knowing when to chime in can lead to frustration and loneliness.

It is interesting to note that 75% of the world's population does not speak English at all. In the United States, 1 in 5 Americans speaks a language other than English at home, and 97% of US immigrants speak a native language that is not English. These statistics highlight the widespread issue of language barriers and the need for a solution.

Snow Huo believes that using AI for good can help break down these language barriers and bring the world closer together. Inspired by the image of a nest of birds, he named the app Byrdhouse. Just like birds migrate to different destinations for various reasons, multilingual families may have members who migrate to different countries with different cultures and languages. Byrdhouse aims to provide accessibility to language and enable individuals to understand and communicate with their loved ones, regardless of language differences.

Now, let's shift our focus to the world of product management and the challenges that arise when defining roles. The confusion between Product Owner (PO) and Product Manager (PM) is a common source of "madness" in the industry.

Madness 1: PO is the same as PM

There is a misconception that the Product Owner role in a Scrum team is the same as the Product Manager job. In reality, the Product Owner is a role within a Scrum team, responsible for ensuring that the product increment satisfies the Sprint Goal and meets the Definition of Done. The term "Product Owner" originated from the need for someone to handle administrative work related to delivering output. However, this role does not fully encompass the need for consistent innovation and ensuring value and viability for customers.

Madness 2: The PM plus PO

Some organizations choose to add Product Owners as a separate position to work alongside Product Managers. This separation allows for a clear distinction between "the business person" and "the person that talks with the developers and manages the backlog." However, this approach may lead to a lack of optimization for outcomes across a diverse and complex system.

Madness 3: The PO as a PM overnight

If the goal is to build products that customers love within sustainable and innovative business models, having both a Product Owner and a Product Manager in the same team can be considered madness. Moving towards an empowered product team model with true Product Managers requires training and empowering Product Owners for the transition to a different role.

In conclusion, language barriers and unclear role definitions can create challenges in both personal and professional settings. To address these issues, here are three actionable pieces of advice:

1. Invest in language learning and understanding: Whether you are an immigrant or someone working with individuals from different language backgrounds, take the time to learn and understand different languages. This will help break down barriers and foster better communication and relationships.

2. Clarify roles and responsibilities: In organizations, clearly define the roles of Product Owners and Product Managers to avoid confusion and ensure that each role focuses on their specific responsibilities. This clarity will lead to more effective and efficient product development.

3. Empower and train Product Owners: If you are transitioning towards an empowered product team model, provide training and support to Product Owners to help them succeed in their new role as Product Managers. Empowering them will enable them to drive innovation and value for both the customers and the organization.

By addressing language barriers and refining role definitions, we can create an inclusive and collaborative environment where language is no longer a barrier to building deep and lasting relationships.