<?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 Commit.to on Medium]]></title>
        <description><![CDATA[Stories by Commit.to on Medium]]></description>
        <link>https://medium.com/@commit_to?source=rss-f17dab0049f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jqEuJasfkXvUpIIjalsHIQ.png</url>
            <title>Stories by Commit.to on Medium</title>
            <link>https://medium.com/@commit_to?source=rss-f17dab0049f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:10:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@commit_to/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[It Takes Trust: Why We Built Our Task Management App]]></title>
            <link>https://medium.com/@commit_to/it-takes-trust-why-we-built-our-task-management-app-28788fcaec09?source=rss-f17dab0049f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/28788fcaec09</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[trust]]></category>
            <dc:creator><![CDATA[Commit.to]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 15:24:25 GMT</pubDate>
            <atom:updated>2018-01-30T17:36:16.850Z</atom:updated>
            <content:encoded><![CDATA[<p>In a world where the modern workday is blemished with unproductive meetings, competing priorities and the proverbial overflowing to-do list, it’s about time we talk about trust.</p><p>In a recent <a href="https://www.inc.com/justin-bariso/google-spent-years-studying-effective-teams-this-single-quality-contributed-most-to-their-success.html">look into Google’s Project Aristotle</a> by Inc., a self-study on what makes their teams effective, they found it wasn’t merely a list of tasks or above-average skills alone that produced positive evaluations and increased sales performance.</p><p><strong>It was trust.</strong></p><p>The vulnerable, often avoided five-letter word in the workplace turns out to be the most vital characteristic to build and nurture in teams that want to thrive.</p><p>And we couldn’t agree more.</p><p><a href="https://rework.withgoogle.com/print/guides/5721312655835136/">Google’s findings</a> pointed out it mattered less who was on these teams, but rather how the team worked together. What they found most important, was psychological safety, dependability, structure and clarity, meaning, and impact. In other words, a whole lot of trust in each other and intentional, meaningful work.</p><p>When it comes to the smaller ins and outs of team collaboration that plays a big role in effectiveness, we saw a huge lack in task completion. And that failure to keep commitments, in turn, was the root of crumbling trust within teams.</p><blockquote>Some 2 out 3 professionals make to-do lists yet only <a href="https://www.wired.com/2016/03/best-to-do-list-app/">41% of those items get completed.</a> At <a href="https://www.commit.to/">Commit.to</a>, our users have a 98% completion rate.</blockquote><p>No, that startling number isn’t some kind of productivity magic, it’s what happens when teams move from writing lists of personal tasks to treating those items as social commitments. Our application recognizes that distinction and simply exists to solve the needs of both the person making a commitment and whom the commitment is made to. Safety and dependability on both sides.</p><p>At the time we started developing Commit.to, there weren’t any other project management tools that handled these kinds of social contracts — and certainly none that allowed effortless, conversational capture right in the environment where those conversations and commitments were happening.</p><p>With Commit.to, capture a commitment right within Slack, and it will automatically notify you and others of your commitment.</p><p>Nothing falls off the radar. Assign a time value and you’ll get a nice reminder at exactly the right times.</p><p>Commitment issues? We won’t let you over-commit. Real-time capacity alerts make sure you’re never taking on more than you can handle.</p><p>We wanted a simple and direct system of managing commitments that would enable you to build trust in a team, reduce anxiety, and avoid burnout for the individual.</p><p>Better teamwork and commitments your team will actually keep is possible. If your team is on Slack we’d love for you to <a href="https://www.commit.to/learn/">add our app</a> and see for yourself.</p><p><em>Written by: </em><a href="http://diana-martinez.com/"><em>Diana Martinez</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28788fcaec09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your selfish workflow is killing your team]]></title>
            <link>https://medium.com/@commit_to/your-selfish-workflow-is-killing-your-team-5a327a5115af?source=rss-f17dab0049f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a327a5115af</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[workflow]]></category>
            <dc:creator><![CDATA[Commit.to]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 14:12:17 GMT</pubDate>
            <atom:updated>2018-01-30T04:32:25.277Z</atom:updated>
            <content:encoded><![CDATA[<p>Every team embodies their own cultural values. Those values feed differing workflows, development life-cycles, team communication and organization strategies. And there’s a reason people and organizations are still experimenting with all of these. They all have critical failures that threaten the health and sustainability of teams over time.</p><p>The failure type may vary, but they all share causality because they are designed from a self centered point of view, essentially originating from questions like:</p><blockquote>How do I get others to do what I want them to do and how does that make my life better?</blockquote><p>This would work if we were programming machines, but we’re dealing with people, who have their own values, motivations, commitments and perspectives that, believe it or not, may not always align with yours. Because of this, more often than not, our work in this space has been ill-conceived and doomed from the start.</p><p>Here’s where the empathy workflow is different. We start from the other’s point of view, and ask questions like:</p><blockquote>What would make their life easier? What would lower their anxiety?</blockquote><p>The irony is that much of <em>our</em> anxiety is driven not just by how overloaded <em>we</em> are, but its impacts on our teammates that are counting on us. As we break more and more commitments, trust starts to erode in our teams. Then as defense mechanisms, we stop being as transparent with our work in effort to hide just how much we’re drowning. As this pattern repeats we feel less and less empathy for the other and stop committing to anything out of self preservation.</p><p>At <a href="https://www.commit.to/">Commit.to</a>, we’ve built a system of managing commitments that retains control for the individual. This gives you transparency and accountability, so you can keep your commitments. What we’ve discovered by considering others first is a sense of shared empathy sown into the team. There’s a rebuilding of trust. The team finds comfort in making commitments because they are made transparently and viewable by your teammates, but only under your control. Plus, accountable parties get updates on your commitments to eliminate the “<em>chase down</em>” when team members want to know your status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*Ik0JKEsNWvFUL8V-3vHBKQ.png" /><figcaption>Tagging a teammate in a commitment through Slack</figcaption></figure><p>We’ve heard from so many of our users about how they appreciate and have grown to depend on team commitment notifications. They can trust each one is being tracked and will be delivered.</p><p>In fact, <strong>our users are showing more than 90% completion rate on commitments made</strong> which far outpaces the <a href="http://www.dailymail.co.uk/sciencetech/article-3462411/To-lists-waste-time-Expert-claims-people-write-tasks-rarely-finish-causes-added-stress.html">industry standard of 41%</a> for to-do list trackers.</p><p>We love the impact Commit.to is having on team health and efficiency and we’d love to have you <a href="https://www.commit.to/?ref=medium-empathy">try our app for free</a> and see how it changes your approach to your workflow.</p><p><em>Originally published at </em><a href="https://medium.com/@kcampos/your-selfish-workflow-is-killing-your-team-eed0713fcd6e"><em>medium.com</em></a><em> on September 6, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a327a5115af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>