Resource management is the planning, scheduling, and tracking of the people, equipment, materials, time, and money a project needs, so the work can actually be done when it is supposed to be. In an improvement program, it is the difference between a kaizen schedule that gets executed and one that keeps slipping because the same three people are on every event, the forklift is never available, and nobody budgeted for floor tape. Most Lean projects fail on resources, not on ideas.
The five resources
- People. Who, with what skills, for how many hours, when. For improvement work, this includes the operators pulled from the line, the maintenance tech, the facilitator, and the manager who has to approve things during the event.
- Equipment. Machines, tools, vehicles, and the floor space itself. A changeover reduction event needs the press; a floor marking project needs the aisle closed; a TPM pilot needs the machine down for a deep clean.
- Materials. Everything consumed: tape, labels, signs, parts, shadow board foam, the whiteboard for the event room.
- Time. Calendar time to the deadline, and the capacity of each person and machine inside it. Time is the resource most often assumed to be free.
- Money. The budget for the four above, and the cost-benefit case that justified it.
Why improvement projects run short
- Nobody counted capacity. A kaizen event takes five people off the floor for a week. If the schedule does not account for it, the event gets cancelled on day two when a rush order lands.
- The same people are on everything. The best operator, the one maintenance tech who knows the line, and the engineer who can draw a layout are on every project. They become the bottleneck and the program runs at their pace.
- Equipment time was not reserved. The project needs the machine for four hours; production needs it for all of them. Without an agreement in advance, production wins.
- Materials were ordered after the start. The team is ready to mark the floor and the tape arrives Thursday.
- Follow-up work was never resourced. The event ends with a list of twelve follow-ups and no hours assigned to them. See scope creep and the 30-day follow-up problem on the kaizen page.
How to manage resources for a project
1. Start from the work breakdown
List the tasks, then for each one write down who does it, how many hours, what equipment and materials it needs, and when it can happen. This is the resource plan; everything else is a view of it. A Gantt chart or a simple timeline with owners is enough for most improvement projects.
2. Check capacity before committing
For each person on the plan, add up their committed hours across every project and their regular job for the weeks in question. Anyone over about 80% of available hours is a risk; anyone over 100% is a plan that will not happen. Do the same for critical equipment. The answer is usually to move dates or drop a project, and it is far cheaper to find that out now.
3. Keep a skills matrix
A grid of people against skills (can run the press, can do changeovers, trained on lockout, can facilitate an event, can print labels, forklift certified), with a mark for trained, qualified, or can train others. It answers two questions fast: who can do this task, and where the single points of failure are. A skills matrix is also the standard TPM training record, so most plants need one anyway.
4. Protect the bottleneck resource
Every program has one resource that everything waits on: a person, a machine, or an approval. Treat it the way a Lean line treats its constraint. Schedule it first, keep it fully used on the highest-value work, and do not let it be consumed by tasks someone else could do. If the maintenance tech is the bottleneck, the kaizen team does its own measuring and marking and uses the tech only for what needs a tech.
5. Level the load
Improvement work tends to arrive in bursts: nothing for a month, then three events in two weeks because a customer audit is coming. Spread events across the calendar so the same people are not pulled repeatedly and the floor is never short-staffed twice in a month. One event per area per quarter, with the follow-up hours scheduled before the next one starts, is a sustainable pace for most plants. This is the same leveling logic Lean applies to production (heijunka), applied to the improvement program.
6. Reserve equipment and order materials up front
Put the machine time on the production schedule as a planned stop, with the same status as a maintenance window. Order consumables when the project is approved, not when the team is ready to use them. For recurring needs (tape, labels, signs for every 5S event), keep a small stock on kanban so the team never waits on a purchase order.
7. Assign the follow-up
Every event or project ends with items that did not get finished. Each one gets an owner and hours on that owner's plan before the event closes. If there are no hours available, the item goes to the next event's charter rather than to a list nobody looks at.
8. Track actuals against the plan
At the end of each week, compare hours used, equipment time used, and materials consumed against what was planned. The point is not to police the team; it is to find out where the estimates were wrong so the next plan is better. Over a few projects this produces real numbers for how long a 5S event in a 2,000 square foot area takes, which is what makes future resource plans credible.
Resource management inside a kaizen event
The compressed version, for a five-day event:
- Three weeks before: team named and their supervisors told, backfill arranged for the line, machine time booked, materials ordered, event room reserved.
- One week before: confirm everyone is still available, materials have arrived, baseline data is collected.
- During: the facilitator owns the schedule; the sponsor is reachable within an hour for approvals; one person tracks what was used.
- Day 5: follow-up items assigned with hours and dates before the report-out.
- 30 days after: follow-ups audited; hours actually spent recorded.
Signs that resources are the problem
- Projects start late because someone was not available on the start date.
- The same names appear on every charter.
- Events get cut short by production demands.
- Follow-up lists from past events are mostly open.
- Nobody can say how many hours the last project actually took.
- Supervisors resist releasing people because the last time nobody covered for them.
Each of these is a planning failure with a specific fix above. None of them is solved by asking people to try harder.
Frequently asked questions
What is the difference between resource management and project management?
Project management covers the whole project: scope, schedule, budget, risk, stakeholders, quality. Resource management is the part of it concerned with whether the people, equipment, and materials the schedule assumes will actually be there.
What is resource leveling?
Adjusting the schedule so that no person or machine is overloaded in any period, usually by moving tasks later or spreading projects across the calendar. The deadline may move; the alternative is a plan that assumes capacity that does not exist.
What is a skills matrix?
A table of people against skills showing who is trained, qualified, or able to train others on each one. It is used to assign work, find single points of failure, and plan training.
How much of a person's time can be planned?
Less than all of it. Meetings, interruptions, and regular duties take a share. Planning improvement work at 70 to 80% of nominal available hours is realistic; planning at 100% guarantees slippage.
Do I need software for this?
Not for a single plant's improvement program. A spreadsheet with a row per task and columns for owner, hours, dates, equipment, and materials covers it. Software becomes worth it when several sites share people or when the project count is high enough that nobody can hold the schedule in their head.
Related tools
Resource management works with the rest of the planning set: project timelines and Gantt charts for the schedule, cost-benefit analysis for the budget, stakeholder engagement for the supervisors who have to release people, and scope creep control for keeping the plan from growing past its resources. The work it supports is on the kaizen, 5S, and TPM pages. For the materials side, 5S Today stocks the floor marking and labels and signs most events consume.