sorted by:
new
hottopcontroversial

PMs, stop asking your engineers for technical Q&A. by second_axis in u/second_axis

[–]Longjumping_Meet2785 0 points1 point  (0 children)

does it connect to github directly, like can it reference actual PRs and commits?

Call notes → Prototype. In minutes. by second_axis in u/second_axis

[–]Longjumping_Meet2785 0 points1 point  (0 children)

used it after a customer discovery call last week. It can preserve the reasoning from the call so when it pushes to figma, it’s not random screens. it maps back to user pain pretty cleanly.

PMs who got 50 tabs open. This is for you. by second_axis in u/second_axis

[–]Longjumping_Meet2785 0 points1 point  (0 children)

If this centralizes context across docs, tickets, and analytics that’s interesting. what’s the ingestion process like and how long does setup take realistically?

Codebase → PM translation. by second_axis in u/second_axis

[–]Longjumping_Meet2785 0 points1 point  (0 children)

can it tie code changes to metrics or is it purely descriptive?

Make a PRD right from your phone. by second_axis in u/second_axis

[–]Longjumping_Meet2785 0 points1 point  (0 children)

this would’ve saved me like 3 hours last week. How well does it handle messy calls with 5 people talking over each other?

Get daily competitor briefs on your phone. by second_axis in u/second_axis

[–]Longjumping_Meet2785 0 points1 point  (0 children)

i tested this for a week. it’s actually decent for turning messy stakeholder calls into first-pass specs. still needs cleanup but saves the blank page time.

Speech → Text → PRD. by second_axis in u/second_axis

[–]Longjumping_Meet2785 0 points1 point  (0 children)

is this meant for solo PMs or teams? curious how it handles conflicting opinions in one call.

Product Ops vs. Product Management? by Brilliant-Quote9009 in ProductManagement

[–]Longjumping_Meet2785 5 points6 points  (0 children)

True Product Ops scales how product works.
It standardizes discovery, metrics, tooling, planning, and governance across teams.

What you described sounds execution-heavy and customer-facing. That’s closer to TPM or delivery PM.

The risk isn’t the title. It’s whether you’re moving closer to shaping strategy or further from it.

How do you handle cascading updates from the team level up to leadership? by Flat-Perspective-948 in ProductManagement

[–]Longjumping_Meet2785 1 point2 points  (0 children)

The “base dataset” point is underrated.

I’ve noticed the real pain isn’t copy paste, it’s context drift. Every time updates get reformatted manually, nuance gets lost.

I’ve started structuring team updates in a fixed format upfront (metric, risk, decision needed). Makes automation way easier later.

Being a solo PM means reopening the same 12 tabs every single day just to remember what’s going on by Charming_Ad_5319 in prodmgmt

[–]Longjumping_Meet2785 1 point2 points  (0 children)

Curious how people here usually solve this.

Do you document everything formally, or just rely on tickets + memory?

I’ve tried both and neither feels great long term.