Why did your last project run over?
Try this in 30 minutes:
1. List every date that moved
2. Find the decision behind each
3. Name who decided it, and where it's written. No record = "unrecorded"
Count your unrecorded entries. Reply with your number.
#ITProjectManagement#CIO
The project ran over. Everyone can explain why. Nobody can say who decided.
Four common causes of IT overruns, the decision behind each, and who should own it.
https://t.co/BU2GTTPg7q
#ITLeadership#ProjectDelivery
We're hiring a CMDB Administrator ๐จ
Own the CMDB, don't just maintain it. Governance, IRE rules, data feeds, root-cause fixes.
4 to 7 yrs IT, 3+ on ServiceNow CMDB.
Apply: https://t.co/LmHtaVLYP1
Or [email protected]#hiringalert#ServiceNow#CMDB#ITJobs
Ask three people in your company how many active customers you have.
If the answers differ, you don't have a data problem. You have a definition nobody owns.
"Active", "closed", "qualified" or "resolved": which word starts the most arguments?
IT reads adoption. Finance reads the ledger.
Cost avoided: a worse outcome that never happened. Real value, still an estimate.
Cost saved: a line item that went down.
Which line on your ServiceNow ROI slide would you pull on first?
#ServiceNow#CIO
The migration plan has a date for cutover. The parallel run often doesnโt.
Every parallel run needs an owner, an exit test and an end date.
https://t.co/mvrP7MBz2H
#ITModernization#CIO
An AI-drafted email can be accurate, polite and right on every fact, and still not sound like you.
The test isnโt โis it correct?โ Itโs โwould our best person have written it this way?โ
Which email would you never let AI send unread?
#AIinBusiness#CustomerExperience
AI-drafted customer emails can be accurate, polite, and still not sound like you.
Four checks before you switch them on. Which do you skip?
#AIGovernance
Revenue is up 12%. Or 9%. Depends who you ask.
Same CRM. Nobody's lying. Sales and Finance just count "closed" differently.
How to find where two "correct" numbers split:
https://t.co/fpEmrLO6Of
#DataGovernance
Most knowledge bases can tell you an article was viewed.
Almost none can tell you it actually stopped a ticket.
Three questions worth running against yours before you trust anything in it โ
https://t.co/es58dpruUe
Knowledge base with 4,000 articles. Ticket volume didn't move.
The number nobody tracks: not article count โ how many times someone trusted an article enough to skip the ticket entirely.
Could you measure that today?
#ServiceNow#ITSM
AI made the call. The call was wrong.
Who owns the outcome?
As AI agents become more autonomous, accountability becomes an interesting question.
When an AI agent makes the wrong call, ______ should own the outcome.
What's your answer?
#AgenticAI#AIGovernance#EnterpriseAI
AI says the change is LOW RISK with 94% confidence.
Would you approve it?
A โ Approve
B โ Review the reasoning
C โ Human review
D โ Need more context
๐ A, B, C or D โ and why?
#ServiceNow#ITSM#ChangeManagement
One incident. 32 minutes total.
4 min = actual fix.
28 min = moving the ticket between teams.
Nobody was slow. The context just took too long to reach the right person.
Where would you fix this first?
A) Assignment B) Knowledge C) Automation D) Service/CI context
Your MTTR improved. But did recurrence drop?Closing tickets faster doesnโt always mean fixing the https://t.co/wH8r9rf9KT close time vs. recurrence rate. The difference may tell the real story.
#ServiceNow#ITSM#LetsFixTheRightProblem
A closed ticket isn't always an improved process.
If the same reset, reboot or workaround returns next week, did we solve the issue โ or just complete the task?
Recurring work should trigger learning, standardization or automation.
#ServiceNow#ITSM