quick-answers.kronis.dev Open in urlscan Pro
65.109.142.43  Public Scan

Form analysis
0 forms found in the DOM

Text Content

WANT QUICK ANSWERS?


ASK QUESTIONS WELL!


IT'S ACTUALLY PRETTY EASY...

In our modern day world, focus is paramount to getting things done.

Every interruption introduces context switching, which makes productivity
suffer.

Thus, it can be good to embrace asynchronous communication and respect others'
time.

Consider the following two situations...


SITUATION #1: COMMUNICATION THAT COULD BE IMPROVED

HERE'S THE SITUATION...



...SO WHAT'S WRONG WITH IT?

 * A greeting without saying what you need makes the other person switch
   contexts and wait on you
 * Not telling the other person what you know and have tried makes figuring it
   all out take much longer
 * Asking for a call means that the other person will have to drop whatever they
   are doing to join it
 * This way, even simple questions need more time, to get the details and start
   talking about the actual problem

And what if they're too busy to help you right now? Will you wait for an hour
until their schedule frees up for that call?

Once or twice a day may not be too bad, but what if there's lots of people with
lots of problems?


SITUATION #2: QUICKER AND MORE USEFUL COMMUNICATION

HERE'S THE ALTERNATIVE...



...SO HOW IS IT BETTER?

 * Offering the details up front is an excellent way to get the other person up
   to speed
 * Being specific with what you're trying to do (links, method/class names, code
   snippets, error messages) eliminates lots of guesswork
 * If you've already tried some steps towards a solution, sharing those can also
   be very useful
 * You won't have to do as much back and forth or calls, the message alone might
   have enough details for them to help

Now, the other person doesn't need to feel frustrated, pausing their work, to
wait for you to explain the situation.

Furthermore, if they're out at the moment (or in a different time zone), they
can just get back to you with the full answer later.


IN SUMMARY

You can make communication more useful and less frustrating with relatively
little effort.

This could cut down on the amount of context switching that you or others need
to do.

Not every question needs a call, not every answer needs to be preceded by lots
of back and forth.

Of course, sometimes you do just need a meeting or a call and that is also okay.

Better yet, write down information about how problems were solved in the past.

Good luck!


FURTHER READING

Some of the nice people on HN suggested a few additional links that may be of
use:

 * The XY Problem - more information might reveal when you're headed in the
   wrong direction
 * How To Ask Questions The Smart Way - a more in-depth article on how to ask
   questions better
 * Don't Just Say "Hello" in Chat - the blog post that inspired many sites like
   this

© 2022 - 2024 Kristiāns Kronis
Version: 3e6479b
Cookieless Analytics by my Matomo instance.
Images by This Person Does Not Exist.