Recently at my new work I’ve faced a dilemma - should I do my task partially, knowing that the outcome won’t be as good and comprehensive as it should be, but would be probably ok? Or should I do comprehensive detailed work, which would take up considerably more time and at the same time surface some bigger questions to ask?

I’ve chosen the latter, and while I could see some colleagues taking the easier path (and the boss probably content with that approach as well), I’m glad I did so. Getting deep allowed me to understand much more of what I need to do and what tools I have available. It also had brought clarity on my role within the organisation, and last but not least, It felt that the job is well done. But mostly I’ve learned so many details about what it is that I need to do, that the exercise alone was wort it, no matter if the boss will see it once and forgets it, or will return to it on regular basis.

This also reminded me situation in one of my previous jobs, where the harder option was to thoroughly learn inner works of the system and understand well the documentation. Not only it helped me a lot in the job, but it is knowledge I’m benefiting from in my new roles since then. And it is possible that without this knowledge I might not be working where I am working today.

When you have a job in front of you, don’t take the easy path. Opt for the complex complicated one and you’ll be surprised how much you’ve learned along the way. And where it can lead you in the future.