# data[].attributes.headline
As part of the business vision section, communicate how the features relate to an integrated customer experience

# data[].attributes.subject
As part of the business vision section, communicate how the features relate to an integrated customer experience

# data[].attributes.headline
There're ways to optimize processes and meetings on both PI and PM end

# data[].attributes.subject
There're ways to optimize processes and meetings on both PI and PM end

# data[].attributes.body
Neelam is working on it, we'll expect more to come.

# data[].attributes.headline
With PM and PI processes now establiished, reduce/eliminate introduction of significant change until end of FY24Q1

# data[].attributes.subject
With PM and PI processes now establiished, reduce/eliminate introduction of significant change until end of FY24Q1

# data[].attributes.headline
Reduce direct communication or meeting by using team slack channel 

# data[].attributes.subject
Reduce direct communication or meeting by using team slack channel 

# data[].attributes.body
Instead of reaching out to individual developers directly, use the team channel to see if anyone who is available to help.
Alternatively, could unified-platform-dev channel, for devs across

# data[].attributes.headline
Use other teams' Stand Up to communicate concerns instead of creating an additional meeting

# data[].attributes.subject
Use other teams' Stand Up to communicate concerns instead of creating an additional meeting

# data[].attributes.body
There're lots of tools we can use to communicate
We don't need to meet, we can lean on the tools more

# data[].attributes.headline
For any meeting over 30 minutes, publish an agenda that allows people to only attend specific sections

# data[].attributes.subject
For any meeting over 30 minutes, publish an agenda that allows people to only attend specific sections

# data[].attributes.headline
meeting suggestion: even this meeting could have been shortened. Everyone fills this out ahead of time then we discuss briefly as a large group then close. 

# data[].attributes.subject
meeting suggestion: even this meeting could have been shortened. Everyone fills this out ahead of time then we discuss briefly as a large group then close. 

# data[].attributes.headline
Let people decline meetings if not important

# data[].attributes.subject
Let people decline meetings if not important

# data[].attributes.headline
Insufficient "big picture" framing of outcomes

# data[].attributes.subject
Insufficient "big picture" framing of outcomes

# data[].attributes.headline
Could some of these meetings just be accomplished in an email/slack? 

# data[].attributes.subject
Could some of these meetings just be accomplished in an email/slack? 

# data[].attributes.headline
Some planning and review meetings seemed redundant

# data[].attributes.subject
Some planning and review meetings seemed redundant

# data[].attributes.headline
Have to work during meetings in order to get anything done

# data[].attributes.subject
Have to work during meetings in order to get anything done

# data[].attributes.body
There's so many meetings I feel I can't get anything done

# data[].attributes.body
Sometimes there are days where I have meetings spread throughout the day and I can't build any momentum to focus on work, so I either work through meetings and risk missing something important or work more after hours

# data[].attributes.headline
Difficult to integrate separate function-focused teams into a cohesive user-centric product experience

# data[].attributes.subject
Difficult to integrate separate function-focused teams into a cohesive user-centric product experience

# data[].attributes.headline
Lack of clarity in tickets/specification docs

# data[].attributes.subject
Lack of clarity in tickets/specification docs

# data[].attributes.body
There were many times when picking up a ticket/planning where it was blocked by dependency or just unclear

# data[].attributes.body
It leads to increased overhead of time and energy spent. I think we should look at all the processes we have and see which ones don't add value and remove them.

# data[].attributes.headline
Introducing too many processes all the time. 

# data[].attributes.subject
Introducing too many processes all the time. 

# data[].attributes.body
We never stick with one thing long enough to get used to it - then it changes again and we have to learn all over again the next milestone.

# data[].attributes.headline
Process seemed to change way too often throughout the quarter

# data[].attributes.subject
Process seemed to change way too often throughout the quarter

# data[].attributes.body
Ex: source of truth documents, process within team seemed to shift far too often

# data[].attributes.headline
Trying to implement the PI process with new Product Management Processes led to a lot of confusion and delays

# data[].attributes.subject
Trying to implement the PI process with new Product Management Processes led to a lot of confusion and delays

# data[].attributes.headline
Good cross-divisonal meetings to gather information 

# data[].attributes.subject
Good cross-divisonal meetings to gather information 

# data[].attributes.headline
Closer collab with Learning led to Internal Trainings on recent M2 & M3 work

# data[].attributes.subject
Closer collab with Learning led to Internal Trainings on recent M2 & M3 work

# data[].attributes.headline
resolving dependencies that were getting lost previously

# data[].attributes.subject
resolving dependencies that were getting lost previously

# data[].attributes.body
Successful management of capacity restrictions and getting work done

# data[].attributes.headline
Seemed to get timing alignment between design and epics

# data[].attributes.subject
Seemed to get timing alignment between design and epics

# data[].attributes.body
Successfully

# data[].attributes.headline
We got a lot done on both Profiles *and* Search - Kyle

# data[].attributes.subject
We got a lot done on both Profiles *and* Search - Kyle

# data[].attributes.headline
Made progress on the completeness of epics

# data[].attributes.subject
Made progress on the completeness of epics

# data[].attributes.body
2 years

# data[].attributes.headline
Overcame a number risks related to how quickly we adopted SAFe - Kyle

# data[].attributes.subject
Overcame a number risks related to how quickly we adopted SAFe - Kyle

# data[].attributes.body
Need some buffer
Prioritize feature for UP
Slow down this quarter, give the org time to create new feature and prioritize requirement

# data[].attributes.headline
Design still at JIT (just in time), rather that ahead of LOE phases

# data[].attributes.subject
Design still at JIT (just in time), rather that ahead of LOE phases

# data[].attributes.headline
Take a break every hour to be more productive

# data[].attributes.subject
Take a break every hour to be more productive