This is really helpful. What else is important to you—that you think the team needs to hear?

I'm sure we've all been on, or at least heard of, projects that haven't gone well. This is where troubled projects can start—at the kickoff. Let's ensure that we are accountable to one another when communicating with others. Be transparent, and check the viability of suggestions. Show your trust in individuals by delegating some of the tasks.

I think it's important to talk about risk mitigation. This is something that we need to ensure we are focusing on within the individual teams. We need to maintain a robust risk log and do our best to keep the Seven Keys to Success green. If you see any issues, please raise them to your team leads immediately. I will be in regular contact with them, and they can pass things along that are serious enough to warrant further discussion.

During the sales cycle, it was determined that we would embed Vencala resources alongside our IBM teams during this project. Additionally, this will be a phased delivery. A live minimum viable product will be built in the first ten months as this is required for Vencala stakeholders. We know that there are risks and dependencies in these elements, so it's vital to adhere to the statement of work and familiarize yourselves with the documentation that has been made available to you.