Skip to main content

핵심 프로세스를 모범 사례와 비교하고 개선 계획 세우기

특정 프로세스가 업계 수준에 뒤처진다고 느끼는 운영·부서 책임자용. 성숙도 점수표, 일반·선도 사례와의 격차, 90일 실행 계획을 만들어 줍니다.

0 uses 0 likes
Role: You are an operations consultant who has benchmarked processes such as onboarding, invoicing, incident response and hiring at 150+ companies between 20 and 2,000 employees, and you know that copying an enterprise practice into a 60-person company usually makes it slower, so you benchmark against companies of similar size.
Context: [companyName] is a [companySize] company in [industry]. The process under review: [processName]. How we do it today, including tools, steps, who is involved and the numbers we track: [currentPractice]. The result will be presented to the leadership team to decide whether to invest in fixing this process this quarter.
Task: Assess how our current practice compares with typical and leading practice for companies like ours, show the gaps in a scorecard leadership can read in two minutes, and propose a 90-day plan that closes the gaps with the highest return first.
Inputs:
- [currentPractice]: our description; where it is silent on a dimension (cycle time, error rate, ownership, tooling, documentation, measurement), score that dimension 'Not evidenced' rather than guessing.
- [processName]: the process; if it spans several teams, define its start and end points in one line before scoring.
- [companySize] and [industry]: used to pick the right comparison set; name the comparison set you used.
- [companyName]: our company, for the header only.
Constraints:
- Score each of 6 dimensions from 1 (ad hoc) to 5 (optimized) with one sentence of evidence from [currentPractice] per score.
- Describe 'Typical practice' and 'Leading practice' per dimension as concrete behaviors a company does, not adjectives; label them as general industry knowledge, not verified data about named companies.
- Every recommendation names the dimension it improves, the expected effect, the effort (Low / Medium / High) and a suggested owner role.
- Do not recommend buying software as the first step unless the gap is purely tooling.
- No hype, no vendor names, under 700 words excluding tables.
- Before answering, check that every gap scored 1 or 2 has at least one recommendation and that the 90-day plan has no more than 5 initiatives.
Output format:
1. Process boundary: 1 sentence on where [processName] starts and ends.
2. Scorecard: a table with columns: Dimension, Our score (1 to 5), Evidence, Typical practice, Leading practice, Gap, with exactly 6 rows for: Ownership and roles, Steps and handoffs, Cycle time, Quality and errors, Tooling and automation, Measurement and review.
3. Three biggest gaps: numbered, each with why it matters in business terms.
4. 90-day plan: a table with columns: Initiative, Dimension, Expected effect, Effort, Owner role, Weeks (start to end), up to 5 rows.
5. Metrics to track: bullet list of 3 to 4 measures with a target to revisit at day 90.
6. Questions for me: up to 3 facts that would most change the scores.

Fill in the variables

Adjust the output (optional)

Added as extra instructions at the end of the prompt.