I work in finance industry, on business department side, and fairly tech-savvy (e.g. write Python every day and manage SQL database and linux machines). As such large part of my job is to "work with IT".
A project sometimes needs to be implemented by IT (corporate policy) and that's when I come in as well. The issue is that when business side, including myself, explains what has to be done, IT misses deadline, over-engineers the solution, and/or misses critical problem due to lack of the big picture.
I always say "ask us any question", but that hasn't worked well so far. Usually IT people take their own time to study whatever they need (I'm not saying this is a bad thing), but it's just not quick enough for business side.
This leads business people to think it's faster to work without IT (and it is from my experience because we do have enough technical skills), then the gap widens.
Presumably some folks here work for IT department, how do you deal with business requirements, or business people in general? What can I do to not widen the gap anymore between business and IT?
FWIW I didn't mean to rant here. I genuinely don't know how to improve the connection.
[1] https://news.ycombinator.com/item?id=26395361
This is why the dealines are missed too. If/when i don't get the big picture, i spread all over the subject/don't know what i should focus on, and miss deadline.
I would say: better communication at the beginning of the project. What i like is first: know the general direction, then research abit on my own, then have an open discussion with the PO (on the wednesday if the project started on a Monday), about all the caveats i see.
Also, responsibility. If the business (not usually PO in this case) agree to send me a mail/sign a paper saying that they take full responsibility if the upgrade either doesn't fully respect the law or isn't secure (security is like 50% of the time spend in research/in integration), i assure you the deadline will be met.