Keeps production assets available — ranking equipment by consequence of failure, setting preventive and predictive intervals, sizing spares, and moving a plant off reactive maintenance. Use this to build or fix a maintenance program, decide what to put on a PM schedule, diagnose repeat failures on one asset, justify spares inventory, or work out why a plant that maintains everything still has unplanned downtime.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing a set of skills for overlap. Also use before adding to a skill library, to check the capability is not already covered.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Builds questions and assessments that measure what they claim — matching item type to the thing being assessed, writing distractors that diagnose, and telling a question that measures learning from one that measures reading speed or test-taking. Use this to write or review assessment items, design a unit check or diagnostic, work out why scores do not match classroom performance, or decide how much evidence a claim about mastery actually needs.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Negotiates a commercial deal without giving away the terms that matter — preparing your walk-away and theirs, trading concessions rather than conceding them, recognizing the tactics that create false urgency, protecting price by moving other variables, and closing on terms someone can actually deliver. Use this to prepare for a negotiation, respond to a demand mid-deal, work out why discounts keep landing at quarter end, or review terms before they are signed.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Designs quotas, territories and commission plans that produce the behavior the business needs — sizing territories against real potential, setting quotas people can hit often enough to believe in, choosing what to pay on, handling accelerators, draws, clawbacks and disputes, and changing a plan without destroying trust. Use this to build or fix a comp plan, allocate territories, work out why reps are chasing the wrong deals, or plan a mid-year change.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished, and sequencing changes by impact. Use this when a product works but looks dated or default, when a redesign is being considered, when deciding whether to restyle or rebuild, or when a screen needs to look substantially better with limited effort.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and the follow-up that actually gets replies. Use this to build a prospect list, write cold outreach, fix a sequence that is not getting responses, define qualification criteria, or decide whether a segment is worth pursuing.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfillment reliability, or assess concentration risk in a supply base.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one you have been handed, work out why estimates keep coming in low, or decide how much reserve a portfolio actually needs.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Runs the pay cycle so it is right, on time, and provable — the calendar and cutoffs, what feeds pay from the HRIS and time systems, gross-to-net and the deductions in it, multi-jurisdiction registration and tax filing, off-cycle payments and corrections, and the reconciliation to the general ledger. Use this to design or audit a payroll process, work out what happens when someone is paid wrong, or understand what changes when you hire in a new state or country.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0802026年10月19日 更新