Please enable JavaScript.
Coggle requires JavaScript to display documents.
Team Strategy - Coggle Diagram
Team Strategy
Enablers
Stability
Customer first
Compliance
Team safety and well being
Capture Team feedback
Most frustration points/ areas
Repatative manual tasks
Tickets that should never reach us
• What would help you fix things faster or with more confidence
IMprove operational effeciencies
Automation opportunities
Identify the recurring support tasks and implement run books or automation scripts
Billing automation
Predictable failures and auto healing ?
Understand L2 pain points
Think Future when implementing - Think about challenges in multi jurisdiction set up
Mostly the discussions are around features
Support is usually not discussed a lot
AWS cost optimisation
Read through FinOPs slack channel
Read on AWS Compute Optimizer
Do we have use cases to use SPOT instances
CI workloads?
Refer the following Coggle Diagram
https://coggle.it/diagram/aHI7T0FqoDLN0wqo/t/-
Ticket Analytics - Round 2026
Latest trends
Identify the knowledge gaps and eliminate single point of failures
Address tech Debt
Develop towards a signal platform that will support venues and regulators
Drive QCOM NSW and QCOM 3 to be close to each other as much as possible
Design decisions to be properly validated to ensure
Towards a single solution
Remove Credit card integration to eliminate PCI
Operational knowledge building
On board more people to support tasks
Kingston - Q1
Jayme - Q2
Build basic level of SOPs
Recognition
Share weekly wins
More RISE awards
Strategic Thinking
Validate the work from broader perspective
What does this mean
When work is presented see whether it aligns with broader strategy
How does it help Vic and Future jurisdictions
If yuo are not sure ask someone who knows this
Understand there may be project constraints that might not allow us to do this. But you should always raise concerns and record the decisions made
Other thoughts
Can we trial/ POC some reporting capabilities via the CMac meters to DWH work
Could this work be used as a model for future delivery
Shift left opportunities
Identify issues early via observability and other means
Automatic - 2nd phase
Manual - 1st Phase
Breaches issue
Improve operational resillience
ISolidify DR capability and kowledge around it
Runsheet fine tunning
Do wehav eto better the current process