Knowing when something is too much for you?
Posted by OrangeGrouchy179@reddit | ExperiencedDevs | View on Reddit | 19 comments
How do you know whether what you’re being asked to do is achievable or not? I often have this problem of being given an impossible task and not pushing back on it. Mostly because I feel like I should be able to do it. I’m neurodivergent as well which I’ve recently learned and I think that plays into it as well.
Leading_Yoghurt_5323@reddit
a good check is: can you explain how you’ll do it? if not, you probably need to push back or ask for clarity .
OrangeGrouchy179@reddit (OP)
No I don’t know. It’s a large migration. I don’t even feel like I know what tools I should be using to understand it.
CrraveCloverPin@reddit
I also have an agreeableness problem that’s gotten me into trouble. Best thing is to ask for time to figure out if it’s doable. Don’t just say “yes."
aa-b@reddit
Yeah, what I do is agree and start making diagrams and solution design documents until somebody notices it's obviously more work than one person can manage.
If nobody notices then maybe it's not really that bad, or at least you can use them to explain your progress (or apparent lack of progress)
Morazma@reddit
You should start any project like this with a timeboxed (1-2hrs) exploratory phase to research how achievable it is.
OrangeGrouchy179@reddit (OP)
The problem is I’m being asked to bring a large system in house. They’ve already asked one team to look at this, they hired a third party contractor to look at it. He produced a report and they didn’t like that so they’ve asked me.
GlobalCurry@reddit
Just say you need time and then do some individual research and write up a document about why you can't do it using the third party contractor and other team's documentation as references to prior research.
Wide-Pop6050@reddit
The third party contractor said it wasn't doable? So it probably isn't. Be careful and don't let them make you the fall guy for something that isn't doable.
As you said be very factual. Focus on the reasons - it would be doable if we stopped all other work. We would need to hire specialists in XYZ. Explain what the gap is.
OrangeGrouchy179@reddit (OP)
Basically they just want to stop paying the third party that develops this solution. However, they don’t want to hire more people either.
johnpeters42@reddit
People want lots of things. "Yes, and it will take 12 months of uninterrupted time and cost $1 million" (or whatever you think are the correct figures) is not "No", but it does ask management to decide: do they want to stop paying the third party that badly? (Maybe so, if dealing with the third party is a PITA beyond just costing money.)
ButWhatIfPotato@reddit
Just an FYI, your bosses are absolutely aware of this and are fully taking advantage of it.
Antique-Stand-4920@reddit
- Instead of thinking about a request in isolation, consider what you have to give up to accommodate the request.
- Know and enforce your limits. You have to work sustainably. Consider how miserable you'll feel or how miserable you'll be to others if you accept the request.
iComplainAbtVal@reddit
I don’t think neurodivergence really plays a part in this issue.
The issue is that you are able to conceptualize a pathway forward but fail to account for how difficult each step is. Just be blunt in response to those tasks. “I can see it potentially being possible through X avenue but lack the background/knowledge to give an accurate estimate of the workload. Let me get back to you by the end of the day with an update”
OrangeGrouchy179@reddit (OP)
I really struggle with planning. I think that’s a big problem. I think I’ve worked on so many failed projects as well now my brain doesn’t even know what success looks like anymore. It’s even bled into my personal life.
OrangeGrouchy179@reddit (OP)
What you made a lot of assumptions there. Typical developer. 😂
kevinossia@reddit
I don’t know. I’ll let you know when that happens.
OrangeGrouchy179@reddit (OP)
You probably need to step out of your comfort zone a bit then.
MonochromeDinosaur@reddit
Never commit to a deadline.
Always push back on scoping and requirements until they’re concrete.
Ask them what they’re trying to solve not what they want you to do (XY problem)
If they push back, tell them it needs a research spike to determine feasibility and even then you’ll only be able to provide a range best case range for delivery and only if it’s narrowly scoped and feasible.
I do this for every ambiguous task. I’m not risking a failed project on someone’s whim.
Mono-Guy@reddit
"Nothing is impossible. But there's a lot of things that are way outside our budget and timeline."