Zero-to-Hero Consulting Cycle — من الصفر إلى التنفيذ الكامل
اقرأ أولاً: ../MASTER_ALL_IN_ONE_SUMMARY.md · ../html/MASTER_ALL_IN_ONE_SUMMARY.html
الدليل الشامل: ../MASTER_ALL_IN_ONE.md · ../html/MASTER_ALL_IN_ONE.html
ممارسة الشاشات: ../html/MASTER_PRACTICE_GUIDE_ALL_TOPICS.html
Australia · Scopex_786686_hr_leave
Platform target: ServiceNow Australia (Sep 2026) · next EA: Brazil
URLs: ../../SERVICENOW_DIRECT_URLS_CATALOG.md · 1-week: ../../SERVICENOW_ONE_WEEK_STUDY_DEPLOY_AUSTRALIA.md
HR Leave: Scope x_786686_hr_leaveUniversal methodology for every module in modules/.
Use with: MODULE_IMPLEMENTATION_PLAYBOOK.md (§14) + each module’s §15 + §16 (full pages, labs, requirements).
الأسلوب: عربية + إنجليزية تكمّلان بعضهما في نفس السياق.
ملخص ووصف بالعربية (Arabic Summary)
| البند | الشرح |
|---|---|
| ما هو هذا الملف؟ | منهجية استشارية 8 مراحل من اكتشاف العميل حتى التشغيل |
| لماذا مهم؟ | يوحّد طريقة العمل على ITSM وGRC وSPM — لغة أعمال قبل ServiceNow |
| من يستخدمه؟ | مستشار، محلل أعمال، قائد مشروع تنفيذ |
| ماذا يغطي؟ | ورش عمل، RACI، فجوات، UAT، تسليم — مع §15/§16 في كل موديول |
ملخص في سطر: كيف تدير مشروع ServiceNow من الصفر — charter → تصميم → بناء → UAT → hypercare.
وصف مختصر: أسئلة ورشة Phase 0، جدول As-is/To-be، ربط كل موديول بـ §15 (مراحل) و§16 (مختبر). اقرأه قبل أي تنفيذ مؤسسي.
Why this document exists
ServiceNow modules are technology. Clients buy business outcomes (reduce risk, pass audit, serve employees faster).
As consultant you must speak business first, then map to ServiceNow. — العميل لا يشتري “بلجن” — يشتري نتيجة أعمال: امتثال، تقليل مخاطر، استمرارية، كفاءة. أنت تربط بين لغة الأعمال ولغة ServiceNow.
The 8 phases (every module)
Phase 0 — Discover & align (workshops)
Phase 1 — Current state & gap analysis
Phase 2 — Target operating model (process + roles)
Phase 3 — Solution design (ServiceNow mapping)
Phase 4 — Build & configure (plugins, data, flows)
Phase 5 — Integrate & automate
Phase 6 — Test & UAT (scenarios + evidence)
Phase 7 — Train & go-live + hypercare
Phase 8 — Run & improve (KPIs, CCM, retros)
| Phase | Business deliverable | ServiceNow deliverable |
|---|---|---|
| 0 | Charter, scope, stakeholders | License check, app list |
| 1 | As-is process maps, pain points | Instance review |
| 2 | To-be process, RACI | Profile/role design |
| 3 | Requirements backlog | Tables, apps, integrations |
| 4 | Configured processes | Plugins, Guided Setup, scoped apps |
| 5 | Connected enterprise | REST, IH, MID |
| 6 | Signed UAT | Test scripts, evidence |
| 7 | SOPs, training | Portal/workspace live |
| 8 | Dashboards, audit trail | PA, continuous monitoring |
Phase 0 — Discover (questions to ask every client)
English — ask in workshop:
- Why now? (regulation, audit finding, board mandate, incident)
- Who cares? (sponsor, CISO, COO, HR, IT)
- What must be true in 12 months? (measurable)
- What frameworks? (ISO, NIST, SOX, local regulator)
- In scope / out of scope? (entities, countries, vendors)
العربي — اسأل في الورشة:
- لماذا الآن؟ (تدقيق، تنظيم، حادث، طلب الإدارة)
- من صاحب المصلحة؟ (راعي المشروع، أمين مخاطر، امتثال، تدقيق داخلي)
- ما المطلوب قابل للقياس؟ (نسبة امتثال، عدد مخاطر معالجة، وقت attestation)
- أي إطار عمل؟ (ISO 27001، NIST، SOX، SAMA، إلخ)
- ما داخل النطاق؟ (فروع، أنظمة، موردين)
Phase 1–2 — Gap → Target model (template)
Document for each module:
| Item | As-is | To-be | Gap |
|---|---|---|---|
| Process | Manual Excel | ServiceNow workflow | Automation |
| Data | Siloed | Single profile/entity | Master data |
| Roles | Unclear owners | Named control/risk owners | RACI |
| Evidence | Email attachments | Platform audit trail | CCM |
| Reporting | Quarterly slide deck | Live dashboard | PA |
Phase 3 — Map business to ServiceNow (pattern)
Business entity → Profile / Account / CI / Employee
Business rule → Policy / Control / SLA / HR Criteria
Business event → Risk / Incident / Case / Audit finding
Business action → Issue / Task / Remediation / WO
Business proof → Indicator result / Attestation / Audit evidence
Business dashboard → PA / Workspace / Report
Phase 4–7 — Build → Go-live (consultant checklist)
- [ ] Plugins activated on sub-prod first
- [ ] Guided Setup phases logged
- [ ] Roles on groups not individuals
- [ ] Pilot entity (one BU / one vendor tier / one service)
- [ ] UAT scripts = real business scenarios
- [ ] Update Set naming + release notes
- [ ] Hypercare 2–4 weeks with daily triage
Module-specific §15 and §16
Each *.md module file has:
| Section | Content |
|---|---|
| §15 | Zero-to-hero phases (scratch → go-live) |
| §16 | Full consultation: requirements, all pages (Navigate), Option A/B/C, PDI lab step-by-step, UAT sign-off (AR + EN) |
| Module | §15 focus | §16 lab highlight |
|---|---|---|
| GRC | IRM + BCM + TPRM (deepest) | 25-step IRM/Risk/TPRM/BCM tracks |
| ITSM | Service delivery & ITIL outcomes | Incident + SLA + Catalog + Change |
| CMDB | Single source of truth | IRE + Import + Dependency |
| ITOM | Visibility & automation | MID + Discovery schedule |
| ITAM | Lifecycle & cost | HAM receive→deploy→retire (+ SAM) |
| HRSD | Employee experience & HR security | EC case + HR Criteria + lifecycle |
| CSM | Customer trust & SLAs | Account + entitlement tiers |
| FSM | Field efficiency | Dispatcher + mobile WO |
| SPM | Strategy execution | Idea → demand → project → resources |
Master cross-module practice: MODULE_FULL_E2E_PRACTICE.md
Interview / consulting phrases (English)
- “We align Profiles to your organizational entities before loading controls.”
- “Inherent vs residual risk — controls reduce residual, not eliminate inherent.”
- “TPRM tiering focuses effort on critical vendors.”
- “BCM links BIA to recovery plans and exercises — not just documents.”
العربي للمقابلة:
- “نربط Profiles بكيانات العميل قبل تحميل الضوابط.”
- “المخاطر المتأصلة vs المتبقية — الضوابط تخفّض المتبقية.”
- “مخاطر الموردين: نُصنّف الموردين حسب الأهمية.”
- “استمرارية الأعمال: تحليل تأثير + خطط + تمارين، ليس ملفات فقط.”
Related files
| File | Purpose |
|---|---|
| MODULE_FULL_E2E_PRACTICE.md | Cross-module labs + universal deliverables |
| GRC.md §1B–1E, §15–§16 | IRM, BCM, TPRM business deep dive + full pages |
| MODULE_IMPLEMENTATION_PLAYBOOK.md | Scenarios S1/S2/S3 |
| MODULE_OPTIONS_AND_INSTANCE_NOTES.md | Missing features on PDI |
| MODULE_END_USER_PLAYBOOKS.md | Persona day-in-life across all modules |
| MODULE_FROM_SCRATCH_30DAY.md | Universal 30-day implementation sprint |
§10 — Persona-based engagement model
For each module, identify 4 personas. Engage differently:
| Persona | Engagement style | Deliverable |
|---|---|---|
| Executive sponsor | 1h KPI-driven briefings | Board-ready slides + dashboard |
| Process owner | Workshops 2-3h | Process map + RACI |
| Power user | Hands-on lab | Updated SOP + how-to videos |
| End user | Short tutorials | “Day 1” quick-start (1 page) |
Each module’s §17 (Power User Playbook) gives you the persona detail.
§11 — Sales / Pre-sales angle (consultant)
When pitching ServiceNow to a prospect, anchor on:
- Time-to-value (TTV): “Wave 1 in 30 days using template-driven approach”
- Risk reduction: GRC + SecOps integrated = continuous compliance
- Employee experience: HRSD + EC + Mobile = consumer-grade UX
- Cost takeout: ITAM + SAM + FinOps = software/license savings
- Modernization: App Engine + AI Agents = future-proof platform
- Single platform: vs. 5-7 point tools — - زمن العائد، تقليل المخاطر، تجربة الموظف، تخفيض التكلفة، التحديث، منصة واحدة بدل 5-7 أدوات.
§12 — Day-by-day discovery script
| Day | Activity | Output |
|---|---|---|
| 1 AM | Kickoff + stakeholder map | RACI v0 |
| 1 PM | Strategy interviews (CEO/CIO/CISO) | “Why now” doc |
| 2 AM | Process workshop (current state) | AS-IS map |
| 2 PM | Data sources inventory | System landscape |
| 3 AM | Pain points + opportunities | Long list |
| 3 PM | Quick wins workshop | Wave 1 candidates |
| 4 AM | KPI agreement | Measurable goals |
| 4 PM | Roadmap option discussion | 3 options (S1/S2/S3) |
| 5 AM | Wrap-up presentation | Steering deck |
| 5 PM | Sign-off + next steps | Charter v1 |
§13 — Solution Design — patterns library
Common cross-module design patterns:
| Pattern | When to use | Reference |
|---|---|---|
| Hub-and-spoke | One central data domain (e.g., CMDB) | CMDB.md §3 |
| Event-driven | Loose coupling, async, scalable | NOTIFICATIONS doc |
| Process orchestration | Multi-step, multi-role workflows | Workflow Studio in APP_ENGINE.md |
| Catalog → Fulfillment | Standardized service requests | ITAM.md, HRSD.md |
| Investigation playbook | Guided problem-solving | SECOPS.md, ITSM.md |
| Continuous monitoring | Indicator-driven | GRC.md §17 |
| Resource allocation | Capacity + skill matching | SPM.md, FSM.md |
| Composite UI | Multiple data sources in one view | Workspace UI Builder |
| Conversational interface | Lower friction, mobile-first | Virtual Agent + AI Agent |
| Citizen-built app | Department-specific quick wins | App Engine |
§14 — RACI baseline by module (Phase 2 template)
| Activity | ITSM | CMDB | HRSD | GRC | SecOps | DevOps |
|---|---|---|---|---|---|---|
| Process owner | IT Director | CMDB Manager | HR Director | Compliance Officer | CISO | DevOps Lead |
| Configuration | SN Architect | CMDB Admin | HR Sys Admin | GRC Admin | SOC Eng | Pipeline Eng |
| Approval | Change Manager | CMDB Owner | HR Service Lead | Risk Committee | IR Manager | Release Manager |
| Day-to-day operator | Agents | CMDB stewards | HR Agents | Control Owners | SOC Analysts | DevOps Eng |
| End user | Employees | (n/a) | Employees | Various | (n/a) | Devs |
Each module’s §17 Personas section refines this.
§15 — Common consultant pitfalls (avoid)
| Pitfall | Symptom | Fix |
|---|---|---|
| Plugin-first thinking | “Let’s activate X” before understanding why | Always start with WHY (Phase 0) |
| OOTB shame | Customizing when OOTB suffices | Default to OOTB; customize last |
| Skipping CMDB | Other modules suffer downstream | CMDB readiness before ITSM/SecOps |
| No data steward | CIs/profiles/accounts decay | Assign named owners |
| Big-bang go-live | Risky for first launch | Pilot → Wave 1 → Wave 2 |
| Training as afterthought | Low adoption | Training plan from Phase 0 |
| Missing comms | Surprise launches | T-30/T-7/T-1 comm cadence |
| No hypercare | Blame on tool | 2-4 weeks active hypercare |
| No KPI baseline | Cannot show value | Baseline before & after |
| No SP/UX love | Adoption stalls | Brand the portal, hire UX |