when someone turns in their notice, you should not respond with:
π silence
π stony stares
π retaliation
π pressure
π guilt tripping
π ignoring them
π failing to meet their eyes
π saying "we're better off without them anyway" TO ANYONE
-- my subtweet of the day
if you really are better off without them, that's a problem with *your* managers, not their fault. saying so is sour grapes, and making it about them inappropriately.
if you loved working with them, by all means tell them how much you will miss them, and you hope to work with them again someday! this is a small industry, and you very likely will.
don't leave them with a lingering sour taste about you.
guilt tripping is just flat uncool. if you loved having them and will miss them, say so. but it's on YOU to make your company the best place for them to work for as long as possible.
try to expect people to do the right thing for themselves, and thank them for doing so.
i say "try to", because in fact most people don't. most people hang on to a job that's no longer what's best for them for WAY TOO LONG, because they feel loyalty to the people, or have an overdeveloped sense of responsibility, or their bar is terribly low due to past experiences.
people actually need encouragement to do what's right for them more often than not. if you're a leader worth your salt, you won't force people to act in ways that aren't in their best interest.
you'll work with them to find a good fit, and you'll wish them well when there isn't.
i realize this is a high bar, and it's okay if people never quite feel comfortable to do it, but our explicit, oft-stated goal for managers at honeycomb is that reports should *always* feel safe bringing up whether or not it's time for them to leave or not.
it's in everybody's best interest to be able to discuss what isn't working openly. "no retaliation" is a low fucking bar, and we should be able to do a hell of a lot better. ALL of us should.
you're not going to get fired or put on a mental "short term" list. if it's not working, if we've exhausted all attempts, it probably sucks more for you than anyone else, so let's come up with a graceful exit plan together that lets you have agency over the process.
but like honestly.. *what are you thinking*, treating people this way?
if you didn't like working with them, it's so easy to say nothing and treat them politely for what, two more weeks? the end is in sight! be decent. you never know who may have power over you in the future. π
if you loved working with them and you want them to think well of you, how do you want them to remember you?
at honeycomb we call it "graduation" when someone leaves, and we throw them a party. we tell stories of their triumphs. π₯³π
it's a small fucking industry full of gossipy people. for purely selfish reasons alone, this is wrongheaded behavior.
if you want to work with your favorite people again, don't salt the earth -- leave them with a warm glow in their belly when they remember you.
the way you build loyalty as a leader is by showing that you do what's best for any individual person, even when it's harder for you in the short term.
people will flock to you, they will want to work with you over and over again. you can fuck up a lot if you get this one right.
and if you're wondering who i'm subtweeting, the list is too long to count at this point. everyone is leaving their jobs, and y'all are *not* making this a pleasant experience for the most part.
(i'd love to hear testimonials of companies that are doing it right βΊοΈ)
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
First: if it's sapping your essence over an extended period of time, just leave. You're no good to us dead.
It's worth persevering through some difficult times when you:
* believe in the mission, that the world is a better place if it succeeds
* have real power to effect change, formally or informally
* can see green shoots, or the wheels beginning to turn, however slowly
and part of that means consistently giving them feedback, constructive as well as praise.
*ask* how they prefer to receive feedback. give it gently, give it timely, give with a true spirit of "trying to help each other become better". don't let things snowball into badness...
and *solicit* their feedback for you with equal vigor. solicit often, receive it gracefully, show that you heard it and are making changes.
trust is built in part by being willing to say awkward things, by showing up to discuss the hard things with care and sensitivity.
if you are working at a place where you are being actively mistreated, i actually think you have a moral responsibility to leave (if you can do so).
caveats abound, of course.. it is not YOUR job to fix shitty companies, many are not fortunate enough for this to be an option, &c
but companies are out there feeling complacent about their employees and blind to their pain. i guarantee you nearly every leadership team is like "this is a great place to work" *pats self on back*
by staying, you vote with your feet and your labor for shitty companies to win.
when people start leaving and being straight up with their leadership teams about why they're leaving, it's one of the only things that can shock a company into changing course or trying to do better.
Once someone has experienced how much easier it is writing code with real observability, you cannot pull it out of their cold dead hands. It's like getting glasses for the first time, and realizing you could barely see the world around you.
This is partly a generational thing. Those of us who grew up writing software with metrics and logs have a lot of unlearning to do, a lot of trauma and frustration to unwind.
Engineers who never learned to navigate monitoring tools actually have it much easier picking up o11y.
I would actually argue that, with the right tooling, production is *exactly* the most effective place to take chances, make mistakes, and get messy. π Otherwise you're like this guy.
Here are the slides for a talk of Liz's that I modified slightly and delivered on Wednesday for the O'Reilly InfraOps superstream. speakerdeck.com/charity/observβ¦
We walk you through the honeycomb backend, some of the ways we perform chaos engineering, and some infamous outages,
to show just how swiftly, accurately, and powerfully you can manipulate systems with modern tooling (feature flags, fast delivery, superb observability) and do whatever the fuck you want in prod without hurting your users.
LARGE SYSTEMS USUALLY OPERATE IN FAILURE MODE, via @dangolant
Or like I used to say, your distributed system exists in a continuous state of partial degradation. There are bugs and flakes and failures all the way down, and hardly any of them ever matter. Until they do.
This is why observability matters. SLOs make large multitenant systems tractable from the top down, but observability makes them comprehensible from the bottom up.
Maybe only .001% of all software system behaviors and bugs ever need to be closely inspected and understood, but that tiny percentage defines the success of your business and the happiness of your users.
And you CANNOT predict what will matter in advance.