Operating Process

Team Productivity & Accountability

A single, connected loop across WebWork, the HR Portal, the weekly review and the scorecard — so tracking stays honest, under-performance is caught early and fairly, and "I have no work" becomes a five-minute fix instead of a lost day.

Module owned by
MB
Mubeen Aftab
Engineering Manager
SG
Sobeeqa Gul
Project Coordinator
MA
Muhammad Asim
Sponsor
01 · The Principle

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.

The Floor

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.

The Score

Outcomes shipped

Work delivered against what you committed to. This is what actually gets evaluated. Delivery beats hours — every single time.

Someone can log eight hours and ship nothing; someone else delivers in five. So hours are a health signal, delivery is the score. A full day with nothing shipped is the real problem — never a quiet, productive five-hour one.
02 · The Engine

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.

1

WebWork

Task-linked time · SOP 7h 30m · activity %

2

HR Portal

Idle & deviation alerts · 6 PM summary

3

Weekly Review

Leads flag amber / red · hours vs delivery

4

Scorecard

Per-role · monthly · eight categories

5

Evaluation

Raises · promotions · improvement plans

Evaluations feed back into expectations — the loop compounds good work into growth, and documents the rest.
03 · The Rhythm

A day, run lightly

No new meetings. The existing standup and weekly review carry the whole thing — the process is a habit, not overhead.

Start of day
Standup — yesterday, today, blockers — and claim today's task.Every IC
During the day
Track in WebWork against the claimed task. No untagged time.Every IC
6:00 PM
HR Portal auto-generates the daily summary and idle / deviation alerts.HR Portal · automated
End of day
Task done with hours to spare? Claim the next — or raise "no work" (§04).Every IC
Monday
Leads review each report's week — hours and delivery — and flag amber / red into the scorecard.Leads → Mubeen & Sobeeqa
04 · The Key Protocol

"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.

1

Self-serve first

Check your board and backlog for the next claimable task. An obvious next item? Take it — done.

0–15 min
2

Ping your lead

One line in the project channel: "finished X / blocked on Y — what's next?" A normal message, not a confession.

within 30 min
lead replies < 1h
3

Lead escalates

Nothing on this project? It goes to Mubeen & Sobeeqa to reassign across projects, or to Asim for a priority call.

same day
4

Logged as capacity

Raising "no work" is recorded neutrally — it tells us who's free and where we're over- or under-staffed.

no penalty
Raising that you're free is good behaviour. Hiding it is the problem.
05 · When Someone Falls Under

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

Meets the SOP floor and is delivering.
Nothing to manage. Recognise strong weeks publicly.
Lead

Amber

Misses SOP 2+ days, activity below floor, or delivery slipping — for one week.
A private, curious check-in: "what's going on?" Logged as watch. No penalty.
Lead

Orange

The amber pattern continues into a second week.
Mubeen & Sobeeqa step in: written expectations, a one-week plan, daily check-in.
Mubeen · Sobeeqa

Red

A third week, no improvement, or tracking dishonesty.
Formal conversation with Asim + HR. Improvement plan or exit path.
Asim + HR

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.
06 · Ownership

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.

MB
Mubeen Aftab OWNER
Engineering Manager
Owns the delivery side of the loop — cross-project reassignment, orange-tier plans, keeping standup and the weekly review honest, and the leave-exclusion fix.
SG
Sobeeqa Gul OWNER
Project Coordinator
Owns the operating rhythm — standup and task-claim discipline, "no-work" routing, tracking-compliance follow-up, and the per-role scorecard. Models compliance herself.
TL
Team Leads
Junaid · Hasnain M · others
Daily unblock, respond to "no work" in under an hour, and flag amber / red each week to Mubeen & Sobeeqa.
IC
Individual Contributors
Every team member
Track honestly, keep a task claimed, and raise "no work" fast.
HR Portal
Automated
Time tracking, idle and deviation alerts, and the 6 PM plus tri-daily summaries.
MA
Muhammad Asim
Sponsor
Priority calls when work genuinely runs dry, red-tier decisions, and the culture framing. Not day-to-day.
07 · Rollout

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

To run with Mubeen & Sobeeqa — ~60 minutes.
  1. Frame it. The HR Portal is live; today we operationalise it into one loop. — 5 min
  2. The no-work protocol. Agree the ladder and the lead SLA. Start here — highest value, least friction. — 10 min
  3. The fall-under tiers. Triggers, owners, and the leave-exclusion + hours-vs-delivery guardrails. — 15 min
  4. The scorecard loop. Sobeeqa's deadline, and how it feeds raises and promotions. — 10 min
  5. Rollout & comms. Who announces it, when, and in what words. — 10 min
  6. Ground truth. Where's the real drag today — untagged time, unclear tasks, specific people? — open