building focused, motivated, self organizing collaborative teams that improve with effective feedback is important. I have several reference points that have been helpful to me.
what's in it for the company?
what's in it for the team?
what's in it for me?
expectations, consequences
CBTP focus
powerful communication, consensus, collaboration
democratic autocracy on decisions, organizing
continuous focus on execution, change management, stakeholder consensus, value delivery
Project Homeruns >> how to deliver solutions: Discovery, Assessment, Design

How to Improve Your Score

...

on Investments in Business, IT

find the domain and stakeholders << VCE definition?
find the purpose << mission, value for the domain?
find the challenges << what are the current issues and problem statements?
find the history <<. what were the expectations, investments, consequences of past efforts?
find the goals and priorities now << what are the current goals, priorities and related KPI, OKR metrics
find the best solution strategy << given the goals, resources, needs, what is a candidate best solution strategy? << VCRS
find the potential value << research the potential value, impacts for a "best" solution strategy with those responsible for delivery and operation << FACTUR3DT.io << POVs
find stakeholder consensus << net value for change? ownership? VCRS keys communication, consensus, collaboration methods
find the commitment for the solution << CBTP << new expectations << new solution commitments << resource and solution planning strategies, tactics
kick off the solution process

how to handle missed milestone in data architecture project

a financial services example ---

need defined for a new, common source of truth with central data warehouse and multiple feeds and services to solutions

<<< prior segregated data marts with ETLs to synch data as needed
<<< DQM issues, impacts
<<< IT management had poor value, credibility score with business
<<< goal was a single source of truth data warehouse with many feeds, services, secure

data services and operations teams were segregated from the data warehouse design team
the new data warehouse had never been done by the company

<<< 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 problems, missed expectations, consequences.
Research together root causes for failures, missed opportunities.
Collaborate with stakeholders on options, best strategy forward to get the consensus and commitment for success in the next stage.

...