Thread regarding PNC layoffs

Technology is gonna suffer

In speaking to others during my lunchtime, we all agree that technology is going to be the biggest area that will suffer. And when technology suffers, the customer base will suffer. No one, and I mean no one is going to bend over backwards, work evenings, or weekends anymore without work/life balance. A lot of good talent will leave. And remember, even though we are replaceable, good talent takes time to find and bring up to speed. We are talking months! Who is going to pick up the slack? The managers? They can only do so much. They are already over stressed and overworked putting in so many hours.

The worst thing as well, is the media will get wind of this confirmation of a 5 day return to work requirement and PNC’s reputation is going to suffer. Mark my words. It will make them look bad. Why couldn’t we just be a leader in the banking industry and keep it at 3 days a week? Why do we always end up being the follower? Can you imagine the talent we could bring in with a good life/balance plan? At the end of the day, when employees are happy, they tend to go above and beyond for their employer. That’s a known fact.


by
| 1162 views | | 6 replies (last January 17) | Reply
Post ID: @OP+1keyqsegb

6 replies (most recent on top)

It already is. Debbie is all "be fintech-like agility (on Dollar General pay,)" and they keep adding more and more procedural blockers. Teams are already not reporting honest issue to stay off the lists. And right now Dev and BAU feels like you are taking a shower with a raincoat on... I supposed it can be done but not done well.

by
| | Reply
Post ID: @re+1keyqsegb

@a4

Brilliance! For more ideas along these lines, please visit:

https://www.cia.gov/static/5c875f3ec660e092cf893f60b4a288df/SimpleSabotage.pdf

by
| | Reply
Post ID: @ag+1keyqsegb

No More meeting during Lunch breaks. Deny them.. all with comments.

by
| | Reply
Post ID: @ae+1keyqsegb

@a4 Unfathomably based.
A lot of the fools on here think protesting works. The only thing that works is leaving. If you can't leave, maliciously comply until you can.

by
| | Reply
Post ID: @aa+1keyqsegb

When an organization optimizes entirely for control, metrics, and process, the only winning move is radical, enthusiastic compliance. Don’t push back. Don’t question it. Become a living embodiment of the workflow diagram.

If a request is past its SLA or marked “HIGH PRIORITY 🔥,” do not proactively follow up. The system will surface blockers organically (or during the postmortem). If a project slips, that’s just data. You’re blocked until the prerequisite ticket is officially completed, approved, and ceremonially closed. No ticket, no work. Tickets are reality.

Adopt a monthly release cadence for user stories and announce it as a “process improvement.” Only accept new stories during that window. Everything else goes into the idea parking lot where innovation goes to hibernate.

Every task—yes, even the five-minute one—must be:
• Written up
• Estimated
• Prioritized
• Groomed
• Blessed by the backlog

If it’s not prioritized, it doesn’t exist. If it exists, it waits its turn.

Additional advanced compliance techniques:
• Documentation or death
If it’s not fully documented in the approved template, it didn’t happen. Screenshots missing? Wrong font? Kick it back.
• Meeting-driven development
If policy implies a meeting is required, insist on one. No meeting, no decision. No agenda? Reschedule. No quorum? Reschedule harder.
• Approval purity tests
Approvals must come from the correct role, in the correct system, using the correct workflow. Slack approvals are folklore.
• Scope absolutism
Deliver exactly what’s in the ticket. Nothing more. If something adjacent is needed, request a new ticket and link it for “visibility.”
• Business-hours boundaries
Respond strictly within documented response windows. Not early (sets expectations). Not late (hurts metrics). Right on time—like a cron job.
• Metric worship
Optimize for what’s measured, not what’s useful. If success is “ticket closed,” close it when acceptance criteria are technically satisfied. Outcomes are someone else’s OKR.
• Process evangelism
When asked for an exception, cheerfully explain the process and link the policy. Bonus points for phrases like “for audit purposes” and “to stay aligned.”

Follow every rule exactly as written, especially when it’s obviously counterproductive. You’re not being difficult—you’re being aligned. If the system breaks, at least it breaks compliantly.

by
| | Reply
Post ID: @a4+1keyqsegb

ah yes, finance... famously ethical and not chasing the bottom line

by
| | Reply
Post ID: @a3+1keyqsegb

Post a reply

: