Slow Thinking. Fast Execution.

Guest Author: Minnu Paul, Director of Global Education

Organizations today are under constant pressure to move faster. Technology continues to evolve, student expectations change, regulations shift, and institutions are expected to adapt while maintaining day-to-day operations. In these environments, leaders can easily begin to equate speed with effectiveness: decisions must be made quickly, problems solved immediately, and results delivered without delay.

Over time, however, I have come to believe that one of leadership's greatest paradoxes is this: organizations often need to move quickly, but leaders need to think deliberately. The challenge is not slowing the organization down. It is creating enough space for deliberate thinking while the organization continues to move.

I experienced this most clearly when I transitioned into the role of Director of Enrollment Operations. Until then, much of my leadership experience had been within Global Education, where I learned how to redesign work, develop people, improve processes, and create organizational capacity in a smaller setting. This new role became an opportunity to test whether those principles could scale across a much larger and more complex operation.

The transformation touched nearly every part of enrollment operations. Within less than a year, our team transitioned to a new student information system, implemented an AI-powered CRM, redesigned admissions operations, reviewed admissions policies, hired eleven new staff members, cross-trained and reassigned responsibilities among existing staff, trained three adjacent departments on new processes, coordinated communication across campus, and continued supporting undergraduate enrollment across traditional, online, military, transfer, and adult learner populations.

None of the daily work paused while this transformation was taking place. Applications still had to be processed, students still expected timely decisions, and enrollment goals still had to be met.

What surprised me most was not the amount of work. It was realizing that the greatest risk was not moving too slowly—it was moving quickly toward the wrong solution.

The difficulty was that we could not separate thinking from execution. There was no period in which we could stop operations, redesign the organization, and then restart. We had to diagnose while operating, design while implementing, and learn while making decisions whose consequences were already unfolding.

That required a different understanding of speed.

The goal was not to make every decision slowly. It was to develop the discernment to understand which decisions required deeper thinking, which required immediate action, and which assumptions needed to be challenged before either occurred.

Slowing Down the Assumption, Not the Decision

Rather than beginning with implementation, we began with understanding. Before configuring workflows in the CRM, we asked whether the existing workflow should exist at all. Before rewriting admissions policies, we considered whether they reflected the kind of student experience we wanted to create. Before redesigning positions, we asked what capabilities the future organization needed instead of simply recreating the past. Before implementing technology, we questioned whether we were improving the work or merely making inefficient processes digital.

This became one of the most important distinctions for me:

Slowing down did not mean delaying decisions. It meant delaying assumptions.

Urgency can make assumptions look like facts. A process exists, so we assume it is necessary. A policy has been in place for years, so we assume there is a good reason for it.

A position becomes vacant, so we assume we need to replace it in exactly the same form. A new technology becomes available, so we assume implementation itself represents improvement.

Deliberate thinking creates enough distance to question those assumptions without allowing reflection to become paralysis.

How I Approach Change

When I am leading significant organizational change, I now find myself returning to several questions.

1. Define the problem before discussing solutions.What problem are we actually trying to solve? Organizations can spend tremendous energy implementing solutions before developing a shared understanding of the problem.

2. Challenge the current state.If we were designing this process today, would we build it the same way? Existing practices should be understood before they are preserved.

3. Design the future before selecting the technology.Technology should enable well-designed work rather than determine how the work is designed. Digitizing a poor process simply creates a digital poor process.

4. Think systemically.What else changes if we change this? A policy can affect technology; technology can change roles; roles affect communication; communication influences the student and staff experience. Decisions that appear local can have organizational consequences.

5. Execute decisively—and continue learning.Deliberate thinking cannot become an excuse for indecision. Once there is sufficient clarity, leaders have to move, communicate, observe what happens, and adjust as new information emerges.

Importantly, I do not see these as five sequential steps. Organizational change rarely unfolds that neatly. During implementation, new information often sends us backward: a technology decision exposes a policy problem, a process change reveals a training need, or feedback from staff challenges an assumption we made earlier.

The discipline is not following a perfect sequence. It is knowing when new information requires us to reconsider an assumption without allowing reconsideration to become paralysis.

Connecting Practice and Scholarship

As I continued my doctoral research, I realized that many of the ideas emerging through practice were also present in scholarship. Different traditions approach the problem differently, but several particularly resonated with my experience:

• Systems Thinking — Peter Senge: Changes within organizations cannot be understood entirely in isolation. This reinforced my instinct to examine the relationships among policy, technology, people, communication, and student experience.

  
  

• Lean Thinking: Improvement begins by understanding how work actually happens rather than how we assume it happens. This supported our decision to examine processes before automating or digitizing them.
  

• Organizational Change — John Kotter: Urgency matters, but urgency alone is insufficient. Sustainable change also requires direction, alignment, communication, and the ability to mobilize people around the change.
  

• Organizational Learning — Chris Argyris and Donald Schön: Organizations need the ability not only to correct problems, but also to question the assumptions, norms, and practices that produced them. This particularly resonated with our willingness to ask not simply, "How can we improve this process?" but sometimes, "Should this process exist at all?"

  
  

The scholarship did not tell me what to do in those moments. It gave me language for experiences I had already lived and helped me understand more deeply why certain approaches worked. Practice exposed the problems; scholarship helped me examine the thinking underneath them.

Looking back, I do not believe our team accomplished so much in less than a year because we simply worked faster. We accomplished it while learning how to think deliberately inside an environment that could not stop moving.

For me, that is what "slow is smooth, and smooth is fast" has come to mean. Slow thinking is not an argument for slow organizations. It is about developing the discipline to question assumptions, understand systems, and create clarity while execution continues around us.

Perhaps the real measure of speed in leadership is not how quickly we make a decision, but how quickly we can move without repeatedly having to undo the decisions we made along the way.