Some problems need a framework built, not just advice given.
A look at two pieces of work: one delivered for a client, one being built as its own product.
Client work — Performance Architecture
Building a global performance culture
The brief: a multinational client wanted the same discipline internally that it demands everywhere else — a clear performance standard, applied consistently, in every market it operates in.
5–7levels, IC + Leadership tracks
1 sprintto deliver the framework
4 phasesfrom levelling to reward
The pitch
Job levelling comes first, because nothing else works without it. You can't set fair pay or manage performance consistently until every role has a clear level. Get this right, and everything else builds cleanly on top.
A simple Individual Contributor and Leadership structure, mapped to how the business actually works: production, supply chain, sales, marketing and R&D. 5–7 levels, delivered in one sprint.
2 · Compensation Framework
Pay ranges by level, benchmarked to local markets.
3 · Performance Instrument Mapping
KPI or OKR — matched to what the HRIS can actually run.
4 · Performance Management Process
Routine and annual feedback, feeding merit-based reward.
The outcome: a culture of high performance, in every market — clear on what great looks like, and rewarded consistently. Same standard, everywhere.
Once that sequence is delivered, here's the cycle it runs on, ongoing:
1 · Framework
Every role's expected capabilities, defined by grade — the foundation everything else measures against.
2 · KPI's / Performance Measurement
Set by role and rolled up company-wide, all anchored to one universal framework rather than reinvented team by team.
Formal feedback and evaluation, judged fairly against the capabilities expected at that grade and role, plus stretch goals drawn from the level above.
4 · Feedback Culture
Regular, performance-enhancing feedback and support — not a once-a-year form. Held to the same role expectations, so it's fair and consistent every time it happens. This is the step that decides whether the system actually changes behaviour, or just produces paperwork.
What the cycle sits on
High trust and psychological safety
None of the above works without this underneath it. A framework can define every level correctly and still fail if people don't trust the feedback enough to act on it, or feel safe enough to give it honestly. This is what turns a well-designed process into an actual performance edge, rather than a compliance exercise.
Illustrative example — client brief and proposal, anonymised. Prepared by Mel Holder Consulting.
If your organisation is scaling into new markets without a shared definition of what "good" looks like at each level, this is the shape of work I'd bring to it.
Own R&D — Capability Intelligence Platform
Building for the capability economy
AI is rewriting the rules of work. Skills go out of date faster than careers do, and roles change shape mid-tenure. Most companies can't see the capability already sitting inside their own walls — and the people who hold it are walking out, because their growth path feels capped.
What's shifting is the unit of organisation itself: less "who holds this title," more "who has the capability to solve what needs solving, or build what needs building, right now." People get redirected toward problems instead of boxed into descriptions.
200–1,000employees — the gap enterprise tools miss
~30 sectarget — evidence-backed answer, once live
5 tiersfrom self-declared to AI-verified
This isn't a universal prescription — plenty of organisations still run well on stable, well-defined roles. But in competitive, fast-moving industries, the ability to see and redeploy capability quickly is becoming a real advantage, not just an HR nicety.
Capability mappingTalent intelligenceProduct in development
The entry point is Skills Finder Bot — a conversational tool built into Slack or Teams that turns "who's done something like this before?" into an evidence-backed answer in about thirty seconds, instead of an ad hoc hallway conversation.
Evidence-based
Capability is drawn from project records and contribution history, not a skills checklist someone filled in once.
Five-tier validation
From self-declared through to AI-verified — a calibrated view of where real expertise sits, not a binary approval.
Built for the gap
Aimed at organisations between roughly 200 and 1,000 people — too small for enterprise talent-intelligence tools, big enough that nobody can see the whole picture anymore.
This only works if it's worth the change for both sides. It asks people to stop introducing themselves by job title and start being found by what they can actually do — that only sticks if it pays off for the person, not just the organisation asking for it.
For the organisation
Visible capabilitySkills surface for the first time, not just job titles.
Less external hiringInternal options get found before a role is posted outside.
Faster staffingMinutes, not weeks, to find the right person for a project.
Higher retentionPeople stay when their growth path is visible, not guessed at.
For the employee
Discoverable potentialFull capability visible, not just what the title says.
Internal mobilityThe next opportunity found inside, not chased outside.
Skill growthStretch work that genuinely builds capability, not busywork.
Career durabilitySkills built to hold their value through the AI transition.
A tool that only helps the employer gets bought, not used. One that helps both sides gets adopted — and that's what makes the behaviour change stick.
If your industry moves fast enough that job descriptions go stale before the ink dries, this is the kind of thinking I bring into the room — whether or not the platform itself is what you need.