<?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 Ana Flávia Garzon on Medium]]></title>
        <description><![CDATA[Stories by Ana Flávia Garzon on Medium]]></description>
        <link>https://medium.com/@anafgarzon?source=rss-30fb5ab3b303------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XaXKlTH03tlwjjABUuVKww.jpeg</url>
            <title>Stories by Ana Flávia Garzon on Medium</title>
            <link>https://medium.com/@anafgarzon?source=rss-30fb5ab3b303------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:05:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anafgarzon/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[How studying marketing can make you a better product manager]]></title>
            <link>https://medium.com/@anafgarzon/how-studying-marketing-can-make-you-a-better-product-manager-eec9f52687df?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/eec9f52687df</guid>
            <category><![CDATA[digital-product]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[product-management-skills]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 22:52:03 GMT</pubDate>
            <atom:updated>2024-01-19T22:52:03.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3NfJTrhNV8gjocLQEzkng.png" /><figcaption>Image generated by DALL-E</figcaption></figure><h3>I have entered the startup universe through digital marketing.</h3><p>As a recently graduated law student, I barely knew what the digital industry was, and while searching for something closer to what I really wanted for a job, I discovered digital marketing as a gateway to the world of startups. I probably chose this path because of a bunch of reasons:</p><ul><li>The nature of digital marketing is fast-paced: Everything is very fast and intense in marketing. I am a learning-centered person, and being in constant change makes me excited to explore and understand all those new contexts.</li><li>It’s generalist: I am graduated in Law and work as a product manager. I started my career producing digital content, and now I manage development and business initiatives. I’ve lived in more than 20 houses, in at least 5 different cities. The whole world is interesting when you have a generalist perspective. That’s why I instantly matched with marketing. Staying up-to-date is crucial in marketing, as it feeds effective strategies.</li><li>It’s metric oriented: I like having a north star to guide my creativity. Having a clear objective puts me in “problem solve” mode and I am much more creative trying to figure something out than just creating freely.</li></ul><p>Studying digital marketing significantly contributed to my success as a product manager and I think it can be both a starting point to someone entering the digital product world and a skill to be improved by those already working as PM.</p><h3>How studying marketing can make you a better product manager</h3><p>Marketing serves as the essential window through which a product is presented to the world. Although marketing theories can be quite specific, the core of marketing is always related to selling a product (or service).</p><p>The most valuable insights from marketing that made me a better product manager:</p><ul><li><strong>Metrics such as AARRR — </strong>Digital marketing provides a wealth of data that can be used to make informed product decisions. This includes customer feedback, engagement metrics, and market analysis. The more famous example are the metrics AARRR: <strong>Acquisition, Activation, Retention, Referral, and Revenue</strong>. It helps improve what you should understand about your customers, their journey, and how you should set actionable goals.</li><li><strong>Customer needs and relationship — </strong>Digital marketing involves a lot of data analysis and market research. By understanding these aspects, a product manager can better comprehend customer needs and preferences, which is crucial for developing products that meet market demands.</li><li><strong>Communication of product value — </strong>A product manager needs to communicate the value of the product to potential customers effectively. Knowledge of digital marketing strategies can help in crafting compelling messaging and positioning the product appropriately in the market. Plus, at some point I saw myself selling the feature I believed was the best for my team to build at that moment and this skill helped a lot!</li></ul><h3>Impacts in my career</h3><blockquote>By understanding the latest trends in digital marketing, a product manager can innovate and keep the product competitive in a rapidly changing digital landscape.</blockquote><p>In my case, coming from a distant context, marketing gave me the whole perspective of how the backstage of a product — even of a company — works.</p><p>Some valuables skills I got from my studies:</p><ul><li><strong>Market Psychology </strong>— With marketing I could understand and leverage consumer emotions, perceptions, and behaviors to effectively market and improve my products.</li><li><strong>Communication with users (and stakeholders!)</strong> — Marketing was an asset to learn how to engage with and understand the target audience to gather feedback and convey product value.</li><li><strong>A comprehensive understanding of how a product is perceived externally </strong>— By understanding external perspectives, including customer perceptions, market trends, and competitive positioning, I felt prepared to make assumptions and take risks at building a feature as a product manager.</li><li><strong>Project operation </strong>— planning content and e-mail marketing calendars gave me the knowledge to orchestrate a delivery and communicate with other teams about the release plan.</li></ul><h3>Case — Features release calendar</h3><h4><strong>Context</strong></h4><p>Me and the team were managing a B2B education platform with significant clients. Our product tribe was composed of 4 different squads, each developing distinct features for the same B2B Education platform, with varied delivery schedules.</p><h4><strong>Challenge</strong></h4><p>Our main concern was to maintain constant and transparent communication with clients about platform updates. It was crucial to avoid overlapping or excessive proximity in the release dates of different features.</p><p>Internally, the Customer Success, Marketing, and Support teams were directly impacted by each feature made available to the client. The squads responsible for other parts of the product also needed to be aware of the publication schedule.</p><h4><strong>Solution</strong></h4><p>We implemented an organized communication system, consisting of a detailed calendar and email templates for each stage of a feature’s release.</p><p>I used the calendar from Notion. Being the main team’s information archive, it would be available to everyone interested and was easy to create and edit.</p><p>To give you a small taste of what the calendar looked like, I created an illustrative template:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0CGwMObXqYO4YJKmLIQNg.png" /></figure><p>The communication plan with clients was divided into three main phases:</p><ol><li><strong>Change Announcement:</strong> The first email informed about future updates to the platform, detailing the features, providing a launch forecast, and a link to an FAQ article for clarification of doubts. It was sent out 15 days before the production launch.</li><li><strong>Launch Email:</strong> On the launch day, we sent an “Go live” email announcing its availability, accompanied by a demonstrative GIF to illustrate the new features or workflows.</li><li><strong>Monthly Wrap-Up:</strong> At the end of the month, we sent a summary of the updates, without going into excessive detail, but assuring clients that we were constantly improving, considering their needs and those of their employees.</li></ol><p>Additionally, internal teams will receive two emails: one informing them about the new features coming up, including all the release dates, and another one right before the launch, either with some calendar changes or just as a reminder about what the customers will receive in the coming days.</p><h4><strong>Execution</strong></h4><p>The project required efficient coordination with the Support team, who needed to be prepared to respond to client queries on the specific dates of the emails. Additionally, it was necessary to align the feature release calendars between the squads and organize trainings to ensure the proper production of GIFs and FAQs.</p><h4><strong>Result</strong></h4><p>This strategic approach to communication not only kept clients well-informed about changes in the platform but also strengthened their perception of our ongoing dedication to improvement and innovation.</p><p>The internal teams benefited from greater clarity and coordination, resulting in less disruptive and more efficient launches.</p><h3>How do I use this knowledge as a PM</h3><p>The skills and insights I gained from digital marketing continue to be an important part of my role as a product manager. The fast-paced, generalist, and metric-oriented nature of marketing has provided me with a versatile toolkit that I apply in various aspects of product management routine.</p><p>I hope this article has introduced something new to you! Share with me how you apply marketing knowledge in your day-to-day life as a product manager 🙂</p><h4>References</h4><ul><li><a href="https://arc.net/l/quote/qeofjufv">What Product Managers Can Learn From Marketers</a></li><li><a href="https://arc.net/l/quote/vwuveykh">Why Product Managers Should Understand The Importance of Market Research?</a></li><li><a href="https://arc.net/l/quote/vzgldibv">Great Products Are Not Just the Product Guy’s Job</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eec9f52687df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Documentation | Part 3 — Rollout]]></title>
            <link>https://medium.com/@anafgarzon/product-documentation-part-3-rollout-aa5986ba90a9?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa5986ba90a9</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[rollout]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Mon, 04 Dec 2023 21:55:15 GMT</pubDate>
            <atom:updated>2023-12-04T22:01:01.640Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Documentation | Part 3 — Rollout</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*loFT4td78rk3XTH20RqsXA.png" /><figcaption>Image generated by DALL-E 3</figcaption></figure><p>Carrying out a product rollout, or a launch, is the most anticipated moment in the development of a feature. It’s about seeing the work of weeks, sometimes more, materializing and finally going live for the users. However, planning and delivering a new product experience is a complex process full of details.</p><h3>What is a Product Rollout Plan?</h3><p>A product rollout plan is a document that captures all the work that must be completed to launch a new product or new features as expected. They are useful for aligning the entire company around what will be delivered, when, and why it matters. In addition, it serves as a way to outline the tactical work that each team will perform to deliver the new customer experience.</p><p>A good practice is to divide all the work into specific activities and list them in a product checklist. A checklist or template makes it easier to organize the necessary activities, which allows for the coordination and monitoring of launch activities, deliveries, and dependencies. A checklist can also be used as an indicator of what is pending for launch and whether each stage is within the expected timeline.</p><p>In my case, the person responsible for this function was the technical leadership of the Squad or Senior Developers leading the technical part.</p><p><em>Note: In my team, the rollout document and the launch document were the same thing.</em></p><h3>What to Include in the Rollout Checklist</h3><p>Not every product rollout plan will need each of the items below, but in my experience, they are key to having a complete view of the rollout.</p><ul><li><strong>Feature Definition:</strong> This involves listing all the prioritization, sizing, and documentation necessary to start development.</li><li><strong>UX/UI Design:</strong> UX research, wireframes, and specifications necessary to start designing experiences and screens.</li><li><strong>Engineering:</strong> Essential and/or pending resources.</li><li><strong>QA and Operations:</strong> Tests to be performed in production.</li></ul><p>Some information that my team and I consolidated in the rollout document:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mn0S5uY711SVvRF6gRsOEw.png" /></figure><p>This is the template we used in my team. There are other excellent and more complete ready-made templates available out there as well. This one from Atlassian, for example, is a good recommendation: <a href="https://www.atlassian.com/software/confluence/templates/product-launch">Atlassian Template</a></p><p><strong>Note that we don’t go into the detail of each action that must be taken</strong> — this is documented in the cards of the sprint tracking board. This document brings a more macro view, where we reflect a complete stage of development, a pending issue, or a necessary action to be carried out for the deployment of the feature or product to happen as planned.</p><h3>Why It’s Valuable for the Product</h3><p>A product rollout plan offers coordination and clarity. Everyone can quickly see exactly the work that needs to be done to prepare successfully for the launch. Besides keeping the team focused, it can also help to see the dependencies between the work of different teams.</p><blockquote>It’s a central point of reference for the Product Manager and the team, focused on continuously checking progress and ensuring that nothing has been forgotten.</blockquote><p>Additionally, knowing that everything is documented is a good way to manage the team’s anxiety. We can rely on this document to remember all the steps even with the pressure of a launch.</p><h3>Experiences</h3><p><strong>Success Case</strong></p><p>We were working on a very sensitive feature for our main B2B clients: the experience of managing students and their teams within the companies’ LMS. To ensure the mitigation of the main risks in this launch, we decided to roll out gradually to different groups of companies, on different dates.</p><p>Marketing and CS teams needed to have a communication map, the product needed to know exactly which group had the feature available, and I, as a PO, should collect all the improvements and bugs that the first group raised to fix in time for the next launches, which would happen to users with more impact on the business.</p><p>The technology leader himself got involved to ensure that all development was functional and correct. Using the updated document as a guide, the moment of the official rollout felt like a rocket launch! The team was aligned and communicating well, everyone knew who was doing what and what was left.</p><p><strong>Challenging Case</strong></p><p>I can’t think of a bad case, my team had minor issues when launching a feature <strong>without</strong> this documentation. After we started having this documentation it helped me to organize the team and I became an advocate for maintaining this process.</p><p><strong>What happened:</strong> In a particular project, more than one squad was working on correlated features — this happened because of the infamous case of too large a scope and a tight deadline for delivery (raise your hand if you’ve been through this). Although the communication between the teams was working well, two developers developed the same thing.</p><p>We discovered this at the time of the daily deploy, after all the work and time the developer dedicated to the job. This catalyzed our initiative to start working with rollout documentation for each new project, detailing the roles responsible for each part of the code.</p><h3>Take aways</h3><p>A product rollout introduces a new offering or update into the market. Successfully doing this involves developing a strategy, defining product features, building, and delivering everything that was planned.</p><p>Here are four essential lessons I learned:</p><ol><li><strong>Create and maintain up-to-date documentation:</strong> Essential for organizing the rollout process, it guides the team, helps manage tasks, and track progress effectively.</li><li><strong>Use the document as a Strategic Planning tool:</strong> Aligning product launch initiatives with marketing strategies and communication with customers ensures a smooth rollout and manages expectations, increasing impact.</li><li><strong>Risk Management:</strong> Documentation is key to addressing risks such as scope creep and tight deadlines, and clear role definitions prevent task overlap and inefficiencies.</li><li><strong>Emotional Management:</strong> A well-structured rollout plan is essential for reducing team anxiety and providing clarity and tranquility during the high-stress period of a product launch.</li></ol><p>I hope this article has taught you something new! Share with me if and how you create this documentation and how your team uses it 🙂</p><h3>References</h3><ul><li><a href="https://www.aha.io/roadmapping/guide/release-management/what-is-a-good-product-launch-checklist">Step-by-step product launch checklist for product managers</a>.</li><li><a href="https://www.atlassian.com/software/confluence/templates/product-launch">Product launch template</a>, Atlassian.</li><li><a href="https://www.notion.so/blog/product-launch-checklist">A product launch checklist to make every rollout a success</a>, Notion.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa5986ba90a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Documentation | Part 2 — RFC]]></title>
            <link>https://medium.com/@anafgarzon/product-documentation-part-2-rfc-868490ae4281?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/868490ae4281</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Fri, 03 Nov 2023 19:01:36 GMT</pubDate>
            <atom:updated>2023-11-03T19:01:36.813Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Documentation | Part 2 — RFC</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T51HMp5KCcO1cNpV6XNlhg.png" /><figcaption>Image generated by DALL-E 3</figcaption></figure><p>Why does a PO discuss technical documentation?</p><p>First, <strong>I don’t believe POs/PMs need to learn programming.</strong> However, by becoming familiar with the Request for Comments (RFC) document, I have broadened my perspective on how the technical aspects relate to my deliveries as a product.</p><blockquote><em>The essence of the product is to communicate and clarify. I realized that the RFC is about gaining perspective on technical feasibility and understanding the details of the development.</em></blockquote><p>That’s why I want to delve into the details of how the RFC impacted my experience as a Product Owner of a technical team.</p><h3>What is an RFC</h3><p>RFC stands for Request for Comments, and its main purpose is to collect contributions from the entire technical team, including from mobile and data. It is a document to assist multidisciplinary development teams in constructing a technical solution.</p><p>Once approved, the RFC serves as a point of reference for the entire team when implementation begins.</p><h3>Importance for product area</h3><p>Just as the Product Requirement Documentation (PRD — article about this documentation here) can be seen as the consolidation of the discovery and the proposed solution to be implemented in the product, the RFC would be its <strong>technical complement</strong>. The PRD fulfills the function of informing the business side, while the RFC is the technical team’s reference for what will be done.</p><p>This document guides POs and developers to adopt a more holistic mindset, including expected milestones and important considerations, ensuring well-founded and well-evaluated decisions.</p><h3>Experiences</h3><p>I learned that together, the RFC and PRD greatly increase the efficiency of the team.</p><p><em>Why it was useful for my context:</em></p><ul><li><strong><em>Prevention of mistakes </em></strong><em>— I learned that the best path for feature/product development is to map out from the beginning the feasibility and risks of the infrastructure and technology that the product already uses. As we were in the midst of a platform migration, the scenario was not just about the technical feasibility of our product but also about what needed to be integrated into the technology of another platform. In addition to giving the developers much more clarity from the start, I could understand closely the backstage of the development.</em></li><li><strong><em>Clarity on details </em></strong><em>— more than once, the RFC brought to light the need to change a route or the behavior of a button because the technical part compromised what the Product Designer and I had envisioned at first. Discovering this before starting development prevented rework and frustration.</em></li><li><strong><em>Anticipation of necessary changes </em></strong><em>— Usually, our new features required some code refactoring or a CRUD</em>, the Tech Lead would define in the RFC how and on what infrastructure this would be done, which directly influenced the sprints (size, weight, and impact of tasks + prioritization); It is important to follow this process in case significant changes need to be made.</li></ul><p><em>(“Create, Read, Update, Delete” is an acronym for ways one can operate on stored data. […] CRUD typically refers to operations performed in a database or datastore, but it can also apply to higher level functions of an application such as soft deletes where data is not actually deleted but marked as deleted via a status”, according to </em><a href="https://developer.mozilla.org/en-US/docs/Glossary/CRUD"><strong><em>mdn web docs</em></strong></a><em>);</em></p><blockquote><em>One of the impacts I felt with the use of RFC was having the description of how to perform a rollback to a previous version of the code if necessary.</em></blockquote><p>Despite all the care with development and testing, it’s common for something to fail and need to be undone quickly to avoid impacting users. Therefore, it is important that everything developed can be reversed and what can be done in different scenarios.</p><p>Having this information in the RFC and knowing that we were covered in case of an emergency, from the beginning of the development, gave security to the team and to me as the manager of that product.</p><h4><strong>Success Case</strong></h4><p>In one particular project, the phase of building the RFC coincided with the vacation of the technical leadership of my team. To avoid delays in development, we took the initiative to have senior frontend and backend developers take on this task.</p><p>We created a document for each part, but there was excellent collaboration between them and the outcome was very positive.</p><p>Because they are close to the code on a daily basis, I felt that the delivery was more pragmatic, less complex, and straightforward. Another positive point was that the developers were very committed to mapping part of the work that they themselves had built.</p><p><strong>Highlights</strong></p><ul><li>Detailed correlation of the database;</li><li>Suggestions for the utilization of existing frontend components;</li><li>Suggestions for refactoring and adapting frontend components;</li></ul><h4><strong>Challenging Case</strong></h4><p>A somewhat more complex experience occurred when the team was without an assigned Tech Lead and the developers did not have seniority in the product.</p><p>We had the support of other developers who worked in other squads, but there was a lack of vision of the infrastructure of the part in which we were operating in the product.</p><p><strong>Highlights</strong></p><ul><li>The RFC was based only on the PRD’s proposal and did not delve into the technical specifics;</li><li>There was no participation from other developers, which resulted in a biased document since the responsible party was only involved in backend (some frontend interactions impacted the creation of a new database);</li></ul><p>The product delivery phase was affected by rework in development, testing, and documentation. Consequently, there were delays, constant scope changes, and team frustration.</p><h3>What I have learned</h3><p>Of course, the idea of creating another document implies the use of precious time from a developer, in addition to the energy that the team will need to invest in studying this material.</p><p>However, this argument can be easily countered if we think about how many times we face misalignments in communication between backend and frontend or realize too late that new problems have arisen due to the use of an inappropriate solution for a technology decision.</p><p>Based on the experiences I’ve had so far as a PO, I find myself fully embracing the culture of creating various product documentations, including the RFC.</p><p>Certainly, we’re discussing different contexts and needs. In my previous experience, at a large company with significant technical complexity, this document was indispensable.</p><p>However, I have spoken with technical leaders from startups who informed me that the speed required for delivering certain features did not allow for the proper use of RFCs.</p><p>Besides the time spent writing the document, there is also the maintenance as things change. Therefore, startups usually do not use them.</p><blockquote><em>I didn’t create any RFCs, of course, but GitHub has various templates that can be followed. I will leave an example that I found here.</em>Nubank has created a public document explaining their use of this documentation, which you can consult <a href="https://building.nubank.com.br/how-decision-making-works-nubank/">here</a>.</blockquote><p>What do you think? Share with me if you create this documentation and how your team uses it 🙂</p><p><strong>References</strong></p><p><a href="https://github.com/vuejs/rfcs#vue-rfcs">Vue RFCs</a>.<br><a href="https://medium.com/@kyberneees/embracing-an-rfc-based-decision-making-culture-at-delivery-hero-5d5ea466acb5">Embracing an RFC-based decision making culture at Delivery Hero.</a><br><a href="https://medium.com/@andrewhowdencom/writing-up-a-request-for-comments-4a6be864bb8a">Writing up a request for comments.</a><br><a href="https://medium.com/@roberttcode/why-you-should-use-rfcs-b88222a5b6c">Why you should use RFCs.</a><br><a href="https://gist.github.com/fauxnik/24e99b44097fda23ef85c413ef80c761">RFC Template.md</a><br><a href="https://developer.mozilla.org/pt-BR/docs/Glossary/CRUD">CRUD</a>, mdn web docs_</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=868490ae4281" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Documentation | Part 1 — PRD]]></title>
            <link>https://medium.com/@anafgarzon/product-documentation-part-1-prd-466e0e2d973e?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/466e0e2d973e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Mon, 23 Oct 2023 14:35:32 GMT</pubDate>
            <atom:updated>2023-10-23T14:52:42.101Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Documentation | Part 1 — PRD</h3><figure><img alt="Foto gerada pelo DALL-E 3" src="https://cdn-images-1.medium.com/max/1024/1*W2xSs8KT6W0DsLLXxvoECg.png" /><figcaption>Image generated by DALL-E 3</figcaption></figure><p><a href="https://www.linkedin.com/pulse/documenta%25C3%25A7%25C3%25A3o-de-produto-parte-1-prd-ana-flavia-garzon">[Article originally published in Portuguese, at this link]</a></p><p>Understand the importance of maintaining documentation and having ownership of how to manage documents at each stage of the process is key to the successful development of features and products.</p><p>However, there are <strong>many</strong> types of documentation to be considered. Addressing each one would be a lengthy task and even uninteresting for my proposal to bring different concepts than those I saw in traditional theories.</p><p>That’s why I chose three formats that were most relevant in practice during my first year as a Product Owner:</p><ul><li>Product Requirements Document (PRD);</li><li>Request for Comments (RFC);</li><li>Implementation Document;</li></ul><p>I’ve divided this topic into three articles, one for each type of document. In this first one, I will delve into the initial material for product development: the requirements of the solution to be implemented.</p><h3>Product Requirement Document</h3><p>A Product Requirements Document, or PRD, “is a document that contains all the requirements for a particular product. It is written to allow people to understand what a product should do,” according to <a href="https://en.wikipedia.org/wiki/Product_requirements_document">Wikipedia</a>.</p><p>When the business department presented the Initiative* that needed to be built, I, as a PO, would conduct the discovery process to determine the best solution and document the key information in the PRD.</p><p><strong><em>I wrote about what an Initiative is in the previous article: </em></strong><a href="https://www.linkedin.com/posts/ana-flavia-garzon_opentowork-productmanagement-opentowork-activity-7119684805184696320-Jxxd?utm_source=share&amp;utm_medium=member_desktop"><strong><em>Backlog Items of a Product article</em></strong></a><strong><em>.</em></strong></p><p>In my context, this document was primarily used to provide clarity for the business area on:</p><ul><li>Purpose and scope, from both technical and business perspectives;</li><li>Product overview and use cases;</li><li>Requirements, including:</li><li>functional requirements (e.g., what the product should do);</li><li>usability requirements and impacts on the user experience;</li><li>technical requirements (e.g., security, network, platform, integration);</li><li>Expected deliverables;</li></ul><p>Before starting the development phase, I presented the main idea to the business department, answered any arising questions, and made scope adjustments based on feedback.</p><p>After validating the solution, this document was also used to provide context to the development team. The first thing we did before starting a new project was the Inception ritual (initial meeting), where I explained the main points of everything included in the PRD. This clarified for the team why we would be working on that feature and what was expected upon delivery.</p><p>The Inception also allowed the product designer to present the prototype and the Tech Lead to discuss the Request for Comments or RFC (<em>I wrote another article about this and other rituals, which I plan to publish here soon</em>). This ritual marked the beginning of the development of that particular feature.</p><p>I insisted on having this moment with the entire team present because I believe in keeping developers fully informed of the overall context, not just handing them isolated tasks to be completed.</p><p>The most significant impact of the PRD was the centralization of information, links, and other documents: the prototype in Figma, the sprint board in Jira, the RFC in GitHub, etc.</p><blockquote><strong><em>This is a practice I strongly recommend: create a single document where everyone can find all the relevant links needed for the development of a feature.</em></strong></blockquote><p><a href="https://artifacts.reforge.com/artifacts?topics=product-specs-and-prds">Reforge, an international school of product management, offers a extensive library with articles and templates for PRDs.</a></p><h3>Experiences</h3><p>Below I’ve listed two cases, one successful and another quite challenging, from the use of PRDs.</p><p><strong>Success Case</strong></p><blockquote><strong><em>Implementing a secure login policy: rules for editing and creating passwords on an education platform.</em></strong></blockquote><p><strong>What it included:</strong></p><ul><li>description of the main problem to be solved;</li><li>business opportunity;</li><li>value for the user;</li><li>success criteria / specific proposal of what would be delivered;</li><li>appetite (set time);</li><li>risks;</li><li>no-gos (what should not be done);</li><li>metrics and ways to measure the solution’s success;</li></ul><p><strong>Why it worked:</strong></p><p>Objective documentation, straight to the point. It wasn’t a lengthy text but rather divided into cards with summaries of each topic. The rules were well specified.</p><p>There were some scope changes due to technical limitations, but all were mapped in the same document. We managed to keep a record of the initial decisions.</p><p><strong>Challenging Case</strong></p><blockquote><strong><em>Reinventing the user management experience: intuitive interface for managing users and teams.</em></strong></blockquote><p><strong>What it included:</strong></p><p>In a nutshell, scope creep. This was the first PRD I ever made, and looking back at the mistakes I made, I even laugh at some of them now. Looking back and identifying the problems is easy, today it’s quite obvious what was wrong, but the past Ana had no way of knowing.</p><p>Now I know because I had this experience that wasn’t a complete failure, but it consumed much more time and energy from the team than I anticipated.</p><p><strong>What happened:</strong></p><p>Being an education platform, users belonged to groups (like classes).</p><p>The delivery proposal of this Initiative was the complete reconstruction of the areas where account administrators could manage, invite, make data changes, alter settings, and perform other actions for both the users utilizing the platform and the teams they were part of.</p><p>We had to overhaul the infrastructure, make new routes and URLs, create new databases, redesign the identity, change steps in the user journey… The expectation was to deliver in three months. It took nine, and there was still much left undone.</p><p><strong>What I learned:</strong></p><p>I now see that the biggest mistake in proposing this solution was precisely not being able to perceive the impacts and risks. The problem was that I, in the product role, lacked the vision of the magnitude that this development would take.</p><p>Despite conducting a discovery, the impact was so vast and varied that the risks and efforts were underestimated. Most of the issues were uncovered during development. And that’s terrible.</p><p>The PRD, the document meant to guide this work, reflected this because it was incomplete. At the same time, it was a lengthy and dense material that didn’t help anyone gain more clarity.</p><p>I tried to cover all the main points of a PRD, treating everything as one single delivery.</p><p>What I would do differently is partition the problem several times until reaching something I could look at and say, “this objective is achievable in X time. This other one is not; I need more time.”</p><p>Had I delved into the details of each part, I probably would have used the same nine months but would have had more frequent deliverables and quicker learnings.</p><h3>Learnings</h3><ul><li>This document can become lengthy and very detailed. Expect that few people will read it and that you’ll often need to repeat the information. <strong>Therefore, create a TL;DR at the beginning</strong> (short for “too long; didn’t read”; it’s a concise summary of the key information);</li><li><strong>Use other documentation to complement your PRD</strong>, but don’t get into the “hows.” For instance, I would include some information about the code infrastructure to be used, detailed by the Tech Lead in the RFC, but wouldn’t delve into what would be transferred to the code;</li><li>Maintain a <strong>history</strong> calendar for reference and tracking development metrics. I used to record the start and end dates of sprints, the date of the project presentation to the team, the date of the final deploy, etc.</li></ul><h4>A word of caution here: it’s important not to make this a calendar of future dates because we know that development doesn’t always follow fixed dates. I suggest keeping the dates from the past, indicating when things actually happened.</h4><ul><li>When the proposal involves developing an entire product or a feature that unfolds into many user journeys, <strong>don’t centralize all the information in just one PRD</strong>.</li></ul><p>Even if all parts integrate into a single value to be built, a lengthy document makes it hard for people to engage and read to the end, and complicates searching for the information they need.</p><p>Consider each action as an individual project and construct a PRD, or a summarized version, for each one.</p><p>I hope this article has introduced you to something new! Share with me if and how you create this documentation and how your team uses it 🙂</p><p>References</p><ul><li>Product Requirements Document, <a href="https://en.wikipedia.org/wiki/Product_requirements_document">Wikipedia</a>.</li><li>Article <a href="https://www.linkedin.com/posts/ana-flavia-garzon_opentowork-productmanagement-opentowork-activity-7119684805184696320-Jxxd?utm_source=share&amp;utm_medium=member_desktop"><strong>Backlog Items of a Product</strong></a><strong>.</strong></li><li><a href="https://productschool.com/blog/skills/product-managers-documentation">Product Managers: This is the Documentation You Need to Obsess Over</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=466e0e2d973e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Backlog Itens]]></title>
            <link>https://medium.com/@anafgarzon/product-backlog-itens-a6c7056a4a21?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6c7056a4a21</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Mon, 16 Oct 2023 13:43:09 GMT</pubDate>
            <atom:updated>2023-10-16T14:07:36.257Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bClVhfQqCdzYH9I541sBIw.png" /></figure><p>[<a href="https://www.linkedin.com/pulse/itens-de-backlog-produto-ana-flavia-garzon">Article originally published in Portuguese, at this link</a>]</p><p>Perhaps this is the most recurring topic in the routine of a Product Manager or Product Owner: the breakdown and organization of Product Backlog Items (PBI).</p><p>Personally, I find this part quite fun. It’s practical and organizes ideas in a structured manner, allowing everyone involved in the development process to see the bigger picture, understanding where we’re headed and what we’re doing.</p><p>If you hadn’t heard the term PBI before, a quick definition would be: it’s an individual task to be worked on during the development of a feature or product. For instance, it could be a development task, a bug fix, an enhancement request, or a modification of something.</p><p>PBIs are typically nested within a hierarchy of Initiatives, Epics, and User Stories, which will also be discussed in this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5maWSfs6IlEV2eZCuuLCUA.png" /><figcaption>Black cards: responsible roles; Green cards: task hierarchy</figcaption></figure><p>While working on the product’s feature planning, I refined my technique to better understand the best dynamics of card division and responsibilities for the team’s preferences. <strong>The process became easier once I realized that each item serves a specific audience</strong>.</p><p>In the end, the broader context becomes clear when we observe all the items, from Initiatives to Tasks.</p><p>Some background details:</p><p>How the team functioned: the squad comprised a Product Owner, developers, QA, Tech Lead, and Product Designer. We operated under the guidance of the Product Manager, who interpreted business needs and assisted in finding the ideal solution to be built. I don’t want to delve too deeply into tools right now, but the team used Jira for organizing the entire product process.</p><p>The company’s phase was one of product maturity and maintenance, adapting to migrate from one platform to another. The new product was gradually gaining traction after the acquisition of a company by the group. This is why the business Initiatives were predefined within a structured Roadmap (if there’s even such a thing, but that’s a discussion for another time).</p><h3>Initiative</h3><p><strong>The business area presented the Initiative to achieve a predefined outcome.</strong></p><p>Initiatives are significant objectives to be achieved over a specified period. They can be created by the board/C-Level or another hierarchical entity.</p><p><em>My experience was receiving this proposal from a Product Committee: individuals familiar with both platforms and the importance of each Initiative for the migration to be done progressively, addressing the most critical priorities for the business.</em></p><p>Examples of Initiatives from the Engagement squad, where I worked as a PO:</p><ul><li>Secure accesses across different devices in 4 weeks;</li><li>An optimized user and team management experience in a quarter;</li><li>The old platform’s experience integrated into the new platform within a quarter;</li><li>Simplified test and question management in 60 days.</li></ul><p>A quarter was the usual duration for most initiatives, varying based on risks, impact, and effort size.</p><p>Why I believe the definition of Initiatives works: documentation has been one of the most beneficial factors for me so far — I’ve written another article on this, which I’ll post soon.</p><p>Initiatives compose a Roadmap in a way that makes the final goal of a deliverable clear and accessible to anyone reading the document. It can be as brief as a sentence. It acts as a valuable communication bridge between the leadership layer and the person leading the creation process.</p><h3>Epics</h3><p>Together with our PM, as a PO, I delved into the problem and conducted research before discovery. This means gathering as much information as possible about the product’s purpose, the direction development should take, and the solutions we could offer to meet business and user needs.</p><p><strong>From this research, Epics emerged, guiding the breakdown into progressively smaller tasks.</strong></p><p>Epics are significant objectives that typically take more than one sprint to complete. They should inform the development team of the success criteria for delivering a set of User Stories. Practically speaking, it’s the top tier in a PO’s work hierarchy, which is broken down into User Stories.</p><p>The Tech Lead and I co-created Epics to incorporate both technical and experiential aspects into the User Stories.</p><p><em>In this case, I added the Tech Lead as a collaborating party in the creation of Epics because: I learned that the best path for a feature or product development is to map the feasibility and risks of the infrastructure and technology that the product already uses from the start.</em></p><p><em>Since we were in a migration between platforms, the scenario was not only about the technical feasibility of our product but also about what needed to be adapted to the technology of another platform. Following this flow in partnership was positive because, in addition to giving the devs much more clarity from the beginning, I could closely understand the backstage of the development.</em></p><p>Some examples of Epics I worked on:</p><p>Within the Initiative “<em>Ensure access security on different devices in 4 weeks</em>”, an Epic could be:</p><ul><li>“Creation and editing of passwords must follow specific security criteria”; Or</li><li>“Disconnect all user sessions when the password is changed.”</li></ul><h3>User Stories</h3><p>From here, I believe we enter into a more common understanding of the divisions of work tasks from the development team, so I will not dwell on the theory, focusing only on the particularities I found in my case.</p><p>User Stories are the responsibility of the PO, and I admit it :took me a while to size them in a way that they were neither too large to stay on the board for a week nor too small to be considered isolated tasks, without direct connection to some other larger one.</p><p>Especially because, in my scenario of a more technical approach, where the focus was on the complexity of development, a User Story should be much more objective than a larger outcome.</p><p><em>In my reality, a User Story could just be a very short interaction flow to perform a specific action within the product. And more than once, in the refinement ritual that I did with the team (I also </em><strong><em>wrote another text about this, to be posted in the future</em></strong><em>), I needed to change a route or a button behavior because the technical part compromised what the Product Designer and I had imagined at first.</em></p><p><em>The immediate goal of the user remained the same, even if achievable by another flow. The difference was that this would be just a single step toward the completeness of what would be the user’s full User Story.</em></p><p><em>Here I also relied on the technical support of the Tech Lead and the Product Designer when there was some particularity of code or user journey. Sometimes I had some purely technical or descriptive User Stories, without product context, but that well directed each stage of development.</em></p><p>Example: if a story was something like “As a user account administrator, I want to implement new password rules to ensure that access on different devices is secure,” I would write it like:</p><p>“[…] I want to access the Password Settings screen through the ‘Settings’ button on the main screen; then activate the application of criteria X and Y, for the accounts I choose; then these will be contemplated with the rules for creating and editing the password by the user.”</p><h3>Subtasks</h3><p>We can consider two aspects: “Bugs or Improvements” and “Tasks”.</p><p>I felt that organizing it this way worked for the team and for me as we left the planning with the User Stories complete and estimated. However, throughout the sprint, small or large things would emerge and disrupt the ideal flow that I, as PO, had projected — which happens quite frequently when working with digital products.</p><p>So my agreement with developers, QA, and even designers was:</p><ol><li>Stories were primarily the responsibility of the PO; they came ready and detailed to the planning;</li><li>Subtasks were the responsibility of the developers, to be broken down, detailed, and adjusted during refinement moments and perhaps in planning;</li><li>The estimate of the weight of each Subtask was the responsibility of the developers. The sum of the weights of the Subtasks was the final estimate of the User Story as a whole;</li><li>after the Subtasks of the User Story are done, it’s better to avoid altering them throughout the sprint;</li><li>design adjustments and corrections/bugs found throughout the sprint were the responsibility</li></ol><ul><li>of the designers, who liked to thoroughly go through the pages to validate if everything followed the prototype’s proposal, which I thought was great;</li><li>of QA, when conducting tests;</li><li>of the PO, when following the development and conducting tests;</li></ul><p>these were created within the Use Story itself, prioritized by the PO, and estimated by the devs at the start of the development.</p><p>Agilists who track the estimates of User Stories might be startled, but I will explain how it worked for me: in Jira, where we worked, the weights of the cards contained within the User Story summed up to give the final weight. It worked well for us to proceed like this, so at the end of the sprint, in the review, I analyzed not only what was planned and delivered but also what had changed in the estimate of the User Story as a whole.</p><p>This was an initial text about product practice. My intention is to release other articles soon, but I’d like to share my <em>backlog</em> of themes with you:</p><ul><li>Rituals;</li><li>Using various frameworks for a single goal;</li><li>Best documentation practices;</li></ul><p>I hope it makes a difference to you, in some way! And if there’s any other topic I might explore here, just let me know!</p><p>References</p><ul><li><a href="https://www.unosquare.com/blog/pbi-product-backlog-item-vs-user-story-when-and-how-to-use-them-in-software-project-management/#:~:text=A">https://www.unosquare.com/blog/pbi-product-backlog-item-vs-user-story-when-and-how-to-use-them-in-software-project-management/#:~:text=A</a></li><li><a href="https://hbr.org/1965/11/exploit-the-product-life-cycle">https://hbr.org/1965/11/exploit-the-product-life-cycle</a></li><li><a href="https://airfocus.com/blog/product-initiatives/#:~:text=Product">https://airfocus.com/blog/product-initiatives/#:~:text=Product</a> initiatives are a set,your business seeks to achieve</li><li><a href="https://www.hotjar.com/product-research/#:~:text=Product">https://www.hotjar.com/product-research/#:~:text=Product</a> research is the process,offer to create customer delight</li><li><a href="https://www.atlassian.com/br/agile/project-management/epics">https://www.atlassian.com/br/agile/project-management/epics</a></li><li><a href="https://www.atlassian.com/br/agile/project-management/user-stories">https://www.atlassian.com/br/agile/project-management/user-stories</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6c7056a4a21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[O poder de acreditar que você pode melhorar]]></title>
            <link>https://medium.com/@anafgarzon/o-poder-de-acreditar-que-voc%C3%AA-pode-melhorar-4468c855ac33?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/4468c855ac33</guid>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Fri, 14 Oct 2022 21:28:32 GMT</pubDate>
            <atom:updated>2022-10-14T21:28:32.454Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/850/0*4vECJxnkUgIvHYV-.jpg" /></figure><p>Recentemente eu assisti o TED da autora do livro Mindset, Carol Dweck: <a href="https://www.youtube.com/watch?v=_X0mgOOSpLU">The power of believing that you can improve</a>.</p><p>E esse TED me trouxe uma reflexão sobre como tudo pode ser aprendizado. Não digo isso sentada em uma cadeira de positividade em que todas as mazelas da vida podem ser olhada sob uma luz polianistica de aprendizado. Essa ideia não precisa ser necessariamente positiva (ainda que os impactos e os efeitos assim o sejam).</p><p>Carol Dweck debate a pressão muito comum de que conhecimento bom é conhecimento espontâneo, o “talento nato”, aquele que vem sem esforço, como quando uma pessoa muito boa em alguma coisa tivesse nascido praquilo.</p><p>Só que não. Aprendizado é uma constante se você se mantém curiosa e aberta para o que ainda não sabe ou para o que ainda não é bom. É divertido ainda não saber tudo! Isso te deixa com uma página em branco cheia de possibilidades sobre o quanto você pode explorar e aprender.</p><p>Mentes curiosas se mantém em aprendizado constante, focadas em aceitar o que <em>ainda não</em> sabem. “Eu posso não saber algo agora, mas eu posso aprender. Eu só ainda não sei.”</p><p>Para essas pessoas, o “só sei que nada sei” é uma vantagem, que permite aprender com qualquer situação.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4468c855ac33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alguns livros para auto conhecimento]]></title>
            <link>https://medium.com/@anafgarzon/alguns-livros-para-auto-conhecimento-1f54d4784753?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f54d4784753</guid>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Wed, 03 Jun 2020 16:10:31 GMT</pubDate>
            <atom:updated>2020-06-03T16:10:31.760Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*0ngpA3llpPrFc_JN.jpg" /><figcaption>Imagem de Deidre Wicks — <a href="https://br.pinterest.com/wuiuu/deidre-wicks/">https://br.pinterest.com/wuiuu/deidre-wicks/</a></figcaption></figure><p>Quem é tu pra recomendar livros para auto conhecimento? Por um acaso você alcançou o ápice do auto conhecimento e dá palestras sobre? Haha Não, bem pelo contrário.</p><p>Acho que tenho a chance de indicar alguns livros sobre auto conhecimento justamente porque tenho passado por essa saga e descobri ombros de gigantes que me abriram caminhos bonitos. E eu acho válido compartilhar pra quem também está na vida pra se aventurar no melhor que puder ser :)</p><ul><li><a href="https://www.amazon.com.br/Efeito-Sombra-Deepak-Chopra/dp/8563066137/ref=asc_df_8563066137/?tag=googleshopp00-20&amp;linkCode=df0&amp;hvadid=379792156976&amp;hvpos=&amp;hvnetw=g&amp;hvrand=11415048910726860167&amp;hvpone=&amp;hvptwo=&amp;hvqmt=&amp;hvdev=c&amp;hvdvcmdl=&amp;hvlocint=&amp;hvlocphy=1001773&amp;hvtargid=pla-829123751929&amp;psc=1">Efeito Sombra — Deepak Chopra</a></li></ul><p>Sabe aquela história de que todos nós temos um lado “bom” e um lado “ruim”? Esse livro nos faz observar e entender o nosso lado sombra, indo fundo em porque nos comportamos de formas que às vezes não condizem com o que queremos ser. Me ajudou a entender uns bons fatos sobre pra onde eu estava indo e se realmente era aquilo que eu queria pra minha vida no momento. E me fez entender que a sombra também é parte de quem eu sou e que isso me faz completa.</p><ul><li><a href="https://www.amazon.com.br/magia-sil%C3%AAncio-descontra%C3%ADdo-tradi%C3%A7%C3%B5es-serenidade/dp/8543106559/ref=sr_1_5?__mk_pt_BR=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;dchild=1&amp;keywords=silencio&amp;qid=1591197382&amp;s=books&amp;sr=1-5">A magia do silêncio — Kankyo Tannier</a></li></ul><figure><img alt="Eu gosto muito dessa foto e tenho um carinho especial por esse livro" src="https://cdn-images-1.medium.com/max/500/0*fpN9rkCbtGE5VGFY" /><figcaption>Eu gosto muito dessa foto e tenho um carinho especial por esse livro.</figcaption></figure><p>Esse livro foi meu companheiro na primeira viagem que fiz completamente sozinha e me ajudou a me colocar no lugar de observadora de mim mesma e a entender o poder que existe em se abrir para escutar o que está acontecendo primeiro com você, pra depois entender o que te cerca.</p><ul><li><a href="https://www.amazon.com.br/Mulheres-que-Correm-com-Lobos/dp/853252978X/ref=sr_1_1?__mk_pt_BR=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=2HRT0NAAQO9E0&amp;dchild=1&amp;keywords=mulheres+que+correm+com+lobos&amp;qid=1591197952&amp;s=books&amp;sprefix=mulheres+que+c%2Cstripbooks%2C285&amp;sr=1-1">Mulheres que correm com os lobos — Clarissa Pinkola Estés</a></li></ul><p>Sinto que ainda rola um certo preconceito sobre esse livro ser apenas para mulheres. Bom, eu não acredito que nada seja apenas para mulheres ou homens, ou apenas para um tipo de pessoa. Esse livro também é exemplo disso, porque toca em pontos sensíveis da <em>existência </em>no geral. É um livro de contos, explicados um a um pela autora (analista junguiana) com o viés de explorar o fato da natureza instintiva das pessoas ter sido domesticada ao longo dos tempos — e de como isso distorce quem de fato somos e o que podemos alcançar.</p><ul><li><a href="https://www.amazon.com.br/coragem-n%C3%A3o-agradar-Ichiro-Kishimi/dp/8543105692/ref=sr_1_1?__mk_pt_BR=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=1PJPD20NWOHN2&amp;dchild=1&amp;keywords=a+coragem+de+n%C3%A3o+agradar&amp;qid=1591198420&amp;s=books&amp;sprefix=a+coragem+de+n%C3%A3o+a%2Cstripbooks%2C277&amp;sr=1-1">A coragem de não agradar — Ichiro Kishimi</a></li></ul><p>A gente se acha muito livre. E na verdade, somos mesmo! Porém ficamos presas em vieses familiares e sociais e tentamos sempre nos apertar em seus moldes. Esse livro me ajudou a entender porque eu achava que só estava fazendo algo certo se recebesse um elogio e estreitou meus laços com o propósito de satisfazer a mim mesma, de acordo com o que eu sei que é bom pra mim (não com o que outras pessoas, por mais bem intencionadas que sejam, palpitassem).</p><ul><li><a href="https://www.amazon.com.br/Linguagem-dos-Sentimentos-David-Viscott/dp/8532301428/ref=sr_1_1?__mk_pt_BR=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=OM334MXXWCA1&amp;dchild=1&amp;keywords=a+linguagem+dos+sentimentos&amp;qid=1591199315&amp;s=books&amp;sprefix=A+linguagem+dos+s%2Cstripbooks%2C290&amp;sr=1-1">A linguagem dos sentimentos — David Viscott</a></li></ul><p>Esse é um pouco “entrar em mata fechada” feelings. Me foi recomendado por uma amiga preocupada em se entender completamente, sem o véu de uma auto percepção distorcida que nos foi ensinada a vida inteira. Porque na verdade a gente acha que sente uma coisa, quando pode ser que seja outra bem diferente. Às vezes a gente acha que está com raiva, mas na verdade está imersa em culpa. Ou sentimos que ficamos ansiosos, mas na verdade estamos com medo. Enfim, a clareza do que realmente se sente é percebida quando entendemos que o que nos foi ensinado a sentir às vezes não reflete muito bem a realidade. E esse livro é um dicionário de sentimentos forte e me ajudou bastante a passar por uns momentos de confusão emocional.</p><p>Selecionei apenas alguns e os listei na ordem que li. Ainda estou (e acredito que para sempre estarei) no caminho do auto conhecimento e isso tem despertado coisas muito boas em mim sobre o que eu quero e o que posso ser. E continuo estudando esse tema sempre, o que significa que gosto muito de recomendações que possam ter impactado outras vidas!</p><p>Sem mais pretensões, espero apenas ter sido uma boa amiga com boas referências :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f54d4784753" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tempos de crise e o que realmente valorizamos]]></title>
            <link>https://medium.com/@anafgarzon/tempos-de-crise-e-o-que-realmente-valorizamos-594d33451c6b?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/594d33451c6b</guid>
            <category><![CDATA[true-value]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Fri, 17 Apr 2020 14:46:40 GMT</pubDate>
            <atom:updated>2020-04-17T14:46:40.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IuGK2mqcfkfQFOQ2.jpg" /><figcaption>Imagem do <a href="https://www.tumblr.com/search/moonxchu">https://www.tumblr.com/search/moonxchu</a></figcaption></figure><p><em>Texto originalmente publicado pela </em><a href="https://fs.blog/2020/03/find-what-you-truly-value/"><em>Farnam Street</em></a><em>, um canal que tem me ensinado um bocado.</em></p><p><em>Nossa devoção aos nossos valores é testada diante de uma verdadeira crise. Mas também é uma oportunidade de se reconectar, se reconfirmar e, às vezes, assar um pouco de pão.</em></p><p>***</p><p>O recente surto de coronavírus está afetando pessoas em todo o mundo — não apenas em termos de saúde física, mas financeira, emocional e até social. Enquanto lutamos para nos adaptar às novas circunstâncias, pode ser tentador enterrar a cabeça e esperar que tudo termine, para que possamos “voltar ao normal”. <strong>Ou podemos ver isso como uma oportunidade incrível para descobrir quem realmente somos.</strong></p><p>O que muitos de nós estamos descobrindo agora é que as coisas que valorizamos há alguns meses não importam: nossos carros, os títulos em nossos cartões de visita, nossos bairros privilegiados. Em vez disso, o que vem à tona é uma mudança para descobrir o que achamos intrinsecamente recompensador.</p><p>Quando tudo é fácil, pode parecer que compreendemos o que é a vida. Quando as coisas mudam e você é chamada para a ação, é bem diferente. Uma coisa é se considerar estóico ao lidar com um café que derrama. Outra completamente diferente é ver toda a sua comunidade entrar em colapso.</p><p>Quando a vida muda e se torna mais difícil, você perce que nunca teve realmente que colocar em prática o que achou que sabia sobre como lidar com desastres.</p><p><strong>Mas quando uma crise chega, tudo é posto à prova.</strong></p><blockquote>O desafio passa a envolver nossas lutas em nossos valores, porque o que valorizamos só tem significado se for importante quando a vida é difícil. Para entender se eles realmente valem à pena, seus valores precisam te ajudar a seguir em frente quando os obstáculos em seu caminho parecem intransponíveis.</blockquote><p>Diante de uma crise, o que é importante para nós se torna evidente quando nos damos espaço para refletir sobre o que vai nos ajudar a passar por tempos difíceis. E só então renovamos o compromisso de voltar às prioridades reais.</p><p><strong>O que antes parecia importante se desfaz para revelar o que realmente importa: família, amor, comunidade, saúde.</strong></p><blockquote>“Eu tinha 32 anos quando comecei a cozinhar; até então, eu só comi.”</blockquote><blockquote>— Julia Child</blockquote><p>Uma atividade inesperada para a qual muitas pessoas estão recorrendo agora que têm tempo e são mais introspectivas é o assado. De fato, nas últimas semana, as pesquisas do Google por receitas de pão atingiram um pico notável.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/0*oFyizWJEZ9cDg2qL.png" /><figcaption>Pesquisas por receita de pão em março de 2020 atingiram um pico.</figcaption></figure><p>O ato de assar é uma experiência muito física: amassar a massa, provar a massa, cheirar os resultados dos ingredientes que se juntam. É uma atividade que requer paciência. O pão tem que crescer. Tortas tem que cozinhar. Os bolos têm que esfriar antes de poderem ser cobertos com glacê. E, por mais que assar pareça superficial, é algo que facilita a criatividade à medida que improvisamos ingredientes com base no que temos no armário. Descobrimos novos sabores e confortamos a nós mesmos e aos outros com os resultados. Os assados ​​geralmente são algo que compartilhamos e, ao fazê-lo, estamos provendo para aqueles com os quais nos preocupamos.</p><p>Por que o assar pode ser útil em tempos de estresse? Em <a href="https://www.amazon.com/gp/product/160882036X/ref=as_li_qf_asin_il_tl?ie=UTF8&amp;tag=farnamstreet-20&amp;creative=9325&amp;linkCode=as2&amp;creativeASIN=160882036X&amp;linkId=86b6cb217615e2fb30b2c66ff3f02785">Superando a ansiedade</a>, Dennis Tirch explica que“pesquisas demonstraram que quando as pessoas se envolvem plenamente em comportamentos que causam uma sensação de prazer e domínio elas começam a superar emoções negativas.”</p><p>Em casa, com seus entes queridos, as pessoas podem reconsiderar o que valorizam como um bolinho de cada vez. Criar com as pessoas que amamos, em vez de apenas comer sozinhos permite-nos focar no que valorizamos à medida que o mundo muda à nossa volta. Tendo mais tempo, atividades lentas e aparentemente improdutivas ganham novo apelo, pois nos ajudam a reorientar as qualidades da vida que mais importam.</p><p>Dar a si mesmo o espaço para sintonizar seus valores não precisa vir do ato de assar coisas.</p><blockquote>O importante é que você encontre uma atividade que te permita superar o medo e o pânico, para se reconectar com o que dá sentido à sua vida. Quando se envolve com uma atividade que lhe dá prazer e libera emoções negativas, você se permite redescobrir o que é importante para você.</blockquote><p>Mudar é estressante. Mas nem o estresse nem a mudança precisam ser assustadores. Se pensar bem, você passa por momentos de mudança todos os dias, porque nada na vida é estático. Nossas vidas são uma constante adaptação a um mundo que está sempre em movimento.</p><p>Toda mudança traz oportunidade. Algumas mudanças nos dão a oportunidade de fazer uma pausa e perguntar o que podemos fazer melhor. Como podemos nos conectar melhor com o que provou ser importante? A conexão não é um exercício intelectual abstrato, mas uma experiência que nos orienta para os valores que nos fornecem direção. Se procurar oportunidades alinhadas com seus valores, poderá ver um caminho através do medo e da incerteza guiados pela luz que é a esperança.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=594d33451c6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A liberdade solitária de se aventurar consigo mesmo]]></title>
            <link>https://medium.com/@anafgarzon/a-liberdade-solit%C3%A1ria-de-se-aventurar-consigo-mesmo-1c9e857750c5?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c9e857750c5</guid>
            <category><![CDATA[traveling-alone]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[solitude]]></category>
            <category><![CDATA[silence]]></category>
            <category><![CDATA[silencio]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Sat, 27 Apr 2019 18:36:15 GMT</pubDate>
            <atom:updated>2019-04-27T18:36:15.357Z</atom:updated>
            <content:encoded><![CDATA[<p>Eu gosto de ficar sozinha. Nunca tive problema em achar um cantinho isolado e me refugiar nos meus livros. Eu gosto de ter o que pensar sem precisar compartilhar nem agradar mais ninguém além de mim mesma. E quando surgiu a oportunidade de fazer uma viagem totalmente sozinha e por minha conta, eu não hesitei e me joguei nessa aventura.</p><p>Passei 5 dias no Peru totalmente solitária (e veja, essa palavra é forte, mas não é negativa). E o que eu aprendi mudou a forma como eu vejo a mim mesma, as minhas relações e o mundo.</p><p>A intenção da viagem era tirar um tempo pra me reencontrar em mim mesma. O tempo inteiro a rotina fala alto alto e não nos deixa esclarecer os pensamentos. O dia a dia é um vórtex. Acordar, pegar o metrô, dar bom dia para as pessoas, fazer o que precisa ser feito, ir para a academia, chegar em casa depois de passar no mercado pra comprar pão e assistir uma série no Netflix. Acredito que essa seja a rotina normal de muita gente por aí. E, mesmo nos intervalos dessas coisas todas — aliás, mesmo estando presentes em nós mesmos durante o dia inteiro — a gente simplesmente não se faz companhia, não reflete profundamente, não se dá tempo de entender tudo o que acontece com a gente.</p><p>Parece que a gente tem companhia o tempo todo, por medo de se ouvir, por medo de ficar sozinho, pela simples comodidade de partilhar tudo o tempo todo.</p><p>Então eu decidi me dar uns dias para sair disso tudo. E não dá pra fazer isso na cidade em que se mora, sabe? Parece que só de estar ali a vida é normal e nada muda.</p><p>Então eu sai. Coloquei a minha mochila nas costas, desliguei o celular e me coloquei numa jornada fora do meu senso comum.</p><p>Como já disse, eu nunca tive problemas em permanecer sozinha, fazer as coisas sozinha, me virar pra explorar lugares desconhecidos por aí. Então, logo quando cheguei, não foi um empecilho sair do hotel e perambular pelas ruas em busca dos pontos turísticos que eu tinha separado para aquele primeiro dia.</p><p>Aliás, é uma aventura estranha poder de fato andar e <em>olhar </em>as coisas, observar sem ter que comentar sobre. Você acaba vendo detalhes que não perceberia na cidade. E outra, é interessante observar a sua própria opinião, sem ser enviesado pelo que outra pessoa acha. Eu vi e entendi muita coisa andando completamente solitária no meio das outras pessoas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iEg3RkGBt5BOK_7h" /><figcaption>Eu tirei uns bons minutos na Plaza de Armas de Cusco para absorver todos os detalhes e entender como me sentia sobre estar ali.</figcaption></figure><p>E é meio libertador você estar livre de julgamentos. Por exemplo, eu me dei a total liberdade de entender que estava tudo bem se eu não tivesse gostado de alguma coisa. “Achei essa igreja feia”, “esse prédio poderia ter sido melhor planejado”, etc. Não sei vocês, mas eu me cobro um pouco para me interessar por tudo e as pessoas acabam alimentando o pensamento de que novidade = coisa boa. Eu reparei isso: que me sentiria meio culpada de manifestar essas coisas se estivesse viajando com alguém super empolgado em estar num lugar novo (como eu estava).</p><p>O meu primeiro desafio foi: refeições à noite. Criada em uma família mineira de cinco pessoas e sempre tendo morado com pessoas muito unidas, a noite era o momento de sentar e contar sobre o dia, contar piada, relaxar entre pessoas de confiança. E, não que eu já não tivesse feito refeições sozinha, mas durante essa viagem eu me tornei muito consciente sobre solitude e rituais.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/0*7xAYdE4VQrmuj05E" /><figcaption>A noite em minha melhor companhia foi uma taça de vinho.</figcaption></figure><p>E admito que foi um pouco esquisito. Eu senti falta de comentar o cardápio e escolher o que comer em conjunto, senti um certo desamparo em ser vista sozinha, me senti independentemente solitária. E eu percebi que o que eu estava fazendo era julgar. Eu estava julgando a minha situação de estar ali e de ser vista ali. Quando meus pensamentos passaram por essa primeira estranheza e quando me dei conta do meu julgamento, consegui relaxar. E o que eu senti ali foi um orgulhinho de “eu estou aqui fazendo isso. Eu escolhi meu prato, eu vou comê-lo no meu tempo e eu vou fazer tudo isso apenas pensando no que eu quiser. Sou independente!” haha é meio bobo de se pensar, mas foi um degrau importante que eu subi naquele momento.</p><p>E sabe, porque a gente não faz isso no dia a dia? Porque nos sentimos tão compelidos a sempre ter alguém do outro lado da mesa de refeições, mesmo que as duas pessoas acabem encarando os celulares durante o jantar? Tá tudo bem comer sozinho! Inclusive, recomendo muito.</p><p>Ainda sobre comidas, a saber: quando você turista por um lugar novo, andando pelas ruas desconhecidas o dia inteiro e sendo estimulada com mil cheiros e indicações do Google, duas coisas são frequentes: fome e dúvida de onde comer.</p><p>Um dia andando pelo centro de Cusco, eu me vi faminta e com dezenas de opções de restaurantes onde comer. Eu queria arrumar logo um lugar pra me sentar e matar a fome, mas, ao mesmo tempo, eu queria uma experiência legal, um restaurante com boas opções vegetarianas, uma vista de uma varanda, um preço justo. E eu demorei quase uma hora, andando no sol e entrando em restaurantes, para me decidir.</p><p>Nesse dia eu me senti feliz por estar sozinha por que pude escolher exatamente o que queria, lidando com a minha própria fome e rebungentisse, sem me sentir culpada por estar atrasando o almoço de outra pessoa. <strong>E percebi que está tudo bem não ter resposta pra tudo. </strong>Não dá pra saber o que se quer o tempo inteiro, é natural do ser humano. E que o seu tempo para a decisão precisa ser respeitado — talvez e principalmente — por você mesmo!</p><p>Estar tanto tempo em companhia de si mesmo te permite um luxo raro: o silêncio.</p><p>A gente está em constante comunicação com pessoas. Seja na demanda do trabalho, em casa ou quando abrimos as redes sociais, sempre tem alguém te falando alguma coisa, sempre tem algo que você externaliza pra puxar assunto. A gente se deixa levar pela presença de outra pessoa e acaba expressando coisas o tempo todo, antes mesmo de processar o que sentimos.</p><p>Eu amo conversar, eu falo muito e gosto de pessoas que falam e, por morar longe de parentes e amigos, é comum ter o celular aberto no WhatsApp o tempo todo (não que essas sejam desculpas né. Eu também fico no celular conversando com pessoas com quem falei há 5 minutos). Meu tempo em silêncio acaba sendo pequeno.</p><p>E mesmo em viagem, é muito muito fácil encontrar companhia. Sempre tem um casal de turistas (especialmente brasileiros) no mesmo hotel que você, sempre tem alguém puxando papo sobre o lugar de onde você veio, sempre tem um garçom engraçado contando casos da vida. As pessoas em viagem assumem um mood gente boa e querem interação.</p><p>Mas eu me propus a quebrar a minha rotina de ser falante e ficar o máximo possível em silêncio enquanto estivesse fora de casa.</p><p>Esse exercício foi facilitado pela experiência de estar em um país cuja língua eu não dominava. Eu evitei falar português em público para não atrair conterrâneos e admiradores de futebol, evitei guias turísticos em locais históricos e até não conversei muito com motoristas de táxi (mesmo eles sendo as melhores fontes históricas de cidades turísticas). E aprendi muito sobre mim mesma fazendo isso.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/0*eswEa3-xseRcFkkE" /><figcaption>A magia do silêncio, de Kankyo Tannier</figcaption></figure><p>Eu estava tão resoluta a aprender mais sobre o meu silêncio que o livro que escolhi para ser minha companhia na viagem foi A magia do silêncio. E um dos ensinamentos que ele me passou foi que ficar em silêncio e trabalhar para não externalizar tudo, principalmente reclamações, faz com que a a mente se acalme e examine situações como elas são de fato, e não como o nosso emocional as projeta.</p><p>Você acaba falando em voz alta um sentimento que nem é tão ruim assim e que acaba se tornando pior porque foi manifestado de certa forma, criando reações expressas de tal e tal maneira. De vez em quando basta apenas analisar o que houve, como se sentiu e o que aconteceu em seguida para internalizar e aprender com as circunstâncias, sem precisar trocar experiências com ninguém.</p><p>É mais fácil quando se está sozinha não se julgar e se cobrar menos. Mas porque fazer isso apenas quando ninguém está te vendo? Todas as coisas que eu me permiti fazer, todos os erros que cometi sendo turista, as risadas que eu dei de mim mesma quando fiz algo idiota e o tempo que eu liberei para estar presente onde estava, apenas aproveitando o momento deveriam — e agora a minha proposta é fazer com que assim seja — acontecer sempre, mesmo quando eu não estou sozinha.</p><p>Sabe, todo mundo erra e faz coisas engraçadas, e se perde e reclama quando está com fome e tá tudo bem! Isso me fez revisitar a ideia de que, na verdade, não importa muito (na verdade, não importa quase nada mesmo)o que as pessoas vão pensar — elas vão te julgar de qualquer maneira.</p><p>Então é melhor ser honesto e leve se libertar das amarras sociais. Sabe? “Emancipate yourselves from mental slavery” e pare de achar que as impressões dos outros devem influenciar o modo como você lida com a vida e consigo mesmo.</p><p>E o exercício de silenciar o barulho externo e ouvir o que você mesmo tem a dizer também deve ser praticado todo dia, em um canto de casa ou mesmo no meio das pessoas que te rodeiam. Se ouça e encontre a voz de quem você é. E se precisar viajar o mundo para começar, vá e apenas deguste a liberdade solitária de se aventurar consigo mesmo :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/0*dESZZy0O1Ull1Ua-" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c9e857750c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Análise | Filme Red Turtle]]></title>
            <link>https://medium.com/@anafgarzon/an%C3%A1lise-filme-red-turtle-d1939cf0695a?source=rss-30fb5ab3b303------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1939cf0695a</guid>
            <category><![CDATA[movie-review]]></category>
            <category><![CDATA[filmes]]></category>
            <category><![CDATA[the-red-turtle]]></category>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[cinema]]></category>
            <dc:creator><![CDATA[Ana Flávia Garzon]]></dc:creator>
            <pubDate>Sat, 13 Apr 2019 18:25:47 GMT</pubDate>
            <atom:updated>2019-04-13T18:25:47.064Z</atom:updated>
            <content:encoded><![CDATA[<p>(sem spoilers)</p><p>Eu sempre gostei de cinema e, recentemente, voltei a escrever o que eu achei de alguns filmes que foram impactantes pra mim de alguma forma.</p><p>Não sou nenhuma crítica nem nada, só gosto do tema e acho que disso podem surgir indicações interessantes pra quem também se interessa :)</p><p>O primeiro filme que vai ter a minha opinião aqui é Red Turtle, dos Studios Ghibli: é uma animação sem diálogos e todas as mensagens são passadas através das imagens incríveis, das cores e das expressões dos personagens.</p><p><a href="https://www.imdb.com/title/tt3666024/">A descrição do IMDB</a>, onde o filme recebeu nota de 7,5, é apenas “A man is shipwrecked on a deserted island and encounters a red turtle, which changes his life.” (Um náufrago vai parar em uma ilha deserta e encontra uma tartaruga vermelha que muda a sua vida).</p><p>Só isso.</p><p>Sabe aquele filme que você vê uma resenha na internet, coloca na wishlist e posterga assistir porque sabe que vai demandar uma maturidade emocional?</p><p>Esse foi o meu caso com o filme Red Turtle. Eu já tinha visto filmes do Studio Ghibli e sabia que o que eles produzem é intenso, bonito e profundo. Então, quando, por acaso, o trailer apareceu pra mim no YouTube, eu imediatamente pensei “mais um filme pra me derreter em lágrimas”. E não deu outra. Assistir esse filme foi uma misturas de sentimentos.</p><p>E muito do que me despertou emoções fortes eu só fui compreender completamente depois, mas mesmo assim é um filme tocante e sensível.</p><p>Se você é como eu que gosta de cores, mensagens subliminares e reflexões, vai amar esse filme também!</p><p>Resumidamente, um homem naufragado encontra uma ilha e luta para sair dali e voltar pra casa, mas é impedido por uma gigantesca tartaruga vermelha. Ele não tem nome e não é dada nenhuma informação ou explicação sobre esse ou sobre os outros personagens que aparecem ao longo do filme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*k5gG8_UQgGzU6nI3" /></figure><p>Visualmente, é <strong>lindo</strong>. É tocante, sem ter nenhum diálogo, é chamativo sem ter efeitos especiais muito elaborados. Usaram cores, às vezes, neutras, às vezes vibrantes, de um forma mágica, que cativa e prende a atenção.</p><p><strong>Minha cena favorita:</strong> logo no começo, o personagem ainda está cheio de sofrimento por estar ilhado em um lugar desconhecido e solitário e anseia desesperadamente por um meio de ir pra casa. Nessa parte, ele sonha diversas vezes com elementos da casa e da civilização da qual sente tanta falta. Pra mim, a cena mais bonita foi um desses sonhos, em que ele caminha pela praia à noite, sob um céu estrelado.</p><p>O que mais me chamou a atenção nessa cena é diferença entre ela e tudo o que tinha aparecido até então. O filme todo é muito colorido, mas esse é um momento sensível, traduzido por imagens em preto e branco. De certa forma, a falta de cor passa a impressão de tristeza, mas também de uma certa paz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9MY__ap548iW3Fcw" /></figure><p>Pra mim, ela representa que, apesar do homem ver beleza onde está, isso não muda a condição em que se encontra: de ser prisioneiro de um lugar que não é o seu.</p><p>A história do filme muda quando um segundo personagem aparece: uma tartaruga vermelha.</p><p>A tartaruga aparece logo nas primeiras cenas, quando o homem tenta sair da ilha. Ele constrói uma jangada que é misteriosamente destruída assim que ele sai das águas rasas da praia.</p><p>Depois descobrimos que é a tartaruga que destrói a jangada.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*soO4RdmAIJT636ZS" /></figure><p>Também não recebemos nenhuma explicação sobre o que ela representa, de onde veio ou qual é o seu interesse no personagem principal, mas a sua presença é tão forte que o entendimento disso tudo deixa de ser o centro das atenções no resto do filme.</p><p>Ela está ali e é a única companhia real naquele lugar inabitado. Engraçado perceber que outros animais já haviam aparecido para o homem, mas nenhum captou sua atenção nem estabeleceu conexões com ele.</p><p>A tartaruga, por ser a única que consegue atenção, acaba transformando o náufrago e faz com que a sua relação com a ilha mude. Ele passa a aceitar o que parecer ser o seu destino (ficar ali) e faz da ilha o seu novo lar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*cbahQnrY0Y8sDemJ" /></figure><p>Lembrando que tudo isso acontece sem nenhum diálogo. A tartaruga não fala. O homem também não. As coisas só vão acontecendo no filme, o que pode causar um estranhamento no começo.</p><p>O que a tartaruga representa pode ser interpretado no desenrolar da história, mas a mensagem não é muito explícita. Em nenhum momento o filme explica de fato o que quis dizer, então é ainda mais interessante ter essa abertura para várias interpretações. Isso me fez pensar em muitas teorias e me deixou curiosa o tempo inteiro.</p><p><a href="https://www.youtube.com/watch?v=ZuolRGvQnW8">Esse vídeo tem uma interpretação sobre mensagem os produtores quiseram passar</a>. Contém spoilers!</p><p>Contudo, eu sugeriria assistir o filme primeiro, sem se enviesar, e ir de mente aberta para ver quais sentimentos e reflexões as cenas te trazem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*qDibORhaUK_PSPPM" /></figure><p>Enfim, esse filme me fez pensar, me fez chorar, me despertou uma sensibilidade difícil de encontrar nos filmes atuais.</p><p>As imagens e as músicas me emocionaram, acredito que pela beleza, mas também pelo inconsciente entendimento de que aquele é tema real e muito presente no mundo de hoje.</p><p>Tenho a impressão cada vez mais frequente que os filmes precisam ser muito explícitos, que os diálogos precisam chegar num nível quase idiota de detalhamento para que as pessoas entendam o que se quis dizer. Isso tira um pouco da magia e castra a nossa habilidade de interpretar.</p><p>E o cinema é uma forma de expressão que não precisa ser assim. Imagens, músicas, personagens bem desenvolvidos e sua interação com o espectador bastam para passar uma mensagem e esse filme explora esses elementos de uma forma quase poética.</p><p>O que achou dessa resenha? Se não viu o filme, ficou curioso ou curiosa pra assistir? E, se já viu, vamos conversar sobre! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1939cf0695a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>