When You Accidentally Send Your Note-to-Self to the CEO

I'm an extremely logical person.

I'm also simultaneously entirely ridiculous, silly, and self-aware, and unaware. I also spend an inordinate amount of time alone with my thoughts.

This combination creates a situation where I'm constantly amusing myself by critiquing what my brain decides to do as well just being, well, let's put it in a nice way -- 'creative.'

People don't generally have to deal with it to any significant degree, but sometimes, moments like the one below happen.

In this instance, we had a number of different blog posts which were supposed to be released on a set schedule. Some of those helping with the creation of the posts are relatively new to the team and processes.

The account from which these posts were to be published, was a shared account, created by none other than, our wonderful CEO, David.

The blog posts were meant to be loaded, saved, but NOT submitted into our queue. The risk being that not everyone on the editorial team would be super in-tune with the exact day of publishing for this specific series of posts and thus publish them prematurely.

Well, a few of those working on them accidentally submitted the content into the queue, uh oh.

Being slightly more OCD than I care to admit, I jumped in to save the situation by rejecting the post until the time was right.

There is a field one must fill out for why they reject a post. Naturally, the technical reason for me in my frazzled state of mind, was "none." Because well, it wasn't a real rejection.

Below is the confusion that ensued.

I don't remember the last time I laughed so hard I hard cried involuntarily.

Mind you, it also took me a second to realize this was my doing...

Hey just got our rejection email for the first time in a while. Can we tweak the rules or copy a bit?

Issue RN is it reads "every writer deserves feedback" and then goes ":none" --- maybe if feedback = none we just remove this copy "When asked why (because every writer deserves feedback) they said: None"? Alternatively could just cut copy of "(because every writer deserves feedback) "

I think here the problem is that whoever rejected the story didn't actually provide a reason. If I was the writer I would be p*** up too lol

Ah ok I see. Maybe another solution is to leave the email as is, but block "none" as an option for editors?

No that email copy is for when editors click on the “other” option and whoever did typed “None” as the reason lol

lol

LOL y'all, I'm dying. I rejected it. Omg I'm crying lmao. I forgot these ones would go to David, Oh I can't.

We should slog this thread!

Sounds good 🙂 David mentioned this already, I said I'd put it in the list I'm compiling, my goal is to have it done in the evening at some point.

richard-kubina Richard, it's not letting me create this Slogging thread 😞

I want to publish it from my account.

Richard 😞

Hey!

Hai 🙂

If you click the channel name and then goto integrations you can add slogging to the channel:

This unfortunately has to be done for each channel you want to use it on.
(though I hear enterprise slack workspaces can manage this in an easier manner).

Last time it gave me an option to do it after, but I will try, one sec.

IT WORKED RICHARD

Yea this came up recently in another channel and the call doesn't even make it to our server.. but it seems really weird that slack doesn't show a helpful message there so maybe there is something in our power we can do.

Thank you 🙂

:deployparrot::dino:

hahah we should add all these instructions in there 🙃 jokes

I want to, it will be the second one with me failing though, not sure how David will feel about that, but I think the ones going forward won't have it, now that I'm an 'expert,' so I think I'll keep it in haha

Can you make a draft a second time? Let me test

OH COOL