# data[].attributes.headline
So far, Any projects involve more than one business unit? - that is a sign for two researchers working together

# data[].attributes.subject
So far, Any projects involve more than one business unit? - that is a sign for two researchers working together

# data[].attributes.headline
Research planning and effort prioritization 

# data[].attributes.subject
Research planning and effort prioritization 

# data[].attributes.body
The research efforts can be pre-scoped and prioritized within each single business unit and/or across business units.
Researchers can be attached to one business unit and have more flexibility. (sometimes certain business unit may not have sufficient research needs, or do not get sufficient support/capability).

How might we make best use of the hours and capabilities of researchers, and create the biggest impact from each individual as well as the whole team?

# data[].attributes.headline
Random 1-1 sessions within the team. Like donut but just for the research team

# data[].attributes.subject
Random 1-1 sessions within the team. Like donut but just for the research team

# data[].attributes.headline
Working with business to get to project goals quickly to enable project to get kickstarted. 

# data[].attributes.subject
Working with business to get to project goals quickly to enable project to get kickstarted. 

# data[].attributes.headline
Some kind of sharing (both professional/ personal interests) during team meeting? Can be short and sweet 

# data[].attributes.subject
Some kind of sharing (both professional/ personal interests) during team meeting? Can be short and sweet 

# data[].attributes.headline
Let stakeholders know what we are working on

# data[].attributes.subject
Let stakeholders know what we are working on

# data[].attributes.headline
Within the team, each one of us should drive a team initiative, solo or with others. Also 1x a year  try to participate in UX community events (do a course, run a talk at a conference, attend a webinar) to keep yourself relevant and have a good network. Helps with hiring etc.

# data[].attributes.subject
Within the team, each one of us should drive a team initiative, solo or with others. Also 1x a year  try to participate in UX community events (do a course, run a talk at a conference, attend a webinar) to keep yourself relevant and have a good network. Helps with hiring etc.

# data[].attributes.headline
Log research requests that were rejected, on top of tracking studies that have already been done to ascertain demand

# data[].attributes.subject
Log research requests that were rejected, on top of tracking studies that have already been done to ascertain demand

# data[].attributes.headline
Initiate a topic you and another researcher are both interested in to work together on:

# data[].attributes.subject
Initiate a topic you and another researcher are both interested in to work together on:

# data[].attributes.body
1. Learn from one another
2. Develop synergies

# data[].attributes.headline
Yes to buddy systems! need an extra pair of eyes for feedback or what's good/bad about the work, tips for improvements, not sure who's my buddy :/ 

# data[].attributes.subject
Yes to buddy systems! need an extra pair of eyes for feedback or what's good/bad about the work, tips for improvements, not sure who's my buddy :/ 

# data[].attributes.headline
Sometimes need more help from research side with stakeholders management - expectably when the design team and business have yet formed strong relationship and process. 

# data[].attributes.subject
Sometimes need more help from research side with stakeholders management - expectably when the design team and business have yet formed strong relationship and process. 

# data[].attributes.headline
if we can create a more visible board of ongoing / upcoming activity, the issue about communicating weekly updates is less important.

# data[].attributes.subject
if we can create a more visible board of ongoing / upcoming activity, the issue about communicating weekly updates is less important.

# data[].attributes.body
less about communicating about updates; more about raising challenges and getting input from others to help problem solve

# data[].attributes.headline
We can have frequent virtual bonding activities as well - (e.g, virtual jeopardy/games)

# data[].attributes.subject
We can have frequent virtual bonding activities as well - (e.g, virtual jeopardy/games)

# data[].attributes.headline
No researcher should work alone and in silo. The buddy system is still semi official with no real accountability for deliverables.

# data[].attributes.subject
No researcher should work alone and in silo. The buddy system is still semi official with no real accountability for deliverables.

# data[].attributes.headline
weekly updates on what we are working on, what's the blocker and if the previous work has been completed

# data[].attributes.subject
weekly updates on what we are working on, what's the blocker and if the previous work has been completed

# data[].attributes.headline
We could have a team lunch to coincide with quarterly research updates to Sandeep

# data[].attributes.subject
We could have a team lunch to coincide with quarterly research updates to Sandeep

# data[].attributes.headline
Would it help if each of us have one or two core strengths that could be activated/ be an expert from time to time? I.e. language/ methodology/ communication with stakeholders etc. E.g. the China native project, I joined because of my language skills, and I contributed and learnt a lot E.g. I know JH has expertise in agile research and knows how to show impact, which I find useful. Then next time I can consult him for this, or even collaborate a project 

# data[].attributes.subject
Would it help if each of us have one or two core strengths that could be activated/ be an expert from time to time? I.e. language/ methodology/ communication with stakeholders etc. E.g. the China native project, I joined because of my language skills, and I contributed and learnt a lot E.g. I know JH has expertise in agile research and knows how to show impact, which I find useful. Then next time I can consult him for this, or even collaborate a project 

# data[].attributes.headline
Celebrating each other's milestones eg work anniversary birthdays

# data[].attributes.subject
Celebrating each other's milestones eg work anniversary birthdays

# data[].attributes.headline
need better overall traffic mgmt of incoming projects / requests; this has been missing

# data[].attributes.subject
need better overall traffic mgmt of incoming projects / requests; this has been missing

# data[].attributes.headline
Can we create an automated Slack bot for updates before team meetings?

# data[].attributes.subject
Can we create an automated Slack bot for updates before team meetings?

# data[].attributes.headline
OKR's for Goal Setting: The system works. Review it as a team quarterly for early trend detection and then yearly to come up with final team score.

# data[].attributes.subject
OKR's for Goal Setting: The system works. Review it as a team quarterly for early trend detection and then yearly to come up with final team score.

# data[].attributes.headline
yes to bonding activities; frequency... tbd

# data[].attributes.subject
yes to bonding activities; frequency... tbd

# data[].attributes.headline
Notion weekly update - I sometimes forget to write it because we do not seem to refer to it at all - so if I forget it seems to have no impact? Unless we have a reason to update this? Or make it useful somewhat?

# data[].attributes.subject
Notion weekly update - I sometimes forget to write it because we do not seem to refer to it at all - so if I forget it seems to have no impact? Unless we have a reason to update this? Or make it useful somewhat?

# data[].attributes.body
4Ps:
1. Progress from last week
2. Plan for the coming week
3. Problems is any
4. Personal

# data[].attributes.headline
Single Source: Start of the year alignment on incoming projects for CBG, IBG, MOT, FOW so we know what is the workload going to be

# data[].attributes.subject
Single Source: Start of the year alignment on incoming projects for CBG, IBG, MOT, FOW so we know what is the workload going to be

# data[].attributes.headline
Working on research-related initiatives, aside from our core work

# data[].attributes.subject
Working on research-related initiatives, aside from our core work

# data[].attributes.headline
Daily stand ups - shall we consider doing it like weekly instead? Beginning of the week - a retro for the past week and what to look forward next week?

# data[].attributes.subject
Daily stand ups - shall we consider doing it like weekly instead? Beginning of the week - a retro for the past week and what to look forward next week?

# data[].attributes.body
As I am aware some of us need to do daily stand up in respective team and might be too much update

# data[].attributes.headline
Team gatherings at least 1x a month to keep the team spirit together

# data[].attributes.subject
Team gatherings at least 1x a month to keep the team spirit together

# data[].attributes.headline
Planning time better with a cut-off period for projects & high level calendar with transparency for all teammates to see

# data[].attributes.subject
Planning time better with a cut-off period for projects & high level calendar with transparency for all teammates to see