Upgrade to Pro — share decks privately, control downloads, hide ads and more …

MoT NL Meetup 19 feb 2026

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
Avatar for Linda van de Vooren Linda van de Vooren
February 19, 2026
4

MoT NL Meetup 19 feb 2026

Avatar for Linda van de Vooren

Linda van de Vooren

February 19, 2026
Tweet

Transcript

  1. Why to ‘they’ ask for the wrong things? • This

    is what they’ve been tought in their management training • This is what they see others do • Their manager asks this of them (and they didn’t ask why) • They think this is what they need
  2. What do you want to know? • Given the context

    • Given the risk • Given the go-live date
  3. How do you actually deal with this? • Ask what

    decision this dashboard is supporting If there is no decision or decisive action a dashboard supports, why make it?
  4. How do you actually deal with this? • What would

    (could?) cause escalation? What information would the most vital and important information you could possibly use to escalate? (And why would you, or would not want to escalate?)
  5. How do you actually deal with this? • What information

    do you need, to make the decision right now to go live? Surely the information of ‘1 blocker’ is not enough. What risk are you interested in for go-live? Where is the risk in production?
  6. How do you actually deal with this? • What could

    delay the release? Why would it be a bad thing? Or should we yolo this to production and see what happens?
  7. What would be on a good dashboard? (audience participation, you

    may now speak) • What risk if we go live right now? • What risk if we go live after defect X is fixed? • Are there dependencies outside the project? • Do we need to update the steering committee? • And then: what do you tell them? • Is there any specific help we can identify?
  8. Tell them this If we go live today: • X

    would fail • Y user group would experience work disrupting errors all day • Z integration is completely untested, we might not be able to send out any invoices and we’ll not know what’s missing afterwards
  9. Our job • Make risk visible • Preferably in a

    visually attractive (or funny) way • Make uncertainty explicit • Enable enforced decisions