Those of you who attended the most recent UW-IT Town Hall have heard that a renovation is going to take place in the UW-IT organization. This blog entry is to follow up with more context and details about the renovation, which will be effective July 1. This renovation is driven by three factors:
- Retirements and succession planning in Senior Leadership. At the Town Hall I announced that Alisa Hata will be reducing her hours and stepping down from the day-to-day leadership of Technology Management in preparation for an eventual retirement later this year. Alisa will continue to play an important leadership role within UW-IT, including in the Leadership Development Program, new governance structure, and other efforts. I deeply appreciate her invaluable contributions to Technology Management and UW-IT, and look forward to her continued involvement with the organization.
- The need for UW-IT to be more accountable to the UW in governance of IT resources.
- The need to right-size organizational leadership positions to reflect the spans and layers of control that are manageable for each individual.
Each of these on its own would be enough to precipitate reorganization; together they make a case for thoughtful analysis of the current organization and how best to position us for the future. This analysis includes considering what is working and what is not, what we need to accomplish, and what external factors will be impacting the campuses, UW-IT, and the UW’s other technology organizations over the coming year.
In addition, there is a need to ensure that any reorganization not be too disruptive, so that it doesn’t negatively impact our ability to execute over the coming year when the University is depending upon us to deliver on so many major projects.
Finally, the need to right-size leadership positions and spread responsibilities means there is an opportunity to bring greater diversity of opinion to senior-level decision making. What skill sets do we need? What synergies can we enable with the organization? What are the most important things we need to accomplish over the next couple of years and how much can we increase the chance for success through having the right voices at the table and the right units under a single division?
There is a lot to think about and consider in this renovation; truthfully I have been thinking about all of these issues for quite a while, so I will try to lay out my thoughts as clearly and concisely as possible.
The Drivers
A key consideration is what are the biggest drivers that will impact UW-IT as the lead technology organization for the University? The UW’s ever-increasing demand for technology and our ever-shrinking budget is probably one of the biggest drivers; it is important for UW-IT to help the University achieve maximum value for its technology dollars.
Another driver is that much of the technology campus relies on is outside our control. For example, bring your own device (BYOD) is the term most often used, but it really should be BYO Devices and Services (BYODS). The University will call on our resources to maximize value of these devices and services through reliable and ubiquitous networks, mobile applications, and ever-increasing needs for faster access to data. At the same time, we need to minimize the risk of these devices and services through better contracts with outside providers, better understanding of responsibilities, and better options for security. We will need to work closely with campus IT providers to determine what can best be done by UW-IT and what is best done by campus units, or through third-party providers, to deliver the most value for our limited IT dollars.
Also important is understanding what are our major projects and where UW-IT’s resources are going over the coming years. The Human Resources/Payroll system replacement project is probably the single biggest venture ever undertaken by UW-IT and the campus. Improving the student experience through Kuali Student and teaching and learning initiatives will also continue to be important for the UW. The University is depending on us to deliver Enterprise Data Warehouse capabilities to advance major initiatives such as Activity Based Budgeting. Focusing on upgrades to deal with infrastructure debt in our data centers and networks is still a priority. The need for upgrades for the digital environment and infrastructure we provide through unified communication, video-conferencing and major initiatives around collaborative applications, such as Office 365 and Google Apps, will only grow.
Finally, considering how best to diversify the Senior Leadership Team and deepen UW-IT’s outreach with the UW community, and particularly, with faculty.
The Senior Leadership Team would benefit from representation from Engineering and Customer Service, as these are central to the services we provide across the University. At the same time, Service Management and Academic Support, which we provide to faculty and departments, will need deep outreach to all three campuses to ensure we are meeting their needs.
The Renovation
With these considerations in mind, Alisa’s current responsibilities will be spun into four operating divisions, creating a flatter organization and bringing more diversity in leadership to the table: Customer Service and Support, Computing Infrastructure, IT Services, and Academic Services.
Four New Operating Divisions
Below are more details about the four new operating divisions. Each division leader will report to me and be a part of the Senior Leadership Team. These changes are effective July 1, 2012.
- Customer Services and Support will be led by Tammy Stockton, and will include Computer Operations, Customer Relationship Management, IT Consulting & Support, and the Technology Service Center.
- Computing Infrastructure will be led by Brad Greer, continuing his current responsibilities, which include Application Integration Services, Applications Engineering, Identity & Access Management, and Network Management Tools, as well as Large-Scale Storage and Systems. In addition, Brad’s responsibilities will now include Unix Engineering and Windows Engineering. Most of you know that Brad led the Unix Engineering group for a number of years and has, over the last year, taken responsibility for a diverse portfolio of applications and infrastructure, including Research Computing and, as mentioned above, Large-Scale Storage and Systems.
- IT Services will be led by Erik Lundberg, who has served as Director of the Computer Science Laboratory for the Computer Science and Engineering Department. For the last year, Erik has worked half-time for UW-IT with cloud services, service management and vendor management. IT Services will include the Program Management Office, Service Management & Planning, Strategic Sourcing & Vendor Relationships, and Technology Business Continuity.
- Academic Services will be led by a yet to be determined member of the teaching faculty. In the interim, Alisa Hata will lead this division. Academic Services will include Academic & Collaborative Applications, Accessible Technology, and Learning Technologies.
I am pleased to welcome Tammy, Erik, and Brad to the Senior Leadership Team and am confident their presence will make a positive impact on this group.
FAQ’s
Why a teaching faculty member for Academic Services?
Much of the work we are doing right now requires an ability to engage faculty. Initiatives such as lecture capture, a campus-wide learning management system, pilots in Massive Open On-Line Courses (MOOCs), and how to teach with eTexts; all involve faculty leadership.
Do you have someone in mind for that position?
No, I really don’t. There are some names that come to mind, but this is an opportunity to have the groups be involved in the process. Potential candidates should have some interaction with the groups before a decision is made. This is an opportunity to build a bridge between the campus and UW-IT, and we need to have a process that makes sure the bridge is strong and productive.
Are we going to be moving offices?
No, this renovation shouldn’t require moving any office spaces; it took months to plan and execute the last move, and moving offices would be too disruptive at this time. The last move was productive because it brought groups working on different parts of the same problem closer together, but this time it shouldn’t be required.