<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Asana Blog</title>
	
	<link>http://blog.asana.com</link>
	<description />
	<lastBuildDate>Thu, 03 May 2012 17:59:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/Asana" /><feedburner:info uri="asana" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Getting Your Team Started on Asana</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/Vl_y0DIW09c/</link>
		<comments>http://blog.asana.com/2012/05/getting-your-team-started-on-asana/#comments</comments>
		<pubDate>Thu, 03 May 2012 17:59:26 +0000</pubDate>
		<dc:creator>Jerry Phillips</dc:creator>
				<category><![CDATA[Best Practices]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=849</guid>
		<description><![CDATA[The launch of Premium Workspaces means that larger teams can now use Asana to manage their workflow. We’re honored that teams of all sizes—from one-person projects to companies with more than 100 employees—are all using Asana to eliminate “work about work.” When it comes to using a new workplace product, both small startups and large [...]]]></description>
			<content:encoded><![CDATA[<p>The launch of <a href="http://blog.asana.com/2012/04/premium-workspaces-for-asana/" title="Premium Workspaces" target="_blank">Premium Workspaces</a> means that larger teams can now use Asana to manage their workflow. We’re honored that teams of all sizes—from one-person projects to companies with more than 100 employees—are all using Asana to eliminate “work about work.”</p>
<p>When it comes to using a new workplace product, both small startups and large corporations have something in common: change can be hard. While many teams adopt Asana after a quick introduction, some teams—especially larger teams—take more time to adapt to a new way of communicating.</p>
<p>Whether you’re a business owner who’s decided to implement Asana company-wide or you’re someone who wants to get coworkers to use Asana, we have multiple resources at the <a href="http://help.asana.com/" title="Asana Help Center" target="_blank">Help Center</a> to help get your team on board. </p>
<p>We also recognize that you might want more in-depth guidance for onboarding team members. So, we’ve outlined a comprehensive list of best practices and tips for adopting Asana. </p>
<p>Read <a href="http://help.asana.com/customer/portal/articles/110493-getting-your-team-started-on-asana" title="Getting Your Team on Asana" target="_blank">Getting Your Team Started on Asana</a>, invite team members to your Workspace, and start getting things done faster than ever before. </p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/Vl_y0DIW09c" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/05/getting-your-team-started-on-asana/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/05/getting-your-team-started-on-asana/</feedburner:origLink></item>
		<item>
		<title>Announcing Premium Workspaces for Asana</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/h-BezRAhgj8/</link>
		<comments>http://blog.asana.com/2012/04/premium-workspaces-for-asana/#comments</comments>
		<pubDate>Tue, 24 Apr 2012 13:45:25 +0000</pubDate>
		<dc:creator>Kenny Van Zant</dc:creator>
				<category><![CDATA[Company]]></category>
		<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=845</guid>
		<description><![CDATA[Almost 6 months ago, we opened Asana to everyone. Teams up to 30 members could join a shared Workspace, and coordinate their efforts faster and more fluidly than ever before. Since our launch, tens of thousands of these teams have trusted Asana to help them do great things, in industries as varied as disease research, [...]]]></description>
			<content:encoded><![CDATA[<p>Almost 6 months ago, we opened Asana to everyone. Teams up to 30 members could join a shared Workspace, and coordinate their efforts faster and more fluidly than ever before. Since our launch, tens of thousands of these teams have trusted Asana to help them do great things, in industries as varied as disease research, mobile networks, professional football, and software development. Many have told us that in this short time, Asana has become the backbone for their teams’ work and transformed the way they communicate. We especially appreciated the marriage proposals ;)</p>
<p>We think Asana has been this well received because it connects with the yearning in all of us to achieve our goals and actualize our dreams. In this way, Asana is just a small piece of something much bigger. We are all contributors to the biggest and most important project of them all: defining, shaping, and realize our collective future. We built Asana because we feel strongly that the best way we can contribute to the world is to help others contribute to the world.</p>
<p>Asana is helping teams with important missions be faster, focused, and more efficient. It’s done this because we’ve stayed true to our core design principles: Asana is fast, flexible, and powerful. As Foursquare’s Noah Weiss says, “Speed was the killer feature that got everyone on board. Since Foursquare moved over to Asana, everyone &#8212; engineer, designer, bizdev, and in between &#8212; has two websites perpetually open: their inbox and Asana.”</p>
<p>To date, people have created 10 million Tasks in Asana. Even more excitingly, they’ve already completed 4 million of them. Teams consistently tell us that Asana is the first productivity product that has stuck &#8212; and, indeed, 75% of the people who have adopted Asana are still using it. Harrison Shoff explains why he loves using it at Airbnb: “Asana feels like I&#8217;m working with a low-friction, smart piece of paper.” </p>
<h3>Asana for larger teams</h3>
<p>Since our launch last November, many small teams using Asana at larger companies have spread the word to other departments in their organization, until their colleagues benefitting from Asana number in the hundreds. They’re now eager to collaborate in groups larger than 30, and in many cases to roll Asana out to their entire company, providing the unified collaboration space for their business.</p>
<p>So starting today, we are making Asana available to teams larger than 30 through Premium Workspaces. Any team can upgrade their existing Workspace to a Premium Workspace, which offers:</p>
<ul>
<li><strong>More Workspace members</strong> &#8211; upgrade to a higher tier of members, starting at just $300/month for up to 50 teammates. Tiers of 75, 100, or more members are also available.</li>
<li><strong>Project-level Permissions</strong> &#8211; share private Projects with a small group within your Workspace, so exactly the right people see the Projects they need to see.</li>
<li><strong>Priority Support</strong> &#8211; questions and issues from customers in Premium Workspacess get a faster response from our outstanding support team.</li>
</ul>
<p>Of course, the same Asana that has been available since we launched will <strong>continue to be free</strong>, continue to offer unlimited Tasks, Projects, and attachments for up to 30 members, and continue to improve every week. This launch is about enabling even larger teams to accomplish their shared goals and coordinate their collective action with less effort. Teams under 30 can also upgrade to a Premium Workspace to enjoy the benefits of Project-level Permissions and Priority Support for just $100/month.</p>
<p>Asana has always been a <a href="http://blog.asana.com/2011/10/every-step/" title="Every step" target="_blank">labor of love</a> for us, and we think you’ll love using it. We look forward to hearing what you think about Premium Workspaces — and seeing what they help you create.</p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/h-BezRAhgj8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/04/premium-workspaces-for-asana/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/04/premium-workspaces-for-asana/</feedburner:origLink></item>
		<item>
		<title>Announcing the Asana API</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/8m6OmojuAy0/</link>
		<comments>http://blog.asana.com/2012/04/announcing-the-asana-api/#comments</comments>
		<pubDate>Thu, 19 Apr 2012 17:47:53 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=844</guid>
		<description><![CDATA[Today we are excited to share that you can now add and access Asana data programmatically using our simple REST API. The Asana API lets you build a variety of applications and scripts to integrate Asana with your business systems, show Asana data in other contexts, and create tasks from various locations. Here are some [...]]]></description>
			<content:encoded><![CDATA[<p>Today we are excited to share that you can now add and access Asana data programmatically using our simple <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer" target="_blank">REST</a> API.</p>
<p>The Asana API lets you build a variety of applications and scripts to integrate Asana with your business systems, show Asana data in other contexts, and create tasks from various locations.</p>
<p>Here are some examples of the things you can build:</p>
<ul style="list-style:disc;">
<li>Source Control Integration to mark a Task as complete and add a link to the code submission as a comment when submitting code.</li>
<li>A desktop app that shows the Tasks assigned to you</li>
<li>A dashboard page that shows a visual representation of complete and incomplete Tasks in a project</li>
</ul>
<p>The API is available for free to everyone with an Asana account. To get started:</p>
<ol style="list-style:decimal;">
<li><a href="http://app.asana.com/-/account_api" target="_blank">Get your API key.</a></li>
<li>Paste this curl command into your console, to test that you can retrieve your user info:<br />
<code style="font-family:Courier,fixed;font-size:83%">export API_KEY=<em>your-key</em> ; curl -u $API_KEY: https://app.asana.com/api/1.0/users/me</code></li>
</ol>
<p>You can find more details in our <a href="http://developer.asana.com/documentation/" target="_blank">API documentation</a>. There, you’ll see some example applications, including a Chrome Extension that lets you select text on any web page and quickly create an Asana Task. </p>
<p>If you have questions about the API, please ask them on <a href="http://stackoverflow.com/" target="_blank">Stack Overflow</a>. We will be monitoring the site for questions and answering them promptly.</p>
<p>Thanks again to everyone who contributed feedback and waited patiently for the API to become available. We can’t wait to see what you create.</p>
<p>For more information, please visit our developer site: <a href="http://developer.asana.com" target="_blank">http://developer.asana.com</a></p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/8m6OmojuAy0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/04/announcing-the-asana-api/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/04/announcing-the-asana-api/</feedburner:origLink></item>
		<item>
		<title>Why We’re Excited About the Real-Time Web</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/KIUMHpF2Au8/</link>
		<comments>http://blog.asana.com/2012/04/why-were-excited-about-the-real-time-web/#comments</comments>
		<pubDate>Wed, 18 Apr 2012 17:34:28 +0000</pubDate>
		<dc:creator>Kenny Van Zant</dc:creator>
				<category><![CDATA[Company]]></category>
		<category><![CDATA[Engineering]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=841</guid>
		<description><![CDATA[ReadWriteWeb recently published an article that Greg Slovacek, one of our software engineers, wrote about the power of real-time applications. The advances in computing leading up to now have had a major impact on the software experience: richer and more powerful clients, access to more information and greater connectivity to other users. We now have [...]]]></description>
			<content:encoded><![CDATA[<p>ReadWriteWeb recently <a href="http://www.readwriteweb.com/hack/2012/04/realizing-the-promise-of-a-rea.php" target="_blank">published an article</a> that Greg Slovacek, one of our software engineers, wrote about the power of real-time applications.<br />
<em><br />
<blockquote>The advances in computing leading up to now have had a major impact on the software experience: richer and more powerful clients, access to more information and greater connectivity to other users. We now have the opportunity to get a desktop software-quality interaction experience combined with a Web-quality network experience, empowering us to build apps that are far better than the best of either of the two experiences alone.</p></blockquote>
<p></em><br />
As Greg explains, it&#8217;s a fantastic time to be a web developer, and we’re looking for awesome engineers to help us write the next generation of collaborative software. Interested? Read the full article <a href="http://www.readwriteweb.com/hack/2012/04/realizing-the-promise-of-a-rea.php" target="_blank">here</a> and send us a message at <a href="mailto:jobs@asana.com">jobs@asana.com</a>.</p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/KIUMHpF2Au8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/04/why-were-excited-about-the-real-time-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/04/why-were-excited-about-the-real-time-web/</feedburner:origLink></item>
		<item>
		<title>I Think I Saw A Unicorn</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/yLUZTmMJ33Q/</link>
		<comments>http://blog.asana.com/2012/04/i-think-i-saw-a-unicorn/#comments</comments>
		<pubDate>Mon, 02 Apr 2012 20:44:18 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Culture]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=836</guid>
		<description><![CDATA[Here at Asana, we work tirelessly to find ways to make our users more effective. We design, build, test, and iterate on all aspects of our product with the goal of helping all of you do great things. So when we recently learned that not only do some of our users like unicorns, but others [...]]]></description>
			<content:encoded><![CDATA[<p>Here at Asana, we work tirelessly to find ways to make our users more effective. We design, build, test, and iterate on all aspects of our product with the goal of helping all of you do great things.</p>
<p>So when we recently learned that not only do some of our users like unicorns, but others have never even <em>seen</em> a unicorn, our creative engine kicked into action. This could be a highly leveraged opportunity to both motivate our users and give them a very special reward for using our product. Of course, we couldn&#8217;t just give everyone unicorns (which are very, very rare) without knowing the consequences. So in true Asana fashion, we decided we&#8217;d have to run an experiment.</p>
<p>To test this opportunity, we engineered our product to randomly deliver a flying unicorn, riding on a rainbow laced with an encouraging message, upon completion of a task. It didn&#8217;t show up for every completed task, but just once in a while. Then we&#8217;d see if our unicorn-spotting users got more productive.</p>
<p><a href="http://blog.asana.com/2012/04/i-think-i-saw-a-unicorn/unicorns/" rel="attachment wp-att-837"><img src="http://blog.asana.com/wp-content/post-images/unicorns-300x180.png" alt="" title="Rainbow-surfing Unicorn" width="300" height="180" class="alignright size-medium wp-image-837" /></a></p>
<p>Now, the introduction of a rainbow-surfing unicorn reward raises many questions regarding user productivity. For example, what is the optimal number of colors for the rainbow to have? Is it important that the creature is, in fact, a unicorn? Does the tone or content of the messages make a difference?</p>
<p>Since we like to learn things quickly, we have already prepared experiments to answer these questions as well. We look forward to comparing yesterday&#8217;s results with those for users who see a three-color-rainbow-surfing narwhal that quotes the Dalai Lama. Yes, narwhals also have horns. We have to control for <em>something!</em></p>
<p>So far, the unicorn has been so well-received that there is already talk internally of moving towards a single-horned UI with a rainbow color scheme. We&#8217;ll look at the data to figure out just how many colors it should have.</p>
<p>Also, <strong>happy April Fool&#8217;s Day!</strong> We hope you enjoyed it.</p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/yLUZTmMJ33Q" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/04/i-think-i-saw-a-unicorn/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/04/i-think-i-saw-a-unicorn/</feedburner:origLink></item>
		<item>
		<title>Best Practices: Using Asana for Customer Relationship Management</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/UY1u1GpMJEI/</link>
		<comments>http://blog.asana.com/2012/03/best-practices-using-asana-for-customer-relationship-management/#comments</comments>
		<pubDate>Fri, 30 Mar 2012 05:44:37 +0000</pubDate>
		<dc:creator>Jerold A. Blain</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=835</guid>
		<description><![CDATA[At Asana, we set out to build an application that enables people to do great things and reduce the volume of “work about work.” Asana is flexible and can therefore meet many needs; teams can accomplish their daily to-dos as well as high-level, long-term goals&#8211;all within one centralized product. Asana is much more than a [...]]]></description>
			<content:encoded><![CDATA[<p>At Asana, we set out to build an application that enables people <a href="http://techcrunch.com/2012/01/20/do-great-things/">to do great things</a> and reduce the volume of “work about work.” Asana is flexible and can therefore meet many needs; teams can accomplish their daily to-dos as well as high-level, long-term goals&#8211;all within one centralized product.</p>
<p>Asana is much more than a simple task and project management tool; it can also be used for specific internal functions, like <a href="http://blog.asana.com/2011/08/how-we-use-asana-for-bug-tracking/ ">bug tracking</a> and <a href="http://help.asana.com/customer/portal/articles/153913-using-asana-for-applicant-tracking">applicant tracking</a>. Since our launch, we’ve received a lot of positive feedback from teams and businesses that rely on Asana as a lightweight tool for customer relationship management (CRM).</p>
<p>When using Asana for CRM, customers become the Task or Project (or, <a href="http://help.asana.com/customer/portal/questions/243234-the-3rd-crm-method">as one of our users explained</a>, customers can even become a Tag). Teams are able to keep a record of every interaction&#8211;from generating leads to maintaining relationships with loyal customers&#8211;in the notes and comments section. </p>
<p>Watch the video below to learn more.</p>
<p><iframe width="640" height="360" src="https://www.youtube.com/embed/oxEW_NyFV-I" frameborder="0" allowfullscreen></iframe></p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/UY1u1GpMJEI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/03/best-practices-using-asana-for-customer-relationship-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/03/best-practices-using-asana-for-customer-relationship-management/</feedburner:origLink></item>
		<item>
		<title>Sort Your Tasks by Due Date</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/CtjKXAtl8Vk/</link>
		<comments>http://blog.asana.com/2012/03/sort-your-tasks-by-due-date/#comments</comments>
		<pubDate>Mon, 26 Mar 2012 20:29:07 +0000</pubDate>
		<dc:creator>Jackie Bavaro</dc:creator>
				<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=830</guid>
		<description><![CDATA[If you like to set dates on tasks, you’d probably like to view those tasks sorted by date. We’re excited to announce that now you can &#8212; just choose the “Date” option in our view selector. The Date view has a few nifty features. When one of your tasks is running behind, it’s likely that [...]]]></description>
			<content:encoded><![CDATA[<p>If you like to set dates on tasks, you’d probably like to view those tasks sorted by date.  We’re excited to announce that now you can &#8212; just choose the “Date” option in our view selector.</p>
<p><a href="http://blog.asana.com/2012/03/sort-your-tasks-by-due-date/sort_by_duedate/" rel="attachment wp-att-831"><img src="http://blog.asana.com/wp-content/post-images/sort_by_duedate.png" alt="" width="339" height="121" class="alignnone size-full wp-image-831" /></a></p>
<p>The Date view has a few nifty features. When one of your tasks is running behind, it’s likely that many of them are.  In the Date view, you can select multiple tasks and then use CMD+down to add a day to all of the due dates.  This makes it easy to adjust schedules and keep the relative timings.</p>
<p>Another new feature of the Date view is that completed Tasks show up next to incomplete Tasks, so you can see your Tasks as a timeline.  Once you’re done looking at completed Tasks, you can archive them to hide them.</p>
<p>Date sorting doesn’t interfere with Priority sorting, so you can switch between both views, depending on how you want to look at a Project. And with great power comes great responsibility &#8211; please make sure to communicate with the other people on the project so that you all agree to use priority or dates for ordering.</p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/CtjKXAtl8Vk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/03/sort-your-tasks-by-due-date/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/03/sort-your-tasks-by-due-date/</feedburner:origLink></item>
		<item>
		<title>Guest Accounts: Asana for Clients, Contractors, and Consultants</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/jgekdYP-bvs/</link>
		<comments>http://blog.asana.com/2012/03/guest-accounts-asana-for-clients-contractors-and-consultants/#comments</comments>
		<pubDate>Wed, 14 Mar 2012 21:53:44 +0000</pubDate>
		<dc:creator>Jackie Bavaro</dc:creator>
				<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=827</guid>
		<description><![CDATA[Since our launch in November, teams have been using Asana to collaborate, work more effectively, and stay in sync on what matters. Of course, it’s not just coworkers who need access to task and project information. Often, you need to share project details with collaborators and stakeholders outside of the company. Starting today, you can [...]]]></description>
			<content:encoded><![CDATA[<p>Since our launch in November, teams have been using Asana to collaborate, work more effectively, and stay in sync on what matters. Of course, it’s not just coworkers who need access to task and project information. Often, you need to share project details with collaborators and stakeholders outside of the company. Starting today, <strong>you can share <em>specific</em> Tasks or Projects</strong> with anyone &#8212; without sharing your entire Workspace with them &#8212; with <strong>Guest Accounts</strong>.</p>
<p>Here’s how it works:</p>
<ul>
<li><strong>Adding Guests</strong><br />
    To add a guest to a Project, click the “Share” button at the top of the Project and type their email address where it says “Add a person.” Then select “Only this Project (Guest).” The guest will get access only to that specific Project, not the whole Workspace.</li>
<li><strong>Guest Account Capabilities</strong><br />
    Guests can add, edit, assign, and follow Tasks in the Project, but they can’t delete the Project. Guests can also add other guests to the Project – so if you’re working with an external team, you can invite just one person from that team and they’ll be able to invite their colleagues.</li>
<li><strong>Collaborating with Guests</strong><br />
    When you use Guest Accounts, you can keep all of your company’s Tasks in one Workspace – no need to create a separate Workspace just to work with someone new. </p>
<p>For example, if you work at an advertising agency, you can create one Project for each client.  You’ll see all your clients in one place, but when a client logs into Asana, they’ll see only the Project you shared with them. Now you and the client can collaborate on tasks together, and have a shared understanding of your project’s status in real-time.</li>
</ul>
<p>Collaboration is the heart of Asana, and Guest Accounts are just the latest development in our ongoing work to help you share exactly what you want with exactly the right people.  By keeping you in control of your data, Asana enables you to collaborate seamlessly with everyone you work with &#8212; inside and outside your company.</p>
<p>Interested in the more advanced privacy controls we&#8217;ll be launching soon?  Click &#8220;Make Private&#8221; in the Share dialog, and then click &#8220;Notify me when Asana Premium is Available.&#8221;</p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/jgekdYP-bvs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/03/guest-accounts-asana-for-clients-contractors-and-consultants/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/03/guest-accounts-asana-for-clients-contractors-and-consultants/</feedburner:origLink></item>
		<item>
		<title>The Power of Tasks in Multiple Projects</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/QIGNWynoBeU/</link>
		<comments>http://blog.asana.com/2012/02/the-power-of-tasks-in-multiple-projects/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 23:17:25 +0000</pubDate>
		<dc:creator>Jackie Bavaro</dc:creator>
				<category><![CDATA[Best Practices]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=820</guid>
		<description><![CDATA[One of the things that makes Asana powerful and versatile is a capability it’s had from the start &#8212; a Task can be in more than one Project at the same time. Instead of treating Projects like closed folders, where the contents inside only live in one place, Asana Projects are more like playlists in [...]]]></description>
			<content:encoded><![CDATA[<p>One of the things that makes Asana powerful and versatile is a capability it’s had from the start &#8212; <em>a Task can be in more than one Project at the same time</em>. Instead of treating Projects like closed folders, where the contents inside only live in one place, Asana Projects are more like playlists in iTunes. Just like a single song can come first in my vacation playlist and last on my dinner party playlist, a single Task can be in multiple Asana Projects.  </p>
<p>Allowing Tasks to be in multiple Projects means a team has access to multiple views of the same piece of work, and each team member can organize Tasks without losing collective view of discussions, history, ownership, or other information. </p>
<p>We built this feature into the fabric of Asana because viewing information from multiple perspectives is essential for collaborative task management, especially in a world where people have their own work and organizational styles. It saves time, improves collaboration, and lets people organize work in a way that makes sense to them. </p>
<p>Let’s discuss a few concrete examples:</p>
<p><strong>Focus on the Work That Matters</strong><br />
The nature of Asana means you can have fewer meetings, but it also helps make your meetings faster, more efficient, and more focused on the important decisions. </p>
<p>For some teams, preparing for a meeting means copying and pasting notes from scattered email threads, last-minute additions, and offline discussion of action items. Perhaps the finalized agenda is projected on a screen during the meeting, or maybe each individual team member views it privately on their own computer. </p>
<p>Whatever the process might be, it usually involves an unnecessary amount of time. But with Asana, you can create a Project for your agenda, and then add items to the agenda from previously created Tasks.  In the agenda the Tasks are sorted by the order you’ll discuss them, but in the original Project they retain their priority order. </p>
<p>The ability to include Tasks in multiple Projects also means that items can quickly be added to agendas during a meeting. And, as your team discusses a Task, you can click on it to pull up the notes and conversation; any decisions you make can be recorded directly in the notes. You can also assign the Task and include it in the relevant Project immediately &#8212; there are no follow-up emails or meeting summaries needed. </p>
<p>When everyone is on the same page from a project’s beginning to end, you can spend less time doing busy work and more time on the issues that matter.</p>
<p><strong>Effortless Cross-Team Prioritization</strong><br />
When two teams work together, you’ll sometimes find Tasks that don’t fall entirely under the scope of one team or the other. But eventually the work has to get done, and with Asana you can track which Tasks are complete without miscommunication.</p>
<p>For example, both the Sales and Marketing teams might want an update to the pricing page on their company’s website, but only one team needs to make the change.  In Asana, you can put the Task in both the Sales Project and the Marketing Project, letting each team prioritize according to their schedule.</p>
<p>When one team starts working on it, the other team will be able to track the assignment’s progress so that they don’t accidentally duplicate the effort.</p>
<p><a href="http://blog.asana.com/2012/02/the-power-of-tasks-in-multiple-projects/multiple-projects-marketing/" rel="attachment wp-att-821"><img src="http://blog.asana.com/wp-content/post-images/Multiple-Projects-Marketing.png" alt="" width="513" height="246" class="alignnone size-full wp-image-821" /></a></p>
<p><strong>The Right View for Each Team Member</strong><br />
On big projects that involve multiple teams, each team might need to view a Project from their own point of view. </p>
<p>For example, if you’re remodeling an office building, the design team might think of the plans on a room by room basis, while the contractor thinks of the plans in the order they’ll be worked on. In Asana, you can create a Project for each team and put the remodeling Tasks in both Projects.  Since the Tasks are the same, you’ll have one single shared history between the teams, and communication won’t get lost in the hand off.</p>
<p>An added benefit to allowing Tasks to be in more than one Project is that you get more freedom and flexibility; you don’t have to adapt to one method of organizing work. You can take the Tasks assigned to you from a shared Project, add them to a new, individual Project, and re-categorize them in your own way.</p>
<p><a href="http://blog.asana.com/2012/02/the-power-of-tasks-in-multiple-projects/multiple-projects-design/" rel="attachment wp-att-822"><img src="http://blog.asana.com/wp-content/post-images/Multiple-Projects-Design-278x300.png" alt="" width="243" height="262" class="alignnone size-medium wp-image-822" /></a><a href="http://blog.asana.com/2012/02/the-power-of-tasks-in-multiple-projects/multiple-projects-contractors/" rel="attachment wp-att-823"><img src="http://blog.asana.com/wp-content/post-images/Multiple-Projects-Contractors-300x262.png" alt="" width="300" height="262" class="alignnone size-medium wp-image-823" /></a></p>
<p>Do you have other examples of putting tasks into multiple projects?  <a href="http://help.asana.com/customer/portal/questions/188805-what-s-your-favorite-way-to-use-tasks-in-multiple-projects-" target="_blank">Share your best practices</a> with the Asana community!</p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/QIGNWynoBeU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/02/the-power-of-tasks-in-multiple-projects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/02/the-power-of-tasks-in-multiple-projects/</feedburner:origLink></item>
		<item>
		<title>Multiple Email Addresses and Choosing the Default Workspace for Emailed Tasks</title>
		<link>http://feedproxy.google.com/~r/Asana/~3/wwIKs_PVJes/</link>
		<comments>http://blog.asana.com/2012/01/multiple-email-addresses-and-choosing-the-default-workspace-for-emailed-tasks/#comments</comments>
		<pubDate>Fri, 13 Jan 2012 01:14:56 +0000</pubDate>
		<dc:creator>Jackie Bavaro</dc:creator>
				<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://blog.asana.com/?p=814</guid>
		<description><![CDATA[People use Asana to stay organized in all parts of their lives, from work, to fun, to family, and more. While it&#8217;s great to keep all of your tasks in one place, it doesn&#8217;t always make sense to have all of the notifications go to one email address. Many of our customers have asked to [...]]]></description>
			<content:encoded><![CDATA[<p>People use Asana to stay organized in all parts of their lives, from work, to fun, to family, and <a href="http://help.asana.com/customer/portal/articles/270187">more</a>.</p>
<p>While it&#8217;s great to keep all of your tasks in one place, it doesn&#8217;t always make sense to have all of the notifications go to one email address.  Many of our customers have asked to use multiple email addresses with one account.  And if you have more than one workspace, you might want to set one as the default to choose where new tasks go.</p>
<p>Now we&#8217;re introducing two new features to make Asana work great in all of the parts of your life: Multiple email addresses and Choosing the default workspace for emailed tasks.</p>
<p><a href="http://blog.asana.com/2012/01/multiple-email-addresses-and-choosing-the-default-workspace-for-emailed-tasks/menu-2/" rel="attachment wp-att-818"><img src="http://blog.asana.com/wp-content/post-images/menu1.png" alt="" width="158" height="100" class="alignright size-full wp-image-818" /></a>You can access both these features from the Account Settings dialog by clicking on your name in the lower left of Asana.</p>
<p>From the Email Notifications tab you can add new email addresses (verify them by clicking on the email link), and then for each workspace you can choose where notifications get sent, and whether you get the daily summary email.</p>
<p>From the Email Dropbox tab you can choose a default Workspace for each of your email addresses.  When you send an email to x@mail.asana.com , it will put it into your assigned tasks list in the Workspace you chose.</p>
<p>We&#8217;d love to know what you think! Let us know at feedback@asana.com.</p>
<p><a href="http://blog.asana.com/2012/01/multiple-email-addresses-and-choosing-the-default-workspace-for-emailed-tasks/email_notifications/" rel="attachment wp-att-816"><img src="http://blog.asana.com/wp-content/post-images/email_notifications-300x156.png" alt="" width="300" height="156" class="alignnone size-medium wp-image-816" /></a> <a href="http://blog.asana.com/2012/01/multiple-email-addresses-and-choosing-the-default-workspace-for-emailed-tasks/email_dropbox/" rel="attachment wp-att-817"><img src="http://blog.asana.com/wp-content/post-images/email_dropbox-300x150.png" alt="" width="300" height="150" class="alignnone size-medium wp-image-817" /></a></p>
<img src="http://feeds.feedburner.com/~r/Asana/~4/wwIKs_PVJes" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.asana.com/2012/01/multiple-email-addresses-and-choosing-the-default-workspace-for-emailed-tasks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.asana.com/2012/01/multiple-email-addresses-and-choosing-the-default-workspace-for-emailed-tasks/</feedburner:origLink></item>
	</channel>
</rss>

