<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Arnau Giró on Medium]]></title>
        <description><![CDATA[Stories by Arnau Giró on Medium]]></description>
        <link>https://medium.com/@arnaugiro?source=rss-662d9faaf8d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*G6EBLzl7WYxpzMef3jvMsA.jpeg</url>
            <title>Stories by Arnau Giró on Medium</title>
            <link>https://medium.com/@arnaugiro?source=rss-662d9faaf8d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:08:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arnaugiro/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ Daily ToDos]]></title>
            <link>https://medium.com/@arnaugiro/daily-todos-eb88a5f0385f?source=rss-662d9faaf8d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb88a5f0385f</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[daily-life]]></category>
            <category><![CDATA[to-do-list]]></category>
            <dc:creator><![CDATA[Arnau Giró]]></dc:creator>
            <pubDate>Mon, 29 Jun 2020 15:49:41 GMT</pubDate>
            <atom:updated>2020-06-29T15:49:41.884Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m very process-oriented, and I&#39;m constantly trying to adopt new (and hopefully improved) frameworks for my life, from daily task lists to weekly reminders to yearly resolutions.</p><p>But the life-changer to improving my personal and professional growth was approaching it with a daily perspective. It is a simple everyday self-reminder on achieving your purpose.</p><h4>DAILY TODOS</h4><p><strong>TOP</strong> <em>These are my 5 top daily priorities. It’s rare that I don’t check off all 5.</em></p><ul><li>🏃🏻‍♂️ Work out intensely</li><li>🧘🏻‍♂️ Meditate calmly</li><li>🥗 Eat healthily</li><li>🎓 Learn something</li><li>🛠 Build something</li></ul><p><strong>MORE </strong><em>This is the expanded version of learning and building.</em></p><ul><li>📖 Read an article or book</li><li>🎙 Listen to a podcast</li><li>🎥 Watch a documentary, series, or movie</li><li>💡 Learn product</li><li>🔺 Learn leadership</li><li>🤝 Learn management</li><li>🏦 Learn finance and crypto</li><li>⚙️ Learn to code</li><li>🙇🏻‍♂️ Learn something else</li><li>🎈 Go to an event</li><li>👨🏻‍🎨 Create something</li><li>🕹 Play games</li><li>🧿 Discover something new</li><li>👯‍♀️ Meet some friends</li><li>💃🏻 Have fun!</li></ul><p>It is my current version, but I’m sure I will change it, again and again.</p><p>I love exploring different possibilities of slicing stuff and take a variety of approaches. It is my way to organise my mind and simplify my thoughts.</p><p>After a whole life of iterations, the pattern is always the same. From complexity to simplification, from overprocessing to frameworks.</p><blockquote>Simplification as a framework for life.</blockquote><p>In these COVID-19 times, we have raised awareness in our daily routine, and it is a perfect opportunity to optimise your day if you haven’t done it already.</p><p>If you are another process obsessed, I’d like to hear your tips!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb88a5f0385f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking for the #PerfectRFC]]></title>
            <link>https://medium.com/@arnaugiro/looking-for-the-perfectrfc-23451f99633d?source=rss-662d9faaf8d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/23451f99633d</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[rfc]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Arnau Giró]]></dc:creator>
            <pubDate>Mon, 06 Nov 2017 20:17:14 GMT</pubDate>
            <atom:updated>2017-11-07T07:46:12.271Z</atom:updated>
            <content:encoded><![CDATA[<p>Since I started working in Product profession I have been looking again and again for the Perfect RFC. This is, basically, the document where all the Discovery information is dumped, and is the Delivery executor. Its role is transcendental when developing features.</p><p>The objectives of this document are:</p><ul><li>Reflect Discovery’s work to do a development.</li><li>Estimate correctly when to incorporate a new feature in the Roadmap.</li><li>Coordinate the different teams that participate in the Delivery.</li><li>Ensure the vision defined by Product in the deploy.</li></ul><p>In the text below I explain my personal approach to the standardisation of the RFC, both regarding the content and the process to follow.</p><p><strong>Main sections:</strong></p><ol><li><strong>Objective: </strong>Main objective of the feature. There’s only one.</li><li><strong>KPIs:</strong> Metrics involved and planned objectives.</li><li><strong>Feature + Overview:</strong> User Story of the feature and general description.</li><li><strong>Child Stories:</strong> Technical requirements, defined with the QA team (BDD).</li><li><strong>Design Thinking:</strong> Wireframe + mockup, from the sketch to the final design.</li><li><strong>Userflow:</strong> Visual diagram, which reinforces and clarifies the flows created / affected.</li><li><strong>Discovery:</strong> Shortcut of the Discovery work done, how the competition is applying the feature, testings, analytics and feedback involved.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/793/1*D1UuLrAGECpWFjLJeTW63Q.png" /><figcaption>#PerfectRFC</figcaption></figure><p><strong>Building Process:</strong></p><ol><li>The feature is discovered, and the initial Discovery involved is incorporated. Goal and KPIs are defined with the entire company, especially with the business department.</li><li>The feature is described in general terms (overview). This is useful for (1) the design team, who can create the wireframe and (2) the development team, who can estimate it(with the wireframe). If any of them are not accomplished, the general description does not have enough detail.</li><li>At this point the RFC is a ‘live document’. We have it faced but not closed, it’s time to do some exercises to obtain feedback, opinions, analysis, etc. Both with our users and internally.</li><li>Once bounded to 90%, the user stories are defined together with the QA team, which aims to control all possible contexts within the feature. It helps to verify that we do not forget any casuistry and to guarantee that the development is going as it is defined.</li><li>Final mockup, which can be built in parallel with the technical specifications. <em>Tip: if you use InVision+Confluence, insert the widget to embed the design. This way you avoid the need to keep updating it in several places while designing and you have everything centralised in InVision.</em></li><li>Userflow: Finally, development and user stories are reinforced by drawing a diagram of user flows. Another visual support to help interpret it completely.</li></ol><h4>A common mistake is understanding the RFC only at the specification level. The process applied to the construction is equally important, and without a combination of both the #PerfectRFC does not apply.</h4><p>I hope that it can be useful, PMs.</p><p>Best!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23451f99633d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking for the #PerfectRFC [Spanish]]]></title>
            <link>https://medium.com/@arnaugiro/looking-for-the-perfectrfc-spanish-8918388a1f91?source=rss-662d9faaf8d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8918388a1f91</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[rfc]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Arnau Giró]]></dc:creator>
            <pubDate>Tue, 22 Aug 2017 08:31:20 GMT</pubDate>
            <atom:updated>2017-08-22T08:31:49.612Z</atom:updated>
            <content:encoded><![CDATA[<p>Desde que empecé en el oficio de Producto he intentado una y otra vez dar con el RFC perfecto. En resumidas cuentas es el documento donde se vuelca todo el trabajo de Discovery, y es el ejecutor del Delivery. Su papel para la construcción de features es trascendental.</p><p>Este doc tiene como objetivos principales:</p><ul><li>Reflejar el trabajo de Discovery para un desarrollo.</li><li>Estimar correctamente para incorporar el feature al roadmap.</li><li>Coordinar los distintos equipos que participan el en Delivery.</li><li>Garantizar la visión definida por Producto en el deploy.</li></ul><p>A continuación explico mi acercamiento personal a la estandarización del RFC, tanto referente al contenido a incluir como al proceso a seguir.</p><p><strong>Secciones principales:</strong></p><ol><li><strong>Objetivo: </strong>Objetivo principal que cumple el feature. No hay más que uno.</li><li><strong>KPIs: </strong>Métricas involucradas y objetivos previstos.</li><li><strong>Feature + Overview: </strong>User Story del desarrollo y descripción general.</li><li><strong>Child Stories: </strong>Especificaciones técnicas, trabajadas con el equipo de QA.</li><li><strong>Design Thinking: </strong>Wireframe + mockup, desde el esbozo hasta el diseño final.</li><li><strong>Userflow: </strong>Diagrama visual, que refuerza y clarifica los flujos creados/afectados.</li><li><strong>Discovery: </strong>Shortcut del trabajo de Discovery, como lo está aplicando la competencia, testings, analítica y feedback implicado.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/793/1*D1UuLrAGECpWFjLJeTW63Q.png" /><figcaption>#PerfectRFC</figcaption></figure><p><strong>Proceso para la construcción:</strong></p><ol><li>Se descubre el feature, y se incorpora el Discovery inicial implicado. Se define objetivo y KPIs con toda la compañía, en especial con negocio.</li><li>Se describe el feature en términos generales (overview). Éste sirve para (1) el equipo de diseño pueda crear el wireframe y (2) el equipo de desarrollo pueda estimar (junto al wireframe). Si alguno de los dos no se logra cumplir, la descripción general no tiene el suficiente detalle.</li><li>Llegados a este punto el RFC es un documento muy vivo. Lo tenemos encarado pero no cerrado, tocan ejercicios para obtener feedback, opiniones, análisis, etc. Tanto con nuestros usuarios como internamente.</li><li>Una vez acotado al 90%, se definen junto al equipo de QA las user stories, que tiene como objetivo controlar todos los contextos posibles dentro de un feature. Ayuda tanto a verificar que no se nos olvida ninguna casuística como a garantizar que el desarrollo sale tal cual estaba definido.</li><li>Mockup final, que pueden construirse en paralelo con las especificaciones técnicas. <em>Tip: si utilizáis InVision+Confluence, insertar el widget para ‘embed’ el diseño. Te ahorras tener que ir modificándolo en varios sitios según evoluciona el diseño, así queda todo centralizado en InVision.</em></li><li>Userflow: Finalmente, se refuerza el desarrollo y las user stories dibujando un diagrama de los flujos del usuario. Un soporte más visual para ayudar a interpretarlo completamente.</li></ol><h4>Un error común es entender el RFC únicamente al nivel de las especificaciones. El proceso aplicado para la construcción es igual de importante, y sin una combinación de los dos no aplica el #PerfectRFC.</h4><p>Espero que os pueda ser de ayuda PMs.</p><p>Best!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8918388a1f91" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>