...
- <<< data warehouse design team reorganized 3 times with new personnel
- <<< data warehouse team had good business but not strong data architecture skills
- <<< after 3 reorgs, the data model came out 6 weeks late
- <<< the data warehouse team shared little until done
- <<< my data services team was fully dependent on the data model
- <<< the warehouse data model delivered was unusable
- <<< the data services team had to engineer a working, useful data model for services
- <<< we communicated weekly to the CIO our dependencies, the expected impacts of delays, bad design
- <<< we weren't allowed to add resources or budget to our team
- <<< our team overcame severe family problems to stay focused on delivery
- <<< CIO made faces and said we needed to make the original deadline without added resources
- <<< we delivered the data services to go to production 6 weeks late as well
- <<< we failed to make up the lost time from the warehouse team
- <<< key - we failed expectations and there were consequences for the team
- <<< we created both useful data services that were accurate and a usable data model
- <<< the business did use the new data lake and it became the core for all internal and client solutions as the source of truth
own the problems first then your team's responsibilities and support clearly
communicate clearly, directly, immediately with all stakeholder groups
agree on the core team to lead analysis and solution definition going forward
identify missed expectations, consequences
research together root causes for failures, missed opportunities
collaborate with stakeholders on options, best strategy forward
...