Explore University Operating Redesign Through Shared Governance

University operating redesign reaches people through ordinary work. Students experience registration, advising, financial aid, and course access. Faculty experience academic authority, committee review, departmental coordination, and teaching time. Staff see forms stall, records move late, and students receive different answers from different offices. A consulting partner helps leaders examine one operating question with evidence, participation, and a visible route toward an authorized decision.

Start with a result stated in plain language. “Students wait twelve days for an advising appointment during registration” offers a clearer starting point than “redesign student services.” Ask where waiting begins, whose cases wait longest, what work happens before an appointment, and how leaders learned of the issue. A budget concern might sit beside long waits, yet neither observation proves a structural answer. Keep observations, assumptions, and decisions in separate columns. This separation stops an early concern from becoming a diagnosis during one meeting.

The first sponsor discussion sets scope. Ask which decisions senior leadership already holds, which choices belong in a senate or committee process, and which groups need early input before options become fixed. Request prior reviews, service records, governing documents, and calendar constraints. Registration dates, budget planning, academic terms, and committee schedules all affect timing. Leave with a short scope note. Name the question, desired result, groups involved, decision route, records requested, and next review date.

In a fictional meeting, Provost Daniel says, “Tell us which departments should combine.” Partner Laila replies, “First, we need to understand the student service concern and the review route. Which student result needs attention? Which faculty and staff groups need a voice before leaders review options?” Daniel reports longer advising waits during registration. He also reports a senate expectation for discussion of changes affecting academic work. Laila records both points and proposes a four week discovery period involving student services, faculty representatives, finance, and the senate liaison.

Laila asks Daniel to name one sponsor and one university coordinator. Daniel names the vice provost for student success as sponsor and the chief of staff as coordinator. The sponsor removes barriers, calls senior reviews, and receives issues needing direction. The coordinator gathers records, schedules interviews, and prevents duplicate requests. Laila places a thirty minute review every second Tuesday on the calendar. Daniel attends when an issue needs senior direction. Everyone knows where a finding goes after an interview ends.

A governance map turns participation from a slogan into work. Put the operating question in the center of a page. Surrounding the question, list students, faculty, staff, finance, academic leadership, and formal governance bodies. Beside every group, record what knowledge exists, what information people need, and how input enters the work. Student representatives might describe appointment barriers. Faculty members might explain program specific advising needs. Finance staff might identify timing and cost categories. The map exposes gaps before a narrow set of voices defines the problem.

Use interviews for focused learning rather than a search for broad agreement. Ask each person to walk through one recent event. Ask a student about the latest effort to secure advising. Ask an advisor where a request enters, when records become available, and where a handoff slows. Ask a department chair which cases need faculty judgment. Invite examples of workarounds, then label every example as an example. Record source, date, role, and context beside each observation. Later discussion needs a record instead of an enlarged anecdote.

Facts need a stable home. Laila creates an evidence sheet with observation, source, question, and next step. One entry reads, “Three students described late appointment openings during registration. Source: student listening session, September 14. Question: do schedules, appointment rules, or demand peaks limit openings? Next step: request appointment data.” No participant calls the issue a staffing shortage before records support such a finding. Another entry records a faculty concern about exception requests, followed by a request for examples and current handling steps.

Disagreement deserves careful attention. A faculty representative says centralized advising would weaken program knowledge. A student services leader says shared intake would reduce repeated explanations. Neither statement settles the question. Laila asks which student cases need program knowledge, which cases follow common rules, and how present handoffs work. Interview notes might show routine requests moving between three offices, while academic exceptions need a faculty review. A shared intake process then becomes one option for routine requests, with faculty review retained for exceptions. Leaders still decide whether such an option fits university priorities.

Meetings need a decision log. Every entry names the question, decision owner or body, information needed, due date, and status. Avoid “align governance.” Use a direct entry: “Determine whether the senate committee reviews changes affecting faculty advising duties. Owner: senate liaison. Information needed: committee procedure and proposed scope. Due date: October 3.” A log makes uncertainty visible. A participant sees whether a concern belongs with a senate body, senior leadership, or a service owner. The consulting partner organizes records and discussion. Authorized university groups make institutional choices.

Options gain value when each option answers the same questions. Describe the student experience, affected work, resources, governance route, risks, and open questions. Keep unknowns visible. A shared service center might improve routing, yet leaders need evidence about training, handoffs, and academic variation. Separate offices might preserve local knowledge, yet leaders need evidence about duplicated work and uneven access. Do not label either path a solution before evidence and authorized review support a choice.

In a fictional workshop, Daniel asks for a recommendation before student interviews finish. Laila says, “We have two early patterns and several open questions. Routine requests appear to move through more than one office. Faculty representatives want clear handling for academic exceptions. Appointment records still need review. Let us brief the senate liaison after we test both patterns.” Daniel agrees. The team keeps momentum without presenting an unfinished view as a final answer.

Communication needs a workplan. Draft short messages naming discovery purpose, groups involved, next input opportunity, and next update date. A staff note might read, “The university is reviewing how students reach advising during registration. Interviews and service record review begin this month. Questions from staff appear at the October forum.” Use plain terms. A dean might understand “intake,” yet a student representative might need an example: a student asks one office for help, receives a referral, and repeats personal details at another office.

Test material before formal review with readers outside the writing group. Ask whether readers understand the problem, evidence supporting each option, choices still open, and next decision. Ask where language hides a practical step. This review does not seek agreement by exhaustion. Its purpose is accurate material ready for the proper forum. Laila then places an option sheet, decision log, source notes, and calendar before Daniel. One issue remains open: who owns follow up when an academic exception reaches shared intake. Daniel asks the faculty representative and student services leader for two handoff rules. Before departure, the chief of staff sends the interview schedule, data request, and October 3 governance question to named owners. At the next session, Laila starts by placing those two handoff rules beside the evidence sheet for review.