Build your career framework

Creates or updates career tracks, levels and a competency matrix in Effy AI, and proposes a level for each employee.

This skill builds or changes your career framework in Effy AI: the tracks people grow along, the levels on each track, the competency matrix that says what each level looks like, and who sits where. It works from your own employee list, job descriptions, reviews and values, shows every change as a diff, and writes to Effy only after you approve. You don't need to know whether you're building or changing before you start.

When to use it

  • A promotion came up and nobody could say what the next level requires.
  • A review cycle is coming and managers have no shared standard to rate against.
  • Someone refused an offer or left because they saw no path.
  • Your titles grew without a plan and "Senior" means something different in every team.
  • You have a framework and need to add a level, reword an expectation, or move someone.

What you get

A framework that lives in Effy AI, where people are assigned to levels and measured against them:

  • Tracks: one per function, each with one ladder. Individual-contributor and management levels are separate sequences.
  • Levels: named with the titles people already have, sized to your headcount. Roughly three to four levels per track under 50 people, four to five from 50 to 200, five to six above that.
  • A competency matrix: six to ten competencies per track, with two or three observable expectations per level.
  • Four extras per level: promotion signals, anti-patterns, growth opportunities including at least one sideways move, and assignment criteria with explicit exclusions.
  • Proposed assignments: a track and level for each employee in scope, with the evidence behind it.

Anything inferred is marked (assumption). Without Effy AI, the approved framework is delivered as a spreadsheet and assignments are skipped.

How it works

  1. It asks about the task. Which company, how big, what scope (one department, the whole company, or one narrow change), and what triggered this. The trigger tells it which part has to be sharp.
  2. It reads what's in Effy and picks the path. Build when nothing covers the scope, change when something does.
  3. It asks for inputs and researches the company. The employee list with titles, previous reviews, job descriptions, values, and any old ladder. It searches your connected tools before asking, and looks the company up publicly for context.
  4. To build, it proposes tracks and levels first. A table of tracks and levels with how many current employees land at each, and the competency names. It waits for approval.
  5. It writes the edges, then the middle. The lowest and highest levels come first, so you can correct the range before it fills in the rest. A framework you corrected while it was built is one you'll defend later.
  6. It saves in order, verifies, then proposes assignments. Thin evidence gets "no proposal, needs manager input", not a guess.
  7. To change, it shows each change as a diff with its consequence: how many people hold a level being edited, or what is lost on a delete. It pushes back once if the change has a flaw.

How it writes expectations. Each cell has to pass two tests. Could two managers looking at the same work disagree about whether it's met? Can you say what changed from the level to its left? A cell that differs from its neighbour only in adverbs is not a level up.

What it never does. Nothing is written to Effy before you approve it. "Looks fine" is not approval. It doesn't invent an expectation, and it asks a second time before any delete, because there is no undo. It doesn't assign anyone to a level without your explicit yes: an assignment is the standard that person is measured against from that day.

How to run it

Install the Effy AI plugin for Claude or ChatGPT. One install adds every Effy AI skill, this one included. Then connect the tools you want the skill to read from, such as email, calendar, your drive or your meeting notetaker, and ask for what you need in plain words: the assistant picks the right skill.

Before you start: have your employee list with titles and departments, job descriptions, last cycle's reviews and your values to hand, or connect the tools where they live.

  1. Ask, for example: "Effy, create a career framework."
  2. Answer the scope questions and share the inputs.
  3. Approve the tracks and levels, then the content, then the assignments.

Once people are on a track, the "Build a growth plan" skill uses their level and the next one as its starting point.

Click. Try. Use.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.