<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Process on Andy Gongea — Product Designer</title>
		<link>https://gongea.com/tags/process/</link>
		<description>Recent content in Process on Andy Gongea — Product Designer</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>© {year} Andy Gongea</copyright>
		
		
			<lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://gongea.com/tags/process/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Moving fast with AI without breaking collaboration</title>
				<link>https://gongea.com/blog/velocity-without-risk/</link>
				<pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://gongea.com/blog/velocity-without-risk/</guid>
				<description>&lt;p&gt;A working note, not the finished piece yet: AI tools make an individual faster, but a team&amp;rsquo;s speed depends on people staying in sync with each other, not just with their own tools. This post will look at where that trade-off shows up and how to keep velocity from costing collaboration. Until then, this is a placeholder.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
