<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Matt Schwarz on Medium]]></title>
        <description><![CDATA[Stories by Matt Schwarz on Medium]]></description>
        <link>https://medium.com/@mattschwarz?source=rss-19fc1da02161------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*U7WTxMEhoq8x04-APJq1fw.jpeg</url>
            <title>Stories by Matt Schwarz on Medium</title>
            <link>https://medium.com/@mattschwarz?source=rss-19fc1da02161------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:51:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mattschwarz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building What Matters]]></title>
            <link>https://medium.com/maslo/building-what-matters-e67b1f8630be?source=rss-19fc1da02161------2</link>
            <guid isPermaLink="false">https://medium.com/p/e67b1f8630be</guid>
            <category><![CDATA[maslo]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[cms]]></category>
            <dc:creator><![CDATA[Matt Schwarz]]></dc:creator>
            <pubDate>Tue, 29 Jan 2019 23:49:26 GMT</pubDate>
            <atom:updated>2019-03-22T19:02:35.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*DLuo1gS2xzjSvfQZgGxRVQ@2x.jpeg" /></figure><h4>Using what you have and keeping it simple</h4><p>2011-me was a little ahead of my time. It was April fools and myself and the rest of the Vimeo team had just released a new ‘feature’. We replaced the search navigation with a voice prompt. (Some) users were obviously surprised by our innovation and upon using it, users were transported to a “Rick Roll” video. They had a laugh, we had a laugh, and it was all in good fun. But who knew that speaking to machines really would be the future — a natural progression of human and computer interaction because it’s, well…simpler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*pWwTec5dH8zcG_SQgXiECw.png" /></figure><p>Fast-forward to my work with Maslo, where speaking with machines is the norm, and I still find myself attempting to simplify things. “I want a blog” is a phrase I’ve heard too many times at too many companies, and the recent launch of the new Maslo website was no different.</p><p>The goal was to increase SEO and organic traffic, but we wanted to avoid creating something that 1) very little will read because [the site] wouldn’t have its own community, 2) excludes an existing and popular community we already make use of for our blog content (Medium), and 3) creates more work for us when it really isn’t needed.</p><p>After experimenting with various approaches our partners at Zajno concluded with the idea to keep the Maslo blog on Medium and ingest the content into our site while also redirecting the user to the source when they click to read an article. We knew letting our Medium presence continue to exist while seamlessly integrating it with our site would be the best option for both Maslo and our community on Medium.</p><p>Now to the issue at hand: Medium has historically only offered a write-only API (<a href="https://stackoverflow.com/questions/36097527/how-to-retrieve-medium-stories-for-a-user-from-the-api">though you can fetch posts via a special URL</a> with some arguments attached, but that requires some more work and is best saved for another post). Luckily <a href="https://medium.jasonmdesign.com/display-medium-articles-on-your-site-d772b3b05779">some other Medium users</a> have run into the same issue and offered up an interesting solution. Medium does offer an RSS feed, and there is an amazingly straight-forward service out there that converts RSS feeds to REST APIs. Enter <a href="http://rsstojson.com/">rsstojson.com</a>.</p><p>Using this service we were able to capture our Medium account’s posts as a REST API using an endpoint rsstojson provides each integration you create. All it took now was some JavaScript to make the API call, parse the content, and lazy-load the posts into our blog page. Most of the heavy lifting came down to DOM manipulation specific to our UI, but when it was all said and done our site had a blog…without all the hassles of a blog!</p><blockquote>The hard part about changing the world (and making good products) is avoiding the urge to do what you know and are good at, and instead become good at what is important — even if that means throwing away what’s comfortable and embracing the simple.</blockquote><p>Maslo is more than a website, or an app, or a blog, but the embodiment of empathy within technology. As we think about how we go about building things we try to remind ourselves to put the emphasis on the people and the process. Technology for technology’s sake is useless — we could have built a brand new CMS which I’ve done too many times to count — it’s the people and the community around it (like the one at Medium) that bring it to life.</p><p>If you liked this, click 👏 so other people will see this here on Medium.</p><p><strong>Maslo is currently in beta. Sign up for early access on our </strong><a href="https://maslo.ai/"><strong>website</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e67b1f8630be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maslo/building-what-matters-e67b1f8630be">Building What Matters</a> was originally published in <a href="https://medium.com/maslo">Your Virtual Self</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some Things I’ve Learned About Supporting an Online Community]]></title>
            <link>https://medium.com/@mattschwarz/some-things-ive-learned-about-supporting-an-online-community-138f1c531ba3?source=rss-19fc1da02161------2</link>
            <guid isPermaLink="false">https://medium.com/p/138f1c531ba3</guid>
            <dc:creator><![CDATA[Matt Schwarz]]></dc:creator>
            <pubDate>Mon, 23 Sep 2013 21:50:31 GMT</pubDate>
            <atom:updated>2013-09-23T21:50:31.103Z</atom:updated>
            <content:encoded><![CDATA[<h4>Love to love the ones who love…or hate.</h4><p>For my inaugrual post on Medium, I thought long and hard about the subject matter. I’ve lived in New York City for three and a half years —that alone must have produced some story worth spreading across the internet, but for the life of me I can’t remember.</p><p>The most obvious experience I can think to reflect on is my time as a community manager, and the seemingly inevitable life lessons it has taught me about interacting with people online.</p><p>Here are some tips on being an awesome internet host for real humans:</p><ol><li><strong>Take a look through their eyes</strong></li></ol><p>I’ve learned to always look at a user’s issue from their perspective first, then determine how to communicate what’s actually possible from my end. When you’ve been with the same company for as long as I have, it is easy to become attached to behaviors that at one point would have been considered acceptable, but are now more or less baseless considering the level of professionalism you’re trying to portray.</p><p>So start-up culture aside, these are humans trying to use a service you provide. They can of course choose not to — and sometimes that’s the best option for both of you — but considering the outside looking in is usually a helpful viewpoint for judgement. If nothing else you’ll be able to decide whether or not that person is crazy and how to act.</p><p><strong>2. Keep your cool</strong></p><p>Your patience, tact, and ability to discern right from wrong (in their eyes) will be tested with every interaction. Loosing your cool, even for a moment, can spell disaster when dealing with users looking for a reason to complain. Trying to foster “good vibes” with that user has to be the end goal, whether they’re right for your service or not.</p><p>I’ve found that angry users will most often bring in non-sensical reasoning to try and justify their point—this is a distraction. Keep in mind they most likely found their way to you out of frustration and they might assume (with good reason) that this attempt is a last-ditch effort or black hole from which no email response ever emerges. As a community manager your job is to locate the actual issue, push the bullshit aside, and keep at it.</p><p><strong>3. Respond to Feedback and be honest</strong></p><p>Your users…actually strike that, let’s call them community members from now on. Your <em>community members </em>are your site, but they are also using the platform or service <em>you</em> provide. That puts you in an interesting position to gather feedback and choose what to implement.</p><p>To me, a well managed community has its goals weighed against the greater product goals. With luck, there will be many ideas that agree with one another and few that do not.</p><p>If you do agree, say so! Let your members know you want to implement a suggested change and if possible, give an ETA. If not, let them know why you disagree and tie the reasoning back to the goal of your product.</p><p>As long as you’re clear, a member’s only decision should be whether or not to stay on with your service. That may sound scary, but loosing them due to your transparency shouldn’t be the fear—having them drag your name through the mud becuase of some silly misunderstanding <em>is</em>.</p><p><strong>4. Empower those who empower you</strong></p><p>As your community grows it becomes harder to respond to users who just want to say “Hi”. Yes you love them, they may even bake you cookies, but with all those help requests piling up, who has the time?</p><p>You do!</p><p>It’s crucial to make the community member who went out of their way to tell you what a good job you’re doing feel<em> awesome </em>in return. Crucial for you, the community, and your team. At <a href="http://vimeo.com/">Vimeo</a> we have affectionately named these interactions “<a href="http://vimeo.com/love">Loveo</a>”. When our team identifies Loveo, we send a personal response which is then forwarded to the entire company. It helps keep our staff on point when thinking about our community and how we as a company should interact with users—especially those who hold us in such high regard.</p><p>This is by no means a tell-all of community management, nor everything I’ve learned over my years with Vimeo, but I hope they are at least helpful when it comes to building your community in to the loving place it should be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=138f1c531ba3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>