avoiding work siloes
you can spend days to weeks solving a problem, but if you fall into the trap of a 'work silo', you may just veer off track just a little bit and solve the wrong thing, or have a not-so-great solution. this is especially true for remote workers.
as a recovering perfectionist I've learned a few things that keep me out of this trap.
seek feedback early and build the muscle of flash demos. show your wireframe, a design doc, or a draft PR as early as possible. you'll get quicker reviews. there's less pressure on the reviewer, and it fosters a collaborative environment. the reality is that whatever project you may be working on had a bunch of guesses on what needed to be completed - but things don't always go according to plan, so it makes much more sense to iteratively build something with fast feedback cycles.
make sure people know what you're working on. this is essential if you're remote. if your colleagues don't know what you're working on currently, you're not doing anyone any favours. there's a high chance that someone can assist you with any blockers or anything you're having trouble with as well.
don't do everything at once. it was easy to cram assignments and projects in school, but I don't recommend it when you start to have real people depend on what you're doing - whether that's your boss, colleagues, or your users. there's something on the line that isn't just your own self-interest.