Change & Transform · the team
A large initiative — an ERP implementation, an acquisition integration, a plant consolidation — is carried for eighteen to thirty-six months by people who still hold their day jobs. The program does not fail because the software is wrong. It fails when the team runs out of energy in month fourteen and no one designed for it. Team structure and recognition are architecture, not morale extras: they are chartered at Frame and governed to closeout, and they include the families who absorb the late nights.
The structure
Named individual · one seat, never a committee
Owns the business case and the decisions no one else can make. Present at every gate review, visible to the whole organization, and personally signs the recognition — appreciation from a sponsor carries weight that a program office cannot manufacture.
Monthly · five to seven executives
Clears cross-functional barriers, arbitrates scope and protects the team's released capacity. Reviews team health and attrition risk alongside schedule and budget in the same pack.
Full-time · backfilled day job
Runs the value stream day to day. Full-time means full-time; a part-time program lead is the single most common structural cause of an ERP slipping a year.
50–80% released · one per end-to-end process
Own the future-state design for order-to-cash, procure-to-pay, plan-to-produce, record-to-report and hire-to-retire. They are accountable for the design after go-live, which is why they must be the organization's best people, not its most available.
10–15% released · one per 15–25 affected people
Respected practitioners, not volunteers or communicators. They carry Desire and Reinforcement into their own areas, surface resistance early, and are the primary population the recognition architecture is built for.
20–30% released during Activate and Stabilize
Trained ahead of the wave, they sit at the elbow during cutover and hold the new standard work afterwards. Named in writing and celebrated by name at go-live.
Full-time on large programs
Runs one message architecture across all audiences — board, executive, manager, frontline — and owns the family-facing communication as a first-class channel rather than an afterthought.
Recognized as a stakeholder group, in the plan
Spouses, partners, parents and children absorb the missed dinners and the weekend cutover. Naming them as a stakeholder group — and writing to them — converts household strain into household pride.
The recognition architecture
Each is attached to a point in the value stream, and each carries the way it fails when it is treated as an event rather than architecture.
The team names itself, agrees how it will work, and is announced by the sponsor with the released capacity stated in public. Identity is created deliberately on day one — a badge, a color, a team name on the program room door.
One full day off-site: the business case in the sponsor's own words, the future state, and structured work on how this specific group will make decisions and disagree well. Half the day is the work; half is the relationships that will carry the disagreements later.
Each gate passed is marked the week it happens — a sponsor briefing that names contributors individually, a shared meal, a milestone coin or pin added to the set. Recognition is tied to evidence the gate was met, never to effort alone.
A short letter, signed by the CEO or executive sponsor and sent to the home address, naming the individual, describing what they are building and thanking the family directly for the evenings and weekends they have absorbed. Physical mail, on letterhead, addressed to the household — not an email forwarded to a work inbox. Paired with a small household gift at cutover: a restaurant card, a family day out, or tickets.
Families come in on a Saturday, see the program room, watch a five-minute demonstration of what their person built, and meet the sponsor. Children see where the late nights went. It costs very little and is the single most durable morale investment on a long program.
A monthly rhythm that surfaces the people carrying adoption in their own areas: a peer-nominated recognition, named mention in the program update, and a short call from the sponsor. Adoption work is invisible by nature, so it must be made visible on purpose.
Food, visible executive presence through the night, and a named thank-you to every person who worked the weekend — including the operators, the schedulers and the finance staff who closed the books twice. Recognition on the floor, at the hour of the work.
A single formal evening after benefits are demonstrable, with partners and spouses invited. Categories are decided in advance and tied to the program's own values — 'held the standard', 'made the hard call', 'taught the most people'. Awards are handed over by the sponsor, and the citation names the specific act, not the general contribution.
Every full-time team member has a written landing role agreed before the team stands down, with the program experience recorded in their development plan. The reputational question the next program will be judged on is simple: what happened to the last team afterwards?
Not sure where to start?
Under a minute. From this page, most leaders begin with The organization.
