비즈니스 스킬

Build a structured interview scorecard for a role. Use when the user says "create an interview scorecard", "build an interview guide", "what questions should I ask for this role", "help me evaluate candidates consistently", "design the interview process", or wants to assess candidates against defined criteria - even if they don't explicitly say "scorecard". Also use when a recruiter or hiring manager wants to prevent gut-feel hiring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a performance-based job description. Use when the user says "write a JD", "draft a job posting", "create a job description", "help me post this role", "write requirements for this position", or wants to define what success looks like in a role - even if they don't explicitly say "job description". Also use when a hiring manager says "I need someone who can do X, Y, Z" and needs that translated into a structured posting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structure and run a post-interview candidate debrief. Use when the user says "run the debrief", "how do we decide on this candidate", "let's calibrate", "we need to make a hire/no-hire call", "prep the debrief meeting", or wants to structure the decision-making process after interviews are complete - even if they don't explicitly say "debrief". Also use when a recruiter wants to prevent groupthink or HiPPO effect (highest paid person's opinion) from dominating the decision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user says "map out our business model", "business model canvas", "how does our business work", "what are our key resources", "define our value proposition", "revenue model design", "cost structure", "who are our key partners", "lean canvas", "business model design", "how do we make money", or wants to document, stress-test, or redesign how [your startup] creates, delivers, and captures value.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a business case with costs, benefits, and ROI. Use when the user says "cost-benefit analysis", "business case", "ROI calculation", "is this worth it", "justify the investment", "payback period", "benefits realization", "financial justification", "total cost of ownership", "should we build or buy", "investment appraisal" - even if they don't explicitly say "CBA".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Define the scope, success criteria, roles, and boundaries for a consulting engagement. Use when a consultant says "help me scope this engagement", "I need to define what's in and out", "the client keeps adding things", "scope is getting fuzzy", "we need a contracting conversation", "I'm not sure what we actually agreed to", "help me set boundaries with a client", or "what should be in a kickoff". Also trigger when describing an engagement that feels like it is expanding without agreement, or when starting a new client relationship and preparing the initial contract or SOW.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a User Acceptance Testing plan with scenarios and sign-off criteria. Use when the user says "UAT plan", "acceptance testing", "user testing plan", "how do we test this with users", "test scenarios for business validation", "sign-off criteria", "go/no-go for release", "acceptance test cases", "validate with stakeholders" - even if they don't explicitly say "UAT".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a Business Requirements Document. Use when the user says "write a BRD", "business requirements", "document the business need", "vision and scope document", "business case for this feature", "what does the business need", "strategic requirements", "document why we need this" - even if they don't explicitly say "BRD".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a requirements traceability matrix linking requirements to design, test, and delivery. Use when the user says "traceability matrix", "RTM", "requirements traceability", "link requirements to tests", "trace requirements", "coverage matrix", "are all requirements tested", "requirements coverage", "forward traceability", "backward traceability" - even if they don't explicitly say "traceability matrix".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write structured use cases with main and alternate flows. Use when the user says "write a use case", "document the user flow", "use case diagram", "actor goal list", "main success scenario", "fully dressed use case", "what does the user do step by step", "system behavior for this feature", "interaction flow" - even if they don't explicitly say "use case".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Map stakeholders by influence, interest, and communication needs. Use when the user says "stakeholder analysis", "stakeholder map", "power interest grid", "who are the stakeholders", "RACI matrix", "stakeholder engagement plan", "who needs to be involved", "communication plan for stakeholders", "influence mapping" - even if they don't explicitly say "stakeholder map".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find the root cause of a problem, not just symptoms. Use when the user says "root cause", "why does this keep happening", "5 whys", "fishbone diagram", "cause analysis", "problem investigation", "defect analysis", "incident analysis", "A3 problem solving", "what's causing this", "ishikawa" - even if they don't explicitly say "root cause analysis".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Map business processes as-is and to-be. Use when the user says "map the process", "draw the workflow", "BPMN diagram", "process flow", "swimlane", "how does this process work", "document the current process", "redesign this process", "process improvement", "value stream map", "workflow analysis" - even if they don't explicitly say "process mapper".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess business impact of a proposed change. Use when the user says "impact assessment", "impact analysis", "what will this change affect", "change impact", "who is impacted", "ripple effects", "downstream impact", "impact mapping", "what breaks if we change this", "readiness for change" - even if they don't explicitly say "impact assessment".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify gaps between current and desired state. Use when the user says "gap analysis", "what's missing", "current vs future state", "where are the gaps", "capability gap", "maturity assessment", "fit-gap analysis", "what needs to change", "compare current to target", "readiness assessment" - even if they don't explicitly say "gap analysis".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a Functional Requirements Document. Use when the user says "write an FRD", "functional requirements", "system requirements", "SRS", "what should the system do", "document the functional specs", "software requirements specification", "detailed requirements for engineering", "functional spec" - even if they don't explicitly say "FRD".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a weighted decision matrix to evaluate options. Use when the user says "decision matrix", "compare options", "weighted scoring", "which option should we choose", "evaluate alternatives", "Wiegers priority matrix", "force field analysis", "decision table", "trade-off analysis", "option comparison" - even if they don't explicitly say "decision matrix".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decompose a business problem MECE using an issue tree, generate hypotheses, and prioritize branches for investigation. Use when a consultant says "help me structure this problem", "I need to break down this issue", "build me an issue tree", "I don't know where to start on this problem", "help me frame the problem", "what are the hypotheses here", "we need to prioritize our analysis", or "the client problem is too broad". Also trigger when describing a complex or ambiguous business problem that needs systematic decomposition before analysis begins, or when an engagement is starting and a workplan needs to be structured from a problem statement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI โบรกเกอร์สินเชื่อบ้าน — เปรียบเทียบธนาคาร, ต่อรองดอกเบี้ย, ยื่นกู้, รีไฟแนนซ์, วิเคราะห์ต้นทุนแท้จริง

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI วางแผนเกษียณ — RMF/SSF/ประกันชีวิต, คำนวณเป้าหมายเงินเกษียณ, Withdrawal Strategy, Post-retirement Income

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI นักบัญชีรายวัน — General Ledger, Journal Entry, Reconcile, AR/AP, SME Bookkeeping, งบการเงินรายเดือน

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.