# data[].attributes.headline
Clean up our Confluence folders with names familiar and easy for everyone to find stuff / winter cleaning

# data[].attributes.subject
Clean up our Confluence folders with names familiar and easy for everyone to find stuff / winter cleaning

# data[].attributes.headline
Try and get decks circulated in due time to provide ample team feedback/insight etc.

# data[].attributes.subject
Try and get decks circulated in due time to provide ample team feedback/insight etc.

# data[].attributes.headline
Reduce the amount of links we keep sending via HipChat/Slack in future, unless asked for a specific link

# data[].attributes.subject
Reduce the amount of links we keep sending via HipChat/Slack in future, unless asked for a specific link

# data[].attributes.body
She's really passionate about having Spanish support and helped us make our case with the Event Calendar!

# data[].attributes.headline
More frequent check ins on service requests with Accenture/CNMP

# data[].attributes.subject
More frequent check ins on service requests with Accenture/CNMP

# data[].attributes.body
Yesterday's demo was kinda bumpy. Would it help to have more frequent, informal check ins with Accenture/CNMP where we could talk through issues rather than waiting for a big pile 'o stuff like that?

# data[].attributes.body
Get better about coordinating internally on emails, calls, etc - who is writing notes? what do we need from census? can we consolidate client emails?

# data[].attributes.headline
"Design System" with coding capabilities

# data[].attributes.subject
"Design System" with coding capabilities

# data[].attributes.body
It was easy to code up some front-end code for the Event Calendar Component and got our foot in the door with Accenture!

# data[].attributes.headline
Streamline processes in place for client calls, meetings etc for better efficiencies

# data[].attributes.subject
Streamline processes in place for client calls, meetings etc for better efficiencies

# data[].attributes.headline
Can we announce ourselves when we join client calls?

# data[].attributes.subject
Can we announce ourselves when we join client calls?

# data[].attributes.body
So. Many.  Many were productive but there was very little time for much else.

# data[].attributes.headline
More face time at Census (Reem), CNMP, James and all other key players

# data[].attributes.subject
More face time at Census (Reem), CNMP, James and all other key players

# data[].attributes.body
Volunteers a lot of things (links, examples, decisions) but we don't hear from him much.  Perhaps set up a meeting with who he needs to talk to to actually book him time to complete our ask?

# data[].attributes.body
for schedule, what's in each batch, etc. right now things get updated in multiple locations

# data[].attributes.headline
"Design System" was pretty much copy/pasting content at this point

# data[].attributes.subject
"Design System" was pretty much copy/pasting content at this point

# data[].attributes.body
Lots of components have been ported and very little needs to be put in place in order to have a new template demonstrated.

# data[].attributes.headline
We're talking more between orders, especially between Reingolders.

# data[].attributes.subject
We're talking more between orders, especially between Reingolders.

# data[].attributes.headline
Bumping into Census Bureau-wide language inconsistencies that could impact UX

# data[].attributes.subject
Bumping into Census Bureau-wide language inconsistencies that could impact UX

# data[].attributes.body
e.g. Census "TAKER" instead of Worker or Employee, "Complete" instead of "take" the census
We get shut down very quickly on our recos but we need to keep emphasizing that these decisions can have a real impact on the 2020 site.

# data[].attributes.body
Feels like we're losing Lisa's faith that we have a vision for the future releases. Not sure exactly how to execute other than get more bodies on this project to sketch stuff out and prove that we're looking ahead.