<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Workflow Weekly</title>
		<link>https://workflowweekly.com/</link>
		<description>Recent content on Workflow Weekly</description>
		<language>en-gb</language>
		
		
		
		
			<lastBuildDate>Fri, 06 Nov 2026 16:25:00 +0000</lastBuildDate>
		
			<atom:link href="https://workflowweekly.com/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Async communication for remote work: rules that stick</title>
				<link>https://workflowweekly.com/async-communication-remote-work/</link>
				<pubDate>Fri, 06 Nov 2026 16:25:00 +0000</pubDate>
				<guid>https://workflowweekly.com/async-communication-remote-work/</guid>
				<description>Async communication rules for remote teams: response-time tiers, how to write a message that needs no follow-up, when to go live, and a rule list to paste.</description>
			</item>
			<item>
				<title>Remote work policy template you can edit in an afternoon</title>
				<link>https://workflowweekly.com/remote-work-policy-template/</link>
				<pubDate>Fri, 06 Nov 2026 15:10:00 +0000</pubDate>
				<guid>https://workflowweekly.com/remote-work-policy-template/</guid>
				<description>An editable remote work policy template covering eligibility, hours, equipment, expenses, security and working abroad, with plain notes on each clause.</description>
			</item>
			<item>
				<title>How to manage remote employees: a practical operating manual</title>
				<link>https://workflowweekly.com/how-to-manage-remote-employees/</link>
				<pubDate>Fri, 06 Nov 2026 14:22:00 +0000</pubDate>
				<guid>https://workflowweekly.com/how-to-manage-remote-employees/</guid>
				<description>How to manage remote employees week to week: written expectations, a meeting rhythm, 1:1s, output-based reviews, early warning signs and a copyable manual.</description>
			</item>
			<item>
				<title>Async communication tools for remote teams, sorted by job</title>
				<link>https://workflowweekly.com/async-communication-tools/</link>
				<pubDate>Fri, 06 Nov 2026 13:34:00 +0000</pubDate>
				<guid>https://workflowweekly.com/async-communication-tools/</guid>
				<description>Async communication tools grouped by job: video updates, team chat, docs and wikis, and a project hub. Free-plan limits and prices from each vendor&amp;rsquo;s own page.</description>
			</item>
			<item>
				<title>Remote employee onboarding checklist: the parts an office does for you</title>
				<link>https://workflowweekly.com/remote-employee-onboarding-checklist/</link>
				<pubDate>Fri, 06 Nov 2026 13:05:00 +0000</pubDate>
				<guid>https://workflowweekly.com/remote-employee-onboarding-checklist/</guid>
				<description>A remote employee onboarding checklist for managers: kit shipping, accounts, right-to-work checks, a written first week and a 30-day review, ready to copy.</description>
			</item>
			<item>
				<title>About Workflow Weekly</title>
				<link>https://workflowweekly.com/about/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://workflowweekly.com/about/</guid>
				<description>&lt;p&gt;You manage people you mostly see as small rectangles. Workflow Weekly is for you.&lt;/p&gt;&#xA;&lt;p&gt;We publish practical notes on running distributed teams: how to write things down so fewer meetings are needed, how to onboard someone you have never met in person, which policies are worth having and how to set up a desk you can sit at for eight hours without regretting it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Advertise with Workflow Weekly</title>
				<link>https://workflowweekly.com/write-for-us/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://workflowweekly.com/write-for-us/</guid>
				<description>&lt;p&gt;If your product makes distributed work less painful, our readers are the people deciding whether to buy it. Sponsored posts on request. Email &lt;a href=&#34;mailto:editorial@workflowweekly.com&#34;&gt;editorial@workflowweekly.com&lt;/a&gt; with your topic and target URL.&lt;/p&gt;&#xA;&lt;h2 id=&#34;prices&#34; class=&#34;relative group&#34;&gt;Prices &lt;/h2&gt;&lt;table&gt;&#xA;&#x9;&lt;thead&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;th&gt;Placement&lt;/th&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;th&gt;Price&lt;/th&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&lt;/thead&gt;&#xA;&#x9;&lt;tbody&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;Sponsored piece&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;on request&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;Link insertion&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;on request&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;Partner listing in a round-up&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;on request&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;Three sponsored pieces&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;on request&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;h2 id=&#34;good-fits&#34; class=&#34;relative group&#34;&gt;Good fits &lt;/h2&gt;&lt;p&gt;Collaboration, video, scheduling and async tools; HR, engagement and onboarding software; desks, chairs, webcams and headsets; virtual team-building companies; and training for remote managers.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Contact</title>
				<link>https://workflowweekly.com/contact/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://workflowweekly.com/contact/</guid>
				<description>&lt;p&gt;The address is &lt;strong&gt;&lt;a href=&#34;mailto:editorial@workflowweekly.com&#34;&gt;editorial@workflowweekly.com&lt;/a&gt;&lt;/strong&gt;, and yes, we do read it asynchronously.&lt;/p&gt;&#xA;&lt;p&gt;Things we like receiving:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A correction, with a link to the page and to the source.&lt;/li&gt;&#xA;&lt;li&gt;A remote-work problem you&amp;rsquo;d like us to tackle. The odder the better.&lt;/li&gt;&#xA;&lt;li&gt;A template request. If you need a policy, a checklist or a meeting format, tell us.&lt;/li&gt;&#xA;&lt;li&gt;Advertising enquiries, once you&amp;rsquo;ve read the &lt;a href=&#34;https://workflowweekly.com/write-for-us/&#34;&gt;advertise page&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;We can&amp;rsquo;t give HR or legal advice on a specific situation. For employment law questions in the UK, Acas offers free, impartial advice.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How We Work</title>
				<link>https://workflowweekly.com/editorial-policy/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://workflowweekly.com/editorial-policy/</guid>
				<description>&lt;h2 id=&#34;facts-and-sources&#34; class=&#34;relative group&#34;&gt;Facts and sources &lt;/h2&gt;&lt;p&gt;Product details come from the vendor&amp;rsquo;s own pricing and feature pages, dated when we checked them. Research findings link to the study, not a summary of a summary. Employment rules link to the government body that sets them, such as GOV.UK or Acas. Where something can&amp;rsquo;t be confirmed, we say so.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Message not sent</title>
				<link>https://workflowweekly.com/form-error/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://workflowweekly.com/form-error/</guid>
				<description>&lt;p&gt;We couldn&amp;rsquo;t send your message. Please email us instead.&lt;/p&gt;&#xA;&lt;p&gt;You can write to &lt;a href=&#34;mailto:editorial@workflowweekly.com&#34;&gt;editorial@workflowweekly.com&lt;/a&gt; or &lt;a href=&#34;https://workflowweekly.com/contact/&#34;&gt;go back to the contact page&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Message sent</title>
				<link>https://workflowweekly.com/thanks/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://workflowweekly.com/thanks/</guid>
				<description>&lt;p&gt;Sent. We&amp;rsquo;ll get back to you at the address you gave.&lt;/p&gt;&#xA;&lt;p&gt;&#xA;      &#xA;    &lt;a href=&#34;https://workflowweekly.com/&#34;&gt;Back to the front page&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Privacy Notice</title>
				<link>https://workflowweekly.com/privacy/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://workflowweekly.com/privacy/</guid>
				<description>&lt;p&gt;Last updated: 4 November 2026.&lt;/p&gt;&#xA;&lt;p&gt;The short version: we collect very little, and we don&amp;rsquo;t sell any of it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-we-collect&#34; class=&#34;relative group&#34;&gt;What we collect &lt;/h2&gt;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Nothing through the site itself.&lt;/strong&gt; There are no accounts, no forms, no analytics scripts, no advertising trackers and no cookies set by this site.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Server logs.&lt;/strong&gt; Our hosting provider processes standard request data, such as IP address, browser type and the page requested, to deliver the site and protect it from abuse.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Emails you send us.&lt;/strong&gt; If you write to &lt;a href=&#34;mailto:editorial@workflowweekly.com&#34;&gt;editorial@workflowweekly.com&lt;/a&gt;, we keep your message and address so we can reply and deal with anything that follows, such as an advertising agreement.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;what-we-dont-do&#34; class=&#34;relative group&#34;&gt;What we don&amp;rsquo;t do &lt;/h2&gt;&lt;p&gt;We don&amp;rsquo;t sell or rent personal data, and we don&amp;rsquo;t use it for profiling.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
