# data[].attributes.body
Keep recording the process sessions

# data[].attributes.body
Don't assume that the US implementation is always the way to go. Look at the actual business need and adapt where necessary

# data[].attributes.body
Trust the expertise of the team members and don't feel the you have to take on everything yourself

# data[].attributes.body
Remember agile principles and ask ourselves if the problem we are solving is worth the current effort. Lets get the core working then tackle exceptions

# data[].attributes.body
Making best use of the time we do have overlapped. If US or UK only try schedule when not overlapped so that that time can be used when both countries need to be on a call

# data[].attributes.body
Support one another. Ask for help when needed

# data[].attributes.body
Ask the right teams for the right things: e.g. data for data questions, business for business questions, integration for integration questions! Appears simple but I don't think we are always doing this currently

# data[].attributes.body
Plan what is going to be covered in the huddle the day prior so individuals are clear whether they have to attend?

# data[].attributes.body
Take into account the need for synced up data in all environments when testing

# data[].attributes.body
Using the time difference to our advantage. EG UK can provide info in the morning for the US to wake up to. The US can then process that and provide things back for the UK morning

# data[].attributes.headline
Keep having regular meetings and communicating

# data[].attributes.subject
Keep having regular meetings and communicating

# data[].attributes.body
Follow up and provide updates on any actions

# data[].attributes.body
Meetings for specific and clear subjects. EG the Ireland and UK specific syncs have worked well to manage scope of call

# data[].attributes.body
Keep huddle meeting short, and have separate meeting for detailed topics with specific member.

# data[].attributes.body
When we need information from someone, pro-actively think if there is anything else we will need from them that week: helps us consolidate the ask, be clear what we need from them, and not have to ask twice

# data[].attributes.body
Use Outlook scheduling assistant to check if people are available before booking a meeting with them

# data[].attributes.body
Document huddles as we go: last few huddles have worked effectively when we have done this

# data[].attributes.body
When asking for something, confirm the person being asked understands what is being asked of them

# data[].attributes.body
Being unclear what is being asked for: document the ask and what is required, and provide a template if possible

# data[].attributes.body
When a meeting has to be made, take other meetings into account.

# data[].attributes.body
Timebox Huddle and have a clear agenda.

Arrange breakout meetings if topics need detailed discussion

# data[].attributes.body
Meeting invites without agendas

# data[].attributes.body
Remain focused on one topic at a time where possible so that we can not get different things mixed up

# data[].attributes.body
Providing templates for information required