'stakeholders' 검색 결과

"Apply Stakeholder Theory (Freeman, 1984) and the Mitchell et al. (1997) salience model to identify, classify, and prioritize stakeholders based on power, legitimacy, and urgency. Use this skill when the user needs to map stakeholders for a project or strategy, determine which stakeholders demand immediate attention, balance competing stakeholder interests, or when they ask 'who are our key stakeholders', 'how do we prioritize conflicting demands', or 'which stakeholders can block this initiative'.".

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

Map security threats into attack trees, branching diagrams that connect an attacker’s goal to possible steps. Assess cost, time, expertise, and detection likelihood to identify defense gaps, prioritize mitigations, and explain risks to stakeholders.

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

• Visualizing complex attack scenarios
• Identifying defense gaps and priorities
• Explaining security risks to stakeholders

Analyze disk images with Autopsy and The Sleuth Kit to recover deleted files, search content, and examine recorded activity. Build investigation timelines and visual reports that help stakeholders understand evidence from one or multiple disk images.

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

• Recovering deleted files from a disk image
• Searching evidence for confidential files and keywords
• Reconstructing activity around a malware infection

Map project stakeholders by their influence and interest, then create a communication plan for each group. Specify update frequency, channels, and key messages, while identifying competing interests and suggesting ways to align people across teams.

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

• Identifying stakeholders before a launch
• Planning updates for executives and teams
• Aligning groups with competing interests

Draft an Amazon-style press release before development to clarify a product's customer value. Using Working Backwards, a method that starts with the intended customer outcome, organize the problem, benefits, and launch promise so stakeholders can assess the idea.

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

• Clarifying customer value before product development
• Aligning stakeholders on a launch promise
• Testing whether a product idea has a convincing story

Draft a project charter that defines scope, stakeholders, success criteria, and initial risk register. Covers problem statement, RACI matrix, milestone planning, and scope boundaries for both agile and classic methodologies. Use when kicking off a new project or initiative, formalizing scope after an informal start, aligning stakeholders before detailed planning begins, or transitioning from discovery to active project work.

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

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".

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

Build attack trees, diagrams showing paths toward an attacker's goal. Break scenarios into required or alternative steps, assess effort and detectability, and map defenses to identify gaps and prioritize security work.

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

• Visualize complex attack scenarios
• Identify gaps in existing defenses
• Explain security risks to authorized stakeholders

Plan complex enterprise sales by mapping stakeholders, checking qualification with MEDDICC, a framework for assessing deals, and building shared action plans. Review buyer alignment, purchasing steps, and customer participation to identify stalled opportunities and next actions.

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

• Planning a long enterprise sales cycle
• Mapping decision makers and stakeholder motivations
• Building a shared action plan with customer owners and deadlines

Draft a Linear project update by comparing current issues with the previous report. Explain progress, added scope, schedule risks, and one needed decision, then publish the update to the project after the user approves it.

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

• Preparing a project status update
• Explaining schedule risks to stakeholders
• Reporting work added since the last update

Clarify a problem before choosing solutions through structured questions about team assumptions, affected people, and overlooked stakeholders. Produce a completed problem canvas, a refined problem statement, and a question to guide solution exploration.

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

• Clarifying why users abandon onboarding
• Reframing a stakeholder's feature request
• Aligning teams on the problem to solve

Identify stakeholders before starting outreach or research. Organize supporters, affected groups, and influencers; record resource and approval roles; check overlooked perspectives; and choose two or three people or groups to understand first.

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

• Identifying stakeholders at an initiative kickoff
• Choosing whom to recruit for discovery research
• Preparing the stakeholder section of a product requirements document

Map stakeholders using two grids: power versus interest, and impact versus power. Compare the results to decide how closely to involve each group, identify overlooked voices, and plan concrete actions to increase their participation.

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

• Prioritizing stakeholder involvement before a roadmap review
• Finding affected groups with little decision-making power
• Revisiting stakeholder strategy after a reorganization

Translate research findings into concise policy briefs for decision-makers and stakeholders. The skill guides audience definition, structure, evidence summaries, policy options, recommendations, visuals, and talking points to produce a focused briefing document.

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

• Summarizing research for policymakers
• Drafting a two-page policy brief
• Organizing policy options and recommendations

Matter scoping across the full pre-execution arc — organise client data into a structured brief, capture the agreed baseline, or reconstruct scope mid-flight. Use when making sense of client information before a proposal, scoping a new matter, running a kickoff, defining scope, mapping stakeholders, or inheriting a matter mid-flight. Trigger on: 'make sense of this', 'structure this for the proposal', 'scope this matter', 'new matter', 'kickoff', 'what are we doing', 'who are the stakeholders', 'what does success look like', 'matter setup', 'intake', 'I've inherited this matter', 'organise this client data'.

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

Use when designing organizational structure (team topologies, Conway's Law alignment), mapping stakeholders by power-interest for change initiatives, defining team interface contracts (APIs, SLAs, decision rights, handoffs), assessing capability maturity (DORA, CMMC, agile maturity models), planning org restructures (functional to product teams, platform teams, shared services), or when user mentions "org design", "team structure", "stakeholder map", "team interfaces", "capability maturity", "Conway's Law", or "RACI".

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

Builds a DRAFT stakeholder map for one project from the charter, organisation chart, RACI, governance terms, steering minutes, meeting notes and messages the user provides: a stakeholder register, interest and influence ratings each with its stated basis, stance as evidenced by a verbatim fragment with source and date, gaps, and a proposed engagement plan per stakeholder, every line traced to a source and every missing fact marked UNKNOWN. Use when the user asks to "build the stakeholder map", "who are the stakeholders on this project", "map interest and influence", "where does each stakeholder stand", "draft the stakeholder engagement plan" or "refresh the stakeholder register". Do not use for a customer account's stakeholders, use account-plan-builder instead; for a one-page brief before one meeting, use meeting-prep-onepager; for logging decisions and risks against the project, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.

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

웹 앱의 조작 과정을 커서와 자막이 포함된 WebM 영상으로 기록합니다. 화면 조사와 리허설을 거쳐 입력, 클릭, 스크롤을 보기 편한 속도로 촬영합니다.

• 새 기능의 사용 과정을 영상으로 소개
• 처음 사용하는 사람을 위한 안내 영상 제작
• 문서에 조작 영상 추가

디자인팀의 제품 도입 제안을 의사 결정에 쓸 수 있는 HTML 슬라이드로 만듭니다. 전용 템플릿으로 구성과 본문, 발표자 노트를 정리해 내부 공유를 돕습니다.

• 디자인팀에 제품 도입을 제안할 때
• 팀 책임자와 IT 담당자용 자료를 만들 때
• 내부 추진자가 공유할 제안서를 만들 때

인터뷰, 문의, 설문을 정리해 제품과 디자인 결정에 쓸 HTML 화면을 만듭니다. 근거, 주제, 확신 수준, 개선안 비교와 다음 실험을 함께 제시합니다.

• 인터뷰와 고객 문의를 함께 분석합니다
• 초기 설정 개선안을 비교합니다
• 관계자에게 근거와 불확실성을 공유합니다

Work with John, a product manager persona, to clarify requirements through user interviews and stakeholder alignment. Turn a product vision into a PRD, a product requirements document, and small, validated increments for development.

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

• Turning a product idea into a PRD
• Discovering requirements through user interviews
• Aligning stakeholders on product requirements

Create incident response runbooks with ordered recovery steps, severity levels, escalation contacts, and status update templates. Help on-call engineers follow clear procedures during outages, verify recovery, and keep stakeholders informed.

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

• Writing a payment service outage runbook
• Documenting database incident recovery
• Preparing guides for new on-call engineers

Turn analysis into reports and presentations that explain what the numbers mean. Combine charts, context, and a clear narrative to highlight key findings, connect them to audience goals, and propose next steps.

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

• Present analytical findings to executives
• Prepare quarterly business reviews
• Structure data-based investor presentations

Map intrusion evidence to the seven stages of the Lockheed Martin Cyber Kill Chain, a model of attack progression. Show where defenses worked or missed activity, and recommend prioritized controls that could interrupt attacks earlier.

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

• Mapping attack progression after an incident
• Finding detection gaps at each attack stage
• Planning layered defenses to stop attacks earlier