Post-Implementation Structure and Governance

Everyone,

We are considering what our post-implementation Luminis personnel and developers structure and governance will consist of. Do any campuses have brief synopses or organizational charts detailing their structure that they are willing to share? I'd be very interested in seeing how other campuses have organized their Luminis design, development and oversight teams after go-live.

Thanks in Advance,
Thom

0
No votes yet

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Governance... a nasty word

As most folks are aware, portals can be politically challenging. Our portal represents all areas of our institution and no single area should have control on the portal. In order to maintain fair thought across all areas we have structured 2 committees to guide our content development and implementation process.

The first committee is our Content Planning group. It has around 30 people from most areas on campus. Their charge is to discuss changes to the portal and make the change recommendations on how the portal should be organized. I am the technical representation and a co-lead to that group. i keep them in check on what can or cannot be accomplished. My other lead is a content specialist who is there to make sure things conform to the universtiy web standards.

The second committee is our Web Presence Advisory committee. These are the true stakeholders of the portal. This group has around 10 members consisting of deans and upper management. My CIO and the associate VP for communications co-chair that group. They drive the initiatives for our environment and task out to the content planning group to develop recommendations.

This model has bene in place a little over a year for us and is working quite well. We are going through a LEAP process from Plus to banner and groups like this are essential to keep things moving forward in an organized manner.

Mission and Guidelines

I meant to mention we do have a document that details the mission of our content planning group. This document also contains guidelines for things like determining role, channel, and tab creation requirements. I am seeking permission to share this document. If you are interested in seeing this, please email me.

-- Jason Wearley
-- jwearley@kent.edu
-- Kent State University