You know a colleague well enough to tease them privately about a late arrival. Posting the same comment in a project group creates a different situation. Other people become witnesses, and the colleague may feel pressure to respond publicly.
Before moving a message into a group, check three things: who needs the information, who is being discussed and whether the message gives someone an unwanted audience. A practical update belongs where coordination happens. A personal explanation may belong with the person who needs it.
For example, ‘We’ll start at ten; Maya will join later’ may be enough for a group. The reason Maya is late is not automatically relevant, even if you happen to know it.
Group requests also need clear ownership. ‘Can someone check this?’ may leave everyone uncertain. ‘Rohan, could you check the totals when you are available?’ names a recipient without making assumptions about immediate availability.
A useful group message is selective. It includes the context needed for shared action and leaves unrelated private information out. If you are unsure whether a personal detail can be shared, ask the person first. Familiarity with one participant does not establish permission from everyone involved.