If you are afraid to sound too pushy, bossy or impolite, when writing about urgent tasks or deadlines, include all “awkward” moments in the subject line
📌Due tomorrow…final estimations 📌Today…mockups for Z project 📌Need your approval for… hiring new QA
4 rules to title your email: 1️⃣say no to no-subject emails 2️⃣your subject should be SMART: specific, meaningful, appropriate, relevant, thoughtful 3️⃣it shouldn’t be longer than 30-40 characters 4️⃣subject should contain keywords to make it easy to filter and find your email later
❌”Question”- 👍”Question about the upcoming retrospective meeting” ❌”Information”- 👍“Change of the end of quarantine date” ❌”Update”- 👍“Update on company payroll procedure”
📌Explain: warn all people who will be impacted, talk to your manager about the reason for the delay. ❗️Just remember not to say sorry, neither blame other people
📌Give an alternative: make a checklist of the steps of your tasks to correctly state the project progress. Suggest delivering what you have done so far
📌Thank you chance: say thank you to have a few extra days to deliver the task ready and reviewed. ❗️The higher the quality, less serious you delay will seem.
1️⃣Do you want to see posts here in English only? 2️⃣или стоит включать перевод?
🤓И пусть сегодня будет день апдейтов! Как говорить о планах во время daily или status/progress checking meetings:
📌Today I`ll start on the code to read the grades from the legacy database, writing tests at the same time, as I’ve started learning.
📌So, I`m going to move this task to ‘Completed”.
📌Today I`d like to keep working on this if it`s OK with you, guys.
📌Today I want to keep working with Carla on the database contention issue with Update Grades.
🤯... и о трудностях:
📌My impediment is that I don't understand some of the recent changes Eddie made to the build file.
📌I`m uncertain whether the automated tests should go all the way to the database tables written by the legacy system, or I should just use mock objects.
🙋🏻♂️Итак, идёт активная дискуссия, нейтивы и нон-нейтивы. Вам начинает казаться, что каждый говорит о своём
Как сфокусировать всех на одной теме:
📌The key issue (idea, problem) here is... 📌What we need to talk about now is... 📌One thing I want to look at is... 📌We now come to the most important phase of our discussion.
А темой следующего поста будет: 1️⃣giving meaning of technical words 2️⃣how to use and pronounce some of IoT words and phrases
🙋♀️Хотим сделать канал ещё полезней. Поэтому давайте проголосуем?
Какие нетехнические навыки вы считаете самыми важными на текущем проекте:
1️⃣communicating complex information in digestible amount 2️⃣active listening 3️⃣oral communication 4️⃣written communication 5️⃣collaborating on solving complex problems 6️⃣teamwork
🥂Если вы ещё работаете и учитесь заодно, давайте глянем фразы, которые помогут скедьюлить митинги:
📌How to arrange an appointment:
✔️Could we set up/arrange/book a meeting? ✔️Are you available/free next Monday at 2 PM CET? ✔️How about 11 AM on Tuesday? ✔️Does next Thursday suit you? ✔️Will tomorrow at 3 PM do for you?
📌How to agree on time
✔️Just let me check my calendar ✔️Yes, Tuesday is fine with/by me ✔️Sounds good. Friday 3 PM then. ✔️Let’s reschedule
📌How to reschedule
✔️I am sorry, but I have another meeting at this time. ✔️Actually, Wednesday noon would work out better for me. ✔️How about Tuesday morning instead?