SaatPro
Where Technology Meets Clarity
🎭 Genre: Satire, Workplace Drama
📖 Duration to read: 4–5 minutes
👩💻 Theme: Service Requests, Access Management, and Freshers’ First Frustrations
🎥 Scene 1: Welcome to the Labyrinth
Location: CyberFloor HQ, San Francisco
Character: Jake, a recent computer science grad, Day 3 of joining
Jake logs in, eager to contribute to the new project. His calendar says: “Code review 9:30 AM.” He opens the repo link… and is greeted with:
🚫 “Access Denied – You do not have permission to view this page.”
🧠 Jake (thinking): “Wait. I work here, right?”
He messages his mentor Ashley:
💬 Jake: “Hey, I can’t access anything… repo, dashboard, even cafeteria menu 😞”
🙃 Ashley: “Welcome to your first Service Request. Get ready for a mini adventure.”
🎥 Scene 2: The Great Ticket Chase
Ashley guides Jake to the company’s ServiceNow portal.
🧭 Jake clicks: “Raise Request” → “Access Management” → “New Joiner Access Bundle”
🤖 The form opens with 17 required fields, most of which make no sense.
He cautiously fills in:
- Manager’s name (he triple checks the spelling)
- Business Justification: “I need to do my job?”
- Required Systems: GitLab, Slack, Jira, Cafeteria App
He hits “Submit.” It vanishes into the digital ether.
🕵️ Later, he gets a status update: “Pending Approval from 3 Managers (1 on leave)”
🎥 Scene 3: The Waiting Game 🎭
Three days pass. Jake keeps refreshing. Still no access. He starts using Notepad to write dummy code.
📣 A voice from the neighboring cubicle: “Still waiting on that Jira access?”
😭 Jake: “At this point I’m writing code on sticky notes.”
His manager Steve appears like a sitcom character.
👔 Steve: “Oh hey, forgot to approve your request. My bad.” clicks Approve.
🪄 10 seconds later, Jake finally gets access.
🎉 Jake: “Was that… was that the final boss?”
🎥 Scene 4: Training Day
Jake now understands the invisible power of the Service Request Form. A week later, a new joiner Nina asks:
🤔 “Why do I need approval to use the printer?”
👼 Jake: “Because corporate law demands sacrifice. 🐐”
He takes a deep breath and writes his second service request — this time like a seasoned warrior. 🛡️
🧠 TL;DR for Freshers:
- If Incident = Something’s broken, then Service Request = Something you need.
- Always check who approves your request (it could be someone on paternity leave).
- Don’t be afraid to ping and follow up.
- Documentation is your best friend.
- Don’t try to “hack” your own access (unless you want an incident 🫣).
