No one likes to be the person at the table who is constantly talking about trimming project requirements. Call them a buzz kill, but it’s important that someone (ideally multiple people) on a healthcare integration project is willing to play the “bad guy” by keeping scope top of mind. This is especially valuable when making critical decisions as third-party dependencies slip or unresponsive resources put the timeline at risk. Knowing what steps are vital to delivering the Minimum Viable Product (M.V.P.) is one of the best ways that technology partners supporting an integration project can encourage forward momentum where it counts.