EM 1:1 — Mubeen Aftab

Noise cleared. Most of the operational backlog from the last two 1:1s is done (strip below). This 1:1 is about 5 live priorities — get HR Portal shipped, then build toward one unified platform, develop Sobeeqa to run the calls, and set up post-Ashura.

✅ Closed since last 1:1 — acknowledge the momentum:
Idle-time logic (>10min grouping) Report-API reconciliation Meeting-break config Paid/unpaid break rule Conductor memory + JSON mgmt Duplicate member cleanup PM / timeline views

✅ Agreed in the 1:1 — 18 Jun

Unification confirmed: HR Portal + Workforce Analytics + WebWork → one platform, single auth + per-user RBAC, with project tracking, leave, reimbursements, requests/tickets & reporting (SMTP-integrated). HR Portal stabilized + live first; then a ~2-week sprint to the unified platform. Sobeeqa to be coached into leading the calls.

→ Asim

Schedule the unified-platform kickoff (Uzair, Jawad, Sobeeqa)

Review Mubeen's spec doc + feedback before kickoff

Send meeting summary + next steps; loop in the team

→ Mubeen

Plan unified platform (Claude/Conductor prototype) + spec

Assess feasibility w/ Jawad + team → detailed spec doc

Coach Sobeeqa on meeting leadership + engagement

Prep a simple kickoff presentation of the platform

1The 5 live priorities

1. HR Portal → Production go-live P1 · THIS WEEK

Get it live, fix bugs, stabilize, secure — LAUNCH BY WED 24 JUN (pre-Ashura)

PR #20 approved (Asim + Uzair) → run the 25 migrations only after a verified backup
Bug-fix + stabilization pass; harden security before exposing prod
Observability (Sentry/CloudWatch/Grafana) wired before launch — not after
Prod user accounts provisioned (Jawad, Sobeeqa); analytics demo Tue 23 Jun

2. Single-Platform Unification P1 · 2–3 WEEKS

Collapse the split stack into one platform. Today we run:

WebWork ─► Wazir Analytics HR Portal ─► Analytics → ONE PLATFORM

One authentication — single login / SSO across everything
Per-user data access (RBAC) — each person sees only their own data + what their role permits
Requests & Tickets — raise requests / tickets natively inside the platform
SMTP-integrated — notifications, invites, ticket updates all email out
Absorbs: Ninja-bot ↔ WebWork ↔ HR Portal leave-approval + step-out/back sync, and the HR Portal ↔ WebWork leave sync (replaces the old manual leave patching)

3. Develop Sobeeqa → own & lead the calls P2 · ONGOING

Mubeen to coach her into the project-coordinator role properly. Goal: she runs the calls without Asim (or Wazir) in the room.

Be upfront in meetings — drive the agenda, don't sit back
As coordinator, she leads — opens, steers, and closes the call
Ask the detail questions herself; chase the specifics that currently come from us
Take ownership of the vision & participation, not just note-taking
Right now the leads come from Asim — shift that to her, deliberately, over the next few weeks

4. Targeted hiring P2

No formal intern cohort for now — go targeted.

Prefer COMSATS job-fair candidates + internal referrals
Lean, vetted adds rather than a big 6–8 intern program

2The 4-week plan

Sequenced around Ashura: ship HR Portal first, then build the unified platform in phases.

Week 1 — Ship HR Portal 🚀

18–24 Jun · launch by Wed

HR Portal LIVE by Wed 24 Jun — bugs, stabilize, secure, observability, prod accounts
Analytics Phase-4 demo (Tue 23)
Kick off unification design: auth/SSO + RBAC data-access architecture

Week 2 — Unify: auth + access

25 Jun – 1 Jul · post-Ashura

HR Portal post-launch stabilization + feedback
Build: single authentication / SSO across WebWork-analytics + HR Portal
Per-user RBAC data access implemented
HR Portal ↔ WebWork leave sync design

Week 3 — Unify: tickets + email

2–8 Jul

Requests & Tickets module + SMTP notifications
Ninja-bot leave-approval + step-out/back sync wired in
Mango Event · begin COMSATS hire onboarding

Week 4 — Consolidate

9–15 Jul

Single platform live — one login, role-based data, tickets, email — de-dupe the old split analytics
COMSATS hire ramped on real work
Sobeeqa running a call solo (target check)
Month review: shipped vs plan → next cycle

3Decisions / asks for Mubeen

Confirm: HR Portal can realistically be live + stable by Wed 24 Jun — what's the risk, and what do you need from me to hit it?

Unification: is 2–3 weeks realistic for one-auth + RBAC + tickets + SMTP? What's the right phasing & who leads it?

Sobeeqa — you own the coaching. How do we visibly hand her the calls over the next 3 weeks? First call she leads solo = ?

Targeted hiring — which COMSATS candidate(s) / referrals are we moving on, and when?

Mango Event + COMSATS onboarding — who's driving the logistics so it doesn't land on you mid-unification?

Where do you need Asim to unblock — decisions, budget, headcount, tooling?

Through-line for the call: "Ship it, unify it, then hand it over." Get HR Portal live before Ashura → build the one-platform / one-auth system over the following 2–3 weeks → and in parallel, deliberately move the calls onto Sobeeqa so the day-to-day runs without you. That's the time-back play.

EM 1:1 — Mubeen Aftab 4-WEEK PLAN

✅ Agreed in the 1:1 — 18 Jun

1The 5 live priorities

1. HR Portal → Production go-live P1 · THIS WEEK

2. Single-Platform Unification P1 · 2–3 WEEKS

3. Develop Sobeeqa → own & lead the calls P2 · ONGOING

4. Targeted hiring P2

5. Post-Ashura runway P3 · LATE JUN / EARLY JUL

2The 4-week plan

Week 1 — Ship HR Portal 🚀

Week 2 — Unify: auth + access

Week 3 — Unify: tickets + email

Week 4 — Consolidate

3Decisions / asks for Mubeen