분기 목표와 핵심 결과를 한눈에 보는 HTML 화면을 시제품으로 만듭니다. 진행 막대, 담당자, 상태를 표시하고 주요 지표와 진행을 막는 문제를 옆에 정리합니다.
- 팀의 분기 목표 화면을 시제품으로 만듭니다
- 핵심 결과의 현재 값과 목표 값을 비교합니다
- 목표 담당자와 진행 상태를 함께 표시합니다
171건 · 관련도순
분기 목표와 핵심 결과를 한눈에 보는 HTML 화면을 시제품으로 만듭니다. 진행 막대, 담당자, 상태를 표시하고 주요 지표와 진행을 막는 문제를 옆에 정리합니다.
Draft three alternative sets of team OKRs, pairing a qualitative goal with three measurable results. Use company strategy and team context to propose numerical targets, explain each option, and support discussions about quarterly priorities and customer or business outcomes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and update OKRs in Lark: objectives and the key results used to measure them. Track numeric progress, record written updates, review relationships between objectives, and adjust their order, weights, deadlines, and comments.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Knowledge base from NASA-STD-8729.1A — NASA's R&M (Reliability and Maintainability) standard covering spaceflight and support systems (Revision A, 2017-06-13). Use for NASA's objectives-driven R&M framework — the R&M objectives hierarchy (one Top Objective decomposed into four sub-objectives, paired with tailorable strategies), how R&M requirements are established inside the SMA Plan required by NPR 7120.5, the SMA Technical Authority concurrence/independent-evaluation governance, milestone vs. readiness review gates, the reliability/maintainability/availability vocabulary (Ai vs. Ao, the failure causal chain, risk as a triplet), and the R&M Evidentiary Methods catalogue (FMEA/FMECA, FTA, RBDA, RCM, LORA, plus the space-environment and parts-pedigree analyses). Scoped to NASA spaceflight and support systems and to assurance planning: it is an objectives-and-strategies standard, so it deliberately does NOT prescribe step-by-step analysis procedures (those live in the referenced NASA Preferred Reliability Practices) and is thin on facility R&M, detailed math/derivations, and non-NASA or commercial life cycles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Help quality leaders at medical technology companies prepare management reviews, define quality objectives, and track performance indicators. Organize audit findings, complaints, corrective actions, and regulatory status into reports and assigned improvement actions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a team OKR tracking page, showing objectives and their measurable results. Arrange three objectives with progress bars, values, owners, and status labels, alongside a quarterly summary that makes progress easy to review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Bloom's Taxonomy of Educational Objectives and mastery learning as practical instructional design tools. Covers the six cognitive levels (remember, understand, apply, analyze, evaluate, create), the revised 2001 taxonomy, the knowledge dimension, mastery learning loops, formative vs. summative assessment, and the writing of learning objectives that are both specific and verifiable. Use when designing lessons, writing objectives, building assessments, or diagnosing why a learner is stuck at one cognitive level.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"Apply Bloom's revised taxonomy to classify learning objectives and design assessments across six cognitive levels. Use this skill when the user needs to write learning objectives at specific cognitive levels, align assessment with instructional goals, or evaluate curriculum for cognitive complexity distribution — even if they say 'how to write learning objectives', 'what level of thinking does this require', or 'higher-order thinking skills'.".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
며칠에서 몇 주에 걸친 목표를 단계별로 나누고 대화가 바뀌어도 진행 상황과 발견을 기록합니다. 매번 할 일을 계획하고 일정 지연과 초기 범위의 변화를 확인합니다.
Plan and measure defensive deception operations with MITRE Engage. Connect decoy systems and credentials to specific attacker techniques, define measurable objectives, and document operating boundaries, response procedures, and criteria for assessing results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Support team leadership with daily progress reports, meeting preparation, weekly summaries, and tasks drawn from email. Share updates in Google Chat and track team objectives and measurable results in a shared spreadsheet.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn user stories and acceptance criteria into detailed test scenarios. Define objectives, starting conditions, user roles, actions, and observable results, including invalid inputs and boundary cases, so a quality assurance team can carry out the checks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build course and workshop slides that keep learning objectives visible on the left. The deck includes concepts with examples, multiple-choice self-check questions, a wrap-up, and a preview of the next module, with warm paper tones and Playfair typography.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and test combat encounters in Three.js action games. Plan arenas, enemy roles, spawn timing, objectives, boss phases, and rewards, then check fairness and difficulty using repeatable starting conditions on desktop and mobile.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or revise Three.js game levels with movement kept on one flat plane. Organize routes, collision, encounters, objectives, and lighting, then verify visibility, traversal, reset behavior, and controls through desktop and mobile browser playthroughs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan and coordinate penetration tests with checklists covering objectives, scope, environment preparation, tester selection, monitoring, and follow-up. Helps teams define deliverables, prioritize vulnerabilities, arrange fixes and verification, and clean up test accounts and artifacts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Expert blueprint for quest tracking systems (objectives, progress, rewards, branching chains) using Resource-based quests, signal-driven updates, and AutoLoad managers. Use when implementing RPG quests or mission systems. Keywords quest, objectives, Quest Resource, QuestObjective, signal-driven, branching, rewards, AutoLoad.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert blueprint for quest tracking systems (objectives, progress, rewards, branching chains) using Resource-based quests, signal-driven updates, and AutoLoad managers. Use when implementing RPG quests or mission systems. Keywords quest, objectives, Quest Resource, QuestObjective, signal-driven, branching, rewards, AutoLoad.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Python framework for single- and multi-objective optimization with evolutionary algorithms. Define vectorized objectives and constraints; solve with NSGA-II, NSGA-III, MOEA/D, GAs, or differential evolution. Analyze Pareto fronts, visualize trade-offs, customize operators and callbacks. For engineering design, hyperparameter search, and conflicting objectives. Alternatives: scipy.optimize (single-objective, gradient), platypus, jMetalPy (Java).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates structured OKR plans (Objectives and Key Results) for teams and companies following Google/Intel methodology. Takes company goals, team function, quarter, and current metrics to produce a comprehensive okr-plan.md with objectives, key results, scoring criteria, alignment mapping, tracking cadence, and retrospective templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organizational strategy and management theory for business decision-making. Covers objectives-based management, the knowledge-worker firm, decentralization, the five management tasks, strategy-as-practice, managerial roles, and the distinction between efficiency and effectiveness. Use when structuring an organization, setting objectives, allocating decision rights, or critiquing a strategy document.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a company needs recovery objectives it can defend, before a continuity plan, a disaster recovery design, an audit or a resilience review, and asks "do a BIA", "business impact analysis", "set our RTO and RPO", "what is our maximum tolerable downtime", "which services are critical", "impact tolerance" or "can our backups meet our recovery targets". Lists services from the customer's view, prices an outage over time in the company's own money and obligations, sets recovery time and data loss objectives, maps dependencies, and compares each objective with what backups, restore tests, suppliers and people actually allow, listing the gaps for a decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Distinguishing aims, objectives, hypotheses, and milestones — the hierarchy that keeps proposals logically tight.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.