Before assessing anyone,
you have to define against what
The job profile is the standard everything else hangs from: the diagnostic, the syllabus, the assessment and the dashboard.
What is a Job Profile in Hypsen?
A job profile in Hypsen defines what a role demands inside a specific company: the tasks it performs, the policies it must know, and the critical situations it has to be able to resolve. Profiles are organized around the company's real structure — units, departments and reporting lines — and serve as the reference the diagnostic measures against, the syllabus is built from, and performance is assessed by.
Most programs are designed around a topic, not a job
A company buys "a sales course." And that course is practically identical for a financial services firm and for a door-to-door sales operation.
The content may be good. The problem is different: nobody can answer whether the person is ready, because it was never defined ready for what.
Without a written standard, "ready" is left to whoever supervises. And that judgment shifts depending on who the supervisor is, how much pressure they're under to fill the operation, and how much they like the person.
Three components, written so they can be measured
What this person does in a day. Not the formal job description, but what actually takes their time and determines their results.
Which company rules they need to know and apply. Prices, restrictions, safety protocols, decision limits.
What they have to be able to resolve when things get hard. The customer who already has service with a competitor. The complaint that escalates. The procedure that has to be executed without skipping steps while someone rushes them.
That third component is what most separates a useful profile from a traditional job description. It's the one that later becomes the assessment simulations.
If you can't observe it, you can't measure it
A profile that says "service attitude" or "results-oriented" is useless for assessing anyone. Two people can read it and score the same employee differently.
A Hypsen profile is written in verifiable behaviors:
“Responds to a complaint without becoming defensive and offers at least one concrete alternative.”
“Identifies the real objection behind what the customer says and addresses it before presenting price.”
Writing it that way is what allows the diagnostic, the voice interview and the simulation to measure the same thing, and makes the result comparable across people and across locations.
Units, departments and who reports to whom
Roles are organized into your company's org structure: units, departments and reporting lines.
That isn't an administrative detail. It's what later allows each manager to see their team and only their team, a regional coordinator to see their managers and those managers' teams, and general administration to see everything.
In operations with several layers — coordinators, managers, supervisors, floor or field staff — that hierarchy is the difference between a usable dashboard and a list nobody can read.
Everything else depends on this
- • A diagnostic that measures against the role's standard, not against a generic syllabus
- • A syllabus that only covers what that role needs, with no filler
- • Simulation scenarios drawn from what that role actually faces
- • A dashboard where "ready" means something concrete: how close that person is to the 10 their role demands