career 5 min read

Don't ask to ask, just ask!

Skip the bare "hello" in chat: put your actual question and context up front, give calls an agenda and a time estimate, and stop making people wait for the real ask.

TL;DR

Rather than just sending greetings or “hello” and then waiting for reply, also enrich your messages with the specific question or problem statement. This saves time and fosters asynchronous communication!

When initiating calls, provide context and a time estimate to respect others’ schedules.


Early in my career at Adobe, I received a piece of advice from my tech lead that profoundly changed the way I approach communication at work. They emphasized the importance of asking direct, well-formulated questions that not only demonstrates clarity of thought but also respects the time of your colleagues. This has become [really] [popular] in [last] [decade], but has been the rule of thumb since the IRC days! Pepperidge Farm remembers.

This lesson has stayed with me throughout my career, and recently I shared the same with our team when I noticed a lot of back and forth over our team’s help-channel queries just to gain context, wasting a lot of dev time which prompted me to write this post.

💬 Rethinking Chat Etiquette

Traditionally, conversations often start with a greeting or a check-in. However, in a chat setting, this approach can be counterproductive. A simple “hello” can lead to unnecessary delays as the recipient waits for the actual query or context before actually responding.

Consider this common scenario:

Chat with a colleague, eight messages. 12:32:12 You: Hi. 12:33:15 Colleague: Hello. 12:40:17 You: How are You? I wanted some help. 12:43:54 Colleague: I am good. Sure, tell me? 12:46:35 You: I'm working on the login feature and I'm having trouble with the authentication API. Do You have any experience with this? 12:48:07 Colleague: Oh, yes. Are You using OAuth2 for authentication? I faced a similar issue last week. 12:49:10 You: Yes, I'm getting an invalid token error. Here's the error log: <...LOG...> 12:50:04 Colleague: That sounds like a configuration issue. Let me send You a guide that helped me: https://.... A red brace over the first four messages reads: about 15 minutes before the actual question.

In this example, your colleague has to wait for almost ~15 minutes before understanding the actual query and help you. This waiting period results in lost productivity and delayed response!

Let’s look at another example:

Chat with a colleague, two messages. 12:32:12 You: Hi, hope you are doing good! I'm currently facing an issue with the authentication API in our login feature. I'm getting an invalid token error in OAuth2 despite following the standard procedure. Here's the error log: <...LOG...> 12:33:15 Colleague: Yes, I've worked with OAuth2. This looks like a configuration issue. Let me send you a guide that helped me: https://.... A green brace reads: about 1 minute from question to answer.

In this efficient example, the query is clear from the beginning, leading to a quicker and more focused response. This approach is more respectful of your colleague’s time as they can immediately engage with the problem, providing helpful feedback within a minute.

Note: One of the advantages of Slack / Confluence is its inherently asynchronous nature. By posing your question directly, you allow the recipient to respond at their convenience, which is crucial especially in a global team like ours where members might be in different time zones.

This approach ensures that even if you’re not online simultaneously, your query has been clearly communicated and can be addressed as soon as the recipient is available.

⁉️ Don’t ‘Ask to Ask’

In many channels I have observed that people tend to preface their questions with queries like:

Don't: a message in #team-help from You: Hello, can anyone help me with a coding issue? Marked with a red cross: asks to ask.

⚠️ Especially, never pair ⬆️ with @here or @channel to ping everyone under the sun! Try to use the approach suggested in the channel’s topic instead, like the team’s support or on-call handle.

This not only wastes time but also potentially discourages peers who could have potentially answered from engaging. Instead of asking a generic query, you can directly present your query like:

Do: a message in #team-help from You: Hi team! When running function XYZ() in this <bitbucket_repo/file.py>, I receive this error message: TypeError: list indices must be integers or slices, not str. It should return a dictionary object containing keys A, B, C, but only returns key A. What can be the issue? I have tried adding the logs and using the debugger as well. I would appreciate some help. Marked with a green tick: just asks.

As we can observe here we:

  • Clearly outlined the problem: Shared relevant details (error messages, expectations vs reality) and avoided ambiguity.
  • Isolated the problem: When possible, minimize the scope of the issue being addressed to ease comprehension and troubleshooting efforts.
  • Limited jargon and abbreviations: Ensure your language remains accessible to everyone involved.
  • Performed research prior to asking: Utilize search engines, manuals, tutorials, and other tools before requesting help. Document attempts made towards resolving the issue based on findings.

📞 Calls: Setting Expectations

The same principle applies to calls. Instead of an abrupt call or a message like:

Don't: You message a colleague: Do you have a minute? Then you wait for 5 seconds and initiate a Zoom call. Marked with a red cross: abrupt call.

A more considerate approach can be to provide context and a clear agenda. For example:

Do: You message a colleague: Hi, can we have a 10-minute call to discuss the challenges with the API integration in XYZ project? I believe your insights could really help unblock me with the OAuth2 related pitfalls. Colleague: Sure, I am free in 20 mins, let's meet then? Marked with a green tick: agenda and time estimate.

This approach shows respect for your colleague’s schedule and allows them to prepare for the discussion, making the call more productive! A win-win if you ask me!

In case you want to explore this further, here are some of the interesting related reads:

Update, November 2026: I folded this into a bigger talk for the new joiners on my team, about asking with context, owning the next step and leaving a clearer path for the next person: Lift Each Other Up.


In conclusion, implementing a more straightforward and succinct communication approach in chats and calls can greatly improve productivity and demonstrate respect for one another’s time, particularly in a remote-first asynchronous environment.

Bonus: This also allows you to embody our values at Atlassian effectively:

OPEN COMPANY, NO BULLSHIT We value open and honest communication. By asking direct questions, we uphold this principle, ensuring that our conversations are clear and devoid of unnecessary fluff!

PLAY, AS A TEAM By being direct and to the point in our communication, we not only respect each other’s time but also build a stronger, more collaborative team.

BE THE CHANGE YOU SEEK As we embody the change we seek, let’s lead by example in our everyday interactions, setting a standard for efficient and effective communication.


Fin.

Comments

    Supports `code`, ```blocks```, **bold**, *italics* and links.

    Keep reading