# data[].attributes.body
communications

roles and responsibilities

working with a contractor

survey design

# data[].attributes.body
communications

roles and responsibilities

working with a contractor

survey design

# data[].attributes.body
During our check ins, I would have asked more questions and reduced the time that I spent giving updates.

# data[].attributes.headline
Number of people involved in the research, specialy after having Integrated staff on board was a bit confusing on who's doing what and make communication a bit hard. 

# data[].attributes.subject
Number of people involved in the research, specialy after having Integrated staff on board was a bit confusing on who's doing what and make communication a bit hard. 

# data[].attributes.body
I was excited about including this research component because it emulates best practices for instructional design, particularly for communities where it is a new offering. The insights gathered fall under the "Analyze" stage of the ADDIE model for ID. (B)

# data[].attributes.body
Starting in July, Becky became "absent without leave" on PRESTIJ as she became more involved in ASAS startup.

# data[].attributes.body
The university teams and UTEs were already overwhelmed with many tasks on their plates, and so was the team at the beginning, so there was a bit of hesitance from the field to take this task on.

# data[].attributes.body
Cameron moved off of PRESTIJ. Dina left the team several months into the research.

# data[].attributes.headline
Limited LoE for research on program team

# data[].attributes.subject
Limited LoE for research on program team

# data[].attributes.body
I think I heard that the program team had very limited LoE for research understandably based on other programming responsibilities. This was the reason for the RACI.

# data[].attributes.body
I was expecting to receive actionable recommendations that could be used in program design, which was mostly what happened. (B)

# data[].attributes.headline
Our involvment as PRESTIJ team was a bit bigger than expected. 

# data[].attributes.subject
Our involvment as PRESTIJ team was a bit bigger than expected. 

# data[].attributes.body
We were able to better understand the importance and usefulness of this approach along the way.

# data[].attributes.body
I think our HQ team ended up being more involved than anticipated in the production of the Integrated deliverables, particularly when it came to presenting back the research in an actionable way. (B)

# data[].attributes.headline
Try to join regular PRESTIJ team meetings to understand the working environment

# data[].attributes.subject
Try to join regular PRESTIJ team meetings to understand the working environment

# data[].attributes.body
I think that it might have been easier to understand what was happening for the team if I could join at least a monthly or biweekly meeting focused on other tasks. That would have helped me contextualize the research and know more about when/if the team would be available.

# data[].attributes.body
The full research suite really helped communicate out the needs and attitudes of both the learners and the UTEs, which was powerful from a motivation perspective and also very helpful for design. (B)

# data[].attributes.headline
I hoped that the results would make the team feel like it was a worthwhile effort

# data[].attributes.subject
I hoped that the results would make the team feel like it was a worthwhile effort

# data[].attributes.body
At the early stages of the Hybrid modality, research was not on the radar for the technical team. So, it was not clear what the themes of the research were, what exactly would be questioned, and how. I was not sure to what level we, the technical team, would be involved, what the role of the university with all its challenges would be, and how this component would support this initiative and at what labor cost. Also, the number of people and teams involved in this project made some extra management overhead and confusion at the early stages.

This context and uncertainty may have delayed the research component a little bit.

# data[].attributes.headline
It took more time than expected, which is understandable  like the translation to arabic part and reviwing it to make sure the terminology is correct. 

# data[].attributes.subject
It took more time than expected, which is understandable  like the translation to arabic part and reviwing it to make sure the terminology is correct. 

# data[].attributes.body
As some point Integrated report sounded like raw data. I believe they could have presented a more streamlined report findings and tied observations.

# data[].attributes.body
My expectation was that we will come to results that we already know about the context ,and I'm happy that the results exceeded my early expectation

# data[].attributes.body
I think the work that we did could easily be transferred to other projects that include an online learning component and all of the tools are already there to do the research in a different setting. I think being proactively about "template-izing" IR tools could be a good way to motivate the extra work that it requires. Using the same instrument in multiple settings could also help show similarities and differences -- which helps identify areas where approaches can be re-purposed. (B)

# data[].attributes.body
As we proceed with the research and had common understanding of the research component and we had a solid plan with clear objectives, sure this changed my early expectation and we could feel the importance of the results and analysis of the available data and how these findings support our decisions and improve the practices