01
Step one: choose a pilot and define success
Select one team with a real deliverable, a willing sponsor and access to its customers or stakeholders. Avoid choosing the easiest or the most troubled group. Write three observable success signals before starting, such as shorter time from request to release, fewer surprise requests mid-cycle, and stakeholders who can see progress without a meeting. Example: a finance operations group of eight people handling reporting requests picks a six-week trial. Baseline how long requests currently take, who prioritizes them, and where work waits. Without that starting record, later improvements will be anecdotal and hard to defend to skeptical colleagues.
02
Step two: set rhythms before adding vocabulary
In days thirty to sixty, install a small number of routines and delay terminology. The example finance team begins with a visible request board, a weekly planning conversation with the requesting departments, a short daily check-in, and a review at the end of each two-week cycle. Roles are described by responsibility, such as who orders the requests, rather than by borrowed titles. Coaches should observe how decisions are made and adjust one routine at a time. This keeps the change understandable, lets people propose modifications, and prevents the pilot from feeling like a compliance exercise handed down from elsewhere.
03
Step three: review evidence and decide the next wave
Around day seventy-five, compare the pilot against the baseline and gather comments from team members and requesters. The finance example might find cycle time improved but priorities still disputed between two departments. That finding shapes the next decision: refine the pilot, add a second team, or train managers first. Present results with limits stated plainly, then publish a one-page plan for days ninety onward covering scope, coaching support, and what will be stopped. A modest, honest review earns more trust than a polished claim, and it gives sponsors a concrete choice to approve.