Happy holidays ((hugs))

This looks awesome. I think you’re on the right track.

In essence, you’re trying to create a great experience for the IAI members, primarily by focusing on the technology and infrastructure. I’m wondering if you can benefit by some of the work we’ve been doing lately. We’ve found the organizations that do best at creating great experiences do so by focusing on three areas: Vision, Feedback, and Culture.

I think those three things can be helpful here too:

1) Think about creating an experience vision: “What will it be like in 5 years to be a member of IAI?”

2) Think about how you’re going to get feedback: “How will you spend time every few weeks watching people interact with your infrastructure?”

3) Think about the culture of your part of the organization: “How will you ensure that you’re celebrating the design mistakes that will be inevitable as you take risks and experiment?”

Just a thought…

Jared

I think long-term it should slant less towards technology and more as tools for processes because I would like the IAI operational capability (our staff) to be primarily responsible for tech ops. So, long-term I think this role should go down that path.

Right now, I think it needs to be closer to the tech side of the spectrum because a) we are not staffed that way b) current technology used in the systems we have is somewhat funky (it’s not broken, but it’s not a well oiled platform we can build on either).

So that’s it. Ha, I think I finally articulated what I wanted. Awesome, you guys rock. This is exactly what I was hoping to get out of posting this draft.

More thoughts very welcome!!!!

I liked the focus on infrastructure (tools for processes) instead of technology, although Crystal’s right. It still sounds like technology. I’m hoping that’s just a perception that you will be able to shift.

It feels like there’s something missing, something fuzzy in the gray are, but I can’t wrap my head around it. When I read it, everything sounds spot on.

One bit of word-smithing. In the line “Assess the organization’s ability to maintain core systems operational”, the end sounds awkward: “to maintain core systems operational”

Maybe change to “Assess the organization’s ability to maintain core systems” or “Assess the organization’s ability to keep core systems operational.”

Although I know you are trying to address more than technology, it still sounds as though it is largely a technology role. Perhaps it’s more the title that’s not bringing home this point as much as I would expect.

May I also suggest this change to one of your responsibilities…

“Assess the infrastructure wants and needs of new initiatives” to
“Assess the infrastructure needs of new initiatives and offer guidance and advice to make the best use of available systems”

Just a thought