<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Redfin Gets Better in Almost 14 Million Different Places</title>
	<atom:link href="http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html</link>
	<description>Redfin Corporate Blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 06:50:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Consultant Ninja</title>
		<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/comment-page-1#comment-5327</link>
		<dc:creator>Consultant Ninja</dc:creator>
		<pubDate>Tue, 24 Feb 2009 00:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html#comment-5327</guid>
		<description>John-

I was looking at a house on redfin today, and wondered to myself, &quot;hmm, what is their $/sqft rate relative to the local market&quot; and scrolled down to the graph.  I had two reactions in sequence:

1)  Holy cow, they actual listened to their blog, and implemented it!  That&#039;s unbelievable!

2) Of course!  These redfin guys really get it, I should have expected them to implement it that quickly.

I think you nailed the solution in the short-to-medium term.  I&#039;m so happy that you didn&#039;t do the tick marks in random ranges (eg 237, 261, 285, etc) like some sites.

So, thank you.</description>
		<content:encoded><![CDATA[<p>John-</p>
<p>I was looking at a house on redfin today, and wondered to myself, &#8220;hmm, what is their $/sqft rate relative to the local market&#8221; and scrolled down to the graph.  I had two reactions in sequence:</p>
<p>1)  Holy cow, they actual listened to their blog, and implemented it!  That&#8217;s unbelievable!</p>
<p>2) Of course!  These redfin guys really get it, I should have expected them to implement it that quickly.</p>
<p>I think you nailed the solution in the short-to-medium term.  I&#8217;m so happy that you didn&#8217;t do the tick marks in random ranges (eg 237, 261, 285, etc) like some sites.</p>
<p>So, thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Kim</title>
		<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/comment-page-1#comment-5153</link>
		<dc:creator>John Kim</dc:creator>
		<pubDate>Tue, 27 Jan 2009 19:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html#comment-5153</guid>
		<description>@Ninja,

We&#039;ll be changing that in the next release.  If you&#039;d like the whole story...

Those graphs are used in multiple places.  In the first release of those graphs, they were scaled so that range was a little below the max and min values.  However, this brought up strange problem.  Regions with small changes looked like they were having massive price fluctuations because the small range was being scaled up to fit the graph.  It&#039;s like when you see a magnified picture of your skin.  It looks like the Grand Canyon.  People were having a hard time differentiating between areas that had small fluctuations to those areas with big fluctuations because they weren&#039;t really bothering to read the scale.

So we went to the data display books and many of them said that the only &quot;honest&quot; way to display data like this was to show them at the same scale.  Due to the wide range of areas we cover, that meant starting the scale at 0.  In reality, we&#039;re not using the exact same scale because the max value still varies.  But it did reduce people thinking there were huge fluctuations when in fact there were often times very little.

But it also made it harder to pick out relevant details.  So now we&#039;re kinda going back to a middle ground were the scale does not start at 0, but it doesn&#039;t just cover the max and min values either.  We pad on either side of the graphs to smooth things out but still let people pick out details.

In the future, we&#039;re thinking of changing the graphs even more to allow user interaction and let you zoom in and out.

John Kim &#124; Product Manager</description>
		<content:encoded><![CDATA[<p>@Ninja,</p>
<p>We&#8217;ll be changing that in the next release.  If you&#8217;d like the whole story&#8230;</p>
<p>Those graphs are used in multiple places.  In the first release of those graphs, they were scaled so that range was a little below the max and min values.  However, this brought up strange problem.  Regions with small changes looked like they were having massive price fluctuations because the small range was being scaled up to fit the graph.  It&#8217;s like when you see a magnified picture of your skin.  It looks like the Grand Canyon.  People were having a hard time differentiating between areas that had small fluctuations to those areas with big fluctuations because they weren&#8217;t really bothering to read the scale.</p>
<p>So we went to the data display books and many of them said that the only &#8220;honest&#8221; way to display data like this was to show them at the same scale.  Due to the wide range of areas we cover, that meant starting the scale at 0.  In reality, we&#8217;re not using the exact same scale because the max value still varies.  But it did reduce people thinking there were huge fluctuations when in fact there were often times very little.</p>
<p>But it also made it harder to pick out relevant details.  So now we&#8217;re kinda going back to a middle ground were the scale does not start at 0, but it doesn&#8217;t just cover the max and min values either.  We pad on either side of the graphs to smooth things out but still let people pick out details.</p>
<p>In the future, we&#8217;re thinking of changing the graphs even more to allow user interaction and let you zoom in and out.</p>
<p>John Kim | Product Manager</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Consultant Ninja</title>
		<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/comment-page-1#comment-5152</link>
		<dc:creator>Consultant Ninja</dc:creator>
		<pubDate>Sun, 25 Jan 2009 18:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html#comment-5152</guid>
		<description>Glenn-

Along this vein of continually finding small improvements, I have a suggestion on refining your listing page.

Currently you have a $/sq ft line chart on every listing page.  You&#039;ve set the baseline of the chart axis at zero, which is normally a good practice for line charts, since variance will be properly put into context of the overall value.

However, in this case, I don&#039;t believe that&#039;s what people are looking for.  Customers are comparing that trend to the current $/sqft price of the listing they are looking at.

For example, a customer is interested in how average prices in that zip code have varied from $200-$250/sqft over the last few years, and that it&#039;s currently at $218/sqft but trending downwards, relative to the current listing&#039;s price of $228/sqft.  

Thus, a better way to show this graph would be to set the y-axis min a little below the minimum $/sqft relevant for the region, rather than 0.</description>
		<content:encoded><![CDATA[<p>Glenn-</p>
<p>Along this vein of continually finding small improvements, I have a suggestion on refining your listing page.</p>
<p>Currently you have a $/sq ft line chart on every listing page.  You&#8217;ve set the baseline of the chart axis at zero, which is normally a good practice for line charts, since variance will be properly put into context of the overall value.</p>
<p>However, in this case, I don&#8217;t believe that&#8217;s what people are looking for.  Customers are comparing that trend to the current $/sqft price of the listing they are looking at.</p>
<p>For example, a customer is interested in how average prices in that zip code have varied from $200-$250/sqft over the last few years, and that it&#8217;s currently at $218/sqft but trending downwards, relative to the current listing&#8217;s price of $228/sqft.  </p>
<p>Thus, a better way to show this graph would be to set the y-axis min a little below the minimum $/sqft relevant for the region, rather than 0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asela Dahana</title>
		<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/comment-page-1#comment-5148</link>
		<dc:creator>Asela Dahana</dc:creator>
		<pubDate>Fri, 23 Jan 2009 18:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html#comment-5148</guid>
		<description>Brilliant! Wow I had no idea. As another person said, small incremental improvements are always better that grandiose percentages. I am definitely buying a house via Redfin. The data you guys provide is incredible.</description>
		<content:encoded><![CDATA[<p>Brilliant! Wow I had no idea. As another person said, small incremental improvements are always better that grandiose percentages. I am definitely buying a house via Redfin. The data you guys provide is incredible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arthur.patterson</title>
		<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/comment-page-1#comment-5147</link>
		<dc:creator>arthur.patterson</dc:creator>
		<pubDate>Fri, 23 Jan 2009 18:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html#comment-5147</guid>
		<description>@Andrew:

Yes, we definitely use the lat/long pairs provided by the MLS in some cases. I say some because like you mentioned, the data can be horribly inaccurate, so we only take it from the sources that our testing found to be reasonably close, most of the time, and then only if we are unable to get a geocode of any reasonable accuracy through any other means. This helps primarily with vacant land; it&#039;s other impacts are minimal. 

Yes, we do very little hand-mapping in house,  usually as a customer support request. We&#039;re investigating whether we can get the user-supplied mappings from Google Maps.

Thank you for the insights you shared! Your theory about smaller MLSs is probably right, and hopefully as the mergers increase the data quality will go up.

It looks like you&#039;ve actually got us beat (slightly!) for SoCalMLS. Do you map the undisclosed address listings there? I&#039;m pretty sure you&#039;re allowed to by MLS rules, but it&#039;s not something we&#039;ve tackled yet.</description>
		<content:encoded><![CDATA[<p>@Andrew:</p>
<p>Yes, we definitely use the lat/long pairs provided by the MLS in some cases. I say some because like you mentioned, the data can be horribly inaccurate, so we only take it from the sources that our testing found to be reasonably close, most of the time, and then only if we are unable to get a geocode of any reasonable accuracy through any other means. This helps primarily with vacant land; it&#8217;s other impacts are minimal. </p>
<p>Yes, we do very little hand-mapping in house,  usually as a customer support request. We&#8217;re investigating whether we can get the user-supplied mappings from Google Maps.</p>
<p>Thank you for the insights you shared! Your theory about smaller MLSs is probably right, and hopefully as the mergers increase the data quality will go up.</p>
<p>It looks like you&#8217;ve actually got us beat (slightly!) for SoCalMLS. Do you map the undisclosed address listings there? I&#8217;m pretty sure you&#8217;re allowed to by MLS rules, but it&#8217;s not something we&#8217;ve tackled yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Mattie</title>
		<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/comment-page-1#comment-5145</link>
		<dc:creator>Andrew Mattie</dc:creator>
		<pubDate>Fri, 23 Jan 2009 15:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html#comment-5145</guid>
		<description>I find it really interesting that you have a measurable percentage of your properties mapped by the MLS. I assume that, it some cases, it means that you&#039;re using the latitude/longitude pairs that the MLS provides in their data? Our internal testing showed that the data from the MLS&#039;s is almost always horribly inaccurate, and so we usually ditch it in favor of the three geocoding sources we use. It&#039;s a really tough decision for us in each case to make the call in each case just because we&#039;re concerned that the listing agents themselves actually had input into where they wanted the property to be located, but we make the decision to sacrifice for the greater good.

Do you actually do hand-mapping in-house? Did you know that Proxix (http://www.proxix.com/) has a &quot;hand-mapping&quot; service? It&#039;s expensive, but it might be something you&#039;re interested in.

Overall, your percentage of &quot;ungeocodables&quot; is surprisingly low. I&#039;m really proud of our own system and the geocoding tips we learned in our travels (which I shared with Arthur via email last week), but our percentage of ungeocodables is definitely higher than yours. My suspicion is that a bunch of our smaller MLS&#039;s that have less mapping data available and so it brings down our percentage of geocodeable properties. In large MLS&#039;s though, like SoCal, our geocoding percentage is very high (95.7%).</description>
		<content:encoded><![CDATA[<p>I find it really interesting that you have a measurable percentage of your properties mapped by the MLS. I assume that, it some cases, it means that you&#8217;re using the latitude/longitude pairs that the MLS provides in their data? Our internal testing showed that the data from the MLS&#8217;s is almost always horribly inaccurate, and so we usually ditch it in favor of the three geocoding sources we use. It&#8217;s a really tough decision for us in each case to make the call in each case just because we&#8217;re concerned that the listing agents themselves actually had input into where they wanted the property to be located, but we make the decision to sacrifice for the greater good.</p>
<p>Do you actually do hand-mapping in-house? Did you know that Proxix (<a href="http://www.proxix.com/" rel="nofollow">http://www.proxix.com/</a>) has a &#8220;hand-mapping&#8221; service? It&#8217;s expensive, but it might be something you&#8217;re interested in.</p>
<p>Overall, your percentage of &#8220;ungeocodables&#8221; is surprisingly low. I&#8217;m really proud of our own system and the geocoding tips we learned in our travels (which I shared with Arthur via email last week), but our percentage of ungeocodables is definitely higher than yours. My suspicion is that a bunch of our smaller MLS&#8217;s that have less mapping data available and so it brings down our percentage of geocodeable properties. In large MLS&#8217;s though, like SoCal, our geocoding percentage is very high (95.7%).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Consultant Ninja</title>
		<link>http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html/comment-page-1#comment-5139</link>
		<dc:creator>Consultant Ninja</dc:creator>
		<pubDate>Fri, 23 Jan 2009 08:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.redfin.com/blog/2009/01/redfin_gets_better_in_almost_14_million_different_places.html#comment-5139</guid>
		<description>Your post describes a rare brilliance in businesses.

Many organizations are driven by either grandiose strategic visions (led by MBAs with strategic differentiating blue-ocean leveraging advantages in their starry eyes), or by inward-looking bureaucratic organizations that change by moving people and roles.

The rare trait you show is the power of starting with a basic but extensible product architecture and then continually looking for small, incremental improvements that improve the customer value proposition.

At IBM&#039;s e-business group in the 90s, I remember this being called &quot;start small, grow fast.&quot;

At another client I worked for, we kept on measuring changes by estimate the % improvement delivered.  We never wanted a 50%, or 100% improvement to their product; we just wanted to keep finding lots of tweaks and adds that really made the service better.  We weekly thought of and implemented, 2%, 4%, 5%, improvements.  This rapid iteration (enabled by the flexible product architecture) quickly added up to a truly kick-ass product.

Which is what you have done here at Redfin.  Well done sirs, well done.</description>
		<content:encoded><![CDATA[<p>Your post describes a rare brilliance in businesses.</p>
<p>Many organizations are driven by either grandiose strategic visions (led by MBAs with strategic differentiating blue-ocean leveraging advantages in their starry eyes), or by inward-looking bureaucratic organizations that change by moving people and roles.</p>
<p>The rare trait you show is the power of starting with a basic but extensible product architecture and then continually looking for small, incremental improvements that improve the customer value proposition.</p>
<p>At IBM&#8217;s e-business group in the 90s, I remember this being called &#8220;start small, grow fast.&#8221;</p>
<p>At another client I worked for, we kept on measuring changes by estimate the % improvement delivered.  We never wanted a 50%, or 100% improvement to their product; we just wanted to keep finding lots of tweaks and adds that really made the service better.  We weekly thought of and implemented, 2%, 4%, 5%, improvements.  This rapid iteration (enabled by the flexible product architecture) quickly added up to a truly kick-ass product.</p>
<p>Which is what you have done here at Redfin.  Well done sirs, well done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

