Career Progression Framework

The flagship PlayBooker offering is a competency-based career progression framework — not a list of role descriptions, and not a one-size-fits-all ladder. It is a library of reusable competency blocks that organizations compose into the levels and tracks that match their structure.

How it is structured

Each competency block contains four explicit layers:

• Competency — the capability area being assessed.
• Outcomes — what “good” looks like for this competency at a given level.
• Activities & behaviours — the observable things people actually do.
• Levels — capability ratings calibrated across the catalogue.

Blocks are versioned and have stable identifiers. Customizations layer on top without forking the source, so updates remain safe to adopt.

Why competency-based

Role descriptions go stale the moment a team reorganizes. Competencies survive reorganizations. They let the same block — for example, driving quality through code review — appear in an Engineer II, a Senior Engineer, and a Tech Lead expectation set, calibrated to a different level each time.

The result:

• Coaching has shared vocabulary across managers and reports.
• Promotion decisions cite specific behaviours, not impressions.
• Growth plans target named competencies with concrete next-level outcomes.
• Reorganizations don’t invalidate the framework — only the composition.

Sample competencies

The launch catalogue ships with foundational engineering and leadership competencies, including:

• Continuous improvement. Spotting waste, proposing change, measuring whether change worked.
• Scrum & Agile rituals. Participating effectively in planning, standups, retros, and reviews.
• High-level design. Writing design documents that surface trade-offs and align reviewers.
• Quality discipline. Driving quality through code review, testing, and operational readiness.

Each competency arrives with leveling guidance, recommended behaviours, and prompts you can hand to managers running 1:1s and growth conversations.

Customization

Out of the box you can:

• Rename levels (Engineer II → Intermediate Engineer).
• Swap tool references (Jira → Linear, Slack → Discord).
• Toggle competencies in or out per track.
• Add organization-specific competencies on top of the baseline.
• Inject internal links, owners, and escalation contacts.

The customization surface is intentionally narrow at launch — a small number of high-value variables and toggles — and expands based on what real customers actually need.

What you receive

A versioned package containing:

• The full competency library with leveling guidance.
• A starter set of role expectations composed from those competencies.
• Manager-facing prompts for coaching, calibration, and promotion conversations.
• Outputs in formats that publish cleanly into Confluence or a Markdown wiki.

Updates ship as new versions with changelogs, so adopting an improvement later doesn’t mean rewriting your customizations.