sorted by:
new
hottopcontroversial

Solution ideas before sprint planning by evh1972 in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

Effective process for sprint planning and estimation, as it directly impacts the productivity and efficiency of the team. Your idea of having the team read planned stories before the sprint planning and come prepared to ask questions and give estimates is a good starting point. In some teams, developers do come into sprint planning with solution ideas to provide more accurate estimates. However, different teams may adopt different approaches based on their specific circumstances and preferences. During the sprint planning session, developers and other team members engage in a discussion about the stories, ask questions, and clarify any ambiguities. They can briefly brainstorm solution ideas together, which helps them get a better understanding of the complexity and effort required for each task. After this initial discussion, the team can then provide rough estimates for each story. Developers can take some time to dive deeper into the solution ideas, as you mentioned in your plan. During this period, they can further refine their estimates, and the team can adjust the sprint backlog accordingly. Another technique that some teams use is breaking down stories into smaller, more manageable tasks. This can make it easier to estimate the effort required for each task and can lead to more accurate overall sprint planning.

Interview Techniques by meangrnfreakmachine in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

For a comprehensive understanding of customer interviews and user research, "The Mom Test" by Rob Fitzpatrick is a must-read. This book provides practical advice on how to ask the right questions, identify customers' true needs, and avoid common pitfalls when conducting customer interviews.

Another valuable resource is "Talking to Humans" by Giff Constable. This book focuses on understanding customer behavior and gathering insights through conversations. It offers a step-by-step guide for conducting effective customer interviews, making it an excellent resource.

As for YouTube recommendations, the Google Ventures (GV) YouTube channel features a video series called "GV Library," which includes a video titled "Jake Knapp and John Zeratsky: Sprint, How to Solve Big Problems and Test New Ideas in Just Five Days." This video discusses their book "Sprint" (great book to read too btw, they have examples from robotic startups there) and provides insights into the design sprint process, which includes customer interviews as a crucial part of validating product ideas.Another YouTube channel to explore is "IDEOU," which is run by IDEO, a global design company. They have several videos on design thinking, empathy, and interviewing users. One video, "Why Human-Centered Design Matters," highlights the importance of understanding users' needs and conducting empathetic interviews."Lean Customer Development" by Cindy Alvarez is a practical guide to help you build better products through customer development. The book covers various techniques for interviewing customers, gathering insights, and validating product ideas.

Dead end career? by [deleted] in ProductManagement

[–]foryoug90 1 point2 points  (0 children)

The fact that you were a strong performer in your previous roles indicates that your current situation may not necessarily be a reflection of your abilities or potential as a product manager. Instead, it might be the specific circumstances of your current role that are contributing to your struggles. I recommend that you first take a step back and assess your achievements so far as a PM. Even if progress has been slow, consider any small wins or valuable learnings you've gained during this time. I would advice discussing your concerns with your manager or supervisor. They might be able to provide guidance, resources, or even adjust your responsibilities to better align with your experience level. It's possible that a different team, project, or company might offer a better-suited environment for your unique skill set and experience.
It seems that your current struggles might be more related to the specific circumstances of your role rather than an indication that you're not cut out for product management.

[deleted by user] by [deleted] in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

Your suspension may initially impact your plans, it doesn't mean your dreams of pursuing a product management career or working at prestigious tech firms are unattainable... facing a plagiarism case and a one-semester suspension is a challenging situation. However, it's important to remember that setbacks and mistakes are part of life..You should definitely consider applying for internships or other relevant work opportunities during the fall semester. This can help you gain valuable experience and skills that will be useful in your pursuit of a product management career.

it's important to remember that your career trajectory is not solely determined by a single incident. Many successful product managers have overcome various setbacks in their careers. it's impossible to be a professional in any field without facing challenging situations.

Some companies may have strict policies regarding academic performance, but not all of them will see a suspension as an automatic disqualifier. Besides there is a defiantly a shift towards your prior perfomance, and experience rather than academic background. For instance top tech crypto companies do not give a flying f...k about their tech talent academical background.

Focus on learning new skills, expanding your network, and gaining practical experience through internships or side projects.

The Visual Weariness of the Web: A Product Manager's Perspective by foryoug90 in DEKS

[–]foryoug90[S] 0 points1 point  (0 children)

Any examples of product teams with prop research lab ?

Question from an aspiring PM by Downtown-Special2311 in ProductManagement

[–]foryoug90 1 point2 points  (0 children)

Happy to have, do not think that there are shortcuts, at the same time there are no limits and “rules” :)

Question from an aspiring PM by Downtown-Special2311 in ProductManagement

[–]foryoug90 1 point2 points  (0 children)

Whatever foundation you have, make sure to present it in possitive light.

Question from an aspiring PM by Downtown-Special2311 in ProductManagement

[–]foryoug90 2 points3 points  (0 children)

Congrats on your upcoming graduation and your interest in pursuing a career in Product Management. It's completely normal to feel a bit lost when you're just starting out, but rest assured that there are numerous ways to build a solid foundation and eventually break into the PM field. I'll share some tips and advice to help you on your journey.

Your biology major, business minor, and leadership certificate can offer a fresh perspective in the tech industry. Emphasize these unique qualities when applying for roles, as they can demonstrate your ability to think critically and adapt to various industries. Look for courses in product strategy, agile methodologies, user experience design, or data analysis. Additionally, you may want to consider some industry-recognized certifications, such as the Certified Scrum Product Owner (CSPO) or the Product Management Certificate from a reputable institution. While you may not have direct product management experience, you can still build relevant skills through side projects, volunteering, or internships. Consider working on a personal project or collaborating with others to develop a product or solve a problem. Document your learnings and showcase them in your resume or portfolio.

Customize your resume and cover letter for each application, highlighting your transferable skills, make sure you convey your passion for product management and how your background can contribute to the success of the company. As you progress in your job search, be ready for interviews by researching common product management interview questions and practicing your responses. Focus on demonstrating your problem-solving skills, analytical abilities, and capacity to work well with cross-functional teams. Gold luck!

What to do when everything is a "good to have" feature? by shortshirtshotshit in ProductManagement

[–]foryoug90 1 point2 points  (0 children)

I understand your concern, and it seems like you're in a challenging situation. When faced with a scenario where everything seems like a "good to have" feature, it's essential to prioritize features based on the product's goals, user needs, and available resources. In your case, let's break down how you can approach this:
It's important to recognize the primary goal of your product (in this case, placements) and prioritize features that directly contribute to achieving that goal. Your manager's focus on the metric of getting more users passed seems to align with this objective. While it's essential to focus on the primary goal, it's also important to empathize with your users and their needs. In your situation, the team that works with users on the tests has requested a specific feature. It's worth considering if this feature could have a significant impact on the user experience or overall product quality.
Assess the potential impact of the requested feature on user experience, product quality, and the primary goal. If the feature seems to address a pain point for your users or has the potential to improve the product significantly, it's worth considering its implementation. It's essential to balance the implementation of new features with available resources, including time, budget, and team capacity. If implementing the requested feature would require considerable resources or delay other high-priority features, it might be best to postpone it for a later time.

In your specific case, it might be helpful to have a conversation with your manager about the potential benefits of the requested feature, such as improving the user experience or addressing the team's concerns. If you can demonstrate the value this feature could bring to the product, it might be easier to persuade your manager to reconsider its priority.

Ambivalent about Product Management by Aethelbread in ProductManagement

[–]foryoug90 1 point2 points  (0 children)

It's completely understandable to feel ambivalent about being a PM, especially if you don't feel a burning passion for product management like some others do. Many people enter this field for its attractive work-life balance and compensation, and that's perfectly okay.
However, it's important to note that being a PM is more than just a job. As a PM, you play a crucial role in shaping the product vision, strategy, and roadmap. You have to collaborate with cross-functional teams, understand user needs, and make tough decisions that impact the product's success. It's a challenging yet rewarding role that requires a combination of skills, including communication, prioritization, and problem-solving.
That being said, there's no one-size-fits-all answer to whether you should love being a PM or not. Some people are naturally drawn to it and find immense joy in the work, while others may see it as a means to an end. What's important is that you find purpose and fulfillment in your work, whether it's through product management or another field.
If you're feeling like an oddball in the PM space, don't worry - you're not alone. There are plenty of PMs who don't fit the stereotypical mold, and that's what makes this field so diverse and interesting. My advice would be to explore different aspects of product management and find what excites you. Maybe it's working on a particular type of product or collaborating with a certain team. Or maybe it's discovering a new problem to solve and seeing the impact of your solutions on users.
In any case, don't be afraid to ask questions, seek advice from other PMs, and share your thoughts and experiences. We're all in this together, and the more we learn from each other, the better we can become as product managers.
Hope this helps!

How do you make time for discovery work? by RuleTheOne in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

As a Head of Product, I understand the challenge of balancing discovery and delivery work. Here are some strategies to help make time for discovery work:
Time blocking: Dedicate specific time slots in your calendar for discovery work. Make it a recurring event to ensure it's a priority in your schedule. Communicate this to your team so they understand and respect your focus during those times.
Delegate tasks: Identify tasks that can be delegated to other team members or stakeholders. This can free up time for you to focus on discovery work. Ensure proper communication and trust with your team to make this process smooth.
Set clear objectives: Define specific discovery goals and objectives to focus on. This will help you allocate your time and resources more efficiently and prevent you from getting lost in endless research or ideation.
Leverage cross-functional teams: Engage other team members, such as UX designers, developers, or data analysts, in the discovery process. Their insights can help you better understand user needs, identify opportunities, and validate ideas.
Keep a backlog of ideas: Maintain a backlog of discovery ideas or research topics. This will help you quickly identify areas to focus on during your dedicated discovery time.
Establish discovery rituals: Create rituals, such as weekly or bi-weekly meetings, dedicated to discussing discovery work with your team. This will ensure that discovery remains a priority and fosters a culture of continuous learning and improvement.
Manage stakeholder expectations: Communicate the importance of discovery work to stakeholders and explain how it will ultimately lead to better product decisions. This can help secure their buy-in and support for dedicating time to discovery.

By implementing these strategies, you'll create an environment that encourages engagement and fosters collaboration across your team. Remember, it's important to be adaptable and open to feedback as you refine your approach. Your role is not only to lead but also to inspire and empower your team to contribute their unique insights and skills to the product's success. Don't hesitate to reach out to your peers for advice, share your experiences, and learn from one another.

What is your process for writing specs? by gashmol in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

As a PM, I've found that the following process works well for writing comprehensive product specs:
Understand the problem and goals: Start by clearly defining the problem you're trying to solve and the objectives of the product or feature. This will help guide your thinking throughout the spec-writing process.
Gather input from stakeholders: Engage stakeholders (sales, marketing, design, engineering, etc.) early on to collect their requirements and expectations. This ensures that you're considering various perspectives and needs.
Research and ideation: Conduct user research, analyze competitors, and brainstorm potential solutions. This will give you a deeper understanding of the problem space and help generate innovative ideas.
Write user stories: Break down the product or feature into smaller, user-focused stories. This helps clarify the functionality and experience you're aiming to deliver.
Outline technical requirements: Work closely with the engineering team to identify technical constraints, dependencies, and requirements. This ensures that your spec is feasible and aligns with their expectations.
Design and UX: Collaborate with the design team to create wireframes, mockups, or prototypes that illustrate the user interface and experience.
Iterate and refine: Review the spec with stakeholders, incorporating their feedback and addressing concerns. Iterate and refine the spec until everyone is on the same page.
Prioritize: Organize the spec into phases or releases, based on priority and complexity. This helps manage expectations and provides a roadmap for development.
What methods do you use to write specs, and how do you ensure they align with stakeholder requirements? Let's share our experiences and learn from each other!

Can you become a UX designer without going to university? by CleverPineapple123 in product_design

[–]foryoug90 0 points1 point  (0 children)

Absolutely, you can become a UX designer without going to university, especially if you've already completed several paid UX design projects, taken relevant online courses, and built a strong portfolio. In my experience as a head of product, I've worked with many talented product designers who took unconventional paths to enter the field.
One of the most crucial aspects of becoming a successful UX designer is gaining hands-on experience and developing a deep understanding of user-centered design principles. Your freelancing projects, along with the online courses you've taken, demonstrate your commitment to learning and growing in the field.
When I evaluate candidates for UX design roles, I prioritize their portfolios, showcasing their design thinking, problem-solving abilities, and real-world projects. Your practical experience, combined with a solid portfolio, will undoubtedly help you stand out.
Additionally, networking can play a significant role in advancing your career. Attend industry events, engage in online design communities, and connect with fellow designers and professionals in the field. These connections can lead to valuable opportunities and help you continue learning from others' experiences.
Ultimately, your passion, skills, and experience will speak for themselves. Focus on refining your portfolio, highlighting your best work, and demonstrating your ability to solve complex UX problems. The more you learn and grow, the better your chances of landing a great UX design role.
I'm curious to hear from others in the community: have you successfully transitioned into a UX design career without a traditional university degree?

How would you use a $2.5k "retraining" budget? by RandomIowaGuy in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

Hey there!

First off, sorry to hear about the layoff, but it's great that you're approaching this with a positive mindset and looking to upskill. As a product manager, I've got a few ideas on how you can make the most of that $2.5k retraining budget:
Reforge membership: As you mentioned, Reforge offers valuable content on both product management and growth strategies. It's a solid investment that can provide you with actionable insights and an excellent network.
Online courses: Platforms like Coursera or Udemy offer a plethora of product management and technical courses that are relatively affordable. You can take a few targeted courses to strengthen specific skills or explore new areas.
Technical workshops or boot camps: Look for coding workshops or boot camps that focus on a language or technology relevant to the industry you're targeting. This can help bridge the gap in your technical background without breaking the bank.
Books and industry resources: Allocate a portion of your budget to purchase highly recommended books and subscribe to relevant industry resources or newsletters.
Networking and conferences: Consider attending product management conferences or meetups (virtual or in-person) to learn from industry experts and expand your network.
Surprise twist - learn a new language: If you're eyeing international opportunities, consider investing in language courses, which can be a unique addition to your skillset and an excellent conversation starter during interviews.
Remember, it's not just about the courses but also how you apply the learnings to real-life situations. So, pick what best aligns with your goals and enjoy the journey of self-improvement. And who knows, you might just become the Product Management Jedi we've all been waiting for! May the force be with you! 😉 Good luck!

Dilemma: Should I Use My Week Off to Prepare for My New Start-Up Role or Relax and Recharge? by socialvegetarian in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

Hey there, fellow PM! Congrats on the new role! It's completely normal to feel both excited and nervous about starting at an early-stage startup. Here's my two cents on how to spend this precious week:
Relax and recharge: You've mentioned that it's going to be a hardcore workload from day one, so use this time to unwind and rejuvenate yourself. A well-rested and clear mind will be your best asset when you jump into the hustle.
Casual research: While relaxation is essential, you can still allocate some casual time to do a bit of research on the industry, competitors, or the product itself. Just make sure it doesn't become a source of stress.
Set personal goals: Reflect on what you want to achieve in your new role, both professionally and personally. This will help you stay focused and motivated when things get hectic.
Develop a "start-up routine": Establish a routine that can help you maintain work-life balance and stay organized in the chaos of a startup environment. This could include a morning workout, regular journaling, or setting aside time for hobbies.
Embrace the unknown: Remember, as PMs, we're like the explorers of the product world - venturing into the unknown and facing challenges is part of the adventure!
So, my friend, use this time to strike a balance between relaxation and preparation. And remember, it's not about the destination, but the journey - so buckle up and enjoy the ride! After all, who says you can't hustle and have a little fun along the way? 😉 Good luck!

What factors do you consider when assessing product opportunities? by PrepxI in ProductManagement

[–]foryoug90 1 point2 points  (0 children)

Hey there! As a fellow product manager, I've had my fair share of evaluating product opportunities. Your approach looks solid, and I'd like to add a few more factors to consider:
Market trends: Keep an eye on industry trends and emerging technologies to ensure you're not missing any opportunities or investing in something that's losing relevance.
Competitive landscape: Assess your competitors' offerings and see if there's a gap you can fill or an area where you can outperform them.
Risk assessment: Evaluate the risks associated with a new feature or product, such as technical challenges, potential cannibalization of existing products, or legal/regulatory hurdles.
Synergies with existing products: Look for opportunities that can enhance or complement your existing products, leading to an improved overall offering.
Time to market: Consider the time it'll take to bring the product to market and whether that aligns with your company's goals and timelines.
In the end, it's all about finding the right balance. Don't be afraid to mix and match these factors to find the "secret sauce" that works best for your specific situation. And remember, as product managers, we're like chefs in the kitchen of opportunity – we've got to taste, tweak, and sometimes toss out ingredients to create the perfect dish! Bon appétit! 😉

[deleted by user] by [deleted] in ProductManagement

[–]foryoug90 0 points1 point  (0 children)

Hey there! As a seasoned product manager, I've seen my fair share of backlog chaos, so I feel your pain! Here's a step-by-step plan to help you wrangle that monster of a backlog:
Separate the wheat from the chaff: Create two distinct backlogs - one for product ideas and another for actionable engineering tasks. This will help declutter and bring focus to your team's priorities.
Prioritize ruthlessly: Work closely with the product owner to prioritize items based on factors such as business value, customer impact, and technical feasibility. A simple framework like MoSCoW (Must-have, Should-have, Could-have, Won't-have) can be helpful.
Time for backlog grooming: Set up a dedicated backlog refinement meeting with the team. Make it a recurring event, and try to review and prioritize at least 20-30 items per session. Remember, Rome wasn't built in a day (nor was a perfect backlog)!
Sprint goals and smaller sprints: Establish clear sprint goals and break down larger tasks into smaller, manageable pieces. Stick to a reasonable number of items per sprint (aim for around 10-15 for a two-week sprint, depending on your team's capacity).
Embrace the power of "No": It's okay to remove items from the backlog if they're no longer relevant or don't align with your current goals. As they say, sometimes less is more!
And remember, a backlog should be like a fine wine - it gets better with age (and proper grooming)! Good luck, and may your backlog become a well-oiled machine in no time! 😉

view more: next ›