.jpg)
Tipping on an oil change
I went into a drive through oil change this week, and half way through the work, I get handed a tablet with one question, how much to tip? It was such a weird extortionesque request because there were 2 guys working on the car that both looked up at me as i took the tablet. Whelp, won’t be going there again.
Jobadvisor
I hear you, and honestly, that sounds incredibly awkward. There is something uniquely high-pressure about being trapped in your driver's seat—quite literally in the middle of a service—while being stared down for a gratuity.
The "tip creep" phenomenon has officially reached the garage, and you aren't alone in feeling like it borders on a shakedown. Here is the breakdown of why this feels so off and how to handle it next time.
Why "Oil Change Tipping" is Controversial
The Power Dynamic: Unlike a restaurant where you tip after the meal, being asked while your car is drained of oil feels like a hostage situation. If you hit "No Tip," are they going to forget to tighten the drain plug? (Probably not, but the brain definitely goes there).
The Wage Gap: Tipping was traditionally designed to supplement sub-minimum wages for servers. Lube technicians are generally paid a standard hourly wage or a base plus commission/bonus.
The Skill Factor: You are already paying a premium for the labor and the oil. In most trades (mechanics, plumbers, electricians), the expertise is built into the invoice.
How to Handle the "Tablet Stare-Down"
If you find yourself in that position again, keep these three things in mind to keep your blood pressure low:
The "Default No" Policy: You are never obligated to tip for a standard automotive service. If they just did the job you paid for, clicking "No Tip" is a perfectly valid response.
The "Above and Beyond" Exception: If they vacuumed your crumbs, scrubbed your windows, or spent 10 minutes explaining a complex engine issue without charging a diagnostic fee—that’s when a few bucks makes sense.
Blame the Software: Remember that these tablets often come with "Tip Screens" enabled by default in the software. Sometimes it’s a corporate cash grab, not necessarily the individual techs being greedy.
The Verdict
Voting with your wallet (by not going back) is the most effective way to tell a business that their service model is off-putting. There are plenty of independent shops and even dealerships that still stick to the "price on the sign is the price you pay" philosophy.
Advice for my job. [24F] with 3-4 jobs. How do I follow chain-of-command?
From my perspective, much of the work I am doing involves identifying operational gaps, clarifying procedures, and thinking through the systems that support our day-to-day operations. In my primary role, I serve as a manager responsible for supervising staff and ensuring that the environment operates effectively during my shifts. My focus is on making sure the space functions smoothly, that staff understand expectations, and that situations are handled appropriately in real time. At the same time, I hold three additional roles that are all connected to improving the environment for the staff who report to me, which means much of my time is spent thinking about how to enhance training, communication, and overall operational clarity for the team.
Because I am responsible for both managing people and maintaining the effectiveness of the space, I often find myself identifying structural gaps in policies or procedures that impact daily operations. When situations arise that require interpretation or ethical judgment, I feel a responsibility to think through the implications and document concerns or propose clearer systems that help staff navigate their responsibilities more confidently. The work I end up doing often involves developing clearer processes, anticipating risk, and trying to build structure where there is ambiguity so that staff have consistent guidance. While these efforts help stabilize the environment for the people working under me, I am aware that much of this type of systems work would typically originate at a higher leadership level. I don't want to step over the chain-of-command and document when I ask for policy, to be told it isn't important; when in reality, it is to my staff if they were to ask.
At the same time, I recognize that the VP appreciates the way I approach problems and the initiative I take when identifying operational issues. However, this dynamic can make conversations with him somewhat complicated. When he asks questions about policies, processes, or operational decision-making, the answers sometimes reveal that much of the analysis and groundwork behind those systems has been done by me. His questions are thoughtful and strategic, but responding honestly can unintentionally highlight how much of the structural work I have already taken on while managing staff and maintaining day-to-day operations. This creates a situation where I am trying to communicate clearly while also being aware that the depth of the work I am describing may expose gaps in the structure above me. I know I need to set up a meeting with him next week and am seeking advice. Of note, there are three management steps between myself and the VP. The VP has also made it clear that he wants me taking over his position, which also makes my day-to-day navigation with upper management difficult. Any advice?
Jobadvisor
This is a classic "High-Performer Trap." You are essentially functioning as an internal consultant or an Operations Director while officially being a front-line manager. When you have three layers of management between you and a VP who has already tapped you as his successor, the "Chain of Command" becomes a minefield of bruised egos.
If you are too efficient, you make your direct supervisors look redundant or, worse, negligent. If you hold back, the systems fail and your staff suffers.
Here is how to navigate that upcoming meeting with the VP and your daily interactions with the layers in between.
1. The "Managing Up" Strategy
Since the VP is already looking at you as a successor, your goal isn't just to do the work—it’s to protect the hierarchy so you don't become a target for the managers above you.
Credit Attribution: When the VP asks how a new process was built, use "We" and "Support" language.
Instead of: "I identified the gap and wrote this manual."
Try: "I noticed the team was struggling with [X], so I drafted a proposal and ran it by [Direct Supervisor] to ensure it aligned with our goals."
The "Gap" Language: When pointing out structural failures, frame them as opportunities for scalability rather than "policies that don't exist." This sounds more like a future VP and less like a frustrated manager.
2. Handling the 3 Layers of Management
This is your biggest risk. Those three managers likely feel the heat when you speak directly to the VP. To mitigate this:
The "No Surprises" Rule: Before you meet with the VP, send a brief "FYI" email to your direct supervisor. “Hey, I have a touch-base with [VP] next week. I’m planning to share the new training workflow I’ve been testing with my shift. Anything specific you’d like me to highlight or keep in mind?”
Ask for "Guidance" (even if you don't need it): People love to feel like mentors. When you create a new system, take it to your boss and ask, "I've drafted this to help the staff—does this align with your vision for the department?" It gives them "ownership" over your brilliance, which buys you political cover.
3. The VP Meeting: Navigating the Succession
If he wants you in his seat, he’s testing your diplomacy, not just your technical ability to write policy.
Focus on Documentation vs. Decision: Tell him: "I’ve found that my team operates best when there is zero ambiguity. I’ve been documenting our internal workflows to ensure my staff feels supported, but I’d like to ensure these align with the broader corporate strategy so I’m not overstepping."
The Ethical Bridge: When you encounter an ethical or policy gap, frame your documentation as Risk Management. Executives love that term. You aren't "complaining about lack of policy"; you are "mitigating liability for the organization."
A Comparison of Approaches
| Scenario | The "Risky" Way (Current) | The "Strategic" Way (Future VP) |
| Missing Policy | "There’s no policy for this, so I wrote one." | "I've created a 'Standard Operating Procedure' for my shift to ensure consistency until a formal policy is released." |
| VP Asks "Who did this?" | "I did. Nobody else was doing it." | "I took the lead on the draft to solve a bottleneck I saw on the floor; I'm happy to see it's helping." |
| Middle Manager ignores you | Doing it anyway and documenting their refusal. | Documenting the solution and "cc-ing" them on the success metrics. |
Advice needed
Hello, I'm in a bit of a predicament. I work in tech and I took over a technology that had already been implemented and several mistakes made by the vendor that has cost us quite a bit of money. My manager has an inappropriate relationship with this vendor. Multiple employees on my team have complained about the mistakes that they've made causing us money and he deflects and never holds them accountable. He had a relationship with the vendor account manager prior to our current organization.
We recently got new executive leadership who came in and upon meeting with the new leader, he asked why we had orphaned storage not being used, and my manager responded that they were misconfigured. He did not state who misconfigured it, so new leadership is going to assume I made the costly mistakes when I had nothing to do with it. I wasn't even the owner of this technology at the time.
Fast forward a couple weeks and layoffs being announced, I suddenly receive direction to drop all work that I'm doing and to focus just on this technology so we have no dependency on a vendor, which I have never depended on this vendor. I was also told to take ownership of the storage that I have no access to and was never given access to, but another person on my team who has nothing to do with the technology was given access to. My manager was a regular employee at one point on my team and did not like me and I think that that feeling is still there. I fully believe he is scapegoating me to protect himself from being laid off. He meant with the new leadership in that same day as when I suddenly Il was told to drop all this stuff and I needed to become an expert, when I am already well versed in the technology (I have 18 years experience in this area of technology, I am not green by any means). I don't think it's a coincidence this happened the same day he had a one-on-one with him.
My question is, should I meet with the new executive leader to understand what their understanding of the situation is, and ensure to clarify what actually transpired? My fear is it backfiring if my manager finds out because he will be mad that he got caught lying and covering for a vendor, as he would be held accountable then. For many years people have felt that there's inappropriate dynamics with this vendor that go beyond just friendship, but I work in a place where everything gets swept under the rug, including people openly harassing others. I've been struggling with what to do for a few months and could really use some good advice. TIA
Jobadvisor
This is a high-stakes corporate survival situation. You are being positioned as the "fall guy" for a "paper trail" that hasn't been written yet. In tech, 18 years of experience is a shield, but it can be bypassed if the person holding the data (your manager) controls the narrative to the new Executive Leadership (EL).
Here is how to handle this without triggering a "mutiny" or "insubordination" charge.
1. The "Audit Trail" Strategy (Immediate Action)
Before you meet with anyone, you must create a paper trail that dates your involvement. If your manager is scapegoating you for the vendor's $180,000+ mistakes (as an example), you need to document the "Inheritance Date."
The "State of the Union" Email: Send an email to your manager (CC yourself on a personal account or BCC) titled: Summary of [Technology] Transition & Current Blockers.
The Content: "Per our discussion, I am shifting focus to [Tech]. To ensure a clean transition, I’ve noted that the misconfigured storage issues predated my ownership (occurring [Date/Year]). I also currently lack the administrative access held by [Colleague Name]. Please provide access by EOD so I can begin the remediation you requested."
The Goal: You aren't accusing him yet; you are creating a timestamped document that proves you didn't have access when the mistakes happened.
2. The Meeting with the Executive Leader (EL)
Should you meet with them? Yes, but not to "tattle." If you go in and say "My manager is lying and loves this vendor," you look like a disgruntled employee. If you go in to "align on technical debt," you look like a senior leader.
The Script for the EL:
"I wanted to sync with you regarding the storage misconfigurations you flagged. Since taking over this technology recently, I’ve been performing a root-cause analysis. It appears these orphaned assets were configured during the initial vendor implementation phase (prior to my ownership). My goal now is to bring this in-house to stop the financial leak. What are your primary KPIs for this recovery?"
Why this works:
It subtly informs the EL that you didn't do it without mentioning your manager's name.
It identifies the Vendor as the source of the error, which forces the EL to look at the vendor contract (and your manager’s relationship with them).
It positions you as the Fixer, making you harder to lay off.
3. Addressing the Vendor "Conflict of Interest"
Since the culture "sweeps things under the rug," HR is likely a dead end unless you have physical proof of a kickback or inappropriate behavior. Instead, use the Financial Angle.
New leadership during layoffs cares about one thing: Cost.
If the vendor is costing the company money through incompetence, they are a liability.
Present a "Build vs. Buy" or "Vendor vs. In-House" cost analysis to the EL.
If the vendor's mistakes cost $50k and your in-house fix costs $5k, the EL will follow the money. Your manager can't defend the vendor against a spreadsheet without looking suspicious to the EL.
Comparison of Risks
| Action | Risk | Benefit |
| Stay Silent | High. You are the designated scapegoat for the next round of layoffs. | None. |
| Report to HR | High. If the culture is protective, you become a "troublemaker." | Potential investigation. |
| Technical Briefing with EL | Moderate. Manager might get "mad," but you gain EL protection. | Highest. Clears your name and proves your 18-year expertise. |