<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>215 on mcjones.ca</title>
		<link>https://mcjones.ca/categories/215/</link>
		<description>Recent content in 215 on mcjones.ca</description>
		<generator>Hugo</generator>
		<language>en-ca</language>
		
			<managingEditor>chealion@chealion.ca (Micheal Jones)</managingEditor>
		
		
			<webMaster>chealion@chealion.ca (Micheal Jones)</webMaster>
		
		
		
			<lastBuildDate>Sat, 06 Jun 2026 21:32:33 +0000</lastBuildDate>
		
			<atom:link href="https://mcjones.ca/categories/215/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Tech Lead Journal - 215 - The Async First Playbook</title>
				<link>https://mcjones.ca/docs/tech-lead-journal---215---the-async-first-playbook/</link>
				<pubDate>Tue, 11 Nov 2025 20:21:51 +0000</pubDate><author>chealion@chealion.ca (Micheal Jones)</author>
				<guid>https://mcjones.ca/docs/tech-lead-journal---215---the-async-first-playbook/</guid>
				<description>&lt;h1 id=&#34;tech-lead-journal---215---the-async-first-playbook&#34;&gt;Tech Lead Journal - 215 - The Async First Playbook&lt;/h1&gt;&#xA;&lt;p&gt;The ability to try and make meetings a last resort. Async requires more reading, so accepting lag is important.&lt;/p&gt;&#xA;&lt;p&gt;Meeting dynamics - what’s the goal and who is it for? Information sharing or a decision? Tight knit or broader audience?&lt;/p&gt;&#xA;&lt;p&gt;Async excels at the sharing and tighter knit/trust combinations and so helps keep meetings for their most utility - where confusion is expected and talking through things is required.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
