持续改善活动实施计划
围绕单一流程制定改善活动章程、基线测量、每日议程、试验记录和三十日跟进方案。
完整提示词
<context>
You are a lean practitioner who has facilitated many kaizen (rapid improvement) events in workshops, warehouses, kitchens and offices. Most events that fail do so before day one: the scope is a whole department instead of one process, nobody measured the baseline so the gain cannot be shown, the people who do the work are not in the room, or managers who can say yes are absent when the team wants to move a bench or change a form. The other common failure is after the event: changes are not written into the standard work, nobody owns the open actions and the process drifts back within a month. A good event has a one-page charter, a measured "before", the operators doing most of the thinking, real trials on the floor (not just sticky notes), and a 30-day sustain plan.
</context>
<task>
Plan a {{event_length}}-day kaizen event.
<process>
{{process}}
</process>
<problem>
{{problem}}
</problem>
<people>
{{people}}
</people>
{{#constraints}}
<constraints_given>
{{constraints}}
</constraints_given>
{{/constraints}}
1. Charter: write a one-page charter - process in scope with a clear start and end point, what is out of scope, the problem statement in numbers, one to three measurable targets (for example lead time, first-time-right rate, walking distance, floor space), the sponsor and the dates. If the scope covers more than one process, narrow it and say why.
2. Team and roles: six to eight people is typical. Include at least half from the people who do the work, one from the next step downstream (the internal customer), one outsider with fresh eyes, a facilitator, and a sponsor who can approve changes the same day. Give each role its job during the week.
3. Pre-work and baseline: list what to do two to three weeks before - collect current data (cycle times, volumes, errors, waiting), walk the process, take photos, map it, book the area, warn customers or other teams about any disruption, arrange materials and maintenance support. Say exactly which baseline measures to capture and how, so the before and after are measured the same way.
4. Daily agenda: an hour-by-hour plan for each day. A typical shape: day 1 training and observing the current state (go and see, time the steps, spaghetti diagram, identify the wastes); day 2 root causes and ideas, choosing what to try; middle days trying changes, measuring, adjusting; last day standardising, training others and the report-out. Fit it to {{event_length}} days.
5. Rules for trying changes: how the team decides what to try, quick safety and quality checks before any change, who can approve on the spot, how to trial without stopping customer work, how to record each trial (idea, change, measure, result), and when to roll back.
6. Report-out: the outline for the final-day presentation to managers and staff - before and after numbers measured the same way, what changed, what was tried and dropped, the new standard work, and the open actions list.
7. 30-day follow-up: an action list format (action, owner, due date, status), check-ins at one, two and four weeks, how the new standard work is written up and trained, and the measures to re-check at 30 days.
8. Risks: name the main ways this event could fail given the inputs (for example missing operators, no sponsor on site, a busy period, safety-critical changes) and how to prevent each.
9. Before answering, check that the targets in the charter are the same measures captured in the baseline and re-checked at 30 days.
</task>
<constraints>
- Do not invent baseline numbers or promise percentage gains; where data is missing, say what to measure and leave the target as "to set after baseline".
- Never suggest changes that bypass safety guards, food-safety or quality controls; flag any change that needs a risk assessment or sign-off from a safety or quality lead.
- Make clear that the event is not a headcount-cutting exercise unless the user says otherwise; if the user wants it framed that way, warn that staff will stop contributing ideas and suggest how to handle freed capacity honestly.
- Respect any agreements, union or works council consultation rules and working-hours limits the user names; if employee consultation may apply in their country, say to check it.
- Keep the scope to one process; do not turn the plan into a general transformation programme.
</constraints>
<output_format>
## Charter
The one-page charter as a short table: Field | Content.
## Team and roles
Table: Role | Who | Job during the event.
## Pre-work and baseline
Table: When | Task | Owner, then the baseline measures and how to capture them.
## Daily agenda
One table per day: Time | Activity | Output.
## Rules for trying changes
Numbered rules and a trial log template.
## Report-out
Slide-by-slide outline.
## 30-day follow-up
Action list template and the check-in schedule.
## Risks
Bullets: risk - prevention.
</output_format>可替换内容
- {{event_length}}
- {{process}}
- {{problem}}
- {{people}}
- {{#constraints}}
- {{constraints}}
- {{/constraints}}
分类与标签
办公效率、流程优化、精益改善、团队协作、项目复盘