code upskilling

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 you.

  • trending_upIntermediate
  • schedule6h 41m
  • menu_book12 lessons
  • publicEnglish
  • workspace_premiumBasic
Explaining Your Work — Briefings, Handovers and Interviews

Briffing

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.

Amlinelliad y cwrs · 4 modules

lockYn datgloi gyda mynediad
  1. 01 Lead With the Answer
    3 lessons·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 lessons·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 lessons·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 lessons·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…

Cwestiynau a ofynnir yn aml

Beth a ddysgaf yn 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
A oes angen profiad blaenorol arnaf?
Argymhellir rhywfaint o wybodaeth flaenorol cyn dechrau Explaining Your Work — Briefings, Handovers and Interviews.
Pa mor hir y mae Explaining Your Work — Briefings, Handovers and Interviews yn ei gymryd?
Mae Explaining Your Work — Briefings, Handovers and Interviews yn cynnwys 4 modules ac 12 lessons. Rydych chi'n dysgu ar eich pace eich hun.
Sut rydw i'n cael mynediad?
Mae Explaining Your Work — Briefings, Handovers and Interviews yn cael ei gynnwys gydag unrhyw danysgrifiad talu.

Mwy yn Rhaglennu

AI Without the Hype
Beginner AI Without the Hype What the model is actually doing when it answers you, why that produces something that looks like thinking, why it invents citations, and the cost mechanic almost nobody explains: a chat resends the entire conversation on every single turn. You will do the arithmetic yourself.
Python From a White Sheet
Beginner Python From a White Sheet The exact sequence nine students have already walked, from a blank file to a program that asks questions, checks the answers and refuses bad input. No prior programming. No maths. You will break it repeatedly, on purpose.
Binary, Hex and Data Units
Beginner Binary, Hex and Data Units The topic that costs more marks than any other on the paper, taught by hand. Bits and bytes, binary and hex in all six directions, the 1000-versus-1024 trap, file sizes, transmission times, overflow, two's complement and character sets. Every module ends in a timed drill marked the way an examiner marks it.
First Program — Scratch for ages 5–9
Beginner First Program — Scratch for ages 5–9 Nine Scratch blocks, three sessions of about twenty-five minutes, and one small program a child of five to nine builds themselves. Written for the parent sitting beside them: what to click, what they will get stuck on, what to say when it goes wrong, and when to keep your hands off the mouse.
IGCSE and GCSE Computer Science — Theory That Actually Gets Marked
Intermediate IGCSE and GCSE Computer Science — Theory That Actually Gets Marked The theory half of the paper, taught so it survives the exam room. The memory hierarchy and what actually happens at boot. Compilers, interpreters and assemblers, including the answer that sounds right and scores nothing. Databases from a spreadsheet up to keys and normalisation. DNS and the full path between pressing Enter and seeing the page. Systems software, and the ethical and legal section that is the easiest ten marks on the paper.
Programming for the Exam — Python Answers That Score
Intermediate Programming for the Exam — Python Answers That Score The programming half of the paper, taught at exam pitch. Pseudocode translated both ways, because the mark scheme is written in a notation nobody practises. Trace tables done column by column, including the ones with a loop and a condition inside it. Linear and binary search, bubble and insertion sort, what each costs and the comparison questions boards love. Validation against verification, and the boundary test data everybody forgets. Procedures against functions, and a systematic method for finding your own error with four minutes left.