diff --git a/common/common.sty b/common/common.sty
index e5037d2515..315db399ee 100644
--- a/common/common.sty
+++ b/common/common.sty
@@ -32,4 +32,10 @@
 % Yocto commands
 \newcommand\yoctovar[1]{\href{https://docs.yoctoproject.org/ref-manual/variables.html\#term-#1}{\codelink{#1}}}
 
-
+% Arnout commands
+\newcommand\questionslide[1]{\begin{frame}{#1}
+  \begin{center}
+    \includegraphics[height=0.8\textheight]{common/question-mark.jpg}
+  \end{center}
+\end{frame}
+}
diff --git a/common/question-mark.jpg b/common/question-mark.jpg
new file mode 100644
index 0000000000..726086fe99
Binary files /dev/null and b/common/question-mark.jpg differ
diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index 54ecc7fd0e..6b2f4b5cb1 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -2,6 +2,8 @@ \section{Linux device and driver model}
 
 \subsection{Introduction}
 
+\questionslide{Why do we need device drivers?}
+
 \begin{frame}{The need for a device model?}
   \begin{itemize}
   \item The Linux kernel runs on a wide range of architectures and
diff --git a/slides/kernel-hw-devices/kernel-hw-devices.tex b/slides/kernel-hw-devices/kernel-hw-devices.tex
index 37813e1f59..0bfa7a6483 100644
--- a/slides/kernel-hw-devices/kernel-hw-devices.tex
+++ b/slides/kernel-hw-devices/kernel-hw-devices.tex
@@ -77,6 +77,8 @@ \subsection{Describing non-discoverable hardware}
   \end{columns}
 \end{frame}
 
+\questionslide{Why is putting description in code not maintainable?}
+
 \begin{frame}{Device Tree: from source to blob}
   \begin{columns}
     \column{0.7\textwidth}
diff --git a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
index 4085a2a6d2..ebbbb09cc5 100644
--- a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
+++ b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
@@ -25,6 +25,8 @@ \subsection{Linux kernel source code}
   \end{itemize}
 \end{frame}
 
+\questionslide{Why doesn't the kernel use the C library?}
+
 \begin{frame}
   \frametitle{No C library}
   \begin{itemize}
@@ -242,6 +244,8 @@ \subsection{Linux kernel source code}
   This will for sure reduce your maintenance and support work
 \end{frame}
 
+\questionslide{Can you implement drivers in userspace?}
+
 \begin{frame}
   \frametitle{User space device drivers 1/2}
   \begin{itemize}
diff --git a/slides/sysdev-kernel-booting/sysdev-kernel-booting.tex b/slides/sysdev-kernel-booting/sysdev-kernel-booting.tex
index 4a482a234f..9821b4e399 100644
--- a/slides/sysdev-kernel-booting/sysdev-kernel-booting.tex
+++ b/slides/sysdev-kernel-booting/sysdev-kernel-booting.tex
@@ -35,6 +35,8 @@
   \end{itemize}
 \end{frame}
 
+\questionslide{How do you specify the kernel command line?}
+
 \begin{frame}
   \frametitle{Passing the kernel command line}
   \begin{columns}
diff --git a/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex b/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex
index 723807d8ad..1bbc83cb99 100644
--- a/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex
+++ b/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex
@@ -33,6 +33,8 @@
   \end{center}
 \end{frame}
 
+\questionslide{What are the Linux kernel main roles?}
+
 \begin{frame}{Linux kernel main roles}
   \begin{itemize}
   \item {\bf Manage all the hardware resources}: CPU, memory, I/O.