# data[].attributes.body
Biweekly formal sync up/meeting with Info Sec Architects will help to understand the roadmap for security engineering.

# data[].attributes.body
Something to outline what platforms each person is supposed to have focus on I know there is stuff on the KB pages but that has not been updated especially with role changes and new additions

# data[].attributes.body
If there is changes that is being made to the firewalls. The team member doing the change needs to stay on their desk and make sure the change has been committed and pushed the targeted firewall successfully instead of leaving it for later and forgetting about it till the next day.

# data[].attributes.body
If someone see an issue that they already did some research on it and familiar with what needs to be done, being brought up again to another team member, they need to own it and communicate about it instead of having them redo the work

# data[].attributes.headline
Great Job Jordon, for staying top of writing up user stories as needed in timely manner!

# data[].attributes.subject
Great Job Jordon, for staying top of writing up user stories as needed in timely manner!

# data[].attributes.body
We are always making changes, but there have been times where there have been outages. I think we just need to be more cognoscente of the pushes we are doing. Especially with tickets as the information end users provide isn't always accurate.

# data[].attributes.body
There needs to be a standard server decom process that is followed so that dead servers aren't left in the F5. Currently server team, web team, and our team each do their own scream tests before decom. These tests could be coordinated so that the servers are being scream tested at the same time between the teams.

# data[].attributes.body
Often feels like we don't have sufficient time to actually think through the problems we are tasked with helping to solve, so I've often found myself reworking, reassessing, or undoing what was previously performed rather than addressing the actual root cause of the issue (addressing symptoms due to constraints).

# data[].attributes.body
Ryan did a great job in mentoring me! walking through of overall Microsoft E5 suite and implementation.

# data[].attributes.body
The team feels more unified now that we are all in the same row

# data[].attributes.body
It feels like Luke really helped us implement a Team working agreement, and it feels like we are slipping away from the items we put on there, and even there hasn't been updates to the working agreement

# data[].attributes.body
Triaging incidents timely and identifying the appropriate SME/next best steps for resolution.

# data[].attributes.body
Helping out with Gemini and handling a lot of the Gemini requests

# data[].attributes.body
We need more of these.

# data[].attributes.body
Kudos for updating the VELOS certs, identifying and escalating the expiring cert issues, and fixing the synchronization issues which manifested in Development F5 environment

# data[].attributes.body
We have been doing a really good job of owning our products. We haven't been a major point of outages, and we are rocking a gold standard PE eval

# data[].attributes.body
Gives a lot of tools to use and learn with, allowing for growth in new technologies while also helping with innovation.

# data[].attributes.headline
Execution on broker out of country tickets

# data[].attributes.subject
Execution on broker out of country tickets

# data[].attributes.body
During cleanup this week found many issues with IP addresses not being in both the F5 and in Palo address group.

# data[].attributes.body
Both of you are spinning up very quickly. Keep asking tough questions.

# data[].attributes.body
Has really been communicative and helps with guiding through tickets and how to handle specific tickets when stuck.

# data[].attributes.body
Kudos to Mike T for taking on more responsibility with F5 and Cloudflare. Keep up the great work.

# data[].attributes.body
Enjoyed the presentation; hopeful for more training!

# data[].attributes.body
You have been a great job spinning up and getting your feet wet. You do not shy away from the challenge of learning something new, and are always eager to help

# data[].attributes.body
There doesn't seem to be any direction or timeline on what promotions or transfers are coming. It seems like we are just being expected to take on more responsibilities without our concerns being addressed

# data[].attributes.body
It seems like lately we have had to step up for other teams to jump in and troubleshoot, at a moments notice. When we need things done in a timely manner, it seems like teams are just tossing it in their backlog and telling us itll get done when they get to it.

# data[].attributes.body
Need to finish the naming convention for Palo's