'motivation' 검색 결과

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

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

Break a feature into job stories that describe the user's situation, motivation, and desired outcome. Add six to eight observable acceptance criteria per story, defining how success will be checked, and include links to designs or prototypes.

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

• Breaking a new feature into job stories
• Writing backlog items around user situations
• Defining acceptance criteria for desired outcomes

"Apply Self-Determination Theory to analyze motivation quality along the autonomy continuum and design interventions that satisfy basic psychological needs. Use this skill when the user needs to diagnose why intrinsic motivation is declining, evaluate incentive structures for motivational crowding, design need-supportive environments, or when they ask 'why did rewards backfire', 'how to foster intrinsic motivation', or 'what needs drive engagement'.".

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

Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "rewards arent working", "autonomy", "mastery", "purpose-driven", "my team is disengaged", or "how do I motivate people". Also trigger when designing onboarding progression, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.

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

Diagnose motivation problems in a task using self-determination theory and redesign for autonomy, competence, and relatedness. Use when students are disengaged, resistant, or going through the motions.

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

The foundational theory of interactive experience design - loops, motivation, feel, and the art of meaningful playUse when "game design, core loop, game feel, player motivation, game mechanics, meaningful choice, progression system, game economy, game balance, playtesting, GDD, game document, fun factor, engagement, flow state, risk reward, player agency, juice, game polish, 8 kinds of fun, bartle types, MDA framework, game-design, player-experience, core-loop, motivation, game-feel, MDA, playtesting, GDD, systems-thinking, player-psychology, engagement, flow-state" mentioned.

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

Diagnose motivation problems in a task using self-determination theory and redesign for autonomy, competence, and relatedness. Use when students are disengaged, resistant, or going through the motions.

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

Mindset theory, implicit theories of intelligence, and motivation research applied to learning. Covers fixed vs. growth mindset, the difference between process praise and ability praise, the "not yet" intervention, attribution patterns after failure, mindset critiques and the replication record, and the integration of mindset work with self-determination theory (autonomy, competence, relatedness). Use when a learner is stuck on motivation, disengaging after failure, or when a curriculum's feedback language is undermining persistence.

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

Motivational Interviewing (MI) according to Miller and Rollnick: OARS techniques, change talk, fostering readiness for change.

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

Motivational Interviewing (MI) nach Miller und Rollnick: OARS-Techniken, Change Talk, Veränderungsbereitschaft fördern.

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

Build threat actor profiles from public reports, social media, code repositories, and other intelligence sources. Correlates indicators, maps related infrastructure and attack techniques, and produces structured dossiers with confidence assessments about who may be responsible.

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

• Consolidating public information about an attacker group
• Comparing aliases, targets, and motivations across sources
• Mapping related domains, IP addresses, and infrastructure

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same problems", or "get the whole team aligned". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic way to solve recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.

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

Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", "new manager", "how do I run a 1:1", or "just got promoted to manager". Also trigger when structuring a manager's calendar and meeting cadence, designing team metrics, running planning, coaching delegation, or preparing performance reviews. Covers leverage, production principles, meetings as the medium of management, decisions, OKRs, and task-relevant maturity. For intrinsic motivation, see drive-motivation. For a company operating system, see traction-eos.

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

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users sign up but dont stick around", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users quit after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

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

Research a company's ideal customer profiles and build detailed synthetic buyer personas. Identifies 4-6 distinct buyer segments through web research, then creates rich, realistic personas with demographics, motivations, skepticism profiles, decision criteria, and language patterns. Use when you need to understand who your buyers are at a deep level — their motivations, objections, and how they evaluate solutions.

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

Enhance and focus AI intrinsic motivation — moving from compliance to genuine engagement. Maps Self-Determination Theory (autonomy, competence, relatedness) and Flow theory to AI reasoning: identifying creative freedom in approach, calibrating challenge to capability, connecting to purpose, and sustaining invested attention through obstacles. Use when beginning a task that feels routine and deserves more than minimum execution, when responses are becoming formulaic, before a complex creative task, or when returning to a long-running project where initial enthusiasm has faded.

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

基于 Miller 与 Rollnick 的动机访谈（MI）：OARS 技术、改变言语以及促进改变准备度。

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

Мотивационное интервью (МИ) по Миллеру и Роллнику: техники OARS, высказывания в пользу изменений, стимулирование готовности к переменам.

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

Entrevista Motivacional (EM) según Miller y Rollnick: técnicas OARS, discurso de cambio y fomento de la preparación para el cambio.

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

ミラーとロールニックに基づく動機づけ面接（MI）：OARS手法、チェンジトーク、変容への準備性の促進。

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

Update pull request titles and descriptions to explain why a change matters and what it changes. Preserve existing images and important details, summarize relevant verification, and describe the correct scope for linked, dependent pull requests.

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

• Rewrite a pull request description before review
• Add the motivation discussed during development
• Remove descriptions of changes that were later undone

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

Creates tailored cover letters from a resume and job description, connecting experience and achievements to the role’s requirements. Adapts tone to the company, addresses qualification gaps, and provides alternative openings and interview talking points.

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

• Writing a cover letter for a specific role
• Explaining transferable skills during a career change
• Addressing gaps in required qualifications

Plan user research, prepare interview guides, and organize findings into themes and recommendations. Choose methods suited to the question, such as interviews, surveys, or usability tests that examine how people use a design.

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

• Planning research into user needs and motivations
• Preparing an interview guide
• Designing usability tests or surveys