<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Innovation on Nick Perkins</title>
    <link>https://nickperkins.au/tags/innovation/</link>
    <description>Recent content in Innovation on Nick Perkins</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 17 Jan 2025 17:48:50 +1000</lastBuildDate>
    <atom:link href="https://nickperkins.au/tags/innovation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Failure MUST be an option for innovation</title>
      <link>https://nickperkins.au/article/failure-must-be-an-option/</link>
      <pubDate>Fri, 17 Jan 2025 17:48:50 +1000</pubDate>
      <guid>https://nickperkins.au/article/failure-must-be-an-option/</guid>
      <description>This week I hosted a brown bag session at work where I explored the idea that failure isn’t something to be avoided at all costs but must be a safe option for software engineering teams. The concept of failure often carries a negative connotation. However, embracing failure as an option can foster an environment of learning, innovation, and psychological safety. Let’s explore this by looking at the benefits this shift in mindset can bring, and the elements required to create a culture where failure is seen as a stepping stone to success.</description>
    </item>
  </channel>
</rss>
