Process redesign is most effective when teams first understand how existing services work and where users encounter problems. A student services assessment effort at MIT illustrates this approach: instead of beginning with a single proposed solution, the team reviewed a range of administrative and educational support processes, gathered feedback, and identified areas for further redesign. For industrial organizations, the setting is different, but the underlying discipline—assess before changing, prioritize deliberately and involve affected stakeholders—applies to complex operational processes as well.
Start with assessment, not assumptions
The MIT assessment team was tasked with reviewing administrative and educational support processes and recommending where changes were needed. Its work covered services such as career assistance, orientation, housing, supplies, personal support and educational program support. The breadth of that review matters: a service experience can involve multiple offices or functions, so examining only one handoff may not reveal the full process.
The team gathered input through more than 50 interviews, 12 focus group meetings and 75 open or department meetings. It also presented preliminary findings at an open house, where students could respond to the issues under consideration. These activities served two purposes: they helped the team build its understanding of the current state, and they gave stakeholders a chance to challenge or clarify early conclusions.
In industrial settings, the comparable lesson is to include the people who use, operate and support a process. Operators, maintenance teams, engineering, planning and management may see different parts of the same workflow. Bringing those perspectives together can help a redesign team identify where its picture is incomplete before it recommends changes.
Use explicit criteria to prioritize process redesign
Not every process can be redesigned at once. MIT’s team assessed candidate areas against several criteria, including importance to students, dissatisfaction, alignment with the educational mission, cross-functional interaction, ease of implementation, cost and volume. These criteria provided a structured basis for deciding where a redesign effort could be most useful.
For technical decision-makers, the specific criteria will depend on the operation. The value of the method is that priorities are made visible rather than left to intuition alone. A team can define which factors matter, compare processes against them and explain why some areas move forward before others. That can help align sponsors and stakeholders around the scope of the work.
Criteria also make trade-offs easier to discuss. A process may be important but difficult to change; another may have widespread impact but involve several functions. By considering these dimensions together, a team can distinguish between areas suited to immediate redesign and those that may require more investigation or a different kind of intervention.
Match the intervention to the problem
The assessment did not recommend the same response for every process. Four areas were identified for redesign: co-curricular support, career assistance, orientation and educational program support. Other processes—including supplies, housing and personal support—were recommended for a different set of changes, such as reorganization or training.
This distinction is a practical reminder that process improvement does not always mean rebuilding a workflow from the ground up. Sometimes the issue may call for clearer coordination, better-defined responsibilities or additional training. A redesign team should first understand the problem it is trying to solve, then choose an intervention that fits.
The proposed changes to housing illustrate how organizational structure can affect service delivery. The team recommended combining the Offices of Housing and Residential Life, then bringing most housing management under the Physical Plant’s purview. For personal support, it proposed senior-level coordinators to organize, train and support service providers across offices and information dissemination. These were recommendations, not reported outcomes, and they reflect the assessment team’s proposed responses to the processes it reviewed.
Separate recommendations from implementation
At the time described, the team was preparing recommendations for a steering committee, with delivery planned for March 12. Its report was expected to detail proposed changes to student services, the structure of future redesign teams and the project schedule. The distinction between assessment and implementation is important: recommendations can define direction, but execution requires further decisions, ownership and planning.
Stakeholder feedback was also intended to guide future redesign teams by identifying where additional work and input were needed. That creates a continuing feedback loop rather than treating consultation as a one-time event. In an industrial process improvement program, the same principle supports more informed decisions as a project moves from initial assessment into detailed design and implementation planning.
Early proposals should be presented as provisional when they are still being developed. At MIT, team members emphasized that the ideas shown to students were preliminary and that feedback was needed to determine what would work. This helps set realistic expectations: consultation can shape recommendations, but it does not mean every suggestion has already been approved or that implementation is complete.
Practical implications for technical leaders
The MIT example points to a disciplined sequence for complex service and process improvement:
- Map the scope: Identify the services, functions and handoffs that make up the process under review.
- Gather multiple perspectives: Use interviews, group discussions and open forums to understand different experiences of the same process.
- Set prioritization criteria: Make the factors used to select redesign candidates clear and relevant to the organization.
- Choose an appropriate response: Distinguish processes that need redesign from those better addressed through coordination, reorganization or training.
- Plan for continued input: Use feedback to refine recommendations and guide the next stages of work.
For plant managers, system integrators and operations leaders, the central takeaway is that process redesign begins with a credible understanding of current work. Structured assessment and stakeholder engagement can help teams define the problem, set priorities and select a suitable intervention. Clear recommendations are only one stage of the effort; effective change also depends on planning the next steps and maintaining a channel for informed feedback.