Dadmin88/hermes-agency - 10ページ

performance-profiling

Profile system performance using representative workloads, time/resource attribution, traces, profilers, query plans, and repeatable evidence to locate where execution cost actually accumulates.

原文の言語: 英語

developer-experience

Improve developer experience by measuring the path from intent to working change, locating friction, reducing unnecessary cognitive load, and validating improvements with real users and delivery evidence.

原文の言語: 英語

golden-path

Create and maintain a paved or golden path that turns an approved common workload pattern into a secure, observable, supportable, self-service default without blocking justified exceptions.

原文の言語: 英語

internal-platform-design

Design an internal platform around repeated consumer needs, explicit service boundaries, self-service contracts, tenancy, policy, lifecycle, reliability, and sustainable ownership.

原文の言語: 英語

platform-adoption

Drive and evaluate internal platform adoption through consumer segmentation, migration paths, enablement, incentives, feedback, support data, and evidence that the platform produces better outcomes than existing alternatives.

原文の言語: 英語

platform-capability

Design and deliver an internal platform capability with a clear consumer contract, paved path, self-service interface, reliability expectations, and operational ownership.

原文の言語: 英語

platform-observability

Make an internal platform observable from the consumer and operator perspectives by connecting platform requests, provisioning, policy, runtime health, dependencies, errors, and adoption signals.

原文の言語: 英語

service-template

Design a maintainable service or workload template that captures approved defaults without freezing consumers to stale generated code, hidden infrastructure assumptions, or unsafe credentials.

原文の言語: 英語

consent-preference-engineering

Design and validate consent or preference controls with explicit purpose, state, provenance, propagation, revocation, and downstream enforcement.

原文の言語: 英語

data-minimization-review

Reduce personal-data collection and persistence to what is necessary for approved product purposes while preserving required functionality and evidence.

原文の言語: 英語

privacy-data-flow-map

Map personal and sensitive data from collection through use, storage, logs, analytics, sharing, export, backup, retention, and deletion with purpose and ownership.

原文の言語: 英語

privacy-threat-model

Threat-model privacy harms including overcollection, linkage, inference, unauthorized secondary use, excessive retention, disclosure, re-identification, and abusive insider/tool access.

原文の言語: 英語

retention-deletion-engineering

Implement retention and deletion across primary stores, derived data, indexes, logs, queues, caches, exports, backups, and external processors with verifiable completion.

原文の言語: 英語

negotiation-prep

Prepare a procurement negotiation from objectives, leverage, evidence, alternatives, tradeable terms, approval limits, and fallback positions without inventing authority.

原文の言語: 英語

procurement-risk

Assess procurement risk across vendor viability, security, privacy, legal terms, concentration, implementation, continuity, data portability, support, and exit conditions before commitment.

原文の言語: 英語

rfp

Build a request for proposal that defines business need, scope, requirements, response format, evaluation criteria, evidence, commercial context, timeline, and process so vendors compete on comparable outcomes.

原文の言語: 英語

total-cost-analysis

Compare procurement options using total lifecycle cost across price, implementation, integration, migration, training, support, infrastructure, usage growth, switching, exit, and internal operating effort rather than sticker price alone.

原文の言語: 英語

vendor-evaluation

Evaluate vendors or tools against requirements, total cost, security, operational fit, contractual constraints, and switching risk.

原文の言語: 英語

accessibility-design

Design product experiences with accessible information hierarchy, semantics, input methods, focus behavior, visual adaptations, content alternatives, and recovery patterns before implementation.

原文の言語: 英語

developer-handoff

Hand product design to engineering with complete flows, states, responsive and accessibility behavior, component intent, assets, content, constraints, and explicit open decisions while preserving implementation ownership.

原文の言語: 英語

interaction-design

Design interaction behavior for a product feature by mapping user intent, controls, feedback, navigation, direct manipulation, interruptions, errors, and platform conventions into a coherent usable flow.

原文の言語: 英語

product-flow-design

Design an end-to-end product flow from user goal through information architecture, states, interactions, errors, accessibility, and implementation handoff.

原文の言語: 英語

prototype-plan

Plan a prototype around a specific design or product uncertainty, selecting the minimum fidelity, scope, participants, scenarios, evidence, and success criteria needed to inform a decision.

原文の言語: 英語

state-design

Design complete product UI states and transitions for normal, empty, loading, permission, validation, error, offline, interrupted, and recovery conditions so the experience remains coherent beyond the happy path.

原文の言語: 英語

acceptance-criteria

Define acceptance criteria as observable product behavior, states, permissions, boundaries, errors, and outcomes that design, engineering, and QA can interpret consistently without prescribing unnecessary implementation.

原文の言語: 英語

prioritization

Prioritize competing product work using explicit outcomes, evidence, urgency, confidence, effort and opportunity cost without treating scoring frameworks as objective truth.

原文の言語: 英語

product-discovery

Reduce product uncertainty before major commitment by framing the problem, identifying risky assumptions, gathering user and market evidence, testing solution hypotheses, and deciding what to build or learn next.

原文の言語: 英語

product-requirements

Turn a product problem into scoped requirements, user outcomes, constraints, acceptance criteria, exclusions, and decision-ready tradeoffs.

原文の言語: 英語

release-scope

Define the smallest coherent product scope for a release by protecting the intended outcome, separating must-have behavior from follow-up work, and making exclusions, dependencies, risks, and acceptance explicit.

原文の言語: 英語

roadmap-decision

Make roadmap decisions by connecting product outcomes, evidence, sequencing, dependencies, capacity, uncertainty, and explicit commitments.

原文の言語: 英語

competitive-battlecard

Produce a concise competitive battlecard focused on customer decision criteria, verified differences, proof, traps to avoid, and honest fit boundaries.

原文の言語: 英語

icp-use-case-definition

Define an ideal customer profile and prioritized use cases from verified customer problems, buying context, alternatives, and product capability.

原文の言語: 英語

launch-messaging-package

Build a launch messaging package that turns shipped capability into audience-specific narrative, proof points, FAQs, objections, and channel-ready message hierarchy.

原文の言語: 英語

product-positioning-brief

Create a product positioning brief that distinguishes target customer, category/frame, problem, differentiated value, proof, alternatives, and intentional tradeoffs.

原文の言語: 英語

sales-enablement-kit

Create sales and solutions enablement with discovery cues, value narrative, technical proof, objection responses, competitive context, and qualification boundaries.

原文の言語: 英語

product-decision-records

Maintain product decision records with problem, evidence, options, owner, rationale, expected outcome, dependencies, revisit conditions, and downstream communication.

原文の言語: 英語

product-feedback-operations

Operate a feedback loop that aggregates qualitative and quantitative product signals, preserves provenance, identifies recurring themes, and routes them into discovery/decision processes.

原文の言語: 英語

product-intake-system

Design a product intake system that captures requests/feedback with source, problem, evidence, affected users, urgency, duplication, owner, and disposition without turning every request into roadmap work.

原文の言語: 英語

product-operating-rhythm

Design a product operating rhythm that coordinates discovery, prioritization, delivery review, launches, metrics, feedback, and decision follow-through with minimal ceremony.

原文の言語: 英語

product-process-health

Measure and improve product-process health through intake age, decision latency, discovery evidence, roadmap churn, launch readiness, feedback closure, and cross-team rework.

原文の言語: 英語