<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	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/"
	>

<channel>
	<title>Design Process &#8211; Fountn</title>
	<atom:link href="https://fountn.design/resource-tags/design-process/feed/" rel="self" type="application/rss+xml" />
	<link>https://fountn.design</link>
	<description>Curated design resources. No clutter. Just flow.</description>
	<lastBuildDate>Sat, 20 Dec 2025 22:25:52 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>

<image>
	<url>https://fountn.design/wp-content/uploads/2024/03/cropped-Default-150x150.png</url>
	<title>Design Process &#8211; Fountn</title>
	<link>https://fountn.design</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>7 Key Questions for Effective Design &#124; Filippos Protogeridis</title>
		<link>https://fountn.design/resource/7-key-questions-for-effective-design-filippos-protogeridis/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Sat, 20 Dec 2025 22:25:51 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=16789</guid>

					<description><![CDATA[A simple yet powerful framework built around 7 fundamental questions that form the foundation of effective design work: Why are we doing this? Who are we doing this for? What evidence do we have? How do we measure success? Are there any significant risks? Are there technical restrictions? And who needs to be involved? These [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Hacking Your Product Requirement Documents to Encourage Better Design</title>
		<link>https://fountn.design/resource/hacking-your-product-requirement-documents-to-encourage-better-design/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Fri, 16 May 2025 06:09:47 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=13086</guid>

					<description><![CDATA[Andy Budd’s Medium article “Hacking Your Product Requirement Documents to Encourage Better Design” explores how traditional PRDs (Product Requirement Documents) can inadvertently stifle creativity and lead to suboptimal design decisions. The author argues that conventional PRDs tend to focus on rigid outputs and granular feature lists, often resulting in design solutions that merely fulfill checkboxes [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Fighill &#8211; Not just a to-do list &#8211; a clear view of where you stand</title>
		<link>https://fountn.design/resource/fighill-not-just-a-to-do-list-a-clear-view-of-where-you-stand/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Thu, 01 May 2025 06:54:08 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=11835</guid>

					<description><![CDATA[Fighill is a Figma widget that adapts the concept of Basecamp’s Hill Charts for visualizing project progress within the design workflow. Rather than relying solely on to-do lists or status checkboxes, Fighill introduces a more nuanced way to reflect where your tasks stand—whether you’re still “Figuring Things Out” or confidently “Making It Happen.” It’s designed [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Design Specifications Template</title>
		<link>https://fountn.design/resource/design-specifications-template-2/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Sat, 26 Apr 2025 07:36:07 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=11221</guid>

					<description><![CDATA[The article “Design Specifications Template” by Maria Meireles, published on UX Collective, discusses the development and implementation of a standardized design documentation template aimed at enhancing communication between designers, engineers, and product managers. The initiative arose from challenges such as inconsistent documentation practices, fragmented communication, and the difficulty of maintaining continuity during team member absences. [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Copy Docs: Make Your Microcopy Full And Consistent, And Maintain It</title>
		<link>https://fountn.design/resource/copy-docs-make-your-microcopy-full-and-consistent-and-maintain-it/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Thu, 20 Feb 2025 09:54:16 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=8313</guid>

					<description><![CDATA[Valeriia Panina explores how copy docs can help designers and writers manage in-product text more effectively. She describes a copy doc as a central document where all interface text is stored, updated, and detailed, making it easier to track changes and ensure consistency. She explains the benefits of using copy docs, emphasizing their role in [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>How to improve your design process with copy docs</title>
		<link>https://fountn.design/resource/how-to-improve-your-design-process-with-copy-docs/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Wed, 19 Feb 2025 09:24:05 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=8276</guid>

					<description><![CDATA[Andrea Drugay discusses the use of copy documents to enhance collaboration between designers and writers. A copy doc is a shared document that combines design elements and written content, allowing teams to work together more effectively. Drugay suggests creating a template for copy docs to standardize the process and improve efficiency. Andrea emphasizes the importance [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Why do they ignore my awesome design documentation?</title>
		<link>https://fountn.design/resource/why-do-they-ignore-my-awesome-design-documentation/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Thu, 13 Feb 2025 10:47:29 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=8142</guid>

					<description><![CDATA[Slava Shestopalov examines why design documentation is often ignored and how designers can make it more effective. The article highlights common pitfalls, such as static, too-detailed, or disconnected documentation from real workflows. Shestopalov emphasizes the need for regular updates, clear structure, and making documentation more accessible and relevant to users. He also discusses how fostering [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Flows – User onboarding for modern SaaS</title>
		<link>https://fountn.design/resource/flows-user-onboarding-for-modern-saas/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Wed, 15 Jan 2025 10:48:58 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=7474</guid>

					<description><![CDATA[Flows is a platform for creating and sharing workflows through simple, visually engaging flowcharts. It offers users an intuitive interface to map out processes, decision trees, and project plans without requiring technical expertise. The platform focuses on accessibility and collaborative use, allowing teams to streamline communication and improve project clarity. Key features include a drag-and-drop [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Measuring Design: Essential Metrics</title>
		<link>https://fountn.design/resource/measuring-design-essential-metrics/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Sun, 12 Jan 2025 10:22:35 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=7377</guid>

					<description><![CDATA[Nick Babich&#8217;s article highlights how product teams can use metrics to evaluate design success and align with business goals. He categorizes these into two types: Outcome Metrics, which measure user and business impact through indicators like task success and customer retention, and Organizational Metrics, which assess design research influence, such as research-informed decisions and stakeholder [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>How to measure and present design input so that the business understands</title>
		<link>https://fountn.design/resource/how-to-measure-and-present-design-input-so-that-the-business-understands/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Sat, 11 Jan 2025 10:07:16 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=7355</guid>

					<description><![CDATA[Rita Kind-Envy, writing for UX Collective, draws parallels between the fantasy world of Game of Thrones and the practical challenges of design communication in her article titled &#8220;Show Me Your Dragons: How to Measure and Present Design Input So That the Business Understands.&#8221; Through the creative use of dragons as metaphors, she explores strategies for [&#8230;]]]></description>
		
		
		
			</item>
	</channel>
</rss>
