Ask HN: To biz people here: what problems does your eng team push back on?
Curious about what problems you get push back on solving from your Eng team. Things like:
>we don’t have enough people to do that
>too costly
>too hard for us to do and nothing on the market we can use because X y z
>solutions are incompatible
>it uses Python and js and we don’t like it
>.. or anything else
- Adding new vendors without regard for ongoing maintenance and compliance work.
- Ill defined requirements.
- Setting something as the highest priority without cutting something else.
- Anything from a biz person who’s burned the engineering team publicly.
Very helpful, so the type of work doesn’t really matter ?
If you can present a reasonably coherent case that something is tied to a targeted business outcome without ethical concerns my team will get it done no matter how unsexy it is.
I think anything vague is and should be pushed back. If we do not know the complete user story, then it is not a feature. The problem needs to be well defined before discussing with the engineering team.
Example: We are building a desktop app. Now the management want to have a "login" page in the desktop app. This is a very vague statement to be discussed with engineering. First decide on who can login, how can one register, is the login possible only when the device is connected to the interenet., are we going to limit features of the app based on subscription, etc.