Hi Kevin,

I appreciate your question as it's one that every leader shares with you at some point in their leadership journey.

WIthout knowing all the details, my advice is to:

1. Review expectations. "Mr. Developer, we agreed that..." [Note that the expectations you shared "in detail" may not have been as clear to the other party as you believe. It's very common.]
2. Discuss the gap. "It's been 120 days and to my knowledge you have not submitted anything."
3. Highlight consequences. "Without this code, we have no project. Without a project, we have no paychecks."
4. Share your interpretation of the facts. "I'm interpreting the lack of submitted code to mean that this project isn't a priority for you and frankly, I'm frustrated by that."
5. Ask for their perspective. "That's the world as it looks to me. How do you see it?" [A vital step - you learn so much about your processes, their challenges, and motivations.]
6. Craft next steps. Depending on what you learn, you'll want to move to a new set of expectations (eg concept delivered in 5 days with a full demo ready in 14) or, if their perspective reveals a lack of commitment to the team or project, it may be fully appropriate to thank them for their service and end the contract. Or you may even learn you goofed up somehow and need to apologize and get things back on track.
7. If you're continuing the relationships, conclude by clarifying who is doing what by when and how you will both know it's been done.

Anyhow, that is a quick thumbnail sketch of how you might go about it. Please contact me directly if you'd like to discuss further from a coaching perspective.

Good luck,

David