Introducing Margin: A Weekly Newsletter on Leadership and AI Insights from Global HR Perspective

Rui B. · 2026-08-03T04:11:56.589Z

Hi all. Rui, joining from the people side rather than the revenue side. I run global HR, which mostly means I am downstream of every number in this Slack. When quota gets missed, when a territory gets redrawn, when a leader quietly burns out, that lands on my desk. I write a weekly newsletter called Margin. about leadership and what AI does and does not change about it. Five minutes, Tuesdays. margin.ruibashir.com/?… (https://margin.ruibashir.com/?utm_source=revgenius&utm_medium=intros) Here mostly to understand how you all think about it upstream.

5 comments

· Sorted by Oldest

jonatan
·
·
welcome Rui. the people side is the angle this channel is short on, and downstream of every number is exactly right. most of what lands on your desk started as a systems decision nobody wrote down. a territory redrawn off bad account data, a quota set from a forecast that was already rotten two quarters earlier. by the time it reaches HR it reads as a performance problem and gets a performance fix, which is why the same burnout keeps arriving from the same team every year and nobody upstream ever hears about it. the question almost nobody revisits is whether the number was achievable on the day it was assigned. good to have someone here who sees the back half of that.
Rui B.
·
·
Thanks jonatan. And this is the sharpest version of that I have read. The part I would add: usually someone did know the number was wrong on the day it was assigned. They said so once, quietly, to one person, and it never made it into anything written down. So a year later, when it surfaces as a performance conversation, there is no record that the doubt ever existed. The performance fix is the only one the evidence supports, because the evidence is the only thing that survived.
jonatan
·
·
that's the part worth underlining. the doubt gets spoken and the target gets written down, so only one of them still exists a year later. and it isn't an accident, it's incentives. saying "i don't think this is achievable" in writing is a career risk on the exact day it would be useful, and free to say twelve months later when it no longer matters to anyone. the cheapest fix i've seen work is recording the assumptions a number depends on next to the number, rather than the objections to it. pipeline coverage assumed, ramp time assumed, win rate assumed. nobody has to go on record doubting a colleague, and a year later you can check which assumption broke instead of arguing about who believed what. it turns the performance conversation back into a forecasting one, which is what it always was.
Rui B.
·
·
That fix is right, and the reason it works is that it does not ask anyone to be brave. The one thing I would guard against is this: any record that can appear in a performance conversation eventually gets written defensively. Once people learn the assumption log shows up when someone's year is being judged, the assumptions start arriving pre-hedged, and you are back where you started with better formatting. What keeps it honest is reviewing it on the forecast cycle rather than the performance one. Same quarter the number was set, reviewed by the people who set it, with nobody's rating in the room. The moment it becomes an exhibit, it stops being a record.
jonatan
·
·
agreed, and i think the thing that decides which way it goes is who writes the entry. if the person carrying the number writes it, it becomes a defense file. if the person setting the number writes it, it is just their own forecast showing its work, and there is nothing to pre-hedge. the other guardrail is only logging assumptions you already measure anyway. coverage, ramp, win rate. the moment the log has a field that exists only for the log, someone starts writing for an audience.

jonatan
·
·
welcome Rui. the people side is the angle this channel is short on, and downstream of every number is exactly right. most of what lands on your desk started as a systems decision nobody wrote down. a territory redrawn off bad account data, a quota set from a forecast that was already rotten two quarters earlier. by the time it reaches HR it reads as a performance problem and gets a performance fix, which is why the same burnout keeps arriving from the same team every year and nobody upstream ever hears about it. the question almost nobody revisits is whether the number was achievable on the day it was assigned. good to have someone here who sees the back half of that.
Rui B.
·
·
Thanks jonatan. And this is the sharpest version of that I have read. The part I would add: usually someone did know the number was wrong on the day it was assigned. They said so once, quietly, to one person, and it never made it into anything written down. So a year later, when it surfaces as a performance conversation, there is no record that the doubt ever existed. The performance fix is the only one the evidence supports, because the evidence is the only thing that survived.
jonatan
·
·
that's the part worth underlining. the doubt gets spoken and the target gets written down, so only one of them still exists a year later. and it isn't an accident, it's incentives. saying "i don't think this is achievable" in writing is a career risk on the exact day it would be useful, and free to say twelve months later when it no longer matters to anyone. the cheapest fix i've seen work is recording the assumptions a number depends on next to the number, rather than the objections to it. pipeline coverage assumed, ramp time assumed, win rate assumed. nobody has to go on record doubting a colleague, and a year later you can check which assumption broke instead of arguing about who believed what. it turns the performance conversation back into a forecasting one, which is what it always was.
Rui B.
·
·
That fix is right, and the reason it works is that it does not ask anyone to be brave. The one thing I would guard against is this: any record that can appear in a performance conversation eventually gets written defensively. Once people learn the assumption log shows up when someone's year is being judged, the assumptions start arriving pre-hedged, and you are back where you started with better formatting. What keeps it honest is reviewing it on the forecast cycle rather than the performance one. Same quarter the number was set, reviewed by the people who set it, with nobody's rating in the room. The moment it becomes an exhibit, it stops being a record.
jonatan
·
·
agreed, and i think the thing that decides which way it goes is who writes the entry. if the person carrying the number writes it, it becomes a defense file. if the person setting the number writes it, it is just their own forecast showing its work, and there is nothing to pre-hedge. the other guardrail is only logging assumptions you already measure anyway. coverage, ramp, win rate. the moment the log has a field that exists only for the log, someone starts writing for an audience.