Skip to content

Live cohort workshop · Online

From Code Review to
Risk-Based Oversight

Whether you’re ready to do away with code reviews altogether or worried that dropping them will leave changes without proper oversight, this workshop is for you.

As AI takes on more of the work of writing and reviewing code, what should your team still check before a change ships? We’ll look at how those responsibilities are shifting and use the risk of each change to decide when a person should review it and what they should check.

You’ll leave with practical steps for your team and a clear sense of what to measure. Use both to cut unnecessary review time and make room for careful human checks where they matter most.

For developers, tech leads, and engineering leaders.

What you’ll learn

  • Know what your review adds

    Recognize where AI and human reviews complement each other, and give human attention a clear purpose after automated checks.

  • Review beyond the diff

    Investigate intent, system behavior, and evidence. Check correctness, alignment, and understanding rather than stopping at plausible-looking code.

  • Choose proportionate oversight

    Use SCOPE to decide who reviews, at which stage, and how deeply—based on the risk and alignment needs of a particular change.

  • Keep your team’s understanding intact

    Spot gaps in shared knowledge and make room for learning, ownership, and the ability to maintain AI-assisted code.

  • Make difficult review decisions

    Practice on realistic SSO and survey-editor scenarios. Weigh failure impact, recovery, and the value of an independent reviewer.

  • Learn how to get rid of code reviews

    Explore what it takes to reduce human effort in code reviews to a minimum, and when automated checks, AI review, and engineering safeguards can replace human review.

  • Improve your next review

    Leave with a practical checklist and a concrete experiment for adapting your team’s review workflow.

Workshop outline

Practice on realistic changes, then apply the same questions to your own team’s workflow.

  1. Part 1

    What does human review add?

    Examine what AI reviewers help with, where their feedback falls short, and how your own review should change.

    Compare your current review practices with the cohort.

  2. Part 2

    Assess risk before opening the diff

    Look at failure impact, security and data boundaries, detectability, and recovery. Decide which questions a review needs to answer.

    Exercise: Two small changes with very different consequences.

  3. Part 3

    Choose the right review for the change

    Decide who should investigate, what evidence they need, and when review should happen. Use SCOPE as one way to organize those decisions.

    Exercise: Review a change that restores access for legacy SSO users.

  4. Part 4

    Practice risk-based code review

    Investigate a survey-editor change. Identify the different risks inside one PR and decide whether splitting it would make review more effective.

    Compare your review decisions with other participants.

  5. Part 5

    How to reduce human code review effort

    Identify which checks can be automated and where human judgment adds value. Decide what evidence you need before reducing manual review.

  6. Part 6

    Plan your next review

    Use the review checklist to choose one improvement for your team. Discuss your questions and the tradeoffs in your own workflow.

    Leave with a specific change to try at work.

Who it’s for

Is this workshop for you?

Join if you review code, lead developers, or set your team’s review practices—and want a clearer approach to reviewing AI-generated changes.

You should have experience developing software, either with or without AI tools. We use shared examples, so you can participate without a paid AI tool.

Learn with Michaela

Your instructor

Dr. Michaela Greiler

Dr. Michaela Greiler

I research code reviews and help teams improve them. At Microsoft, I worked with engineers to understand where reviews get stuck and which practices help.

I hold a PhD in Software Engineering from Delft University of Technology. This workshop builds on my research and work with teams adapting their reviews to AI.

More about my workshops ↗

Before you join

Practical questions

When and where does it take place?

Both sessions are online. Join the Americas session on 3 December 2026 from 09:00–11:30 PST or the EMEA session on 4 December 2026 from 10:00–12:30 CET. Each session includes a short break. Joining details will be shared during registration.

What if neither date works for me?

Leave your email to hear about future workshops and courses.

Is this a live workshop?

Yes. You’ll learn directly with me and a cohort of peers through live discussion, shared exercises, and Q&A. Plan to attend the full two and a half hours.

What will I take away?

A practical approach to allocating human attention, a review checklist, experience applying SCOPE to realistic changes, and an experiment to try with your team.

How do I register?

Use “Reserve your spot” to complete the registration form. I’ll email you with payment details and the next steps to confirm your booking. No payment is taken through the form.

All participants are expected to follow the Code of Conduct.

Hear about new courses

We’ll use your email to notify you about new courses. Privacy policy

Know where your review matters.

Join the live cohort on 3 December 2026 or 4 December 2026.

Reserve your spot · €129 excl. VAT

Corporate training for your team

Book this workshop as a private session for your team. I’ll tailor it to your needs and schedule it at a time that works for you. Prices start at €229 per person.

Discuss corporate training