At some point in the annals of corporate history, we decided that “low-hanging fruit” was the perfect metaphor for easy wins, quick fixes, and tasks so obvious that any reasonable person could dispatch them before their second cup of coffee. And now, decades later, we’re all stuck with it – tossing the phrase around in meetings as though we’re all working in the same orchard while standing at the same height, with the same reach and/or the same ladder.
But who decides what scrumptious pieces of fruit are, in fact, hanging “low?
Because the fruit that’s dangling right at eye level for you might be somewhere around my kneecaps, or, depending on a dozen other variables I don’t have visibility into, it might require a cherry picker, three bucket trucks, and a cross-functional task force just to locate the tree. “Just grab the low-hanging fruit,” someone says, breezing into the room with the confidence of someone who has never once, or so they like to pretend, misjudged the distance between a concept and its execution.
What if I make the wrong call? What if I look at the situation, assess the orchard, and confidently pick something that turns out to be neither low-hanging nor particularly ripe and everyone else in the room knew it was the wrong choice, but no one said so, because the metaphor made the whole thing sound so obvious? There’s something slightly terrifying about that possibility … especially in workplaces where “just handle the easy stuff first” is code for a WHOLE set of unspoken assumptions that nobody has ever bothered to define.
A Question of Altitude
The existential problem with the low-hanging fruit directive is that it presupposes shared context, shared perspective, and roughly equivalent fruit-reaching capability across all parties. None of which can be assumed. The person issuing the directive may be working from a completely different vantage point – organizationally, politically, informationally – and the thing that looks effortless from where they’re standing might look, from where you’re standing, like it involves a significant amount of untangling, stakeholder navigation, and at least one uncomfortable conversation with someone in Finance.
This isn’t a complaint about the phrase itself – though I do have feelings – so much as it’s an observation about how casually we deploy it … as though “low” is a fixed point in space rather than a deeply relative one. Low compared to what? Low according to whom? The orchard looks different depending on where you enter it, and two people standing in the same grove will walk away with very different assessments of what was reachable and what wasn’t.
Which means, of course, that the directive itself is the problem – not because the fruit doesn’t exist, but because “low” is a relative term masquerading as an obvious one. So before anyone starts reaching, the more useful conversation is probably about the orchard itself: what we’re looking at, from whose vantage point, and whether we’re all even standing in the same grove.
Because perspective, it turns out, is the whole thing. The fruit just hangs there.
There was a time – and I know you remember it, if only dimly – when you could wander down to the break room, pour yourself a cup of terrible coffee, and exist, unbothered, for twelve glorious minutes. No one knew where you were, nor did anyone need to know. You were simply… between things. Thinking, maybe. Or staring at the walls. Maybe reading a 5-year-old copy of Martha Stewart Living from the pile of periodicals strewn on the end table next to the couch. It really didn’t matter because you were gloriously off the grid.
Sadly, that era is gone and, in its place, we have the Status Field.
Whether your workplace runs on Slack, Teams, Google Chat, or Facebook Messenger, the expectation is the same: your digital presence must be accounted for, at all times, during all working hours, with the precision of Artemis II mission control. The little colored dot beside your name – green, yellow, red, that ambiguous grey – has become the modern-day equivalent of clocking in, and lord help you if that dot goes grey for longer than it takes to use the bathroom, because somewhere, someone is watching.
It’s accountability theater, really: the performance of availability in a world that has conflated being reachable with being productive.
A Taxonomy of What Your Status Actually Means
Let’s be honest now: the status you post, and the reality of your afternoon are not always the same. Here’s a more accurate field guide, from out here in the real world, of what your workplace “status” really means:
“In a meeting” might signify you are in an actual meeting, It might also mean you’re staring at the middle distance after having endured forty-seven meetings this week alone (and it’s only Wednesday) and you simply need people to stop making demands of you for twenty minutes. You’re present, technically, but your soul has left the building.
“Focusing” – a personal favorite, particularly on platforms that let you schedule a “Focus Block” – means you have erected a small digital velvet rope around yourself. “Focusing” communicates that you are “in the zone” where deep, important work is underway. It does not, however, specify that the work involves watching all of Britney Spears’ official music videos in strict chronological order, from “…Baby One More Time” through the Blackout era and onward, because someone mentioned “Toxic” in a meeting and now you’re three decades deep into a YouTube spiral that started as research and has become spiritual.
“Away” means you stepped away from your desk and forgot to change it back two hours ago. Or you changed it on purpose and are currently assembling a charcuterie board with items procured entirely from the vending machine (Gardetto’s, a bag of M&Ms, a sleeve of Animal Crackers) arranged with more care and architectural precision than anything you’ve accomplished at work this quarter. You’ve got the pretzels doing the heavy lifting in the corner, the M&Ms are the accent color, and you’re quite proud of it.
“On a call” can, of course, mean you are on a call. It can also mean you are avoiding a call you were supposed to make an hour ago and are using this status pre-emptively. It’s aspirational really; just like your organizational culture.
“BRB” means you are either returning shortly, or you just typed “BRB” and then walked directly into another meeting, started a new task, or went to go put out another fire. You will eventually surface again sometime before the end of the day. Maybe.
The Myth of the Open Door (Digital Edition)
What we’ve built here, collectively, is a culture in which the expectation of instant availability has been woven so deeply into how we work that we now police our own downtime. We’ve become workers droids who pre-emptively justify our absence and change our status before we take a walk around the block to clear our head because, apparently, a fifteen-minute absence requires documentation. And oh boy…do we feel guilty about the grey dot and the unanswered message that sits there (read but not yet responded to!) while we do something as audacious as eat lunch.
But what are we gaining from all this? The illusion of connectedness? Maybe. For those managers and organizations that aren’t sure they trust their people, they have the comfort, I guess, of knowing (for a moment) that everyone is accounted for. It’s a new version of the old-school time clock for the knowledge-worker/desk-bound class.
What we’re not gaining is the kind of creative thinking that happens precisely when people are not staring at a screen waiting for the next message to land.
A Modest Proposal
I do wonder what would happen if everyone, for a designated stretch of time, simply didn’t have a status? No dot, no label, no “focusing” or “away” or the dreaded “Do Not Disturb” that, perversely, seems to invite more disturbance. What if being unreachable for an hour were treated not as a crisis or an anomaly, but as a normal, healthy, expected part of a working human’s day?
Here’s my guess: most of the things that seemed urgent would resolve themselves, because they always do. We would discover that the questions that feel like they need an answer right now rarely do. We would find that the people you’re surround by every day – your team, your colleagues, yourself – might emerge from that hour with a thought they hadn’t had before or an idea that simply needed some peace and quiet to take shape.
We’ve normalized the expectation of perpetual availability as a baseline condition of employment, but maybe it’s time to normalize the opposite. And no; not as an exception or a perk or a “wellness initiative” (please, not another wellness initiative), but as a simple acknowledgment that people who are allowed to be unreachable – occasionally, on purpose, and without explanation – come back better.
The break room is still there, metaphorically speaking, so go wander. And when you do, set your status to whatever you like.
At some point in the evolution of the workplace, someone decided that the polo shirt was the ideal canvas for a company logo. That decision has never really been questioned since.
The “company polo” became a mainstay of corporate life; as immutable as mandatory fun and the phrase “circling back.” If your organization has ever launched an employee recognition program, onboarded a new team member, had employees attend a conference together, or celebrated a milestone of any kind, there’s a near-certainty that polo shirts were involved. Piled into boxes and handed out by enthusiastic Marketing and HR staffers with genuine enthusiasm, they were accepted by employees with the kind of polite smile that doesn’t quite reach the eyes.
The polo shirt is, in theory, business casual. In practice, it is neither business nor casual, but rather a garment suspended in an uncomfortable liminal zone where formality and leisure cancel each other out and produce something that flatters essentially no one. Not the tall person whose torso it skims in all the wrong places, not the shorter person swimming in a size that was probably the only one left, and, let’s be honest, not even the tennis player or golfer, for whom the polo was ostensibly designed.
And yet, here we are. Every fiscal year, organizations spend real money – budget that could theoretically fund professional development, or better coffee, or at minimum a modestly improved onboarding experience – on polo shirts. Stiff, heavy polo shirts in colors selected by committee, embroidered with a logo that will be permanently affixed to the left breast, which is, without exception, the exact wrong location for approximately every human body it encounters.
The Fabric Problem
Let’s start with construction, because the fabric deserves its own reckoning. The traditional corporate polo tends toward a heavy pique cotton that’s designed to hold its shape and project a certain… seriousness of purpose, I suppose. It is also, in practice, quite warm; particularly delightful in the summer months when your organization decides to send everyone to an outdoor event in matching polos, and they all spend the afternoon wilting in unison. And if the organization has moved toward the more “modern” moisture-wicking performance fabric – the kind that’s marketed as breathable and athletic – the experience is not meaningfully better, because that fabric will cling in ways that feel deeply personal. (And is rarely flattering to anyone who is not actively competing in a triathlon).
The Neckline Problem
Then there’s the neckline, which is to say: the placket. That two-to-three-inch strip of buttons sitting at the collar, rubbing against your neck with the persistence of a minor grievance. For anyone who has worn a polo for more than two hours, that placket becomes impossible to ignore; a low-grade irritant that you keep trying to adjust, unconsciously, approximately every eighteen minutes throughout the event. It’s the kind of design detail that makes you understand, at a visceral level, why turtlenecks need to have a revival.
Women, in particular, have reached a kind of collective, unspoken consensus on the polo neckline, and that consensus is not favorable. The collar sits at an awkward height, neither open enough to be comfortable nor structured enough to look deliberate, and the buttons suggest a formality that the rest of the shirt doesn’t quite support. It’s a highly unflattering neckline that commits to nothing while simultaneously managing to irritate everyone.
The Logo Problem
And then we arrive at the logo; the whole reason we’re here and the very point of the shirt’s existence. The logo is embroidered with careful precision onto the left breast and placed, through some alchemy of garment sizing and human biology, in a location that is uniquely – and reliably! – wrong for women across the full spectrum of body types, ages, and sizes. It’s too high on one person, too low on another, and occasionally landing in a spot so anatomically nipple-specific that it becomes a conversation starter in itself.
The logo, to be clear, is not the problem; it merely has the reasonable ambition to represent the company brand. It’s the placement of the logo that raises the question of whether anyone involved in this process has ever worn one of these shirts, or whether the decision-making happened entirely as an abstract exercise.
Safe, Not Strategic
Now the impulse behind giving people corporate branded apparel – shirts, bags, mugs, whatever – is a fundamentally nice human gesture. There’s warmth in it and organizations that invest in belonging and shared identity are doing something meaningful. The intent behind the polo is not the problem.
The problem is that the polo has become the default because it feels “safe”. Oh, it’s undoubtedly the “best practice” of corporate swag; no one gets fired for ordering polo shirts, no one raises an eyebrow, and no one challenges the assumption that this is simply what you do. So, the purchase requisition gets approved, the shirts are ordered in bulk, they arrive 14-17 business days later, and they’re distributed by already-overworked department supervisors. Each employee takes the shirt home and shoves it in the bottom drawer of a dresser where it is destined to reside for eternity with an occasional appearance for either yard work or the casual Friday when every other wardrobe option is in the laundry.
But if organizations are willing to think critically about engagement strategy and employee experience and about whether their systems and processes meet the needs of the people using them (and most organizations will tell you they are), then perhaps it’s not too radical to extend that thinking to the corporate polo shirt. To ask before placing the default order:
Does this represent ALL of us?
Does anyone even want to wear this style/color/fabric?
Does this shirt make the people wearing it feel good?
Does it fit and/or flatter the range of bodies on our team … or just the theoretical average (male) body someone was imagining?
The Corporate Polo Shirt endures because no one has asked, for 50+ years, whether it should continue to do so. And that, if you’ll forgive my pointing it out, is a very HR thing to do.
For decades, HR professionals have played an unspoken career game: chase the biggest logo you can land. The assumption baked into this – that working for a massive, household-name enterprise signals intelligence and ambition, while toiling at a mid-market privately-held bank or a 300-employee hospitality group signals something lesser – has shaped career decisions, résumé choices, and professional identities across the field. Nobody wrote this rule down because nobody had to.
It’s OK to acknowledge this weird ego-driven reality, as well as realize that it doesn’t just play out on the coasts. Even in middle America, if you’re in a city of 70,000, the “prestigious” (and coveted) HR gigs will be those at the regional medical center, community college or lone remaining name-brand manufacturer as opposed to the family-owned home building company.
And we are currently at yet another work and tech inflection point – one that, like early 2020, has the potential to reorder nearly everything we thought we knew about how work functions, and fast. As agentic AI – autonomous systems that can execute complex projects rather than just answer prompts – becomes standard in 2026, I predict that the “prestige” of the enterprise HR role is evaporating.
I believe that in a swiftly coming reversal of all we have previously believed, HR professionals will soon be clamoring to work for Small and Medium Businesses (SMBs) and mid-market organizations and backing away from enterprise giants.
Let me tell you why.
The Enterprise Efficiency Trap: Math That Eliminates You
Imagine you’re an HR Manager, an HRBP, or an HR Generalist (whatever moniker they’ve assigned you) working for a large enterprise with 100,000 employees. Using a headcount calculation in a shared services model that also has HR Centers of Excellence, there is roughly one HR staffer for every 300 employees. That puts the total HR population at around 333 people, with perhaps 175 of those being you and your fellow HRBPs.
In this environment, each of those 175 HR Managers might spend seven hours a week on repetitive administrative tasks — data entry, routine inquiries, performance review tracking. With the agentic revolution, companies can now deploy AI to take over these tasks, compressing seven hours of work into roughly 20 minutes of oversight. Speakers at HR conferences and various HR pundits tend to call this the “strategic dream,” but the enterprise reality looks considerably different.
Saving seven hours per week across 175 managers equals 1,225 hours – the equivalent of more than 30 full-time HR positions. Jittery CEOs, eager to reassure boards in an uncertain economy, will use these efficiencies to justify headcount cuts, and the end result is that you either absorb a much larger, more stressful territory with no increase in pay, or you discover you’ve been replaced by the very software that promised to free you.
The SMB Sweet Spot: Scale That Protects You
Now in an SMB or mid-market firm – think organizations in the range of 100 to 999 employees – the math is entirely different. These organizations often operate with a tighter ratio, perhaps 1:50, meaning a company of 150 people might have a small, dedicated HR team of three or four people. In these environments, AI is deployed to improve the work rather than eliminate the worker, and the reasons why are worth understanding.
When AI saves time on administrative tasks for a three-person HR department, the time recovered simply doesn’t reach the threshold of elimination for a full-time position. That said, the time freed up also just doesn’t disappear into a spreadsheet, but rather gets redirected into genuinely high-value work: culture building, employee retention, and organizational effectiveness. SMBs will continue to rely more heavily on human judgment to navigate performance issues, mental health conversations, and interpersonal conflict – all those areas where AI still lacks the nuance and empathy that HR work demands.
From Transactional Partner to Human Capital Consultant
This realignment isn’t just about job security, though. It’s also about job fulfillment.
A Mercer survey just two years ago found that nearly half of HR Business Partners felt more like “transaction partners” than strategic advisors – and that was before AI accelerated the commodification of routine HR work. In my estimation, the most exciting roles emerging right now may be in mid-market firms, where HR can finally evolve into something closer to a Human Capital Consultant: someone who uses Generative AI (GAI) to process and interpret talent data, who acts as a genuine strategic partner to senior leadership, and who is adept at translating people data into the business actions that leaders will take.
The concept of antifragility is worth naming here – the need to develop HR professionals who don’t just withstand disruption but grow stronger because of it. That’s the kind of work that requires a human being who understands an organization’s culture, history, and people – not the kind of work that scales nicely into some sort of workflow automation.
The New Career Currency: AI Adaptability
To thrive in this realigned market, it’s time to recalibrate what career success looks like for HR professionals which includes recognizing the logo on your resume matters considerably less than your digital agility. The good news is that making this shift to AI adaptability isn’t as daunting as it sounds.
Prompt engineering, for instance, sounds intimidating until you realize it’s essentially learning to give very precise instructions – something HR has been doing for decades (am I right?) just usually with managers instead of machines. Learning to design refined AI instructions for functions like recruitment screening or engagement analysis is a skill that transfers quickly and pays dividends fast. Beyond that, HR can lead the AI transformation by example; practically integrating GAI into everyday workflows and then telling that story to leadership (loud and proud!) and demonstrating, concretely, what the HR function is now capable of.
On the flip side, the ability to use explainable AI to understand things like attrition patterns and adjust the contributing factors for individual employees will become one of the most valuable skills in the profession. In an economy where organizational anxiety runs high and stability is a genuine competitive advantage, understanding staff retention (with precision!), is clearly much more than a soft skill.
The most important year of your HR career
The window to adapt, however, is brief, and the HR practitioner who understands what’s coming – and can navigate the shift with both strategic clarity and human judgment – will be the most valuable HR pro in the room. And while enterprise organizations are using AI to satisfy shareholders by thinning the herd, SMBs and mid-market firms are where AI is rapidly being used to empower HR to finally do the strategic, human-centric work we’ve always wanted to do.
It’s time to stop chasing the biggest logo and start chasing the biggest impact.
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
