DEV Community

Cover image for About being some steps ahead
Duca
Duca

Posted on

About being some steps ahead

I think we all have struggled with some moment or issue at our work that made the world stop and all you could think about was how that had any solutions and you're only escape plan was to get mad.

Being ahead of the issue

This may sound like some coach peep talk that does not change anything in your life, but, check this out.

This week I was talking with a manager that I really appreciate a lot and we were talking about my proactivity and how today it became rare to find people that works like this..

One of my major learnings from last year is that you really CAN'T stop and wait for your problems to solve theirselves alone. They say "if your problem has not a lot of solutions it means that your work is not good" and somehow this is a fact.

Once you find a bump in your sprint and need to take a day low in order to find the source of the issue and cut it off, your behavior can not be to send some e-mails, some tickets, some DMs and just wait for others to finish what your started -- if this was the case, they should be hired, not you.

How to behave in case of a barrier

If something or someone is making it impossible for you to continue your task or to do your work, there are some behaviors that I am trying to learn recently and I am sure that they will be of a great help for you:

  • Divide and conquer: this means baby steps. Try to unlock your first problem and whilst you are waiting for a third party to solve it, you can go and start working on the next one.
  • Communication: this is really obvious, but communication is keys while working with other person: you need to make sure that your team knows where are you working, how you are working, and, mainly, how they can make your life easier.
  • Smart think: take a look at this situation that happened to me last year: I was trying to make the front-end work be better in order to supply some lack of organization that our back-end had, and this made your front-end much more smarted than he was supposed to be. I do not even need to say that this caused us some trouble afterwards, so, think, what is best: make the front-end smarter or make the back-end work better?

Some final thoughts

Do not make your team disappointed because you are the one slowing down the sprint at every issue that you have to solve. Think smarter, act quickly and effectively.

You must not wait for other to do your job.

Top comments (0)