Gatekeepers picture and small reporganization

source/shorten-cycle.html.haml

@@ -17,9 +17,6 @@
 %p
   The first thing to consider is to start working on smaller pieces of functionality. Instead of minimum viable products or minimum viable features, start thinking in terms of Minimum Viable Changes.
-
--# %div.aside The idea of MVC echoes with Kaizen - a Japanese term for continuous improvement.
-
 .row
   .col-md-2.col-xs-1
      
@@ -28,12 +25,13 @@
   .col-md-2.col-xs-1
      
-%p
-  Shipping smaller has following benefits:
-%row
+%h3
+  Benefits of shipping smaller
+
+.row
   .col-md-6.col-xs-6
-    %h4 for business:
+    for business:
     %ul
       %li More in line with expectations and needs of stakeholders
       %li Easier to coordinate and to reason about
@@ -42,7 +40,7 @@
       %li Higher predictability
   .col-md-6.col-xs-6
-    %h4 for developers:
+    for developers:
     %ul
       %li Prevents overshooting needs and gold plating
       %li Higher code review quality
@@ -54,17 +52,21 @@
 %h3 Include Gatekeepers into conversation
 %p
-  Think about Gatekeepers who had to approve something before you can ship it: Security review, Operations department, UX check, Translation department, QA testing.<br/>
-  We often exclude them from the equation, assuming there’s nothing we can do about it.
-%p
-  But we usually can. Give early access to your code to security department, make UX guy a part of the team, automate testing and operations together, etc.
+  Think about Gatekeepers who had to approve something before you can ship it: Security review, Operations department, UX check, Translation department, QA testing.
+.row
+  .col-md-3.col-xs-1
+    &nbsp;
+  .col-md-6.col-xs-6
+    =img("gatekeepers.png")
+  .col-md-3.col-xs-1
+    &nbsp;
 %p
-  PICTURE about gatekeepers
-%p
-  Here’s list of changes to think about:
+  We often exclude them from the equation, assuming there’s nothing we can do about it. But we usually can. Give early access to your code to security department, make UX guy a part of the team, automate testing and operations, etc.
+
+%h3 List of changes to think about
 %ul
   %li Deploy infrequently → Deploy frequently (if it hurts, do it more often)
   %li Multiple changes → Single changes (able to link problems to changes quickly)