LEVELWORK
Org charts, role descriptions, job profiles. Written at one moment, then filed.
Meanwhile the work moves. Someone quietly takes on the thing nobody else will. A departure gets absorbed instead of replaced. A new tool changes what a role even means. None of it is written down anywhere, because nobody ever measures a second time.
Within two years the document and the work have little left in common. And every decision about people is still made from the document.
The role is defined. Document and reality agree.
First tasks arrive that were never in the profile. Nobody objects, so nobody records it.
A colleague leaves. The work is redistributed in conversations, not in documents.
Hiring, training and restructuring decisions rest on a profile that describes almost nobody.
Approval for aviation, automotive and defence supply requires a register of the workforce: job title, competencies, planned training. For the production roles the standard scheme produced it. For the digital team it produced nothing usable. The matrices had to be written by hand.
A media house merged four advertising units into a single digital agency. 124 people. Before anything could be designed, one question had to be answered: who is actually here, what do they really do, where does knowledge sit, where does authority sit, and where is there room to move.
It was answered the only way that question can be answered: by talking to people. From the working student to the chief executive. From the colleague with forty years in the house and four months left before retirement, to the apprentice who had started two months earlier.
Both halves of Levelwork were born there. Constat, because the picture had to be established at all. And Loop, because of the question that arrived the moment it was. The role is clear now. And then what? How does clarity survive Monday?
Our own agency was the first organisation we mapped with the framework. We were not willing to sell something we had not survived.
Since then the same gap has shown up in software, in manufacturing, in property management, in media. Different sizes, different industries, the same distance between the document and the week.
It is usually recognisable within minutes. A managing director describes what is going on in his company. He is not asking for a product, just describing a place where nobody can say with confidence who is carrying what.
“You cannot put an assessment in front of someone with forty years in the house and four months to go. You can only come with curiosity.”
Everything below follows from that.
Every statement stays linked to where it came from. Observation and interpretation are reported separately, never blended. No source, no finding.
We analyze how work is distributed across an organization. We do not measure how well a person performs, and we build no instrument that could.
Nobody is ever asked to rate themselves, and nothing we produce can be used against the person who said it. Call it a value if you like. In practice it is the precondition: without it, nobody answers honestly.
Tools that mine HR systems take what has already been recorded. We ask people directly what their week actually looked like. They answer honestly only as long as the answer cannot be turned into a judgment. Remove that guarantee and the raw material disappears.
Two products, one arc. The first tells you where you actually stand. The second keeps that answer from going stale.
The finding. One structured conversation per role, compared against the role as designed. Where the two diverge becomes visible and evidenced, in sixty minutes, starting with a single role.
See how Constat works In development LoopThe follow-through. Role, requirement, measure, evaluation, follow-up. Findings become decisions, decisions become measurable change, and the picture stays current instead of ageing back into fiction.
See the cycle
A company of eighty people has no data about its own capability. It was simply never collected. In the small companies we have worked in, what people can do was on record nowhere.
So the basis has to be created, not found. That is the work we are doing.
What we are building toward is a living picture of what an organization can actually do: current, evidenced, and owned by the company itself.
Every decision about people (who to hire, what to train, how to restructure, who could take over) should be able to rest on it. Today almost none of them do.
At the German end of Lake Constance, an hour from Zurich. Small enough that the work is done by the people who built the method.
Spent years inside other people’s companies with the same brief under changing names: make this fit for what comes next. Every time, the work began the same way: by finding out what people actually do. Levelwork is that beginning, made repeatable.
Works on human experience design: making Levelwork something people want to use, and not only something they have to. Trained in AI engineering, and has been building the product with Michael since late spring 2026.
We take one role from your organization, capture the profile and the reality, and show you the difference. Then you decide whether the whole team should follow.