Receber por email
← Voltar para o catálogo

outcome-orientation

Reframe work around measurable outcomes using OKRs, KPIs, and the outcome-vs-output distinction. Use when the user asks to define success criteria, write OKRs, set KPIs, clarify what "done" means in terms of impact, distinguish outputs from outcomes, or make a goal statement measurable and time-bound. NOT for ranking or scoring features by priority (use prioritization). NOT for systemic feedback-l

9estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add viktorbezdek/skillstack

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/outcome-orientation/svg)](https://www.skillteca.com.br/skills/outcome-orientation)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Outcome Orientation

Focus on results that matter, not just activities completed. Outputs are what you produce. Outcomes are what changes as a result. Impact is the business-level change that outcomes drive. Most teams measure outputs because they're easy to count; measuring outcomes requires defining what "better" looks like before you start.

When to Use

  • Defining success criteria for a project, initiative, or feature
  • Writing OKRs (Objectives and Key Results)
  • Setting KPIs for a team

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn