Vrftjkry

I disagree with parts of the other anwers.

Your message is unclear.

Things like we need your help in this space to double-confirm that everything is ready are very vague. What are you asking/saying? Your colleague is now left to guess what you mean and will respond following his own interpretation of your text (that's what human beings do).

You should be more clear in your communication. Be specific in your requests.

I can partially agree with most of the given answers. I do find the message unclear, but I don't think that that's the main issue here. Even if you had been clear on the tasks, it's the phrasing that is raising my eyebrow the most.

What I immediately noticed is that you never asked anything, you only stated things.

If I were to tersely rephrase your message:

• You were asked to organize project delivery.


• You need to double-confirm that everything is ready.


• You can involve [people] when you need to.

"We need you to" is about the politest thing in your message, but it can very easily be interpreted as "you need to" (which is why I did so in my terse summary).

Oversimplifying your message even further, the core message here is:

John, do the work you were asked to. Ask for help if you need it.

At a glance, your message is a message sent by a boss to their subordinate. It is stating the fact of needing to do work, and not even bothering to ask if they have time to do this or if it can be done.

Politeness generally revolves around asking instead of stating, simply to avoid coming across as commanding something. Ask John is he can help, and if he can do this soon. A simple example:

John, are you the one who's working on the [project] delivery? I'm trying to double-confirm that everything is ready, can you tell me if this is the case? If not, do you have an idea when we can be ready? If you need more information or are otherwise blocked, you can talk to [scrum master name], [stakeholder name] or [individual developers names].

My version may not be fully applicable to your case (I don't know your exact environment), but it should be clear that this is more polite than dryly stating that John needs to do the work he was assigned.

Disclaimer
Cultural differences apply here. It may be acceptable or even common in some cultures to phrase things the way you did. I'm looking at this from a Western European point of view, where polite communication is a general expectation between coworkers no matter their relative place on the chain of command.

Look at this from his point of view. He's a new member of a team. A few days before a project that he didn't work on is scheduled to be delivered, you send a message that this project's readiness is now his responsibility. And you send it publicly, without giving him any warning. What makes it worse is that the comment about "pressure coming from the above" sounds like this project is in trouble.

Of course he is angry. Basically you threw him under the bus: "hey new guy, here's an almost completed project that you didn't work on and don't know anything about, you are responsible for its success".

I noticed that in you post you say

it was agreed that he will take ownership of similar projects

but then in your message that gets changed to

John, according to my conversation with Chris, he asked you to take ownership in organizing project delivery of the [small project name]

So you are making it sound like you are just confirming something that he already agreed to do, when in fact he did nothing of kind.

The combination of giving him responsibility for something at the last minute, and making it sound like this is something he already agreed to, is of course going to make him angry. Probably the smoothest way to recover is another email clarifying that you are still responsible for the project readiness, but you want him to help you out, gather information, etc, as a way of getting up to speed on project development.

I 100% agree on the individual discussion first.

John, according to my conversation with Chris, he asked you to take ownership in organizing project delivery of the [small project name] and we need your help in this space to double-confirm that everything is ready.

This sentence can be interpreted as implying that John was asked to do something and didn't do it. It is borderline passive-aggressive. Its (possible) implication of a failure on John's part is exacerbated by your having copied other people in to the message.

I really recommend providing criticism in person. In this case, the impersonal nature of email makes your message seem harsher than it was intended to.

I think he actually reacted really well and provided good feedback in an appropriate forum. I could definitely envision a scenario where he replied back in a similar manner to your email and made a lot more people unhappy (by blaming others publicly).

To me the text passage you copied is ok.

It wouldn't be ok if you wrote only that and send it to the new colleague putting everybody else in cc. But if it's an email on the general project organisation and includes other information directed at everybody it's ok.

I think the issue here was, however, that he was new and may not even know the people you listed in the email. He might not understand the project either. New people need a bit of coaching.

On the other hand, his reaction was much, much more off than your email. He should have asked you to discuss the project with you instead of criticising you for what you wrote. In a stressful environment close to delivery dates, it's difficult to expect people to analyse every sentence they utter twice. Not to mention that as his superior you have a bit more leeway to decide on the way you communicate.

I sent this a couple of hours before the working day started, and when I reached the office he asked for a chat with me and told me that I should not give public orders but had to have an individual discussion with him to agree on this work.

Maybe I am misunderstanding your question but prior to the above quote, you said:

As we had a couple of days left before the small project has to be delivered, I sent email to our developers and asked about individual status apart from that I wrote the following to our new employee in that email:

It sounds like John is complaining that you sent an order to him PUBLICLY as in everyone in the TO, CC, and BCC lines now know that he's to take over the project. What John is trying to tell you is that by doing this, it will confuse the heck out of everyone since it will be assumed he's taken over the project but he might not be ready for it (prior project obligations, etc).

So John is correct that you should have talked to him first. However you being the boss, you can tell John too bad, because he was hired for that role and now he's to do that. But don't expect John to hang around for a long time after that.

How this should have gone

Ideally it would have started with an individual email to John (and granted, I'd question whether this wording was entirely appropriate even then, but at least then you and John would have had room to privately go back and forth over it in a more relaxed way, as John wouldn't feel like he got torpedoed in front of the entire group):

John, according to my conversation with Chris, he asked you to take ownership in organizing project delivery of the [small project name] and we need your help in this space to double-confirm that everything is ready. You can work on organizational details with our [scrum muster name] and business [stakeholder name] and double-check individual development status with [individual developers names]

After a response from John, the inclusion in the group email:

John will be organizing project delivery for [small project name].

At most you might have additionally said something like:

Since he's being brought in cold for that given he hasn't been on that project prior to now, please prioritize any requests from him.

Or something similar, which puts it on the group to act accordingly to expectations and to the situation with bringing John in like this, rather than on John individually, and doesn't speak negatively about John in doing so (avoids implying he's "not up to speed" or something similar by not using related language). Personally I wouldn't even go this far, and would instead individually contact related members regarding how you're dropping John in on this cold at the last minute, and expectations in helping him navigate that if he needs it, rather than dropping it in a group wide email.

The upfront issues I'm seeing here with how this was originally done

Rather than acting as a flat structure leader/coordinator, you very easily came across as if you were not only acting as John's manager, but very easily could have also come across as effectively passive aggressively chiding him for not doing his job, per "according to my conversation with Chris, he asked you to take ownership in organizing project delivery of the [small project name] and we need your help in this space". In a public space email before the entire group.

There are degrees to which, even in a flat structure, the leader has to give what amount to being hard direction, which can easily be called commands. I'm not going to debate the pros and cons of flat structures. Personally I don't mind a teammate at the same level saying what they need from me in order to finish a project, but I feel like it does easily set things up for miscommunication, versus being able to route things through a clear superior.

Also, honestly, I'm confused. In your redacted email, you're claiming he was asked to take ownership in organizing project delivery of this specific project. In your question's text, you simply say that during his hiring process it was explained that he would be involved in project delivery of similar "small projects", not this project specifically:

but during his interview with my manager, before he was hired, it was agreed that he will take ownership of similar projects

If John wasn't already aware of this project (and per your own question, he certainly hadn't previously been involved in it) and aware of his expected involvement in it like this, then this really does come across as at best just dropping it in his lap as if he was expected to already be on top of everything… in front of the entire group. I'm not going to say it's highly inappropriate, but it is very easy to see how someone might be caught off guard and then take it very poorly, and I can't really fault such a reaction.

At worst, this does come across as calling him to the mat for not doing what Chris asked, which would be highly inappropriate in a group email.

Particularly given that you just pulled someone in with "a couple days left" on delivery and asked them to organize project delivery. Depending on what's involved with delivery of this project, this could easily feel like getting blind sided in a very negative way, and it would be easy to question what the intent was behind how you approached doing it like this, in such a tight situation.

Avoiding this in the future

Don't use group emails for asking people to take on roles on specific projects, even if you think they've already been asked/tasked to generally take on that role for projects fitting in that space. Discuss it individually, discuss the specifics individually that pertain to that individual, then explain to the group that the person in question is taking on that role for the project. Don't tell someone what to do in a group email, explain what will be happening in the group email where it pertains to the group. This distinction may seem subtle but it's still actually significant in how it informs what you say, how you word it, and what you omit. At that point, even in terms of coordination, all anyone needed to know is that John is organizing project delivery.

To another extent, you also are kind of implying that John doesn't know how to do something that you've just gotten done saying is considered to be part of his job, with the last sentence. Always assume competence of others publicly, especially when sending an email to a group: it's not the right place to effectively explain how to do something to an individual. I realize you probably meant it as some kind of an introduction to the people involved, but presumably John has been working with these people for a few weeks now, albeit not on the given project, and has had enough onboarding to be able to look up the project details and figure out who he needs to talk to himself. Failing that, let him come to you with questions. In an individual email this wouldn't be so bad, but I can see where some people would feel embarrassed (and the point isn't about whether they're right or wrong to: the point is avoiding an entirely unnecessary and easily anticipated point of tension) with this being lumped into a group email in front of everyone else.

Part of being a good leader is making sure that team members feel like they're being made to look good in front of each other by you

…and I do feel like you let John down here on that, at least by degrees, in multiple ways. This is especially important with new employees who are trying to fit into the group and still working on establishing themselves. This follows generally from the concept of praise in public and criticize/critique/reprimand in private.

When in doubt? Just err on the side of keeping the communication—or at least anything beyond the barest minimum—private. It also helps keep the public communication channels cleaner. I realize that one concept of Agile, including Scrum, is being aware (or at least able to be aware when it counts) of what's going on with everyone else, but a side to that is not overloading your entire Scrum team with extraneous details that stop it from being actually agile. Anyone would tell you: my writing style could be described as wordy, loquacious even (no, really?). But there's a time for brevity, and a lot of what makes Agile actually agile hinges on exercising it appropriately and trusting people to speak up or ask if they need more, rather than doing things like micro managing them.

In my read on this I do not think you did anything really wrong here from a functional team level. But you may have made some assumptions on the ramp time needed for the new individual.

It is very common for folks to feel uncomfortable taking ownership for something until they feel that they have had time to ramp up to the familiarity level with product, processes and procedures. Your wording comes across as the individual is fully ready to engage.

It looks like you sent an email to the whole group and singled out this individual publicly in the portion that you quoted. That is likely the reason that this employee was upset. In the future, if you need to address something with a specific employee, don't copy the rest of the team.

It seems your new member is sensitive by the way you issue requests toward him, and interpret as orders what is implicit or ambiguous, which is something that happens often by writing.

If you are working with people that are easy to get defensive, trying to get your written language as clear as possible is key. A first tip is to avoid impersonal phrasing when issuing requests :

John, Chris asked if you could take ownership in organizing project delivery of the [small project name]. We would like you to confirm everything is ready.

And even better :

John, can you please take ownership of [small project name] project delivery and make sure everything ready ?

This is a nuancial change but it makes a really much better window for him to decline when he is directly asked than when being said "That's what must be done".

Additionally, as sf02 suggested, you should send this request to him privately.

I don't think that anything is necessarily wrong with what you said or the words you used to say it.

I think that the issue is that you sent these directions meant for him to the entire team. It probably would have gone over smoother if you had sent that paragraph in an email directly to him and only him. Or better yet, gone up to him to discuss it with him. Seeing as he wanted to chat with you in person, he likely prefers face to face communication.

Putting directions for someone in an email sent to multiple people is super annoying because

1. It implies that you don't trust him to do something you discuss privately--you need others to know and hold him accountable for it




2. It comes off as a huge "CYA" thing so that everyone knows that you have directed him and now that they know, supposedly you've done your part and this is out of your hands




3. To go along with point 1, the fact that this is getting sent to a bunch of people who don't have context, the way that you say that Chris asked you to take ownership could give others the impression that John has already received direction to do something and this email is a way of putting him on blast for not doing it yet, so let me tell you in front of everyone to pressure you to start doing it.