Each week, I come across dozens of articles and think pieces. Most are fine. Some don’t just quite land with me. But a handful? Those stop me in my tracks. They make me think differently, challenge an assumption I didn’t know I had, or give me language for something I’ve been feeling but couldn’t quite name.
This isn’t a comprehensive roundup of “the most important news” or some curated list. It’s just honest. These are the pieces that hit me this week, the ones I bookmarked, commented on or liked, and shared with colleagues. Most are about leadership, teams, and how we show up at work. A few aren’t. But they all mattered.
If even one of these lands for you the way it did for me, that’s a win.
In no particular order, here’s what caught my attention this week:
1. The Scoreboard Is Lying to You
By: Joel Trammell
What it’s about: When a company rides a hot market, results look strong even when the leadership team is mediocre. The market does the heavy lifting but the wins get attributed to the people, and nobody questions the process when revenue is flowing. The real test comes when conditions shift, and suddenly the team that looked like A-players is paralyzed because they were never actually that good to begin with.
The argument is that leaders need a higher standard than the scoreboard, things like evaluating discipline, process, development, and values-alignment during the good times, because that's the only window where you have the luxury to do it honestly.
2. Don’t Confuse Hard Work with High Potential
What it’s about: The video argues that talent is always relative. What looks exceptional in a weak talent pool is often just average performance with a low bar, and organizations consistently mistake relative superiority for actual excellence.
The more important distinction is between hard work and high potential, which are frequently confused but fundamentally different: hard work is effort and reliability, while high potential is the cognitive capacity to operate at higher levels of complexity, learn faster, and scale impact as demands increase. Someone can be the hardest worker in the room and never advance beyond their current level. Not from lack of dedication, but because the bandwidth required for the next level simply isn’t there.
The closing reframe is the right one: the question isn’t whether someone is good, it’s good compared to what, good compared to whom, and good for what.
3. Do You Choose to Work with Broken Tools?
It’s hard for people to love their job when leaders provide broken tools!
What it’s about: The article uses a home renovation analogy to make a pointed argument: most organizations would never hire a tradesperson who showed up with broken, outdated tools, yet they ask their own staff to do exactly that every single day.
The double standard is the core problem: frontline employees cobble together workarounds with failing systems while leadership remains insulated from the same friction, creating no burning platform at the top to drive change. Budget constraints get cited as the reason nothing improves, but budget is always a choice of priorities, and the people paying the price are the ones closest to the customer.
The closing point lands hardest: employees are then reviewed on performance with no acknowledgment of the broken environment they’re working within, asked to develop themselves with little time or budget, while the tools problem that’s limiting them goes unaddressed.
4. Nobody gives up territory without a fight
How to protect value when interests collide
By: Luca Foppoli
What it’s about: The article presents a three-step framework for navigating resource conflicts with peers, the kind of territorial disputes that happen constantly in organizations but rarely get handled with any real structure.
The three moves build on each other: step back to agreed value to reframe the conversation on shared ground, push to measurement to shift the burden of proof onto whoever is making the competing claim, and propose alternatives only after the value argument has already won, because alternatives offered too early read as concessions under pressure and create precedents you don’t want to set.
The closing point is the most honest thing in the piece: the framework takes you as far as your position allows and not one step further, and the only sustainable long-term defense is a reputation for optimizing for the organization rather than yourself, built visibly enough over time that people trust your pushback is principled, not territorial.
5. Donated Competence: When Capability Turns Into Dependency
Employee Lens
What it’s about: The article introduces a framework distinguishing three layers of workplace competence: contracted competence (what your role formally requires), extended competence (discretionary effort that adds capacity without filling structural gaps), and donated competence (compensatory effort that quietly holds a flawed system together in place of actual structural fixes).
The core insight is that donated competence feels like professionalism and gets praised as loyalty, but it actually masks organizational design failures rather than correcting them, the system adapts around the reliable person instead of fixing the underlying problem, making that person infrastructure rather than a candidate for development or promotion.
The diagnostic question at the end cuts to the heart of it: if you stopped compensating tomorrow, would the system continue functioning within its designed boundaries, or would instability surface immediately? The answer tells you whether you’re adding value or quietly carrying weight the organization has chosen not to acknowledge.
6. Every Leader Is In Sales
A business leader needs to effectively sell their ideas in order to garner support, inspire action, and drive meaningful change.
What it’s about: The article argues that influence (persuading, convincing, and getting people to believe in a direction) is one of the most critical leadership skills, yet it never appears in a single leadership competency model because we dress it up in more palatable language like alignment or stakeholder management.
The core insight is that logical arguments alone rarely move people because resistance to change isn’t stubbornness, it’s human wiring, and when leaders fail to actually sell their vision, the consequences are quiet rather than loud: passive resistance, initiatives that get announced and then disappear, and talented people who disengage rather than dissent.
The closing reframe is the right one: the ultimate measure of leadership isn’t the quality of your ideas, it’s your ability to turn those ideas into shared conviction and action, and that skill is learnable by anyone willing to understand how people actually make decisions.
7. Strategy Is Mostly Waiting
On finished products, founder instincts, and the discipline of not shipping
By: Joseph Fung
What it’s about: The article is a first-person account of one of the hardest strategic decisions a founder-turned-executive can face: holding back a finished, ready product because the timing wasn’t right. Not because the work wasn’t good enough, but because launching early would have tipped off a competitor and undermined deals already in progress.
The core tension is between founder instincts, ship early, get signal, move fast, and strategic patience, which requires sitting with uncertainty for months or years without the feedback loops that normally tell you whether you’re right. The author’s honest observation is that the pull to do something, anything, feels like decisiveness but is often just noise that muddies the data and distracts the team from the original bet.
The closing reflection is the most useful takeaway: sometimes the hardest strategic decision is the one where you don’t move, and sometimes you never get a clean answer on whether it was right, you just hold still, trust the bet, and find out later, if you’re lucky.
8. Trust and Delegation
Post 4 of the series titled ‘The Promoted’
By: From The Climb
What it’s about: The article is an honest reflection on how delegation is harder than it looks, specifically the gap between how a leader prefers to receive work and how the people they’re leading actually need it handed to them.
The core insight is that delegation isn’t one thing. It looks different depending on the work, the person, and where they are in their development, and the instinct to solve delegation problems by over-engineering the handover or taking the work back both have real costs that compound over time.
The closing point is the most useful: trust and delegation are the same problem. You can’t delegate well to someone you don’t trust to own it, and you can’t build that trust without giving them something real to own, which means handing things over before you feel entirely ready to, accepting that the outcome might look different than if you’d done it yourself, and resisting the urge to take it back when the silence makes you nervous.
I appreciate this inclusion, thank you.
The idea behind Donated Competence is simple but uncomfortable: systems don’t just fail, they adapt to the people who keep them running.
Thanks for sharing. Insightful articles!