this post was submitted on 22 Oct 2023
61 points (94.2% liked)
ADHD
9286 readers
42 users here now
A casual community for people with ADHD
Values:
Acceptance, Openness, Understanding, Equality, Reciprocity.
Rules:
- No abusive, derogatory, or offensive post/comments.
- No porn, gore, spam, or advertisements allowed.
- Do not request for donations.
- Do not link to other social media or paywalled content.
- Do not gatekeep or diagnose.
- Mark NSFW content accordingly.
- No racism, homophobia, sexism, ableism, or ageism.
- Respectful venting, including dealing with oppressive neurotypical culture, is okay.
- Discussing other neurological problems like autism, anxiety, ptsd, and brain injury are allowed.
- Discussions regarding medication are allowed as long as you are describing your own situation and not telling others what to do (only qualified medical practitioners can prescribe medication).
Encouraged:
- Funny memes.
- Welcoming and accepting attitudes.
- Questions on confusing situations.
- Seeking and sharing support.
- Engagement in our values.
Relevant Lemmy communities:
lemmy.world/c/adhd will happily promote other ND communities as long as said communities demonstrate that they share our values.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Saw this post on 'All'. I do not have ADHD, but I believe I work with someone who does. I don't want to take over ops question, but perhaps add an additional question/angle that could be helpful:
How should I work with him? It's just not feasible to work on everything he wants at once. And he overwhelms me daily with long documents and emails full of random thoughts. I worry I'll be next on the chopping block if I don't figure out a way to work with him.
I'll throw my hat in. Get an idea of what his goal is, ask him to lay it out in steps. Tell him you'd like to focus on just one throughline before you move to the next. When he overwhelms you let him know that it's distracting.
Most importantly though, start working on your resume, because you're working at a company that refuses to manage expectations and does not support you. If one Engineer is causing high turnover like that and management doesn't care, that's a big red flag.
In this situation, we are both management level. I don't think anyone has tried to just flat out tell him he's making a mess of things and distracting people. Maybe being upfront about it could help avoid repeating history.
Bingo.
If he's getting people fired I'd just start interviewing. Sounds like others have tried to work through the tasks in a reasonable way and it didn't work out.
Otherwise, document EVERYTHING and CYA!
Is this in a software context? If so, mandating structured RFCs will help a lot. It will channel random streams of thoughts into constructive, actionable proposals.
Have your first RFC be about how to structure an RFC. Make a cost/benefit analysis (in real money if possible) be a mandatory part of the proposal. Commit all of them to a main branch in git even if they are rejected because you would preserve the original discussions around that particular proposal.
Basically anything that can be an epic ticket can and should be an RFC first.
Thanks, good advice. The context is technology. I'm on the tech side. The other person is outside of tech ("the business").