Lean-Agile Center of Excellence (LACE): How to Establish One

A lean agile center of excellence, commonly written as LACE, is a small, dedicated team that drives an organization's shift to SAFe. It is not a compliance office. It is a guiding coalition that builds capability, coaches leaders, and keeps the transformation on track. Most LACE teams start with 3 to 12 people, depending on organization size.

A LACE typically reports into senior leadership and works closely with the Agile PMO, Release Train Engineers, and Communities of Practice. It is strongly recommended in SAFe, though not strictly mandatory. Organizations that skip it often struggle to sustain change beyond the first few months.

Key Highlights of Lean-Agile Center of Excellence (LACE)

• A LACE is a small, dedicated cross-functional team (typically 3-12 people) that drives and sustains an organization's SAFe transformation, acting as a guiding coalition rather than a compliance or auditing office.
• It owns five core areas: communicating the change vision, managing the transformation roadmap and backlog, coordinating training and coaching, supporting value stream identification and ART launches, and tracking progress through metrics.
• Building a LACE follows seven steps: securing executive sponsorship, defining the mission, selecting the initial team, assigning clear roles, creating a charter, launching Communities of Practice, and then scaling the transformation.
• Three structural models exist: centralized (best for single, tightly integrated organizations), decentralized (best for independent business units), and hub and spoke (best for large enterprises and Global Capability Centers needing both consistency and local relevance).
• The first 90 days follow a phased approach: days 1 to 30 focus on assessment and charter creation, days 31 to 60 on capability building and launch preparation, and days 61 to 90 on measuring results and planning to scale.
• A LACE differs from an Agile PMO in that the LACE creates and drives the transformation itself, while the Agile PMO operationalizes the new way of working permanently once the transformation matures, with LACE responsibilities often transferring over time.

Agile transformations rarely fail because teams do not want to change. They fail because nobody owns the change itself.

A single Scrum team can adopt Agile practices on its own. An entire enterprise cannot. When hundreds of people across different departments, locations, and reporting lines need to shift how they work, someone has to hold the transformation together. That is the job of the Lean-Agile Center of Excellence, commonly known as LACE.

This guide explains what a LACE is, why it matters, and how to build one from the ground up. It covers LACE roles and responsibilities, charter design, structural models, and the first 90 days of standing one up. It also compares LACE with an Agile PMO, a question that comes up in almost every SAFe transformation.

If you are a transformation leader, an SPC, a Release Train Engineer, or someone tasked with scaling agile practices across your organization, this article will give you a practical roadmap grounded in how SAFe actually recommends building this capability.

What is a Lean-Agile Center of Excellence (LACE)?

The core job of LACE is to turn transformation intent into daily practice across the enterprise, serving as the third and final piece of what Scaled Agile, Inc. calls a "sufficiently powerful guiding coalition," a concept borrowed from change management expert John Kotter.

LACE Meaning in SAFe

A Lean-Agile Center of Excellence is a small, dedicated team responsible for guiding an organization's adoption of Lean-Agile practices under the Scaled Agile Framework. When people search for what LACE SAFe actually means, the short answer is that it is the internal engine that turns transformation intent into daily habits, rather than a policy or a slide deck. It is defined in SAFe as one of the earliest and most important steps in theSAFe implementation roadmap.

The LACE is not a governance body that enforces rules from a distance. It behaves more like an Agile team itself. It has a mission, a backlog, and a set of stakeholders it serves. Its job is to turn transformation intent into daily practice across the enterprise.

Scaled Agile, Inc. positions the LACE as the third and final piece of a "sufficiently powerful guiding coalition," a concept borrowed from change management expert John Kotter. The first two pieces are training Lean-Agile change agents as SAFe Practice Consultants (SPCs) and training executives and managers on the framework. The LACE brings these efforts together into one accountable team.

What Does a Lean-Agile Center of Excellence Do?

A LACE typically owns five broad areas of work:

1. Communicating the business need, urgency, and vision for change across the organization
2. Developing and managing the SAFe implementation roadmap and transformation backlog
3. Coordinating training and coaching for executives, teams, Product Owners, Scrum Masters, and Release Train Engineers
4. Facilitating value stream identification and supporting Agile Release Train (ART) launches
5. Establishing metrics to track progress and sustaining the change over time

In practice, this means a LACE might run a workshop with executives one week, help a new ART prepare for its first PI Planning event the next, and publish a transformation dashboard the week after that. It works across every level of the organization, from portfolio strategy to team-level execution.

Why Organizations Create a LACE?

Most organizations that skip building a LACE run into the same problem. Individual teams adopt Agile ceremonies, but the organization as a whole never actually changes. Leadership sends mixed signals, training happens once and is never reinforced, and momentum fades within two or three quarters.

A LACE solves this by giving the transformation a permanent home. It keeps the effort visible, coordinated, and accountable to outcomes rather than to a one-time rollout event. It also gives people a place to bring problems when Agile practices collide with existing processes, budgeting cycles, or org structures.

A Lean-Agile transformation touches culture, structure, and process at the same time, it needs a team that can operate across all three. That is precisely the role the LACE is designed to play.

LACE vs Agile PMO

This is one of the most common points of confusion in SAFe adoptions, and it deserves a clear answer.

A traditional Project Management Office focuses on schedules, budgets, resource allocation, and status reporting for projects. An Agile PMO evolves this role. It shifts from auditing compliance to enabling delivery, and it often works closely with Lean Portfolio Management to support value stream funding and program execution.

A LACE is different in scope and intent. It is focused specifically on driving and sustaining the Lean-Agile transformation itself. It is not there to manage day-to-day project delivery. It exists to change how the organization thinks and works, and to build the capability that eventually allows the Agile PMO, Release Train Engineers, and Communities of Practice to run this new way of working sustainably.

A simple way to frame the agile pmo vs lace difference: the Agile PMO operationalizes the new way of working. The LACE creates it. The lace vs agile pmo differences become clearer once you look at their time horizons. 

A LACE is usually a temporary or evolving structure tied to the active phase of transformation, while an Agile PMO is a permanent operating function that continues long after the transformation itself is considered complete. Many organizations eventually see the 

LACE's responsibilities gradually pass into the Agile PMO and Communities of Practice as the transformation matures, at which point the LACE either evolves into a smaller advisory function or is retired altogether.

How to Establish a Lean-Agile Center of Excellence?

Building a LACE is not a single meeting or a policy document, it is a structured, sequential effort. If you are wondering how to build a LACE that actually sticks, the answer lies less in the framework itself and more in sequencing: sponsorship before structure, structure before scale. 

Here is a practical seven-step process that mirrors how SAFe recommends approaching this work.

Step 1: Build Executive Sponsorship and a Guiding Coalition

No LACE succeeds without visible executive backing. Before anything else, identify a senior leader, ideally someone at the C-level or a direct report to the C-suite, who will act as the transformation sponsor. This person needs to understand the change well enough to defend it publicly and to remove organizational barriers when they appear.

This is the guiding coalition change management principle at work. Kotter's research on organizational change shows that transformations led by a small group of influential people, rather than a single champion, are far more likely to survive setbacks. A single champion can be reassigned, promoted out of the role, or simply lose enthusiasm after a difficult quarter. A coalition spreads that risk across several people, so the transformation keeps moving even if one supporter steps back.

Your coalition should include the executive sponsor, one or two senior operational leaders, and the SAFe Practice Consultants who will do the hands-on coaching. Take time to genuinely test their commitment before finalizing the group. Ask each person what they are personally willing to change about how they work, not just what they expect from others. Coalitions built on shared talking points but no real behavioral change tend to fall apart the first time the transformation asks something difficult of a senior leader.

Step 2: Define the LACE Mission and Transformation Goals

Once sponsorship is secured, define why the LACE exists and what it is trying to achieve. This should tie directly to business outcomes, not just Agile maturity for its own sake. Common goals include faster time to market, improved predictability, better cross-team collaboration, or stronger alignment between strategy and execution.

Write this mission down in plain language. Avoid vague statements like "become more agile." Instead, aim for something specific, such as "reduce feature delivery time from six months to eight weeks within 18 months while improving release predictability."

Step 3: Select the Initial LACE Team

Keep the initial team small. Most guidance suggests starting with three to five people for a first pilot, scaling based on the size of the organization. A useful benchmark: organizations with roughly 100 Agile practitioners often run a LACE of four to six people, while organizations closer to 200 or more practitioners may need ten to twelve.

Look for a mix of skills and credibility. You want people who understand SAFe deeply, people who are respected across departments, and at least one person with enough seniority to speak for leadership. This diversity is what allows the LACE to operate credibly at both the portfolio and team level.

Step 4: Define LACE Roles and Responsibilities

Every member of the LACE needs a clear role. Ambiguity here is one of the most common reasons transformations stall. Typical LACE roles include a facilitator similar to a Scrum Master, a prioritization owner similar to a Product Owner, one or more SAFe Practice Consultants providing coaching, and representatives from HR, Finance, and business units who can address non-technology barriers to change.

We cover this in more depth in the dedicated section on lace roles and responsibilities later in this guide.

Step 5: Create a LACE Charter

A charter formalizes the mission, scope, roles, and success measures into a single reference document. It becomes the anchor the team returns to whenever priorities get murky or new stakeholders ask what the LACE actually does. We dedicate a full section below to what a strong LACE charter should include.

Step 6: Establish Communities of Practice

Communities of Practice, or CoPs, are groups of practitioners across the organization who share a common domain, such as Scrum Mastery, Product Management, or DevOps engineering. They meet regularly to share lessons, solve shared problems, and spread good practice organically.

Communities of practice agile groups are one of the most effective ways to make a transformation self-sustaining. Rather than relying entirely on the LACE to push change downward, CoPs let practitioners pull knowledge across the organization horizontally. A LACE should help launch these communities early, even before the full transformation is underway.

Step 7: Launch and Scale Lean-Agile Transformation

With the mission set, the team assembled, roles defined, and the charter published, the LACE moves into execution. This usually starts with identifying value streams, preparing for the first Agile Release Train launch, and coaching that first cohort of teams intensively. Once the first ART shows results, the LACE uses those lessons to launch additional trains and expand the lean agile transformation to other parts of the business.

Lean-Agile Center of Excellence Structure: Which Model Is Right?

There is no single correct structure for a LACE. The right model depends on how the organization is set up, how many business units are involved, and how mature the transformation already is.

1. Centralized LACE Model

In a centralized model, one LACE serves the entire organization under a single SAFe portfolio. Funding, coaching resources, and decision-making are consolidated in one team. This model works well for organizations with a single business line or a tightly integrated technology organization.

The advantage is consistency. Everyone hears the same message, follows the same roadmap, and uses the same metrics. The drawback is that a centralized LACE can struggle to stay close to the specific challenges of distant business units, especially in large or geographically spread organizations.

2. Decentralized LACE Model

In a decentralized model, each business unit or portfolio runs its own LACE with its own funding and priorities. This model suits organizations where business units operate independently, with different customers, different technology stacks, or different regulatory requirements.

The advantage is relevance. Each LACE can tailor its coaching and roadmap to local realities. The drawback is fragmentation. Without deliberate coordination, business units can end up interpreting SAFe differently, which makes it harder to compare progress or share best practices across the enterprise.

3. Hub-and-Spoke LACE Model

The hub-and-spoke model tries to combine the benefits of both. A smaller central "hub" LACE develops overarching messaging, foundational practices, and shared tooling. Individual "spoke" LACEs then adapt these to their local business unit while staying aligned to the central vision.

This model is popular among large enterprises and Global Capability Centers because it balances consistency with the flexibility that different regions or business functions need. The hub also becomes the mechanism for spreading success patterns from one part of the organization to another, without forcing every unit into an identical playbook.

Centralized vs Decentralized vs Hub-and-Spoke LACE

The centralized vs decentralized agile question is not about which model is objectively better. It is about matching structure to organizational reality. Many enterprises that start centralized eventually shift toward hub-and-spoke as the transformation scales beyond the first few value streams. 
LACE Roles and Responsibilities

A LACE only works when everyone involved understands their part clearly. Here is how responsibilities typically break down across the roles most commonly seen in a functioning LACE.

Executive Sponsor and Transformation Leadership

The executive sponsor provides air cover for the transformation. This person removes structural barriers, secures funding, and models the behavior change expected of the rest of the organization. Without this role filled by someone credible, LACE recommendations often get ignored the moment they conflict with existing incentives or reporting structures.

SAFe Practice Consultant and Agile Coaches

The SAFe Practice Consultant certification prepares professionals to lead SAFe implementations, train teams, and coach leadership through the change. A safe practice consultant is often the most technically knowledgeable person inside the LACE, responsible for designing the training curriculum, coaching Release Train Engineers, and helping identify value streams. Agile coaches supplement this work at the team level, helping individual Scrum teams adopt new practices day to day.

Release Train Engineer and LACE Collaboration

The Release Train Engineer, or RTE, runs the Agile Release Train once it launches. Release train engineer collaboration with the LACE is essential during the early stages of a transformation, since the LACE typically supports the RTE through the first few Program Increments before stepping back. During this handoff period, the LACE often sits in on PI Planning and Inspect and Adapt events, not to run them, but to observe where teams are struggling and where coaching needs to be reinforced.

The LACE also relies on RTE feedback to understand where training gaps or process friction are showing up in real ART execution, which shapes the ongoing transformation backlog. This feedback loop matters because it keeps the LACE grounded in what is actually happening on the ART, rather than relying only on surveys or secondhand reports from managers.

Readers who want a deeper explanation of this role can reviewWhat is an Agile Release Train, which covers how ARTs function inside SAFe.

Change Agents and Communities of Practice

Change agents are practitioners embedded across teams who champion new practices locally. They are often the first people trained as SPCs and are typically the most enthusiastic and credible voices for change within their own departments. Communities of Practice extend this influence further, letting change spread peer to peer rather than only top-down from the LACE.

LACE Leadership, Governance and Decision-Making

Governance inside a LACE should stay lightweight. Decisions about training priorities, coaching allocation, and roadmap sequencing typically rest with the LACE team itself, guided by input from the executive sponsor. Bigger decisions, such as funding additional ARTs or changing organizational structure, usually require sign-off from senior leadership outside the LACE. Keeping this decision boundary clear prevents the LACE from becoming either powerless or overreaching.

LACE Charter: What to Include

A LACE charter is a short, practical document, not a lengthy governance manual. It should be something the team can reference in a single sitting.

LACE Mission Statement

Start with a one or two sentence statement of purpose. This should describe what the LACE exists to do and for whom, tied to a measurable business outcome rather than abstract Agile language.

Transformation Scope and Objectives

Define which parts of the organization are in scope for this phase of the transformation. Most LACE charters intentionally limit scope early on, focusing on one or two value streams before expanding. List the specific objectives for the current phase, such as launching the first ART or completing executive training.

Roles, Responsibilities and Decision Rights

Document who sits on the LACE, what each person is accountable for, and what decisions the LACE can make independently versus what needs escalation. This section prevents the confusion that often derails early-stage LACE teams.

Success Measures and Transformation Metrics

Include the specific safe transformation metrics the LACE will track. These might include Program Increment predictability, employee engagement scores, time to market for key initiatives, or the pace of ART launches. Metrics should be reviewed and adjusted as the transformation matures.

Sample LACE Charter Structure

A practical charter typically follows this structure:

• Mission statement (2 to 3 sentences)
• Sponsoring executive and LACE team roster
• Transformation scope for the current phase
• Key responsibilities, organized by role
• Decision rights and escalation path
• Success metrics and review cadence
• Charter review date, usually every two to three Program Increments

Keeping the charter this concise makes it something people actually read and use, rather than a document that gets filed away after the kickoff meeting. Revisit it at least once every two Program Increments, since a charter that never changes usually means nobody is actually consulting it anymore.

The First 90 Days of Building a LACE

The early months of a LACE set the tone for the entire transformation. A 90 day safe transformation roadmap gives structure to this critical period.

Days 1 to 30: Assess, Align and Define

The first month focuses on groundwork. This includes securing executive sponsorship, assessing current organizational readiness, identifying the first value streams, and defining the LACE mission and charter. By the end of this period, the core LACE team should be selected and trained, and the initial transformation backlog should exist in draft form.

Days 31 to 60: Build Capabilities and Launch

The second month shifts toward action. This is when executive and leadership training happens at scale, the first ART is identified and prepared, and Communities of Practice begin forming. The LACE should also start publishing early communication about the transformation to build organizational awareness ahead of the first PI Planning event.

Days 61 to 90: Measure, Improve and Scale

By the third month, the first ART should be live or very close to launch. The LACE shifts its attention to coaching this initial train through its first Program Increment, collecting early metrics, and documenting lessons learned. This is also when the LACE begins planning how to extend the transformation to a second value stream or business unit.

What a Successful First 90 Days Should Deliver

By day 90, a well-run LACE should have a published charter, a trained and functioning core team, at least one ART either launched or ready to launch, an active set of Communities of Practice, and a baseline set of metrics against which future progress can be measured. Organizations that hit these markers tend to sustain momentum far better than those that spend the first quarter only on planning.

How to Measure LACE Effectiveness?

Measuring a LACE's effectiveness means looking beyond activity metrics like the number of training sessions delivered. SAFe recommends assessing progress across three domains: outcomes, flow, and competency.

Outcome metrics ask whether the transformation is actually improving business results, such as revenue impact, customer satisfaction, or time to market for strategic initiatives. Flow metrics capture how efficiently value moves through the system, including flow velocity, flow time, flow load, flow efficiency, and flow predictability. Competency metrics assess how proficient teams and leaders have become in Lean-Agile practices, often through structured self-assessments.

A well-run LACE tracks a small, balanced set of metrics from each domain rather than trying to measure everything at once. Common examples include Program Increment predictability, employee engagement and Net Promoter Scores tied to internal transformation surveys, escaped defect rates, and the pace at which new value streams and ARTs are successfully launched. These safe transformation metrics should be reviewed regularly, ideally at each Inspect and Adapt event, so the LACE can adjust its coaching focus based on real data rather than assumptions.

LACE and SAFe Implementation at Enterprise Scale

How LACE Supports Agile Release Trains

The relationship between the LACE and an Agile Release Train evolves over time. In the early stages, the LACE is deeply involved, helping identify the value stream, select the initial teams, and coach the Release Train Engineer through the first few Program Increments. As the ART matures and becomes self-sufficient, the LACE steps back into a lighter advisory role, freeing its capacity to support the next ART launch.

LACE and SAFe Implementation Roadmaps

The fullSAFe implementation roadmap includes steps such as reaching a tipping point, training change agents, training leaders, creating the LACE, identifying value streams, preparing for ART launch, and eventually extending the transformation to the full portfolio. The LACE is not just one step in this roadmap. It is the team that actively drives most of the remaining steps once it is chartered.

Extending Lean-Agile Practices Beyond Technology

Mature LACE teams eventually push Lean-Agile thinking beyond the technology organization into functions like marketing, HR, finance, and operations. This extension is often where transformations create the most business value, since these business functions frequently sit on the critical path for approvals, budgeting, and go-to-market execution that technology teams depend on.

LACE Support for Lean Portfolio Management

Lean portfolio management connects strategy to execution through practices like strategic themes, lean budgeting, and portfolio Kanban systems. A LACE typically plays a foundational role in standing up lean portfolio management, often training the Agile PMO and portfolio leadership directly and co-facilitating early portfolio-level events before handing this responsibility over to a permanent portfolio function.

Lean-Agile Center of Excellence Examples

LACE Example for an Indian IT Services Organization

Consider a mid-size Indian IT services company delivering software for global clients. Its LACE might start with five members: an SPC-certified transformation lead, two agile coaches drawn from delivery teams, one HR representative to handle role changes, and a senior delivery director acting as executive sponsor. Given that client engagements often span multiple geographies and time zones, this LACE would likely favor a hub-and-spoke model, with the hub setting shared training standards and each client account team acting as a spoke that adapts practices to individual client contracts and SLAs.

LACE Example for a Global Capability Center

A Global Capability Center supporting a multinational parent company often needs to align local execution with a transformation already underway at the parent organization. In this case, the local LACE frequently functions as a spoke, adopting practices, metrics, and charters largely defined by a central hub LACE at headquarters, while contributing local insights specific to the GCC's talent structure, delivery model, and stakeholder relationships back to the global effort.

LACE Example for a Large Enterprise SAFe Transformation

A large enterprise running multiple product lines across different business units typically needs a more layered structure. A central LACE might set the overall vision, transformation metrics, and SPC training standards, while each business unit runs its own smaller LACE focused on launching and coaching ARTs specific to that unit's products. Over eighteen to twenty-four months, this structure often evolves as business units mature, with some local LACEs shrinking into advisory functions absorbed by the Agile PMO once Lean-Agile practices become embedded in daily operations.

Common LACE Implementation Challenges and How to Solve Them

Lack of Executive Sponsorship

Without a credible executive backing the transformation, a LACE has no authority to remove barriers or challenge existing ways of working. The fix is straightforward but not easy: secure a genuinely engaged sponsor before chartering the LACE, not after problems appear. If sponsorship weakens partway through, address it directly rather than trying to push the transformation forward without it.

Unclear LACE Roles and Responsibilities

When LACE members are unsure what they own, decisions stall and duplicate work becomes common. Revisit the charter, clarify roles explicitly, and make sure every LACE member can describe their responsibilities in a single sentence.

Treating LACE as a Compliance Function

Some organizations turn the LACE into an auditing body that checks whether teams are "doing Agile correctly." This approach kills trust quickly. A LACE should coach and enable, not police. If teams start avoiding the LACE or hiding problems from it, this is usually the underlying cause.

Failing to Measure Transformation Outcomes

Without metrics, a LACE cannot demonstrate value, and leadership support erodes over time. Establish a small set of outcome, flow, and competency metrics early, and review them consistently at Inspect and Adapt events rather than waiting until a formal transformation review.

Scaling Too Quickly Without Building Capability

Launching multiple ARTs before the first one has stabilized often overwhelms a small LACE team and dilutes coaching quality across the board. Resist pressure to scale faster than your coaching capacity allows. A slower, well-supported rollout consistently outperforms a rushed one. If leadership is pushing for faster scaling than the LACE can realistically support, it helps to show them the data: half-coached ARTs tend to regress within two or three Program Increments, which costs more time to fix than a deliberate rollout would have taken in the first place.

LACE and SAFe Certification

Why SAFe Practice Consultants Are Important to LACE

An SPC brings structured knowledge of the entire SAFe implementation roadmap, along with practical experience training teams and coaching leadership through resistance. Because SPCs are trained directly on how to build and run a LACE, they are usually the anchor role inside any newly formed LACE team.

SAFe Certifications Relevant to LACE Teams

Several certifications support the different roles inside a LACE. A SAFe Practice Consultant certification prepares coaches and change agents to lead the transformation itself, covering the full implementation roadmap, coaching techniques, and how to charter and run a LACE from day one. A Leading SAFe certification equips executives, managers, and leaders with the foundational understanding needed to support the change from the top, which matters because leaders who only hear about Agile second hand rarely champion it convincingly. A SAFe Product Owner or Product Manager certification is valuable for LACE members who will help prioritize the transformation backlog or support new Product Owners during ART launches, since backlog discipline is often one of the hardest habits for new teams to build.

Building LACE Capability Through SAFe Training

Certification alone does not create a functioning LACE, but it gives the team a shared vocabulary and a common understanding of SAFe practices before the hard work of organizational change begins. Organizations that invest in training their LACE members properly tend to move through the first 90 days with far fewer missteps than those that assemble a LACE without formal preparation.

Final Takeaway: How to Build a Successful Lean-Agile Center of Excellence

A Lean-Agile Center of Excellence is not a committee, and it is not a compliance office. It is a small, dedicated, cross-functional team that carries the responsibility of turning a Lean-Agile vision into daily practice across an organization.

Building one successfully starts with real executive sponsorship, a clear mission, and a small team with the right mix of credibility and SAFe knowledge. It requires a charter that defines roles and success metrics honestly, a structure that fits your organization rather than a generic template, and a willingness to measure progress and adjust along the way. Most importantly, it requires patience. A LACE that tries to change everything in the first quarter usually accomplishes very little. A LACE that focuses on one value stream, learns from it, and scales deliberately tends to build a transformation that actually lasts.

If your organization is preparing for a SAFe transformation, building the right internal capability matters as much as building the right team structure. Simpliaxis offers a full range of SAFe training programs designed for every role in this journey, including theSAFe Practice Consultant (SPC) Certification for coaches and change agents, theLeading SAFe 6.0 Certification for executives and managers, and theSAFe Product Owner/Product Manager Certification for teams driving backlog priorities.

For organizations looking to train multiple teams together, Simpliaxis also providesCorporate Training Solutions tailored to your transformation timeline and team structure. Explore these programs to give your LACE the foundation it needs to succeed.