Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Analiza

work-analysis

/work-analysis

Prowadzi analizę stanowiska pod dobór kadr: określa kompetencje, wymagania KSAO i kryteria zgodne z rzeczywistą pracą.

Licencja
MIT
Ostatnia zmiana repozytorium
01.06.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 01.06.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Prowadzi analizę stanowiska pod dobór kadr: określa kompetencje, wymagania KSAO i kryteria zgodne z rzeczywistą pracą.

Wyzwalacze z opisu

job analysiswork analysisdefine KSAOs/competenciescompetency modelwhat should the test measureidentify the criteria for this jobSME workshop
Oryginalny opis (EN)

Use when analyzing work to support a selection effort — to identify worker requirements (KSAOs/competencies), define the work content domain, or develop job-relevant criteria. Covers choosing methods, level of detail, SME sampling, competency modeling, and documenting results. Triggers: "job analysis", "work analysis", "define KSAOs/competencies", "competency model", "what should the test measure", "identify the criteria for this job", "SME workshop".

Jak działa

  1. Two purposes — be clear which you're serving
  2. Level of detail — match it to the use
  3. Constructs vs. methods (frame the requirements correctly)
  4. Process
  5. Competency modeling — when it counts as work analysis
  6. Pitfalls
  7. Checklist
  8. See also
Sekcje z nagłówków SKILL.md, w oryginale · 94 linii, 756 słów
Podgląd SKILL.md
---
name: work-analysis
description: >-
  Use when analyzing work to support a selection effort — to identify worker
  requirements (KSAOs/competencies), define the work content domain, or develop
  job-relevant criteria. Covers choosing methods, level of detail, SME sampling,
  competency modeling, and documenting results. Triggers: "job analysis",
  "work analysis", "define KSAOs/competencies", "competency model", "what should
  the test measure", "identify the criteria for this job", "SME workshop".
version: "1.0.0"
author: OpenMatter-Network
license: MIT
category: research
tags: ["Community", "io-psychology", "personnel-selection"]
permissions: []
---

# Analysis of work

"Analysis of work" is the *Principles*' umbrella term for what has been called job analysis, work
analysis, and competency modeling. It is the empirical foundation that links a selection procedure
to the job. Most other validation strategies depend on it.

## Two purposes — be clear which you're serving

1. **Define worker requirements (predictors).** Identify the KSAOs/competencies workers need to be
   successful, and how similar requirements are across settings or job families.
2. **Develop criteria.** Assemble the information needed to understand the work, its setting, and
   the organization's goals so you can build relevant, uncontaminated criterion measures.

A single analysis can serve both, but design it deliberately for the purpose(s) at hand.

## Level of detail — match it to the use

The required detail depends on the intended use and the availability of existing information.
- **Less detail** may suffice when prior research lets you generalize requirements across a job
  family, or when an indicator's relevance is self-evident (e.g., absenteeism, turnover are
  relevant to virtually all jobs).
- **More detail** is needed when little work information exists, or when you intend to develop
  predictors of **specific job knowledge** (content-based work especially).

There is **no single preferred method**. Choose methods based on the nature of the work, the
organizational setting, the workers, and the study's purpose, informed by the research literature.

## Constructs vs. methods (frame the requirements correctly)

Distinguish **what is measured** (the predictor *construct*, e.g., general mental ability,
conscientiousness, job knowledge) from **how it is measured** (the *method*, e.g., interview, work
sample, test). Confounding the two (e.g., "the interview" as if it were a construct) produces
uninterpretable comparisons later. Define requirements at the construct level where possible.

## Process

1. **Scope the work domain.** Work complexity, environment, context, tasks, behaviors, activities,
   and worker requirements. Decide which dimensions of work matter for your purpose.
2. **Choose methods** appropriate to the work and purpose (e.g., observation, interviews,
   questionnaires, critical incidents, task inventories, existing documentation, O*NET, competency
   modeling). Any method used should be understood by participants and have reasonable psychometric
   properties; note and investigate lack of SME consensus.
3. **Plan the SME sample.** Include incumbents/SMEs spanning relevant shifts, locations, equipment,
   software, experience levels, and demographics. A broad, representative SME sample increases the
   representativeness of results. Don't assume same job title = same work — study multiple
   incumbents when complexity, context, or behaviors may differ.
4. **Vet existing documentation.** Existing job descriptions and prior analyses may or may not serve
   the current purpose; evaluate relevance and currency before relying on them.
5. **Account for changing work.** When work is being transformed (or the job doesn't exist yet),
   obtain reliable, relevant information about *anticipated* behaviors, activities, and
   KSAOs/competencies. Reanalyze when the nature of work has changed meaningfully since any prior
   analysis.
6. **Derive worker requirements and/or criterion content.** Translate work information into
   KSAOs/competencies (for predictors) and into work behaviors/outcomes (for criteria).
7. **Document** methodology, data collection, analyses, results, and implications — including the
   major work activities, important worker requirements, and their relationships to selection
   procedure content and scoring. Feeds the `technical-validation-report`.

## Competency modeling — when it counts as work analysis

Competency models are widely used (for training, selection, compensation, signaling aspirational
goals). A competency model can serve as the foundation for content-oriented or other validation
**only if it is detailed and rigorous** — i.e., built like a rigorous work analysis, not a list of
aspirational labels. You must judge whether the model is rigorous enough to support the intended
inference. (See Campion et al., 2011, on best practices.)

## Pitfalls

- Letting a glossy competency model substitute for a rigorous analysis when content evidence rests
  on it.
- Grouping dissimilar jobs under one title and analyzing them as if homogeneous.
- Defining requirements as methods ("we need interviewing") instead of constructs.
- Using stale job descriptions for rapidly changing work.
- Insufficient/biased SME sampling.

## Checklist

- [ ] Purpose (predictor requirements, criterion development, or both) stated
- [ ] Level of detail justified by the intended use
- [ ] Methods chosen and rationale recorded; psychometric quality considered
- [ ] SME sample spans relevant subgroups, shifts, locations, experience
- [ ] Requirements expressed as constructs (KSAOs/competencies), not methods
- [ ] Changing/future work accounted for if relevant
- [ ] Results documented and linked to selection procedure content and/or criteria

## See also

`validation-planning` (upstream) · `content-based-validation` and `criterion-related-validation`
(downstream consumers) · `technical-validation-report`

*Source: Principles (5th ed., 2018), "Overview → Analysis of Work" and "Operational Considerations
→ Understanding Work and Worker Requirements."*
Pliki w paczce (2)
  • README.md 1 KB
  • SKILL.md 6 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · openmatter-network/agent-io-skills90MIT
dmzoneill/skills90Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki eec34ffc6c9b (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100content-based-validation
    Buduje dowody trafności treściowej procedury selekcji, łącząc jej treść z dziedziną pracy: definiuje domenę, kwalifikacje ekspertów SME, próbkowanie, wierność, modele kompetencji i ocenę dowodów.
  • 100hr-competency-management
    Pomaga projektować i stosować modele kompetencji w rekrutacji, ocenie okresowej, szkoleniach i sukcesji: biblioteka kompetencji, wskaźniki behawioralne i integracja z ocenami.
  • 90hr-job-analysis
    Przeprowadza analizę stanowisk: definiuje wymagania, opisuje zadania i klasyfikuje role na potrzeby wynagrodzeń.
  • 100artemis-competencies
    Tworzy i przegląda kompetencje kursu w Artemis oraz relacje między nimi w postaci grafu, na podstawie materiałów zajęć.
  • 100competency-matrix
    Tworzy macierz kompetencji z oczekiwanym poziomem biegłości dla stanowiska i grade, metodą oceny i powiązanym obszarem umiejętności, do ram ról i progów rekrutacyjnych.
  • 100competency-matrix
    Tworzy macierz kompetencji z oczekiwanym poziomem biegłości dla stanowiska i grade, metodą oceny i powiązanym obszarem umiejętności, do ram ról i progów rekrutacyjnych.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.