{"id":8106994,"date":"2026-04-15T11:46:47","date_gmt":"2026-04-15T18:46:47","guid":{"rendered":"https:\/\/agilealliance.org\/?post_type=aa_event_session&p=8106994"},"modified":"2026-04-15T11:58:44","modified_gmt":"2026-04-15T18:58:44","slug":"how-project-managers-reduce-risk-by-delivering-earlier","status":"publish","type":"aa_event_session","link":"https:\/\/agilealliance.org\/resources\/sessions\/how-project-managers-reduce-risk-by-delivering-earlier\/","title":{"rendered":"How Project Managers Reduce Risk by Delivering Earlier"},"content":{"rendered":"\n

The following is an AI summary of the event.<\/em><\/p>\n\n\n\n

You can download the slide deck for this presentation at the bottom of the summary.<\/strong><\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

This session, led by Mike Lyons, focused on a simple but often overlooked idea: project managers reduce risk by delivering value earlier, not by creating more detailed plans. The core argument is that real progress comes from evidence (working outcomes), not forecasts or status reports.<\/p>\n\n\n\n

The Problem with Planning as Risk Management<\/h2>\n\n\n\n

Mike challenged a common instinct in organizations:<\/p>\n\n\n\n

    \n
  • The more uncertainty there is, the more leadership demands detailed plans<\/li>\n\n\n\n
  • This creates a false sense of control, since plans are made when teams know the least<\/li>\n\n\n\n
  • Increased planning leads to more status reporting, more dashboards (often misleading), and less time producing real outcomes

    Key point: plans are not assets; they are overhead. Customers don\u2019t pay for plans; they pay for results.<\/li>\n<\/ul>\n\n\n\n

    Evidence Reduces Risk<\/h2>\n\n\n\n

    The central idea is that delivery creates evidence, and evidence reduces risk:<\/p>\n\n\n\n

      \n
    • Every delivery turns assumptions into knowledge<\/li>\n\n\n\n
    • Frequent delivery lowers uncertainty faster than planning<\/li>\n\n\n\n
    • Delaying delivery keeps risk high until late in the project

      Instead of trying to predict the future, teams should show the future through working results.<\/li>\n<\/ul>\n\n\n\n

      What to Deliver: Small, Real, Visible<\/h2>\n\n\n\n

      To make early delivery practical, Mike emphasized three characteristics:<\/p>\n\n\n\n

        \n
      • Small: break work into thin slices<\/li>\n\n\n\n
      • Real: deliver something that actually works<\/li>\n\n\n\n
      • Visible: make it observable to stakeholders

        Examples include releasing a component of a system or a limited feature to a subset of users. The goal is not completeness, but learning through real use.<\/li>\n<\/ul>\n\n\n\n

        Improving Flow to Deliver Faster<\/h2>\n\n\n\n

        Delivery speed depends on how work moves through the system:<\/p>\n\n\n\n

          \n
        • Focus on flow, not just activity<\/li>\n\n\n\n
        • Limit work in progress (WIP)<\/li>\n\n\n\n
        • Prioritize finishing work over starting new work

          Helpful questions:<\/li>\n\n\n\n
        • What is the oldest work in progress?<\/li>\n\n\n\n
        • What is blocking it?<\/li>\n\n\n\n
        • What will we stop starting so we can finish it?

          This helps teams finish and deliver more frequently.<\/li>\n<\/ul>\n\n\n\n

          Leadership Shifts for Early Delivery<\/h2>\n\n\n\n

          Project managers need to change how they lead:<\/p>\n\n\n\n

            \n
          • Manage the system, not individuals<\/li>\n\n\n\n
          • Shift to team accountability for outcomes<\/li>\n\n\n\n
          • Push decisions closer to the team

            These changes remove bottlenecks and increase speed.<\/li>\n<\/ul>\n\n\n\n

            Empowering Teams to Surface Risk Early<\/h2>\n\n\n\n

            Risk is often hidden when teams don\u2019t feel safe to speak up:<\/p>\n\n\n\n

              \n
            • Encourage shared ownership<\/li>\n\n\n\n
            • Build psychological safety<\/li>\n\n\n\n
            • Avoid siloed knowledge

              If issues are not surfaced early, risk simply appears later at higher cost.<\/li>\n<\/ul>\n\n\n\n

              Learning as a Risk Reduction Mechanism<\/h2>\n\n\n\n

              Continuous learning is essential:<\/p>\n\n\n\n

                \n
              • Every delivery provides feedback<\/li>\n\n\n\n
              • Teams should learn throughout, not just at the end<\/li>\n\n\n\n
              • Frequent adaptation prevents risk from becoming expensive

                Sprints are not delivery boundaries. Teams should ship continuously.<\/li>\n<\/ul>\n\n\n\n

                Key Takeaways<\/h2>\n\n\n\n
                  \n
                • Planning creates an illusion of control; delivery creates real control<\/li>\n\n\n\n
                • Evidence from working outcomes is the strongest way to reduce risk<\/li>\n\n\n\n
                • Deliver small, real, visible increments early<\/li>\n\n\n\n
                • Improve flow by limiting work in progress<\/li>\n\n\n\n
                • Shift leadership toward systems thinking and team ownership<\/li>\n\n\n\n
                • Empower teams to surface risks early<\/li>\n\n\n\n
                • Learn continuously and adapt quickly

                  If you boil it down, the message is simple: if you\u2019re not delivering, you\u2019re not reducing risk.<\/li>\n<\/ul>\n\n\n\n

                  <\/p>\n","protected":false},"excerpt":{"rendered":"

                  A practical breakdown of how project managers reduce risk by delivering early, focusing on real outcomes over excessive planning and status reporting.<\/p>\n","protected":false},"author":8033092,"featured_media":8107219,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[],"tags":[2197],"event_session_cat":[],"session_aud_level":[494],"event_session_type":[],"content_source":[1697],"event_session_tags":[],"class_list":["post-8106994","aa_event_session","type-aa_event_session","status-publish","has-post-thumbnail","hentry","tag-free","session_aud_level-learning","content_source-agile-minicon"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session\/8106994","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_event_session"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8033092"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8106994"}],"version-history":[{"count":5,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session\/8106994\/revisions"}],"predecessor-version":[{"id":8107227,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session\/8106994\/revisions\/8107227"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8107219"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8106994"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8106994"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8106994"},{"taxonomy":"event_session_cat","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/event_session_cat?post=8106994"},{"taxonomy":"session_aud_level","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/session_aud_level?post=8106994"},{"taxonomy":"event_session_type","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/event_session_type?post=8106994"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8106994"},{"taxonomy":"event_session_tags","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/event_session_tags?post=8106994"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}