Hey everyone, I’m doing some research on post-go-l...
# general
m
Hey everyone, I’m doing some research on post-go-live technical debt. For the admins and devs here cleaning up after a NetSuite implementation: what percentage of your current custom scripts or manual spreadsheet workarounds exist simply because the original vendor 'ran out of time/budget' to deliver the automated process promised in the SOW? Feel free to share the percentage. Much appreciated!
t
I would be shocked if someone knew exactly what they needed PRIOR to go-live.
m
Correct if I'm wrong, but you're saying it's inevitable because it's nearly impossible to capture every single requirement prior to go-live.
t
Yes, that's my opinion.
TBH, I'm still doing things years after go-live at my work that they would have benefited from if they were thought out at the beginning.
m
I hear you. That leads to my next question: when those unknowns inevitably pop up mid-project, what usually happens with the implementation partner? Do they pause to architect a proper solution, or do they just slap a band-aid/manual workaround on it so they can hit the go-live date and get the milestone invoice paid? Which sounds exactly like the debt you are stuck cleaning up years later.
c
You must think in terms of domino effect based on an analytical position of how much information management will cause pain later one, one item mismanaged can be a 2^100th power, a simple yes no, can turn into 1,024 yes/no as I have measured.
That said drawing system architecture and mapping out via whiteboard process, is something I do with clients time and time again so we identify, inputs, to expected transformations, to expected outputs.
m
Thanks for sharing your approach.