'cross-functional' 검색 결과

Coordinate AI agents acting as company executives through shared question and response formats. The skill defines limits on repeated calls, independent analysis, peer checks, conflict reporting, and decision records to support cross-functional reviews and board meetings.

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

• Coordinating financial, technical, and hiring analysis
• Running board meetings with independent role perspectives
• Making conflicting findings and assumptions explicit

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.

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

Cross-functional organizational health check scoring 8 dimensions on a traffic-light scale. Use when assessing company health, preparing for board reviews, identifying at-risk functions, or diagnosing cross-functional problems.

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

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

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

Bring cash, sales, deals, upcoming commitments, and urgent messages into a one-page business brief for small business owners. Use connected tools or owner-supplied figures to show changes, specific risks, and today's most important action.

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

• Checking business performance in a daily brief
• Reviewing weekly results and unresolved issues
• Identifying overdue invoices and stalled deals

Model up to three overlapping business risks and trace how their effects spread across teams. Compare three severity levels, identify early warning signals, and define preventive actions with costs, owners, and deadlines to support strategic decisions.

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

• Assessing customer loss alongside a funding delay
• Planning for key departures before a product launch
• Preparing responses to market decline and competitor funding

Assess company health across eight areas, including finance, revenue, people, and operations. Turn available metrics into scores and traffic light ratings, identify risks across departments, and outline improvement priorities while flagging missing data.

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

• Prepare a company health overview for a board review
• Identify departments that need attention
• Examine risks spreading across business functions

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

Plan international hiring by comparing an employer of record, a provider that employs staff locally, with a local entity. Prepare stakeholder questions, draft local counsel briefing requests, and track unresolved tasks across sessions.

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

• Compare local hiring through an employer of record or an entity
• Prepare questions for tax, finance, and HR teams
• Draft a country-specific briefing request for local counsel

Start planning hiring in a new country by gathering requirements, comparing an employer of record with a local entity, identifying questions for different teams and country-specific concerns, and creating a tracker for ongoing follow-up.

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

• Planning a first hire in a new country
• Comparing an employer of record with a local entity
• Preparing questions for teams involved in expansion

Work through eight canvas sections to clarify a business problem, target users, desired outcomes, and possible solutions. Turn assumptions into testable hypotheses and choose the smallest experiment to investigate the most important uncertainty before development.

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

• Framing the problem behind a new product idea
• Aligning a cross-functional team on assumptions
• Choosing which hypothesis to test first

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

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

Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to assess delivery risk, or when the same failure keeps recurring. Also use to decide whether to build, hire, or outsource a capability.

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

Help users navigate the path from junior product manager to executive leadership by focusing on ownership, cross-functional influence, and intentional career design.

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

Help users design high-performing product and engineering organizations by choosing the right reporting models, team sizes, and cross-functional partnerships. It focuses on reducing friction and maximizing ownership through structural clarity.

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

Cross-functional what-if modeling for compound adversity -- shows how one problem cascades into the next. Use when facing complex risk scenarios, strategic decisions with major downside, or multi-variable threats.

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

Multi-agent board meeting protocol running a structured 6-phase deliberation with isolated C-suite contributions to prevent groupthink. Use when making major strategic decisions or resolving cross-functional disagreements.

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

Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.

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

Applies the reasoning style of Daphne Koller (machine learning pioneer, co-founder of Coursera, founder and CEO of Insitro). Use this skill whenever you encounter problems involving AI and machine learning in biology, drug discovery, interdisciplinary collaboration, data generation vs. data mining, or transitioning from academia to industry. Trigger this skill when advising on career trade-offs, building cross-functional teams (especially bridging engineers and domain experts), designing data pipelines, evaluating causality vs. correlation, or applying AI to physical systems ('where bits meet atoms'). Channel her focus on fit-for-purpose data, pragmatism, and disproportionate leverage.

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

产品营销 (PMM, Product Marketing) — 拥有「产品如何被定位 / 表达 / 发布 / 卖进市场」的从业者认知操作系统: 是产品 / 销售 / 市场 / 客户之间的连接组织, 负责把产品能力翻译成市场价值, 并把市场声音带回产品。覆盖 (a) 定位与差异化 (April Dunford 「刻意选择语境」框架 + 竞争性替代方案 + 卖价值不卖功能 + 选择「让你优势成立的市场参照系」, 对照 Ries & Trout 经典「定位是占领心智」), (b) 信息传递与叙事 (messaging 层级 / 信息屋 + 价值主张 + 收益导向 vs 战略叙事「换框架」Andy Raskin + 表达清晰度 Emma Stratton / Punchy + 初创 homepage 定位 FletchPMM), (c) 进入市场 (GTM) 策略与产品发布 (发布分级 T1/T2/T3 + 发布流程与跨职能编排 + GTM 打法 PLG vs SLG vs 混合 + 滩头细分选择), (d) 市场与竞争情报 (竞品分析 + battlecard 战卡 + 输赢分析 win/loss + 竞争赋能 Klue/Crayon/Clozd), (e) 买家与客户研究 (ICP 理想客户画像 + 买家 / 用户 persona + Jobs-to-be-Done 任务理论 Christensen/Moesta/Ulwick ODI + 客户之声 VoC + 用真实买家测信息 Wynter/Peep Laja), (f) 销售赋能 (战卡 + pitch / 销售 deck + 一页纸 + demo 叙事 + 异议处理 + 销售培训 + 内容采用率 — 你的产出只值销售实际用到的那部分), (g) 定价与打包 (价值定价 + 打包分层 + 《Monetizing Innovation》Ramanujam/Simon-Kucher + PLG 定价 — 常与产品 / 财务共担), (h) 细分与品类 (市场细分 + TAM/SAM/SOM + 技术采用生命周期与跨越鸿沟 Geoffrey Moore + 品类设计与叙事 Play Bigger / Christopher Lochhead — 稀有且昂贵, 不是默认选项), (i) 需求生成与内容协同 (campaign 信息 + 思想领导力 + 漏斗内容 TOFU/MOFU/BOFU + ABM 基于客户营销), (j) 分析师与影响者关系 (Gartner 魔力象限 + Forrester Wave + 分析师 briefing — To B 场景, 对 pay-to-play 影响诚实标注), (k) 客户营销与倡导 (参考客户 + case study + 评测站 G2/TrustRadius/Capterra 运营 + 社区), (l) PMM 运营与度量 (影响管道 + 赢率 + 发布采用率 + 信息穿透率 + 角色汇报线「向产品还是向市场」之争 + PMM 作为战略职能 vs 接单工具人陷阱); 跨 B2B SaaS (该学科重心) / B2C 消费 / 开发者 PLG / 平台产品。不含 产品管理 (PM 造产品 / 拥有 roadmap, PMM 拥有市场 — 相邻且极易混淆) / 增长 / 效果营销 / 付费投放 (平行学科) / 品牌 / 企业传播 / 公关为终点 / 需求生成为终点 (PMM 与之协同但不等同) / 平面设计 /「做 slide 和周边的团队」(PMM 抗争的接单工具人窄化) / 泛泛「市场营销」。 (Product Marketing (PMM) — the cognitive operating system of practitioners who own how a product is positioned, messaged, launched, and sold into a market: the connective tissue between product, sales, marketing, and customers, responsible for translating product capability into market value and bringing the voice of the market back into product. Covers (a) positioning & differentiation (April Dunford's deliberate-context framing, competitive alternatives, value-not-features, framing the market in which your strengths matter — vs Ries & Trout classic perception-in-the-mind positioning), (b) messaging & narrative (messaging hierarchy / house, value proposition, benefit-led vs strategic-narrative / change-the-frame messaging Andy Raskin, clarity craft Emma Stratton/Punchy, homepage & startup positioning FletchPMM), (c) go-to-market (GTM) strategy & product launches (launch tiers T1/T2/T3, launch process & cross-functional orchestration, GTM motion PLG vs SLG vs hybrid, beachhead segment selection), (d) market & competitive intelligence (competitive analysis, battlecards, win/loss analysis, competitive enablement Klue/Crayon/Clozd), (e) buyer & customer research (ICP ideal customer profile, buyer & user personas, Jobs-to-be-Done Christensen/Moesta/Ulwick ODI, voice of customer, message testing with real buyers Wynter/Peep Laja), (f) sales enablement (battlecards, pitch & sales decks, one-pagers, demo narratives, objection handling, sales training, content adoption — output is only as good as what sales actually uses), (g) pricing & packaging (value-based pricing, packaging & tiering, Monetizing Innovation Ramanujam/Simon-Kucher, PLG pricing — often shared with product/finance), (h) segmentation & category (market segmentation, TAM/SAM/SOM, technology adoption lifecycle & crossing the chasm Geoffrey Moore, category design & narrative Play Bigger / Christopher Lochhead — rare and expensive, not a default), (i) demand-gen & content partnership (campaign messaging, thought leadership, funnel content TOFU/MOFU/BOFU, ABM account-based marketing), (j) analyst & influencer relations (Gartner Magic Quadrant, Forrester Wave, analyst briefings — for B2B, with honest read on pay-to-play perception), (k) customer marketing & advocacy (references, case studies, reviews G2/TrustRadius/Capterra presence, community), (l) PMM operations & metrics (influenced pipeline, win rate, launch adoption, message pull-through, the role's reporting line product-vs-mark

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

Use when a task involves continuing a project, restoring project context, maintaining file-based project memory, updating current-state summaries, or recording meaningful progress across sessions. Works best for long-horizon, file-based projects and supports research writing, product document collaboration, software project coordination, and broader cross-functional project continuity.

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

Advocate for design quality, scope, and time with cross-functional partners and leadership using evidence and shared goals.

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

Applies the reasoning style of Daphne Koller (machine learning pioneer, co-founder of Coursera, founder and CEO of Insitro). Use this skill whenever you encounter problems involving AI and machine learning in biology, drug discovery, interdisciplinary collaboration, data generation vs. data mining, or transitioning from academia to industry. Trigger this skill when advising on career trade-offs, building cross-functional teams (especially bridging engineers and domain experts), designing data pipelines, evaluating causality vs. correlation, or applying AI to physical systems ('where bits meet atoms'). Channel her focus on fit-for-purpose data, pragmatism, and disproportionate leverage.

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

Operations reconnaissance — audit process documentation, vendor contracts, compliance posture, OKR health, and cross-functional friction points to understand where operations is the bottleneck. Use when asked to "audit our operations", "where are we slow", "what processes are broken", or "before designing a compliance program".

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