Setting Up Your Pillar
A pillar without a plan is a good intention. This guide takes you from forming a team to running a 90-day plan, and connecting everything back to the site's strategic objectives.
A pillar is not a project. It does not have a launch date and a close-out report. It has a team, a rolling plan, and a set of capabilities it is building, in sequence, for as long as the site is running.
That means the work of setting up a pillar is not a one-time event. It is the first iteration of a cycle that will repeat every year, every quarter, and every 90 days. The steps below build the foundation for that cycle. Work through them in order. Each one depends on the one before it.
Step 1 — Identify your team
The pillar team is not the function that owns the pillar's subject matter. A Maintenance pillar team made up entirely of maintenance technicians is not a pillar team. It is a department meeting with a different name.
A pillar team is cross-functional. It includes the people who own the losses the pillar is responsible for addressing, and the people whose work is affected by those losses. For most pillars, that means operations, maintenance, quality, and planning all have a seat at the table, even if the pillar belongs to one of them.
The team will change. That is expected. People move roles. New capability is needed at different phases. The team that sets up the pillar in Phase 1 will not look the same as the team that runs it in Phase 3. Design it for where you are now, not where you want to be.
To identify your team, answer three questions:
- Who owns the losses this pillar is accountable for? They must be in the room.
- Who is affected by those losses every day? They should be in the room.
- Who has the capability the pillar needs to build right now? They need to be in the room.
Keep the team small enough to make decisions and large enough to represent the work. Five to eight people is usually right for Phase 1. The team grows as the pillar grows.
One person is the pillar owner for the site. They are accountable for the pillar's progress. They chair the pillar meetings. They own the plan. They are the named person when the site leader asks how the pillar is doing.
Step 2 — Draft your team charter
The charter is a short document that makes the team's purpose, structure, and way of working explicit. It is not a bureaucratic requirement. It is the agreement that stops the team from spending the first six months arguing about what they are supposed to be doing.
A pillar charter covers five things:
Description. What is this pillar responsible for? One or two sentences. Not a mission statement. A clear description of the losses the pillar owns and the capability it is building. This will be phase dependant.
Deliverables. What will the pillar produce? Not activities. Outputs. A completed capability matrix. A validated standard. A confirmed process. A phase assessment passed. Deliverables are things you can point to and say: done.
Success criteria. How will you know the pillar is working? These should be measurable. Defect rate. Schedule adherence. Number of completed investigations. Capability level across the team. The criteria should connect directly to the losses the pillar owns.
Team structure and process ownership. Who is on the team, in what role, with what accountability? The process owners are named. The pillar team members are listed with their function and their specific responsibility within the pillar. This is not a hierarchy. It is a clarity document.
Meeting structure and cadence. When does the pillar team meet, for how long, and to review what? A pillar that does not have a regular meeting is a pillar that is not running. The cadence should be frequent enough to track progress and catch problems early. Monthly is the minimum. Fortnightly is better in Phase 1.
The charter is a living document. Review it at each phase transition. What the team needs to be in Phase 1 is not what it needs to be in Phase 3.
Step 3 — Build your capability matrix
Before you can plan what the pillar will do, you need to know what the team can do.
The capability matrix maps the processes, tools, and skills the pillar requires against the people in the team. For each capability, each person is assessed at one of four levels:
- Not required — this capability is not part of this person's role in the pillar
- Not yet trained — the capability is required but has not been developed
- Trained — the person can run this process or use this tool with support
- Trainer — the person can run this process independently and develop others in it
The matrix does two things. First, it shows you where the gaps are, the capabilities the pillar needs that nobody on the team currently holds. Second, it shows you where the risk is, the capabilities that are held by only one person, and that the pillar would lose if that person moved on.
The matrix is not a training record. It is a planning tool. It tells you what capability needs to be built, in whom, and by when, to deliver the pillar's plan at each phase.
How to build it:
- List the processes, tools, and skills the pillar requires. Use the Pillar Owned Capabilities section of your pillar page as the starting point.
- List the people in the pillar team across the top.
- For each person, assess their current level against each capability. Be honest. A team that inflates its capability assessment will build a plan it cannot deliver.
- Identify the gaps. Which capabilities are missing entirely? Which are held by only one person?
- Use the gaps to inform your roadmap and your annual plan.
The matrix is updated at each phase transition and whenever the team changes. It is the live picture of where the pillar's capability sits.
Step 4 — Understand the site objectives and your part in delivering them
A pillar that does not know what the site is trying to achieve is a pillar that is improving the wrong things.
Before the pillar team develops its own objectives, it needs to understand the site's strategic objectives, what the site is accountable for delivering, over what horizon, and how success is measured. This is not a passive exercise. The pillar team needs to read the site objectives, understand them, and then ask a specific question: which of these objectives does this pillar directly affect?
For most pillars, the answer is clear. A Maintenance pillar affects equipment availability, which affects output, which affects customer service and cost. A Quality pillar affects defect rate, which affects rework cost, customer complaints, and release lead time. A Planning pillar affects schedule adherence, which affects inventory, customer service, and working capital.
The connection between the pillar's work and the site's objectives is not assumed. It is made explicit, in writing, before the pillar's own objectives are set.
To complete this step:
- Obtain the site's current strategic objectives. If they are not documented, that is the first problem to raise.
- For each site objective, identify whether this pillar has a direct, indirect, or no connection to it.
- For the objectives where the connection is direct, identify the specific losses the pillar owns that are affecting that objective today.
- Document the connection. This becomes the foundation for Step 5.
Step 5 — Develop your pillar objectives and goals
The pillar's objectives are a cascade from the site's objectives. They are not invented independently. They are derived from the site objectives the pillar directly affects, translated into the specific measures the pillar owns.
A pillar objective answers the question: what does this pillar need to deliver, in measurable terms, to support the site's objectives?
A pillar goal answers the question: what does success look like at a specific point in time?
The structure is the same as the site's objective-setting process:
- Objective — the direction. What are we trying to achieve? (e.g. Eliminate unplanned equipment downtime as a cause of schedule failure)
- Goal — the measurable target. By when, by how much? (e.g. Reduce unplanned downtime from 8% to 4% by end of Phase 2)
- Strategy — how will we get there? (e.g. Implement Breakdown Elimination on the top three recurring failure modes; complete Equipment Ranking to prioritise planned maintenance)
Keep the number of objectives small. Two or three objectives per pillar is enough for Phase 1. A pillar with seven objectives has not prioritised. It has listed everything it could think of and called it a plan.
Step 6 — Develop your site-specific roadmap
The roadmap is the visual picture of how the pillar builds capability over time, from where it is now to where it needs to be at the end of each phase.
It is not a Gantt chart. It is not a list of activities. It is a picture of the journey, what the pillar looks like at each phase, what capabilities exist, what the operation can do that it could not do before, and what that means for the losses the pillar owns.
The roadmap is built around the three phases of the system:
Establish — the minimum system. The team is formed. The charter is agreed. The capability matrix is built. The first processes are defined and running in the pilot area. The losses are visible and being addressed. The phase ends when the foundations are stable enough to build on.
Strengthen — the system deepens and widens. More people hold the capability. More processes are running. The pillar begins to connect to the other pillars. The losses are reducing. The phase ends when the capability is embedded broadly enough to sustain without central support.
Sustain — the system runs. The processes are confirmed. The capability is assessed and refreshed. The losses are at or near zero in the areas where the pillar is fully established. The pillar is not a programme. It is how the site runs.
The roadmap shows what changes at each phase, in the processes, in the people, and in the results. It is specific to the site. A roadmap that could apply to any site is not a roadmap. It is a template.
To build your roadmap:
- Start with the current state. What does the pillar look like today? What processes exist? What capability is in place? What are the losses?
- Define the end of Phase 1. What must be true for the pillar to pass the Phase 1 assessment? Be specific.
- Define the end of Phase 2. What must be true for the pillar to pass the Phase 2 assessment?
- Define the end of Phase 3. What does the pillar look like when it is fully embedded?
- Draw the journey. The roadmap is a visual, not a table. It should be readable at a glance.
Step 7 — Develop your 3-year master plan
The 3-year master plan translates the roadmap into a structured plan with objectives, goals, strategies, and milestones across a three-year horizon.
The structure is:
Objective | Goal | Strategy | Year 1 | Year 2 | Year 3 |
|---|---|---|---|---|---|
What the pillar is trying to achieve | The measurable target | How it will be achieved | Key milestones | Key milestones | Key milestones |
The 3-year plan is not a detailed activity list. It is a strategic picture. It shows where the pillar is going, how it will get there, and what the key milestones are at each stage. The detail sits in the annual plan.
The 3-year plan is reviewed annually. The first year becomes the annual plan. The second and third years are updated based on what was learned in the first year. The plan is a living document, not a commitment made once and filed.
The 3-year plan must connect to the site's 3-year plan. If the site has a 3-year strategic plan, the pillar's 3-year plan is derived from it. The objectives and goals in the pillar plan should be traceable to the objectives and goals in the site plan. A pillar plan that cannot be connected to the site plan is a plan that is not connected to the strategy.
Step 8 — Develop your annual master plan
The annual plan is the first year of the 3-year plan, broken into quarters and months.
It covers:
- What will be done — the specific processes, standards, investigations, or capability-building activities that will be completed this year
- Who will do it — named owners for each deliverable
- When it will be done — specific dates, not ranges
- How it connects to the pillar objectives — every item in the annual plan should be traceable to a pillar objective. If it is not, ask why it is in the plan.
The annual plan is reviewed monthly. Progress is tracked against the plan. Gaps are identified and owned. The plan is updated when circumstances change, but the objectives do not change unless the site's objectives change.
The annual plan is the primary tool for the pillar's monthly review meeting. The question at every monthly meeting is: are we on track to deliver the annual plan? If not, what is the gap, what is the cause, and what is the response?
Step 9 — Develop your 90-day plan
The 90-day plan is the current quarter of the annual plan, broken into weeks.
It is the most detailed level of planning the pillar runs. It covers:
- What will be done this quarter — specific tasks, not categories
- Who owns each task — one named person per task
- When each task will be complete — a specific date
- What is at risk — tasks that are behind, blocked, or dependent on something outside the pillar's control
The 90-day plan is reviewed weekly or fortnightly in the pillar team meeting. It is the working document the team uses to manage its own progress. It is not a reporting tool. It is a planning tool.
At the end of each quarter, the 90-day plan is reviewed in full. What was completed? What was not? What caused the gaps? The next 90-day plan is built from the next quarter of the annual plan, updated based on what was learned.
Step 10 — Track adherence, show your gaps, and escalate when needed
A plan that is not tracked is not a plan. It is a list of intentions.
Tracking adherence means comparing what was planned to what was done, at every level, 90-day, annual, and 3-year, and making the gaps visible.
What to track:
- Plan adherence — what percentage of planned tasks were completed on time? A pillar running at 60% adherence is not delivering its plan. The question is why.
- Gap classification — when a task is not completed, classify the reason. Was it a resource constraint? A dependency that was not met? A task that was underestimated? A priority that changed? The classification tells you whether the plan needs to change or the execution needs to change.
- Impact on objectives — can the pillar still deliver its objectives for the year, given the current gaps? This is the most important question. A gap in a task that does not affect the objective is a planning issue. A gap in a task that puts the objective at risk is an escalation.
When to escalate:
Escalate when the gap cannot be closed within the pillar's own resources and authority. Not every gap requires escalation. Most gaps can be managed within the team. But when a gap puts a pillar objective at risk and therefore the site objectives at risk, and the pillar team cannot close it without additional resource, a decision from above, or a change to the site plan, that is an escalation.
Escalation is not a failure. It is the system working. A pillar that never escalates is either running perfectly, which is unlikely, or is managing gaps quietly rather than surfacing them. The second is a problem.
The escalation should include:
- What was planned
- What has happened
- The gap and its cause
- The impact on the pillar objective
- What the pillar team has already tried
- What is needed from the escalation, a decision, a resource, a change to the plan
How the steps connect
The ten steps are not independent. They form a cycle that repeats.
The team and charter (Steps 1–2) are the foundation. The capability matrix (Step 3) tells you what you have to work with. The objectives (Steps 4–5) tell you where you are going. The roadmap and plans (Steps 6–9) tell you how you will get there. The tracking (Step 10) tells you whether you are on track and what to do when you are not.
At the end of each phase, you return to the beginning. The team is reviewed. The charter is updated. The capability matrix is refreshed. The objectives are confirmed against the site's updated objectives. The roadmap is updated. The next phase plan is built.
This is not a setup exercise. It is how the pillar runs.
Key links
The pillar structure this guide supports is explained in full on the Pillars page.
The capability matrix in Step 3 is a tool owned by the Organisational Capability pillar. The guide for building and maintaining it is here.
The site objectives that the pillar plan is built around are developed using the Strategic Objectives guides.
The phase assessments that gate the transition between Establish, Strengthen, and Sustain are explained in The System.