I have just spent three weeks building out a process that takes two pieces of data, manipulates them, creates custom records, blah blah blah. Layers and layers of processes of the two pieces working together. Sent it over for initial testing. "Oh, we've decided we're getting rid of that second piece of data. Can you just turn that part off?" 😐

I used to get frustrated w/ this. In the end I was like "well you're paying for it so its your money" and just went on. If they wanna waste money then go for it.

In my case, they aren't clients. They're coworkers. So now I gotta navigate the "make sure the higher ups know that the delay is not me" game. lol

as a consultant I loved those - more billable hrs. But as an internal admin/dev I hate this, it happened so many times. One way to stop it to do a requirement elicitation instead of requirement gathering. Utilize agile method to break down the requirements to as small as possible user stories to expose the final goal. Long story short just beat the shit out them to come to a final decision before dev work starts.

What I love is sometimes the functional only tells you that the requirements have changed after you are done and ask them to test it. facepalm