MT
Marcus T.
★★★★★· 8 days ago
Used this to map out competing features for our mobile banking app against 3 main competitors. The framework forced us to be specific about what we were actually different on—saved us from chasing the wrong priorities.
Describe a product challenge and get back user stories, competitive comparisons, prioritisation matrices, and roadmaps — for everyday PM work. ## What it does - **User stories:** requirements written in standard format, ready for sprint planning - **Competitive comparisons:** feature matrices and positioning analysis - **Prioritisation matrices:** RICE, MoSCoW, or impact-effort scoring applied to your backlog - **Roadmaps:** a structured plan mapped to your priorities and timeline ## Where it fits - **A PM writing sprint tickets:** "Write user stories for this feature." Stories in the right format to hand to engineering. - **A team benchmarking competitors:** "Compare our feature set against these three products." A matrix to share in the strategy review. - **A PM prioritising a backlog:** "Score these items by impact and effort." A ranked backlog to walk into planning. ## How it works 1. **Describe the challenge:** a feature, a decision, or a product question. 2. **It applies the right framework:** user stories, competitive analysis, or prioritisation. 3. **You get a deliverable back:** a doc or matrix ready to review and act on. Built for product managers and teams. Every output is a draft for you to verify and adapt.
12 ratings · showing the 12 most relevant
Marcus T.
Used this to map out competing features for our mobile banking app against 3 main competitors. The framework forced us to be specific about what we were actually different on—saved us from chasing the wrong priorities.
Jennifer L.
Built our Q2 roadmap with the priority matrix skill. Really helped align the exec team on *why* we chose what we chose, not just what we were shipping.
Arun K.
The user story generation is solid and saves time, though I still need to tweak the acceptance criteria for our edge cases. Good starting point though.
Sophie B.
Competitive analysis framework cut my research time in half. I was able to quickly spot where our SaaS product was underserving mid-market vs. enterprise, which shaped our entire messaging strategy.
Diego R.
Works well for structured problems, but struggled a bit when my product challenge was fuzzy and ill-defined. Had to do more upfront thinking before the framework could help.
Priya M.
Used it to decompose a complex feature request into actual user stories. Our engineering team appreciated the clarity, and it made sprint planning way smoother.
Tom H.
Good framework for thinking through trade-offs. Helped me justify deprioritizing a flashy feature in favor of platform stability—got stakeholder buy-in faster than usual.
Yuki T.
Built quarterly roadmaps for 2 product lines using the skill pack. The templates were adaptable enough for our different contexts (B2B vs. B2C) without being overly rigid.
Elena C.
使用priority matrix来评估我们支付平台的8个新功能提案。这个框架强制我们同时考虑影响和复杂度，而不是依赖直觉。最后我们做出了更平衡的决策。
James W.
Felt a bit generic for my use case (niche B2B HR software). The frameworks are solid, but required significant customization to fit our specific buyer journey and compliance constraints.
Leah G.
User story skill saved us hours of back-and-forth with stakeholders on definition of done. Could use more examples for non-web products, but overall really practical.
Rashid A.
我用它来组织一个新产品的初期研究。竞品分析框架帮我系统化了思考，找到了3个未被满足的市场需求。现在这些洞察驱动了我们的MVP定义。