...

1. <<< data warehouse design team reorganized 3 times with new personnel
2. <<< data warehouse team had good business but not strong data architecture skills
3. <<< after 3 reorgs, the data model came out 6 weeks late
4. <<< the data warehouse team shared little until done
5. <<< my data services team was fully dependent on the data model
6. <<< the warehouse data model delivered was unusable
7. <<< the data services team had to engineer a working, useful data model for services
8. <<< we communicated weekly to the CIO our dependencies, the expected impacts of delays, bad design
9. <<< we weren't allowed to add resources or budget to our team
10. <<< our team overcame severe family problems to stay focused on delivery
11. <<< CIO made faces and said we needed to make the original deadline without added resources
12. <<< we delivered the data services to go to production 6 weeks late as well
13. <<< we failed to make up the lost time from the warehouse team
14. <<< key - we failed expectations and there were consequences for the team
15. <<< we created both useful data services that were accurate and a usable data model
16. <<< the business did use the new data lake and it became the core for all internal and client solutions as the source of truth

...

Process to move forward after a missed key project milestone

1. Own the problems first then your team's responsibilities and support clearly.

...

1. Communicate clearly, directly, immediately with all stakeholder groups.

...

1. Agree on the core team to lead analysis and solution definition going forward.

...

1. Identify problems, missed expectations, consequences.

...

1. Research together root causes for failures, missed opportunities.

...

1. Collaborate with stakeholders on options, best strategy forward to get the consensus and commitment for success in the next stage.

Candidate Solutions

Step-by-step guide for Example

...