Flow, not surveillance
Everything here rests on one distinction. We measure two different things — and we must never confuse them. Lead the team with this, or tracking becomes theatre people quietly game.
Effort & presence
WebWork hours and activity. Did you show up and put the time in? This is a health signal that surfaces problems early — it is not the ranking.
Outcomes shipped
Work delivered against what you committed to. This is what actually gets evaluated. Delivery beats hours — every single time.
One connected loop
Every piece already exists — they've just never been wired together. This is the loop the process closes, from a tracked hour all the way to a promotion.
WebWork
Task-linked time · SOP 7h 30m · activity %
HR Portal
Idle & deviation alerts · 6 PM summary
Weekly Review
Leads flag amber / red · hours vs delivery
Scorecard
Per-role · monthly · eight categories
Evaluation
Raises · promotions · improvement plans
A day, run lightly
No new meetings. The existing standup and weekly review carry the whole thing — the process is a habit, not overhead.
"I have no work"
The quiet killer is someone burning a whole day idle because raising it feels awkward. Make it fast, blameless, and expected. The rule: no one stays blocked or work-less for more than ~30 minutes of active time without raising it.
Self-serve first
Check your board and backlog for the next claimable task. An obvious next item? Take it — done.
Ping your lead
One line in the project channel: "finished X / blocked on Y — what's next?" A normal message, not a confession.
lead replies < 1h
Lead escalates
Nothing on this project? It goes to Mubeen & Sobeeqa to reassign across projects, or to Asim for a priority call.
Logged as capacity
Raising "no work" is recorded neutrally — it tells us who's free and where we're over- or under-staffed.
Fair, early, and only if it repeats
A traffic light on both signals together — hours / activity and delivery. It escalates only when the pattern continues. One off day is never a case.
Green
Amber
Orange
Red
The guardrails that keep it fair
- Approved leave is excluded. The report patches out on-leave days — a known gap Mubeen owns before the first scorecard runs.
- Read hours and delivery together. Low hours but everything shipped is fine; full hours and nothing shipped is the real problem.
- Dishonest tracking jumps straight to red. Idle-faking or mouse-jigglers is a trust breach — a different thing from low output.
Whose module this is
This runs end-to-end as Mubeen & Sobeeqa's module. Asim sponsors it — red-tier and genuine priority calls only, never the day-to-day.
Decide today, live this week
Five moves to go live — then run it two weeks and tune from real data.
Ratify the numbers — SOP 7h 30m, the activity floor, and tier windows.
Leave-exclusion fix lands before the first scorecard runs.
Scorecard draft — Sobeeqa, on a firm date.
Announce to the team — lead with "flow, not surveillance" and the no-work win.
Run two weeks, review, and adjust.
Kickoff agenda
- Frame it. The HR Portal is live; today we operationalise it into one loop. — 5 min
- The no-work protocol. Agree the ladder and the lead SLA. Start here — highest value, least friction. — 10 min
- The fall-under tiers. Triggers, owners, and the leave-exclusion + hours-vs-delivery guardrails. — 15 min
- The scorecard loop. Sobeeqa's deadline, and how it feeds raises and promotions. — 10 min
- Rollout & comms. Who announces it, when, and in what words. — 10 min
- Ground truth. Where's the real drag today — untagged time, unclear tasks, specific people? — open