# data[].attributes.headline
Proactively communicating with the team and other teams, and updating of ClickUp cards

# data[].attributes.subject
Proactively communicating with the team and other teams, and updating of ClickUp cards

# data[].attributes.headline
Keep improving as an individual and as a team

# data[].attributes.subject
Keep improving as an individual and as a team

# data[].attributes.headline
Collaboration on possible and best solution for complex issues

# data[].attributes.subject
Collaboration on possible and best solution for complex issues

# data[].attributes.headline
being naughty and loud that helps other to be comfortable with them

# data[].attributes.subject
being naughty and loud that helps other to be comfortable with them

# data[].attributes.headline
Pushing fixes ot uat without unit testing

# data[].attributes.subject
Pushing fixes ot uat without unit testing

# data[].attributes.headline
Being shy and worried talking to teammates

# data[].attributes.subject
Being shy and worried talking to teammates

# data[].attributes.headline
being afraid that you could be wrong when trying to correct others

# data[].attributes.subject
being afraid that you could be wrong when trying to correct others

# data[].attributes.body
Set up an event with a regular cadence where engineers can bring a problem they face(d) to discuss potential solutions.

# data[].attributes.body
Allow anyone to create a proposal to change something: process, code, architecture. It invites your team to be creative.

# data[].attributes.body
Document the team's reflection on what went wrong, how it could've been avoided, and how to improve for the future if the situation happens again.

# data[].attributes.body
Engineering leaders have regular conversations with the customer support and sales teams to answer their questions about the product and what's happening in engineering.

# data[].attributes.headline
Create internal release notes with release notes for all stakeholders. 

# data[].attributes.subject
Create internal release notes with release notes for all stakeholders. 

# data[].attributes.body
Notes are sent via email + slack channel so people can reply in a thread if they have questions.

# data[].attributes.body
I can't say this enough: Document your decisions and discussions. They can serve you well in the future when trying to solve a similar problem. I recommend creating decision records, using comments on Jira, and sharing code on slack channels.

# data[].attributes.headline
watch other OS training especially on mobile devt

# data[].attributes.subject
watch other OS training especially on mobile devt

# data[].attributes.headline
Involving BPM or other teams in collaborating

# data[].attributes.subject
Involving BPM or other teams in collaborating