Explaining Your Work — Briefings, Handovers and Interviews

Tóm tắt

You can do the job. You find things other people miss, you fix things nobody else wants to touch, and when the week is over you can describe none of it in a way that makes anything happen. You have sat in a stand-up and heard yourself narrate a day. You have written an incident report that was accurate, complete, and forwarded to somebody technical with three questions attached. You have been asked a question in an interview and watched a perfectly good answer fall apart on the follow-up. None of that is a knowledge problem. Every one of them is an ordering problem, and ordering is learnable in a way that talent is not. You start with the first fifteen seconds. The conclusion, not the journey, then the detail if they want it, then what you need and from whom. Three lines — changed, blocked, need — replace forty seconds of verbs in a stand-up. Then the written artefact. Four headings, one page, a subject line that is a sentence. A severity score describes the hole and knows nothing about your building, so you learn to say what a nine point eight actually means here, including the ones where the honest answer is that it can wait. Then pressure. Six interview stories carrying a specific number, a setback said plainly and a decision that went partly against you. The three moves — acknowledge, answer, bound — that keep you credible in a room that has decided to test you. Then a mock interview where every answer gets pushed on twice, because the follow-up is where prepared material comes apart. Finally the two rooms nobody prepares for. The handover, which fails because you left out everything you knew. And the client briefing, where the deck is answering a question the room stopped asking, and the only move left is to shut the laptop. This is not spoken English. If you lose words under pressure, do the technical-english segment first.

1. 01 Lead With the Answer

   3 bài học·1h 23m

   Every investigation you have ever run went evidence, evidence, evidence, conclusion, and you narrate it that way because that is how it is stored. The room does not want your head, it wants your…

2. 02 A Report That Causes a Decision

   3 bài học·1h 46m

   A competent, technically correct incident report that does not contain the amount of money stolen is the failure this module is built around. Four headings: what happened, what it cost or risked,…

3. 03 Answers That Survive Being Pushed

   3 bài học·1h 46m

   Six stories, one per area, each carrying a specific number, a setback said plainly and a decision that did not fully go your way. Then the three moves for a hostile question — acknowledge, answer,…

4. 04 The Bit You Did Not Say

   3 bài học·1h 46m

   A handover is the only document you write where your own competence ruins it — you drop the context because you are carrying it, and the context is the only part the next person does not have. Then…

Các câu hỏi thường gặp

Tôi sẽ học gì trong Explaining Your Work — Briefings, Handovers and Interviews?

You can do the work and you cannot make anybody act on it. This is the ordering: the answer in the first sentence, an incident report a manager will act on, interview answers that survive the second question, and a handover the next person can use without ringing you. Four artefacts, all written by

Tôi có cần kinh nghiệm trước đó không?

Nên có một số kiến thức trước đó trước khi bắt đầu Explaining Your Work — Briefings, Handovers and Interviews.

Explaining Your Work — Briefings, Handovers and Interviews mất bao lâu?

Explaining Your Work — Briefings, Handovers and Interviews bao gồm 4 mô-đun và 12 bài học. Bạn học theo tốc độ của riêng mình.

Làm cách nào để tôi có quyền truy cập?

Explaining Your Work — Briefings, Handovers and Interviews được bao gồm trong bất kỳ gói đăng ký nào.