How Do I Keep a Software Rollout from Stalling after Kickoff?

A SaaS implementation stalls after kickoff when the sponsor's attention moves on, the team's regular work comes back, and nothing is scheduled to carry the rollout past the first week or two. Keep one moving by booking the next two touch points, naming an owner inside the account, and putting a date on the first small win, all before the kickoff meeting ends.

A kickoff gives a rollout a week or two of attention. Everything after that has to be set up on purpose.

Why Does a SaaS Implementation Stall after Kickoff?

On kickoff day the sponsor is in the meeting, the product is new, and using it is the point of the day. By week three the sponsor has moved to the next project. The deadlines the team had before you arrived are all still there.

Michael Fullan, who has studied change in schools and other organizations for decades, calls the early stretch of any change the implementation dip. In a 2002 article in Educational Leadership, he describes the first months as bumpy however well they were planned, because people are slower and less sure of themselves in the new way. The team feels the cost of learning before they see the benefit.

When a rollout has nothing on the calendar for week three, the team's regular work fills that week. Other meetings take the time the rollout needed.

What Should Be Booked before the Kickoff Ends?

Book three things while everyone is still in the meeting.

1. The next two touch points. Dates, times, and what each one is for. Agreed in the kickoff, they are part of the plan.
2. The first small win, with a date. One person does one task in the first several days and produces a result someone else can see. Pick it together, name the person, write down the date.
3. The check on behavior. A date, around week three, when you and the owner look at whether the team is doing the work in the new way.

The small win carries the most weight. John Kotter's 1995 Harvard Business Review article on why transformation efforts fail lists skipping short-term wins among the common errors. A result the team can see gives the rollout its own evidence, which makes the next step easier to ask for.

Who inside the Account Has to Own the Rollout?

The owner is a person on the customer's side whose own work depends on the rollout landing. You sit outside their company and can't assign anyone anything, so every push has to come through someone inside.

The sponsor may not be the right owner. They approved the purchase, and their week doesn't change because of it. Look for the manager or team lead who will feel it when the team slides back, and who works alongside the users every day. Name that person in the kickoff and agree on what they are responsible for.

Then name a backup who has seen the plan, in case the owner changes roles.

What if the Customer Won't Name an Owner?

Sometimes the sponsor says everyone owns it, or names themselves and then travels for three weeks. Treat that as the most important finding of the kickoff, because it tells you nobody on their side will notice if the rollout slows down.

Steven Karau and Kipling Williams, in a 1993 review that pooled dozens of studies of group effort, found that people put in less effort on shared tasks than on tasks they do alone, across many kinds of tasks and people. The drop was smaller when each person's contribution could be evaluated. Put one name on the first small win and one on the week-three check, so each person's part can be seen.

Ask a narrower question. Whose team will feel it first if the new process doesn't take? That person may not have a title that sounds like ownership, and they are still the one with a reason to keep it moving.

If nobody fits, ask the sponsor for one person to work alongside you for the first two weeks only. A short, dated commitment is easier to agree to than open-ended ownership. By the end of the two weeks you will know whether that person is the owner, or whether the sponsor needs to hear that the rollout has no one inside carrying it.

What Should Happen in the First Three Weeks after Launch?

Week one. The first small win happens. Confirm it with the owner the day it is due, and make sure the result reaches someone who will notice it, such as the owner's manager or the person who asked for the report.

Week two. The first booked touch. Bring the owner something that makes the next step easier, such as an answer to a question the team raised or the next task set up and ready to try. Ask for nothing in this touch.

Week three. The behavior check. Look at whether the team still does the task the old way. If it is, find out which step of the old process people still rely on and why, and fix that step first.

Marcie Tyre and Wanda Orlikowski, in a 1994 study in Organization Science, followed new process technology into three manufacturing and service organizations. Users explored and adjusted the technology in a brief window after it was introduced. After that, routines set, and problems still open were often built into how the work got done. Later changes came in episodes, set off by a new discovery or an event that exposed a gap.

Prosci's research, summarized by Tim Creasey in a 2018 article on reinforcing change, found that projects which planned their follow-through met their objectives more often than projects that treated go-live as the finish. Booking those three weeks before the kickoff ends is how you plan the follow-through.

Take the next kickoff you have scheduled and add the three bookings to its agenda now, so the meeting can't close without them.

References & Related Reading

• The Change Leader, Michael Fullan, Educational Leadership (ASCD), 2002.
• Leading Change: Why Transformation Efforts Fail, John P. Kotter, Harvard Business Review, 1995.
• The 8-Step Process for Leading Change, Kotter Inc., current page.
• Social Loafing: A Meta-Analytic Review and Theoretical Integration, Steven J. Karau and Kipling D. Williams, Journal of Personality and Social Psychology, 1993.
• Windows of Opportunity: Temporal Patterns of Technological Adaptation in Organizations, Marcie J. Tyre and Wanda J. Orlikowski, Organization Science, 1994.
• Reinforcement and Sustaining Change Management, Tim Creasey, Prosci, 2018 (updated 2026).
• How to Avoid a False Start When You're Leading a Big Change, Timothy R. Clark, Harvard Business Review, 2026.