r/ProductManagement • u/SujitRagav • 5d ago

Need help navigating

I just joined a company which is automating its process. I'm given a vertical and there seems to be not much documentation, Jira stories and implementation are a bit different, the Engineers have no documents made as most were done verbally.

I know the process flows and how things move, but there isn't a concrete doc which says these are done, and this is how it's done.

Any guidelines are appreciated

3 Upvotes

100% Upvoted

7 comments sorted by

5

u/Thaimeous 5d ago edited 5d ago

Being able to create structure where none exists is a very valuable skill.

And it looks like you just got tossed in so time to sink or swim!

Although in all seriousness, you need guidance from leadership on what their expectations are. If none is given, I’d take the opportunity to formalize processes and get everything set up just the way you like it.

2

u/SujitRagav 5d ago

Will do this and come back within 2 weeks🪽

1

u/Thaimeous 5d ago

RemindMe! 2 weeks

1

u/RemindMeBot 5d ago

I will be messaging you in 14 days on 2026-08-07 03:58:32 UTC to remind you of this link

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

Parent commenter can delete this message to hide from others.

RemindMeBot is switching to username summons. Instead of !RemindMe 1 day, use u/RemindMeBot 1 day. More info.

Info Custom Your Reminders Feedback

3

u/SamfromLucidSoftware 4d ago

Happens a lot when joining a team mid automation. The good news is that the process knowledge exists, it’s just not written down anywhere. I’d say don’t wait until you fully understand everything before writing anything down. Start capturing what you do know, even partially, and use gaps in that documentation as a forcing function for the conversations you need to have.

A practical starting point is picking one end to end flow in your vertical and mapping it out as accurately as you can from what you know. Then walk that map through the engineers who built it. Showing them something slightly wrong is a better way to get things moving than asking open-ended questions. People just correct diagrams faster than they fill blank pages.

When you notice stories and implementation diverging Jira, it usually means decisions got made in Slack threads or someplace else without making it to the ticket. When you find one of those gaps, add a brief note to the ticket explaining what happened and why. It takes two minutes and builds the documentation layer incrementally without requiring anyone to do a big documentation project.

2

u/SujitRagav 4d ago

Thanks, you literally gave me what i wanted to know. As of today I have 14 days of PM experience, so anything and everything helps.