I work on a small development team: approx. 7 devs with some SysAdmin folks with experience in a broad range of tech stacks, languages etc. The Transportation and Logistics industry is notably behind the times when it comes to technology adoption and is still greatly controlled by incumbents and tenured employees. They're used to sending an email to an operator and the person just "does the needful". As we all know, that's not how software works.<p>I am familiar with the stereotype of folks from Operations/Business not being able to properly define requirements. However, instead of accepting that as reality, I'm trying to do something about it.<p>So, HN, have any of you been in a company where you've needed to train your Operations teams on requirement documents? Maybe hired an external trainer? How did it go? Any help appreciated.
Why do they need to write requirements? That’s primarily an engineering function. An engineer should know how to translate the user/business need into a technical requirement.<p>Let the business and ops people focus on what they’re good at.