Design question: our team has been tasked with building a large multi-state collections process for customers. As someone with a strong development background, I’d prefer a fully scripted solution. However I also have two very knowledgeable and seasoned admins helping out that have good workflow knowledge. One of them has a decent grasp of scripting, and the other is less comfortable with it. I am trying to decide how to structure this. I can see multiple solutions: a single large script or workflow, or many separate scripts or workflows (possibly a mixture of both), one for each individual state. The downside of a large script or workflow is that there is really no way we can multiple people working on it together at the same time. With separate tasks, each person could contribute and we could break it down into small tasks. But we may end up with a hodgepodge of different solutions and a mess to look at and troubleshoot. I also have testing concerns. I know I can write unit tests for code, but is there any way to test workflows in an automated fashion, or is that just not possible? Anyone dealt with a project like this and have some suggestions?

I would not go with a mix of both since the triggers might be a conflict or if there is any dependency among them. I would prefer go with scripting and you can create a library that will be adding units of work (functions), then your team will need to define a strategy to push, pull and merge functional pieces of work, resolving conflicts together and using code review. Not a fan of workflows.

I also think scripting is better solution

pick the solution easiest for maintenance