<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on Sasha Rosenbaum website and blog</title>
    <link>https://www.sasharosenbaum.com/blog/</link>
    <description>Recent content in Blog on Sasha Rosenbaum website and blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Sasha Rosenbaum - 2023</copyright>
    <lastBuildDate>Fri, 10 Feb 2023 00:00:00 -0500</lastBuildDate><atom:link href="https://www.sasharosenbaum.com/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hacking Habits</title>
      <link>https://www.sasharosenbaum.com/blog/hacking-habits/</link>
      <pubDate>Fri, 10 Feb 2023 00:00:00 -0500</pubDate>
      
      <guid>https://www.sasharosenbaum.com/blog/hacking-habits/</guid>
      <description>I have always been fascinated by what BJ Fogg calls &amp;ldquo;behavior design&amp;rdquo; and have read quite a few books on it - &lt;em&gt;The Power of Habit&lt;/em&gt;, &lt;em&gt;Atomic Habits&lt;/em&gt;, &lt;em&gt;Nudge&lt;/em&gt;, Allen Carr&amp;rsquo;s &lt;em&gt;The Easy Way to Control Alcohol&lt;/em&gt;. So far, none came closer to giving me the feeling that I am “hacking the source code” of my own behavior than BJ Fogg’s &lt;em&gt;Tiny Habits&lt;/em&gt;. {{&amp;lt; line_break &amp;gt;}} I found lots of good ideas in the book, including two that are causing me to look at human behavior in a new way. The kind of ideas I call &lt;em&gt;&lt;strong&gt;revelations&lt;/strong&gt;&lt;/em&gt;</description>
    </item>
    
    <item>
      <title>Stand with Ukraine</title>
      <link>https://www.sasharosenbaum.com/blog/ukraine/</link>
      <pubDate>Sat, 05 Mar 2022 00:00:00 -0500</pubDate>
      
      <guid>https://www.sasharosenbaum.com/blog/ukraine/</guid>
      <description>This war is much bigger than a single country invasion. {{&amp;lt; line_break &amp;gt;}} Please do not stand idly by as the worst parts of our history repeat themselves.</description>
    </item>
    
    <item>
      <title>Getting Actionable Customer Feedback</title>
      <link>https://www.sasharosenbaum.com/blog/getting-actionable-customer-feedback/</link>
      <pubDate>Sat, 10 Jul 2021 00:00:00 -0500</pubDate>
      
      <guid>https://www.sasharosenbaum.com/blog/getting-actionable-customer-feedback/</guid>
      <description>Customer feedback is absolutely crucial to product success. The worst sin a company can commit is not listening to their customers. Yet product teams, especially at large companies, get inundated with hundreds of customer requests and escalations. How do you make sure that the requests you are relaying are useful, non-redundant, and detailed enough to be actionable?</description>
    </item>
    
    <item>
      <title>The Anatomy of a Customer Presentation</title>
      <link>https://www.sasharosenbaum.com/blog/anatomy-of-customer-presentation/</link>
      <pubDate>Sun, 18 Apr 2021 00:00:00 -0500</pubDate>
      
      <guid>https://www.sasharosenbaum.com/blog/anatomy-of-customer-presentation/</guid>
      <description>Most speaking advice is written for the kind of presentation you are likely to give at a conference, the kind I will call a &amp;ldquo;narrative talk&amp;rdquo;. And yet, there is another kind of presentation altogether, the kind I will call a &amp;ldquo;customer presentation&amp;rdquo;. If you are just starting out in Technical Sales or Developer Relations, you might think that these two are one and the same, but they are distinctly different.</description>
    </item>
    
  </channel>
</rss>
