Receber por email
← Voltar para o catálogo

pareto-principle

Isolate the 20% of inputs driving 80% of results, and explicitly name what you're deprioritizing. Outputs a blockquote (vital 20%) plus a list (deprioritized 80%). Use for ruthless prioritization, "what should we focus on", or step 4 of a strategic analysis.

6estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add ConrayGambit/Strategy-Consultant-5-Consulting-Frameworks

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/pareto-principle/svg)](https://www.skillteca.com.br/skills/pareto-principle)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 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

Pareto Principle (80/20)

Concept

In most systems, ~80% of the outcome comes from ~20% of the inputs. Strategy consultants use this constantly: figure out which 20% of customers, products, channels, or root causes drive the lion's share of impact, and ignore the rest until later.

The discipline isn't naming the vital 20%. It's having the spine to explicitly deprioritize the 80%. If everything is important, nothing is.

Required output format

Two parts, in this order:

  1. A Markdow

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

Compartilhar X LinkedIn