Role Ledger — from a website to a weighted scorecard
Website → OKR → KRA → KPI → JD
The ledger is empty.
Paste a URL and a JD on the left. Everything below is produced from those two things and nothing else — every inferred objective arrives with the page it came from, linked, so you can check it.
Objectives inferred from the site, each with its evidence and source link
3–5 KRAs from the JD, one KPI each, with target, source and cadence
Every KPI linked to a named KR, tagged BAU, or cut
Weights that sum to 100, and a score you can run
The method this follows
Settle the OKRs first — official ones if they exist, inferred and labelled as inferred if they don't.
Read the JD, not the OKR, to find the KRAs. Only what's quantifiable qualifies.
Limit to 3–5 KRAs. More and focus dilutes until nothing is prioritised.
Attach a KPI to each — a number, a target, a data source, a cadence.
Link every KPI to a specific KR, or tag it BAU, or delete it. Then read the map top-down: any KR with no KPI pointing at it is unowned.
Accept that enabler and innovation work won't map. Keep it on a separate list rather than inventing a number.
Weight the KRAs to sum to 100. Weight follows outcome ownership, not effort.
Score: achievement = actual ÷ target, capped at 120%. Final = Σ (weight × achievement).
KRAs hold for the year; KPIs get revisited quarterly.
A marketing site lags real strategy by a quarter or two and never shows what isn't working. What comes out here is a strong first draft to take to the founders — not a substitute for asking them.