# data[].attributes.body
Tech eco system page

# data[].attributes.body
Checking authorised software list

# data[].attributes.body
Talking to others

# data[].attributes.body
Calling IT Help

# data[].attributes.body
Speaking to their LTC (if they are aware that person exists)

# data[].attributes.body
Using tools they are already familiar with (possibly not on the authorised tools list)

# data[].attributes.body
Staff induction (when they turn up)

# data[].attributes.body
Yes. A nightmare.

# data[].attributes.body
Learning Futures Website

# data[].attributes.headline
UQ Learning Design community meetings showcasing tools

# data[].attributes.subject
UQ Learning Design community meetings showcasing tools

# data[].attributes.body
Word of mouth from colleagues

# data[].attributes.body
Thing seen at a conference

# data[].attributes.body
There is a committee that serves as a doorkeeper for the uni. But tools can be trialed with permission then, once seen as working well, progress to the committee. The TEL Advisor Group (TELAG) also play a role in this.

# data[].attributes.headline
Learning analytics through ITaLI/ITS (UQ)

# data[].attributes.subject
Learning analytics through ITaLI/ITS (UQ)

# data[].attributes.body
Ask LDs

# data[].attributes.body
Ask learning designers

# data[].attributes.body
What they already use

# data[].attributes.body
What's recommended by a peer

# data[].attributes.body
Generally

# data[].attributes.body
Depends if it is supported

# data[].attributes.body
Not really

# data[].attributes.body
Our Learning @Griffith team monitor this.

# data[].attributes.body
Learning analytics