HR onboarding workshop
01 · Start from the conversation.
A sentence, a Jira epic, or a workshop transcript from Teams or Zoom — meeting transcripts are available on request.
Plan
Plan — From a sentence to a sprint-ready backlog.
Say “implement ITSM” and Phyllis returns sequenced stories with priorities, points, and acceptance criteria — synced both ways with Jira or ServiceNow Agile 2.0.
14.2%
I want to implement ITSM Pro — build me the backlog.@ for records · / for commands
Plan
acmedevProject
acmedevProject Read what already existsIncident, problem, changeRead
Drafted 22 storiesPoints and acceptance criteriaDrafted
Plan critic reviewed2 gaps added, 1 duplicate mergedReviewed
Synced to JiraITSM-102 → ITSM-123Synced
Built for the platform
3,000+typed ServiceNow tools~230expert skill packsHundredsof health checks8acceleratorsISO 27001 certifiedPer-user OAuthApproval on every changeLands in your update setsATF on every build
What you can ask Plan to do.
Describe the outcome in a sentence. Phyllis researches the live instance and she returns a sized, sequenced backlog — epics, stories, points, owners and acceptance criteria — ready for review, not a blank template.
Implement ITSM22 stories · 50 pts
ITSM-102Incident categories & assignment rulesDone5
ITSM-103Major incident workflowReady8
ITSM-104Change CAB approvals by riskReady5
ITSM-105Problem → known error handoffPlanned3
ITSM-106SLA definitions for P1–P4Draft3
Plan
Implement ITSM for us — end to end
Say “implement ITSM” or “stand up a CSM case model” and Phyllis breaks it into epics, then stories — each one sequenced, dependency-aware, and grounded in what already exists on the instance. Nothing is built here: Plan produces the backlog, Develop builds it.
Outcome · VIP incident path3 stories
VIP-11Flag VIP callers from HR dataReady3
VIP-12Route VIP incidents to the VIP DeskReady5
VIP-13Escalate if unassigned after 30 minPlanned3
Plan
Just the stories to add a VIP incident path
Not every job is a full programme. Ask for just the stories to hit one outcome — “add a VIP incident path” or “onboard a new fulfilment group” — and Phyllis scopes a tight backlog for that goal alone, each story cited to the records it touches.
Scope check · ITSM rolloutpre-estimate
Stories22
Points50
Reused configuration14 records
Net-new8 records
Out of scope · Major incident workbenchneeds a licence check firstFlagged
Plan
What are we forgetting to scope?
Before the estimate, ask. Phyllis reads the live instance — the modules, plugins and integrations already in play — and surfaces the requirements and dependencies a discovery workshop misses, so the backlog is complete before sprint one.
How Plan works. Step by step.
Backlog6
02 · A backlog, not a brain-dump.
Sequenced stories with points, priorities and acceptance criteria — each traced to where it came from.
Critic reviewedSynced to Jira
03 · Critiqued, then synced.
An independent plan critic challenges scope and gaps before you approve — then stories sync both ways with Jira or ServiceNow Agile 2.0.
Plans you can present. Exported, not screenshotted.
Design doc · Employee onboardingExported .docx
1 · Scope and outcomesFrom the workshop · 6 stories
2 · ArchitectureDiagram · catalog, flow, Now Mobile
3 · Data model2 tables · 14 fields
4 · Approvals and SLAsManager threshold · $2k
5 · Test approachATF · 9 tests planned
Design docs, discovery reports and plans export as branded Word documents, with architecture diagrams as a standard output — ready for the steering committee.
What’s included
Branded Word export of plans and design docs
Architecture diagrams, generated with the plan
Two-way sync with Jira or ServiceNow Agile 2.0
Private projects with their own instructions and memory
BA/PM planning mode and read-only stakeholder mode
From one sentence to a review-ready plan.
Describe the outcome once. Phyllis researches your live instance and she returns a sized, sequenced backlog — every story with acceptance criteria and a place in the order.
Every story has acceptance criteria
Sequenced by dependency
Implement ITSM22 stories · 50 pts
ITSM-102Incident categories & assignment rulesDone5
ITSM-103Major incident workflowReady8
ITSM-104Change CAB approvals by riskReady5
ITSM-105Problem → known error handoffPlanned3
ITSM-106SLA definitions for P1–P4Draft3
Plan, across the platform.
CHG-301: Governed Normal Change Model1 epic · 4 stories
CHG-302Normal Change model + lifecycle statesReady5
CHG-303Risk assessment + risk rulesReady5
CHG-304CAB approval policy with catch-allPlanned5
CHG-305CAB definition + Thursday schedulePlanned3
ITSM
Implement ITSM
From “implement ITSM” to a sequenced backlog to staged update sets — incident, problem, change, catalog, SLAs.
Read the use caseHR-214: Parental Leave HR Service1 epic · 4 stories
HR-215Service & record producerReady5
HR-216Manager approval optionReady3
HR-217Case template & activitiesPlanned5
HR-218AWA routing, retire matching rulesPlanned3
HRSD
HR Service Delivery
COEs, HR services, lifecycle events, Employee Center — onboarding journeys your HR team can run.
Read the use caseSPM-208: Cloud Modernisation Intake Pipeline1 epic · 4 stories
SPM-209Innovation portal + category hierarchyReady5
SPM-210Demand screening stage + scoringReady5
SPM-211Stakeholder register populationPlanned3
SPM-212Cloud portfolio + strategic goalPlanned5
SPM
Ideas that screen, score, and stack-rank into funded work.
Phyllis builds and extends your whole idea-to-funded-work pipeline — intake, scoring and portfolios — grounded in your live instance and staged for your approval.
Read the use casePlan, answered.
Does Plan change my instance?
No. Plan is read-only, enforced on the server. It reads what exists so the backlog reuses it, then waits for you.
Which backlog tools does it sync with?
Jira and ServiceNow Agile 2.0, both ways — stories, points, acceptance criteria, status and comments.
Can it work from meetings?
Yes — Teams and Zoom transcripts become stories traced to the moment they were said. Meeting transcripts are switched on per workspace, on request.
Who checks the plan?
You do, with help: an independent plan critic reviews scope, gaps and duplicates before the plan reaches you.
The rest of the lifecycle.
One teammate from the first question to a promoted, tested change.
CMDB health scorecardcmdb_ci · 48,213
68of 100
CriticalDuplicate servers across SCCM and Discovery2,114 CIsFix with Phyllis
Analyze
Ask your instance anything
Phyllis grounds herself in the full context of your ServiceNow instance — its tables, ACLs, flows, update sets, configurations, and dependencies. Every answer is evidence-backed and traceable to the records it came from.
Explore Analyzesys_script · P1 network auto-assign+6 −0
1(function executeRule(current, previous) {
2 if (current.priority != '1') return;
3 var onCall = new OnCallResolver().forGroup('Network Ops');
4 if (!onCall) return;
5 current.assigned_to = onCall.user;
6 gs.eventQueue('network.p1.page', current, onCall.user);
7})(current, previous);
Update setFeature: P1 network auto-assign
ATF12 / 12 passed
Develop
The whole change, built in your instance
Phyllis develops on the platform — from tables, business rules, flows, and ACLs to the records behind them — then verifies and tests every change.
Explore DevelopPromote · Feature: Warranty claim flowAwaiting approval
devtestprod
Records14
ATF12 / 12 passed
Instance ScanClean
Rollback planAttached
Promote to prod?Platform owner
Approve & promoteReject
Deploy
Sequence and promote from one canvas
Batch and release update sets through chat — in the right order, with conflicts surfaced before you promote.
Explore Deploy
