# What tips / best practices do you all have for creating success in low accountability orgs? — retained record

> Retained reddit record from reddit:ProductManagement.

Canonical: https://highsignal.app/data/records/e85890149699ebe0

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ProductManagement)  published 2026-11-01 19:31 ingested 2026-11-02 02:39

[original source ↗](https://www.reddit.com/r/ProductManagement/comments/1xlc3h5/what_tips_best_practices_do_you_all_have_for/)

## retained text



```
Hey everyone, I’ve been having conflict with the development team and I’d like to get advice from others who have been in similar situations.  Also happy to take any book recommendations or review other resources.

I’m a product manager for a startup product in a mature organization.  The org itself does not specialize in software, but is creating a software business.  On my team, we have a team lead, 2 QA resources, and (mostly) junior developers.  

I’m seeing signs of what I consider to be low accountability.  These include:

1. Devs don’t perform estimates, technically decompose work, or raise blockers.  Devs say that I as PM have to do all user story decomposition, write exhaustive specs, and proactively identify that they are blocked.  If they are blocked, it’s on my plate to schedule & facilitate a design meeting, research the problem, etc. 

2. QA does not understand the product.  As far as I can tell, they just rubber stamp features.  I independently asked each of them to walk me through the product, and it was evident that had no idea how to do so.  They then got defensive and said it is “product’s job to understand the product”, not theirs.  To get them to check anything, I’m having to write exhaustive (and extremely detailed) steps on expected behavior, navigation, etc.  Even if the feature is extremely intuitive…

3. There is zero automated testing, branch strategy, and other fundamentals for software.  We have tons of regression with every merge, which devs blame me for.  They say it is on me to essentially write in all business rules for all dependencies in every user story, even for features they built.  

4. Tech lead is totally uninvolved and not interested in solving these issues.  He does not attend meetings, check in on developers, or provide any degree of mentorship.  He says “that is the product manager’s job”.  When I’ve raised this to the engineering manager, they essentially told me to drop it or I’d be blamed.  

5. Business has zero idea what they want, so I am doing all discovery work, competitor analysis, UIUX, and figuring out exactly how every feature works.  If I try to get insight from others in the business, they get mad.

Saying all this to say: I feel like I have a lot on my plate, and it’s getting hard to juggle.  A personal mentor has advised me to delegate more, but any time I attempt to delegate…whatever I delegated either doesn’t happen, or it is done with such low quality that I have to redo it myself. 

Essentially: virtually no work is getting done, we are missing all milestones, and the org is extremely frustrated with me.  I know I’m the only one who can fix this problem, but in struggling to figure out how.  Does anyone have any advice, or ideas on how I can improve myself to help better?  I’m already taking software development classes so I can better manage these processes, and looking for any other input or help.  
```



document fetched 2026-11-02 00:27 · canonical https://reddit.com/r/ProductManagement/comments/1xlc3h5/what_tips_best_practices_do_you_all_have_for
