# data[].attributes.body
I think we could use a mission statement. Followed by things that we value.

An overview of projects that highlight these values would be a way to convey these beliefs.

I like the way OSU has presented these course snippets.

# data[].attributes.attachment_link.title
Preview Online Learning | Oregon State Ecampus | OSU Degrees Online

# data[].attributes.attachment_link.description
Tour our innovative online classes from across Oregon State, and see what all of the hype is about.

# data[].attributes.headline
UWC2 instructional designers collaborate with experts and teachers, applying evidence-based educational practices to co-create engaging and effective courses and programs.

# data[].attributes.subject
UWC2 instructional designers collaborate with experts and teachers, applying evidence-based educational practices to co-create engaging and effective courses and programs.

# data[].attributes.body
UWC2 instructional designers collaborate with faculty, instructors, and other experts to co-create a learning path that is student-focused and engaging.

I think anything we produce should come with a list of the ways in which we do this, as in some of the examples we've looked it. It's really hard to be transparent and succinct at the same time.

Also, totally stole bits of this from Jan, Judith, and Laura's posts and comments. I think those were all great thoughts!

# data[].attributes.body
UWC2 instructional designers work with subject matter experts across the university to co-create transformational experiences for a variety of learners.

Our values include:
empathy for teachers and learners;
evidence-based practice;
creating community;
authentic, applied, learning for maximum relevance, and
creative use of tools and resources.

Obviously there could be more...

# data[].attributes.body
One of the barriers I see to easily being concise is the Instructor/Faculty/Subject Matter Expert (SME) conundrum. Internally, we understand "instructor" to be inclusive of both faculty and non-faculty SMEs. I worry that some faculty members view that language as insufficiently respectful of their position (if not actually demeaning). Add to that the layer of course developers, who may not ultimately be the course instructors. When we refer simply to "developers" I think we've stepped over a jargon line that can easily lead to confusion, particularly in subject areas rife with software developers (think CA!).

# data[].attributes.headline
Link back to our first Padlet - in case you want to see the key ideas that emerged there

# data[].attributes.subject
Link back to our first Padlet - in case you want to see the key ideas that emerged there

# data[].attributes.headline
Making a draft mission statement together

# data[].attributes.subject
Making a draft mission statement together

# data[].attributes.body
Apparently, this format allows us to form connections among the posts! Click the ... in the action menu for each post to choose other posts to which to connect.

Let's have at it!

My very drafty draft. trying to capture the essence of our discussion today, might be:

We work collaboratively  across the university ecosystem of experts and beyond, across a variety of course formats and a spectrum of domains, to co-create evidence-based, student-centered courses and programs with our partners.

We see our role as interpreter / translator; as advocate for faculty and students;  and as bridge between excellent domain content and teaching strategies and the tools and resources which enable transformational learner experience.