Please enable JavaScript.
Coggle requires JavaScript to display documents.
Technology Execution Interference (Process (Siloed and diverging goals;…
Technology Execution Interference
Code Red Barriers
Deadline trumps all other criteria
Role confusion, who is boss? Prod, PMO, Glen, Sales, Jackie, Julie?
Knowledge and comms across teams, nothing unified
Delivery process, PM, ARB, Test, Eng, SD, TS, PS :
Lack of accountability, no one makes hard decisions; opposing criteria (timeline v. quality v. process)
Product starts us developing before consulting with SMEs, leads to rework
Lack of central authority on process and architecture; no clear governance or data strategy
Engineers are reduced to programmers, code to order, micromanaged by Product Mgmnt, Test, and PMO; no true partnership btwn End and Product
Leadership
Senior leadership (EVPs, G, T) reality gap; sanitization of data
Slow decision making
Everything has to go through Glen
Same validation circle for 15 years, not good to question authority
Risk averse mentality
Unwillingness of leadership to reduce projects
Lack of one Vision: Sales, TS, Product, Eng, SD
Infrastructure deficits
Lack of senior level role and responsibility clarity
Too many decision makers
Product and Tech collaboration is assumed; does not really exist
Mixed messaging from senior leadership; focus on platform v. enhance legacy systems
Too many meetings, no clear agendas or outcomes
Shifting priorities due to unreasonable plans and expectations
Process
Siloed and diverging goals; poor goal alignment
Inability to respond to requests fast enough (prioritization, dm, alignment)
Lack of metrics to measure success
Measured by process adherence v. actual outcomes
New testing process, slow, no evidence it's working; SQA 'black hole'
Lack of automation
Process difficult to change, incentivized to maintain status quo
Validation process slows development of functionality; doing too much? Validation does not equal testing
Post mortems do not lead to actions due to lack of authority
Resourcing
New products struggle to get scalability; rush to functionality
Resource shortage; lack of domain experience (extends timelines)
Customer Success
No process for taking on new products