<aside> 🚧 Work-in-progress: I am still compiling key learnings, challenges, processes, and some useful resources from my product management experience at RAx**.**

</aside>

Challenges

• Prioritisation -
  • Prioritising quarterly release goals
  • Prioritising requirements for projects versions
  • Prioritising bugs and improvements and to make sure it aligns with quarterly goals
  • Reprioritising based on business and user requirements
  • Not just product projects but also taking into account lots of marketing projects pending
  • Add team hiring on top all that
  • Making sure speed is not affected amidst all this 🤯

Planning and documenting release notes

• Feature Ideation with key stake holders

• Roadmap building

• Competitor Analysis

• Documentation

  Feature documentation template

Better prioritization of Improvements

<aside> 🚧 CHALLENGE

Working with a small team and tight deadlines, it was difficult to timely incorporate bugs and leftover (or newly identified) improvements into the engineering pipeline. Such improvements hampered the overall user-experience and the effort put in by the engineering team in major projects.

Also, the lack of a good decision-making framework made prioritization subjective and ambiguous.

</aside>

<aside> 💡 SOLUTION - A well structured management of all improvements with decision-making framework that makes it easy to prioritise, coordinate with engineers and track progress.

</aside>

• Goals Always prioritize improvements as per the goals that align with overall company goals during a certain period of time.

• Category

  Breaker - Issue that is breaking an existing experience/flow OR is a legal/security threat. The danger for retention. — User can't use existing functionality.

  Blocker - Issue that is blocking a smooth usage of existing functionality/experience. Important for retention. — User can't enjoy existing functionality/use cases.

  Builder - Issue/tasks that are important to bring in new useful features OR improvise user experience OR user engagement. — User can't get new more useful functionality/experience.