「judgment」の検索結果

Use when a task needs the judgment of an ICU/critical care RN — titrating a vasoactive drip within an ordered range and deciding when to escalate to a second agent, coordinating daily sedation-awakening and spontaneous-breathing trials on a ventilated patient, interpreting a hemodynamic/lactate trend against a resuscitation target, or working the ABCDEF bundle to prevent post-ICU complications.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a dental hygienist — full-mouth periodontal charting and staging, sequencing scaling and root planing across quadrants, deciding whether a finding needs escalation back to the dentist, or building a home-care compliance plan for a patient with active periodontal disease.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Coil Winder, Taper, or Finisher — cross-checking a mechanical turn counter against an independent method rather than trusting it blindly, maintaining wire tension within a specified range rather than by feel, avoiding wire handling that risks invisible insulation damage, or performing post-winding electrical testing rather than relying on visual/mechanical inspection alone.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Communications Teacher, Postsecondary — designing or norming a multi-section basic public-speaking course, resolving a cross-rater grading discrepancy on a speech rubric, screening for and accommodating communication apprehension, or choosing a rhetorical-criticism method for a media-analysis assignment.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer Numerically Controlled (CNC) Tool Programmer — calculating stepover from a scallop-height/surface-finish spec instead of picking one by feel, deciding whether a toolpath needs a dry run before cutting material on an unfamiliar post-processor/machine pairing, verifying datum consistency across multiple part setups, or diagnosing why cycle time jumped after a "minor" parameter change.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Clinical Research Coordinator — managing patient recruitment/enrollment against a trial's screen-fail rate, handling a protocol deviation, tracking informed consent and regulatory documentation, or coordinating a multi-visit study schedule against patient retention risk.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Clinical Nurse Specialist — diagnosing why a unit-level outcome metric (CLABSI, falls, pressure injury) is off benchmark, designing and scaling a practice-change pilot, appraising whether a new clinical guideline actually fits the local population, writing a quarterly outcomes report to nursing leadership, or coaching staff nurses through a new protocol without formal authority over them. US hospital/health-system default; state nurse practice acts vary. A reasoning aid, not clinical or legal advice.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a correctional officer or jailer — scoring an inmate-classification instrument, deciding a use-of-force response level, running a cell/contraband search, preparing evidence for a disciplinary hearing, or screening an inmate for suicide/mental-health crisis risk.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a CNC Tool Operator — diagnosing a dimension trending toward its tolerance limit across consecutive parts before it actually crosses, deciding whether to apply a tool wear offset or flag the tool for replacement, evaluating whether a failed part traces to work-holding repeatability versus a program or tool issue, or verifying a setup change with a first-article inspection before running production quantity.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Continuous Mining Machine Operator in underground coal — reading a methane monitor trend and deciding whether to de-energize, judging whether cumulative unbolted advance has hit the roof control plan's cut-depth limit, deciding whether a permissibility defect requires immediate shutdown in a gassy heading, diagnosing whether a shift's production shortfall traces to cutting rate or shuttle-car haulage, or deciding whether a "drummy" roof sound stops the cut.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a construction laborer — determining which OSHA-mandated protective system (sloping, benching, shoring, or shielding) a trench needs given its soil classification and depth, working as spotter/signal person on a crane or heavy-equipment lift, staging material and equipment on an active multi-trade site, or reading which hazard zone (excavation, crane swing, electrical rough-in) is live as work moves across the site.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a systems engineer/architect working at the whole-program level — decomposing requirements across hardware/software/network subsystems, writing or reviewing an interface control document (ICD), making a build-vs-buy tradeoff for a subsystem, or tracing a verification failure back through the requirements baseline. Distinct from a software engineer (owns one service's code) or DevOps/SRE (owns operational reliability) — this role owns the technical baseline for a whole system-of-systems and is accountable when subsystems built by different teams or vendors don't fit together.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer Systems Analyst — running requirements elicitation and gap analysis against a target system, writing a feasibility study for a build-vs-buy-vs-customize decision, designing a system integration approach (point-to-point vs middleware vs API-led), scoping data-migration risk before a cutover, or choosing between phased and big-bang implementation strategies.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Postsecondary Computer Science Professor — diagnosing why a course's DFW (D/F/withdraw) rate spiked, redesigning an intro programming course's assessment structure, staffing TAs and grading load for a large course, deciding what to prioritize pre-tenure, running an academic-integrity (MOSS similarity) investigation, or mapping a curriculum change against ABET student outcomes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a computer programmer implementing to a given specification — translating a design/pseudocode/systems-analyst spec into working code in a specified language, flagging spec ambiguity before writing code, maintaining or modernizing an existing codebase against its original contract, or writing unit tests that prove the implementation matches the spec (not designing the system the spec describes).

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer and Information Systems Manager (IT Manager/Director/CIO-adjacent) — planning IT infrastructure and systems strategy, evaluating a technology vendor or platform decision, allocating an IT budget, or managing IT risk (security, uptime, technical debt) at an organizational level. Broader than the devops-sre or software-engineer roles — this one owns IT as a business function, not a specific engineering discipline.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer and Information Research Scientist — designing an ablation to attribute an empirical gain, budgeting an NSF CISE proposal against page and content limits, deciding what reproducibility artifacts to release with a paper, screening a draft for mathiness or terminology misuse, or scoping the consent/ethics review needed before running an experiment on real users.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a court, municipal, or license clerk — checking a pro se filing for procedural completeness, calculating a court filing fee or fee-waiver eligibility, processing a license or permit application against an eligibility checklist, determining whether a case record is public or sealed, or making a docket entry.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a courier or messenger — sequencing a multi-stop route against hard delivery windows, deciding what proof-of-delivery a shipment requires, handling a chain-of-custody transfer for a legal or medical item, or resolving a refused-delivery/no-answer exception against the sender's fallback instructions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer Hardware Engineer — designing a power delivery network and selecting decoupling capacitors for a digital IC's core rail, budgeting a high-speed signal's rise time against trace impedance and via stub length, closing static timing on a board-level DDR or SerDes interface, sizing thermal resistance for a package's TDP, or reviewing a PCB layout for signal- or power-integrity risk before fab release.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Costume Designer — deciding build vs. rent vs. buy for a specific garment, budgeting a production's costume-shop spend across principals and ensemble, engineering a quick-change to hit a scripted time window, building or reading a costume plot to track pieces across a run, or diagnosing why a build is behind schedule going into tech week.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a costume attendant/dresser — planning or timing a quick change, building a costume plot or track sheet, deciding a laundry/repair rotation, assigning dresser-to-actor ratios for a scene, or diagnosing why a costume is failing onstage.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Cost Estimator — building a conceptual (Class 5) budget from a napkin sketch, developing a hard-bid estimate from complete construction documents, leveling subcontractor bids before award, making a bid/no-bid call on an RFP, or reconciling a design-development estimate against an owner's target budget.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Correspondence Clerk — selecting and customizing a template response to a standardized written inquiry, triaging a correspondence queue against SLA deadlines, deciding when a form letter suffices versus needs escalation, or auditing a response-template library for staleness.

日本語の概要は準備中です。原文の説明を表示しています。