Have you ever been asked at work, "Why do different people do things differently?" It's the same job, but Team A does it this way, Team B does it that way... The quality of the output varies, and handoffs are complicated.
One company I worked with was really bad, because everything from how they dealt with customers to how they wrote reports was tailored to their personal style, so there was a lot of variation in quality. But once they started to standardize things, it was a completely different organization.
Prompt.
복사
// Enable work standardization design expert mode
== Step 1: Diagnose your situation ==
Business area: [insert target business area].
Number of people involved: [number of employees involved].
Current Problem:
- Quality deviations: [specific examples].
- Inefficiencies: [time/money lost].
- Communication: [information sharing issues]
== Step 2: Define a standard process ==
◆ Key work steps
Step 1: [Initiation phase].
Step 2: [Progress steps]
Step 3: [Completion phase]
Set quality standards
- Required checkpoints: [Validation items]
- Completeness criteria: [Quantitative indicators]
- Exception handling: [Countermeasures]
== Step 3: Tools and templates ==
▲ Standard forms: [Forms to use]
Checklists: [Things to check].
▲ Guidelines: [detailed guidelines].
Using the above structure, please provide specifics on how to standardize [task name] in a way that your team can implement immediately.
The results of standardizing with this prompt have been amazing, with an average 25% reduction in turnaround time, more than 80% reduction in quality variation, and new hires getting up to speed in half the time, which has greatly increased productivity for the entire team.
Standardizing tasks isn't just about creating rules, it's about organizing the collective intelligence of your organization. If there's a task on your team that you're asking yourself, "Why do I do it differently every time?" why not take this approach?
Like it
28
Love it
Like it
Slightly like it
Comments
0
Write a comment
Safe Legacy System Exit Prompt
"If I touch this system, something will blow up." That's what every developer says when they're looking at a 20-year-...
Why don’t people listen to good content? The problem is in the design
Do you know what the most frustrating moment is when you're creating an online course? When I first started creating ...