<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aphantasia on marwa.gorvan.com</title><link>https://marwa.gorvan.com/tags/aphantasia/</link><description>Recent content in Aphantasia on marwa.gorvan.com</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Tue, 22 Sep 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://marwa.gorvan.com/tags/aphantasia/index.xml" rel="self" type="application/rss+xml"/><item><title>I don’t see it: Designing with aphantasia</title><link>https://marwa.gorvan.com/writing/designing-with-aphantasia/</link><pubDate>Tue, 22 Sep 2026 12:00:00 +0000</pubDate><guid>https://marwa.gorvan.com/writing/designing-with-aphantasia/</guid><description>&lt;p>&lt;em>In June 2026 I had the chance to present at the &lt;a href="https://pixelpioneers.co/events/bristol-2026">Pixel Pioneers&lt;/a> event. Here is the corresponding blog post.&lt;/em>&lt;/p>
&lt;p>Being a designer often comes with the assumption that we can clearly picture the outcome before it exists. We may be expected to have a vision, imagine the outcome, and “see” the solution early on.&lt;/p>
&lt;p>But what if you can’t? Not all designers work that way, and in this post, I’ll explore ways to design without relying on mental imagery or a fully formed vision. Drawing from my experience with aphantasia and enterprise B2B design work, I’ll show how replacing imagined outcomes with structure, language, and shared artefacts leads to clearer decisions, better collaboration, and understanding.&lt;/p></description></item></channel></rss>