<?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 Taufan Satrio on Medium]]></title>
        <description><![CDATA[Stories by Taufan Satrio on Medium]]></description>
        <link>https://medium.com/@taufans?source=rss-3714f35f558c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NaS3m4NXvwpPpHXgYkqeEg.jpeg</url>
            <title>Stories by Taufan Satrio on Medium</title>
            <link>https://medium.com/@taufans?source=rss-3714f35f558c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:48:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@taufans/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[Trust, but Verify]]></title>
            <link>https://medium.com/@taufans/trust-but-verify-35716d945de3?source=rss-3714f35f558c------2</link>
            <guid isPermaLink="false">https://medium.com/p/35716d945de3</guid>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[workplace-relations]]></category>
            <dc:creator><![CDATA[Taufan Satrio]]></dc:creator>
            <pubDate>Sun, 31 Oct 2021 00:52:28 GMT</pubDate>
            <atom:updated>2021-10-31T00:52:28.659Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9OqqTl9Smw2kJhSM" /><figcaption>Photo by <a href="https://unsplash.com/@cytonn_photography?utm_source=medium&amp;utm_medium=referral">Cytonn Photography</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Picture this: a coworker tells us that the slides for an upcoming presentation have been reviewed and the deck is ready to go. Later on, we found out that the order of the slides has been changed significantly such that you need to revisit and adjust our delivery.</p><p>Life often exposes us to situations similar to the imaginary example above: we are faced with a choice of whether to trust the information received and move along or double-check before proceeding.</p><h3>Trust</h3><p>Merriam-Webster dictionary defines <a href="https://www.merriam-webster.com/dictionary/trust">trust</a> as ‘assured reliance on the character, ability, strength, or truth of someone or something’. In simpler terms, you believe that someone or something is reliable.</p><p>In the workplace environment, trust is an essential factor. Employees working in high-trust organizations are:</p><ul><li><strong>106%</strong> more energized at work</li><li><strong>76%</strong> more engaged</li><li><strong>50%</strong> more productive</li><li><strong>29%</strong> more satisfied with life</li><li><strong>74%</strong> less stressed</li><li><strong>40%</strong> less burned out</li><li><strong>13%</strong> less absent due to sickness</li></ul><p>The <a href="https://hbr.org/2017/01/the-neuroscience-of-trust">study</a> also finds that high-trust organizations foster better collaboration among their employees, fuel stronger performance, and promote longer employment terms. Those are quite impressive findings, right? So the business case for building trust in the workplace is well established.</p><p>From my personal perspective, trusting co-workers enables us to show up as our whole and truest selves, without concerns about judgement or social repercussions. Trust makes you feel ‘safe’ and helps build genuine relationships within the organization.</p><p>Monthly virtual gatherings/lunches are good examples where often work matters are sidelined and people get to tell stories about themselves, songs they currently put on repeat, TV shows/Animes/K-dramas they’re binge-watching, daily obstacles they’re struggling with, and everything else happening outside work. All of the above contributes to building trust between individuals.</p><h3>But</h3><p>Yes, trust is important. However, the reality is ugly. Sometimes trust alone is insufficient in getting the outcome you want, and it could be due to several aspects</p><ol><li>Different expectations on the quality of deliverables (<strong>what</strong> good/success looks like)</li><li>Approach mismatch (<strong>how</strong> it should be done)</li><li>Misalignment on the timeline (<strong>when </strong>it needs to be done)</li></ol><h4>Different expectations on the quality of deliverables</h4><p>When two people agree on the delivery of something, sometimes they miss the part on what is considered ‘good’. Going back to our coworker example, what we expect, based on our past experiences and personal standards, the deck should be 10 slides max, with content organized from A to Z, supported by charts and graphs. The coworker might consider that a 15 pages presentation that starts with B and finishes with testimonial videos.</p><p>There lies the issue. And trust is not the source, both can trust each other and still have different expectations.</p><p>Potential mitigation: Have a common understanding of what output is expected and what is considered good for both. Is it the usual company Wiki page or a GDocs would suffice? How many words/slides does it need? What sections are required? Are visuals crucial or content is more emphasized?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U0bIcfsR70MWN9b1aPv8kg.png" /><figcaption>Different expectations on the quality of deliverables</figcaption></figure><h4>Approach mismatch</h4><p>It is no mystery that any two people can have different ways of doing things, even though you’ve worked together for quite some time. We prefer to look into the past by sifting through usage data while the coworker tends to trust recent testimonials acquired from user interviews. And it is often difficult to dismiss one over the other.</p><p>Potential mitigation: Sit together and talk about the methods of getting to the deliverable. What data needs to be examined? How far back are we talking about? Who needs to be consulted or inquired? Are we relying on a quantitative or qualitative approach?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UR6Dpgdlfe-obtmIp5yQsA.png" /><figcaption>Approach mismatch</figcaption></figure><h4>Misalignment on the timeline</h4><p>Timing is another essential aspect to be agreed on. And when misalignment occurs, disappointment is almost always bound to happen for both sides. We might expect that the first draft of the slide is shared 3 days before the presentation to allow for feedback and editing. The coworker is currently juggling many tasks at once and aims to finish it just 1 day before, as long the deadline is met.</p><p>Potential mitigation: Again, agree on the timeline beforehand. Do we expect multiple feedback and editing sessions? Are we comfortable going with whatever we have on presentation day? What are the cases when we should reconsider the schedules?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92XnuEyTiqRkvHfrF5I-NA.png" /><figcaption>Misalignment on the timeline</figcaption></figure><h3>Verify</h3><p>We’ve gone through several cases where trust alone is not enough, and when the cases come knocking at our door, we might resort to double-check and confirm to see if everything is up to our expectations.</p><p>However, verifying also comes with a risk: it could diminish the trust that came with it. The coworker might consider us as micro-managing, especially if the what-when-how aspects were not agreed on beforehand. The working relationship could take a hit.</p><p>Apparently ‘trust, but verify’ approach is not a silver bullet. Like many things in life, knowing <strong>when and why to use it </strong>is essential. A good principle I’ve <a href="https://www.psychologytoday.com/us/blog/trust-the-new-workplace-currency/201507/the-problem-trust-verify-approach">read about</a> and tried myself is that when the outcome is essential and matters more than the relationship, use the ‘trust, but verify’ approach.</p><blockquote>When the outcome is essential and matters more than the relationship, use the ‘trust, but verify’ approach</blockquote><p>To add a historical context, according to <a href="https://www.psychologytoday.com/us/blog/trust-the-new-workplace-currency/201507/the-problem-trust-verify-approach">the article</a>, the phrase was popularized by US President Ronald Reagan back in the Cold War era of 1980s. The president was referring to having reliable and transparent information on nuclear possessions, and thus, was a case where the outcome holds more weight than the relationship. Misinformation could potentially lead to catastrophic results. However, not all of us are in similar situations in the workplace.</p><p>Circling back to our coworker (last one, promise) we assess the situation and realize that the upcoming presentation is simply for the purpose of routine sync-up with a stakeholder, so we decided that in this specific case, the working relationship matters more than the outcome, so revisiting and adjusting the delivery might be ok. Trust is intact, but we keep in mind that depending on the situation, it is still our job to verify.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35716d945de3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics: 3 Lessons from My First 3 Months as a Product Manager]]></title>
            <link>https://medium.com/@taufans/back-to-basics-3-lessons-from-my-first-3-months-as-a-product-manager-bc599abd7e53?source=rss-3714f35f558c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc599abd7e53</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Taufan Satrio]]></dc:creator>
            <pubDate>Sat, 29 May 2021 00:00:57 GMT</pubDate>
            <atom:updated>2021-05-29T00:00:57.212Z</atom:updated>
            <content:encoded><![CDATA[<p>When I was doing my Master’s degree, many of the assignments incorporate writing reflective essays. For an author, a <a href="https://www.oxbridgeessays.com/blog/complete-guide-to-writing-a-reflective-essay/">reflective essay</a> aims to 1) recall particular life experiences, 2) explore how the person has changed or learned from those experiences.</p><p>In the Program Essay — which could be considered as the final boss of reflection essays — I wrote: “If I were to pick just one takeaway from the entire program, it would be the importance of reflection and self-criticism”. Obviously, I wrote it not because I was hoping to get a satisfactory mark 😉 but because I’m profoundly excited about the benefits and how I might apply them as a worker.</p><p>Since now I’m back in the workforce and life has been kind enough to reward me with a career as a Product Manager (PM), I consider this piece as an attempt to reflect on the past months (and also as written proof that I did not lie in most of my reflection essays when I wrote ‘would continue to reflect after I graduate’ ). And reflecting on the past 3 months, there are 3 topics I would like to discuss: <strong>communication, time management, and prioritization.</strong></p><h3>Communication</h3><p>This is probably the most fundamental skill for a PM, if not all knowledge workers.</p><ul><li>When you’re moderating or leading a meeting, you’re communicating</li><li>When you’re casually conversing non-work topics in a Zoom/Hangout/Teams room while waiting for that last participant to join, you’re communicating</li><li>When you’re staying silent or suppressing your concerns, you’re communicating</li></ul><p>The scope of communication extends beyond verbal expression to written form. Whether it’s writing product specifications, preparing a presentation deck, or replying to stakeholders on Slack, you’re trying to articulate your thoughts so readers would reach an understanding and be on the same page with you — you’re communicating.</p><p>Considering how frequently it is used on a daily basis, being a good communicator would be beneficial for a PM. However, good communication is easier said (or written) than done.</p><p>Along the way between the sender and the receiver, messages get distorted. Miscommunication happens and can lead to complications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*YDnFMeCPoePL8ST-Pd3JHg.png" /><figcaption>Fetal Miscommunication, by Cyanide and Happiness on <a href="https://imgur.com/gallery/0V3ifEj/comment/43369709">Imgur</a></figcaption></figure><p>These are <strong>a couple of tricks</strong> that I found helpful to minimize communication errors:</p><h4>1. Try to clarify</h4><ul><li>“Ok, so we all agree to do X by date Y, right?”</li><li>“Wait, back up a bit, are we talking about Y already? I think we should focus on X first”</li><li>“Sorry, could you repeat that? What I understand is X, is that correct?”</li></ul><h4>2. When in doubt, over-communicate</h4><p>I always ask ‘what makes a good PM in [company_name]?’ to my interviewers and one of them gave me this tip about over-communicating. It resonated strongly with me and has since become an echo in my head every now and then.</p><p>Over-communicating is about giving frequent updates/ answers on projects, feature updates, release timelines, and general inquires, even if it’s a simple “Not sure about that, let me check and get back to you soon”. It is the preferable option to taking a long time to respond or not replying at all.</p><h3>Time Management</h3><p>In my previous role as an Engineer, I prefer to write code in big chunks of time (minimum of an hour). If the available time is less than 60 mins, I’ll spend it doing anything else but coding because I simply can’t get into ‘the zone/flow state’ in such a short time.</p><p>Now that I’m a PM, 60+ mins of free time in a workday is a luxury I rarely get. This demands alteration on my approach: from only doing work on a long time breaks to <strong>make the most out of the time at hand</strong>.</p><p>Another nontrivial aspect is to <strong>keep my perfectionism in check</strong>. There’s a part of me that wants something done as flawless as possible, even if it requires hours. Now I open more room for leniency: it’s actually ok to not do it perfectly on the first go, as long as you revisit it later and improve it.</p><blockquote>Perfection is the enemy of progress ~Winston Churchill</blockquote><p>Let’s take an example:</p><ul><li>Before: “Only 15 mins before the next meeting, huh? Then I’ll do this product spec later since it will take at least 1.5 hours”</li><li>After: “Ok, so I have 15 mins before the next meeting. I’ll just start scribbling a rough outline for this product spec and continue later after the X meeting ends”</li></ul><h3>Prioritization</h3><p>Most PMs will inevitably be exposed to multiple action items in a single day. In my case, I’m often tempted to finish them all, which equates to doing multiple tasks at one time. However, more research (both in <a href="https://www.apa.org/research/action/multitask">academia</a> and <a href="https://hbr.org/2010/05/how-and-why-to-stop-multitaski">industry</a>) shows that multitasking reduces productivity. The growing number of evidence slowly indicates that humans are not really built for multitasking. At some point, you will need to choose which ones to <strong>do, delegate, delay, and delete.</strong> In other words, pick your battles. This ties back in with my previous point on time management.</p><h3>Allen Holub on Twitter: &quot;For every task you add to the number of things you take on at once, you lose 20% of your productivity (from Jerry Weinberg&#39;s &quot;Systems Thinking&quot; volume of &quot;Quality Software Management&quot;). Do 5 things at once; you&#39;ve lost 80% of your productivity. pic.twitter.com/erQSCXibRz / Twitter&quot;</h3><p>For every task you add to the number of things you take on at once, you lose 20% of your productivity (from Jerry Weinberg&#39;s &quot;Systems Thinking&quot; volume of &quot;Quality Software Management&quot;). Do 5 things at once; you&#39;ve lost 80% of your productivity. pic.twitter.com/erQSCXibRz</p><p>Zooming out from personal time management, prioritization becomes even more important when it comes to tasks that involve multiple individuals. And as the number of people involved gets larger, the more important it becomes. Why? because now it’s not just about how you spend your time <strong>but also how other people spend their time.</strong></p><p>For example, I think Feature A is the next one to be released, so I persuade my team to work on it. I’m essentially asking other people to devote their time to Feature A, and if it is the ‘wrong’ feature, I could potentially waste not only my time but also my team’s. Meanwhile, they also have a list of tasks to work on besides Feature A.</p><p>There are <a href="https://roadmunk.com/guides/product-prioritization-techniques-product-managers/">many prioritization frameworks</a> that PMs could leverage. However, reviewing some of them and help you choose which one to try is out of the scope of this write-up. My priority here is to kindly remind you that prioritization is crucial, especially when it involves other people. So the next time I need to decide the next backlog items to include in the next Sprint, which meetings to attend, or which Slack thread I need to respond to, I have to <strong>stop, think, and assess properly.</strong></p><p>Whether it’s a simple First-In-First-Out (FIFO) rule, Cost-Benefit Analysis, or the <a href="https://productschool.com/blog/product-management-2/prioritization-techniques-product-managers/">more specific prioritization framework for PMs</a>, the choice comes down to personal preference and what works for you. What matters more is to be more mindful of how I plan to spend my time and other people’s as they directly influence the business/company.</p><h3>Jack Butcher on Twitter: &quot;1. Say yes to almost everything.2. Figure out what you&#39;re good at.3. Say no to almost everything. / Twitter&quot;</h3><p>1. Say yes to almost everything.2. Figure out what you&#39;re good at.3. Say no to almost everything.</p><h3>Back to Basics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j8HvB89IgViByTV8" /><figcaption>Photo by <a href="https://unsplash.com/@element5digital?utm_source=medium&amp;utm_medium=referral">Element5 Digital</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Before I got the job, I imagined myself as a PM tackling product-specific tasks daily, such as conducting A/B tests, mapping user journeys, and leading design-thinking or ideation sessions. Now I see that I need to get back to the basics: <strong>communication, time management, and prioritization</strong>.</p><p>They sound less cool and may not be resume material, but I realize that they are core competencies in my daily routine. And that realization comes only after I reflect on the road behind. Now I look forward to continuing my journey, reflect, and (hopefully) learn from past experiences.</p><blockquote>We do not learn from experience…we learn from reflecting on experience ~John Dewey</blockquote><p><em>P.S. I work as a PM @ Lemonilo, an Indonesian startup (</em><a href="https://www.techinasia.com/lemonilo-series-b-funding-sequoia-capital"><em>Series B r</em>ound</a><em>) that produces healthy consumer goods. We are on a mission to make healthy lifestyles accessible to everyone and </em><a href="https://www.linkedin.com/company/lemonilo/jobs/"><em>currently </em><strong><em>hiring</em></strong><em> across many roles</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc599abd7e53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’d like to remember]]></title>
            <link>https://medium.com/@taufans/id-like-to-remember-bf5fdb0b685b?source=rss-3714f35f558c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf5fdb0b685b</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[thoughts]]></category>
            <dc:creator><![CDATA[Taufan Satrio]]></dc:creator>
            <pubDate>Wed, 08 Feb 2017 17:05:22 GMT</pubDate>
            <atom:updated>2017-02-08T17:05:22.233Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I received a wonderful reminder, it goes like this</p><blockquote>When TV came to my house, I forgot how to read books <br>When the car came to my doorstep, I forgot how to walk<br>When I got the mobile in my hand, I forgot how to write letters<br>When computer came to my house, I forgot spellings <br>When the AC came to my house, I stopped going under the tree for cool breeze<br>When I stayed in the city, I forgot the smell of mud<br>By dealing with banks and cards, I forgot the value of money<br>With the smell of perfume, I forgot the fragrance of fresh flowers <br>With the coming of fast food, I forgot to cook traditional cuisines<br>Always running around, I forgot how to stop<br>And lastly when I got Whatsapp, I forgot how to talk</blockquote><p>Tried searching the original author to no avail. To whomever he/she is, thank you for reminding me.</p><p>I’d like to remember how easy it is to get caught up with life and to take seemingly trivial things for granted.<br>I’d like to remember that life consists of not just paramount phenomenons but also minutia.<br>I’d like to remember that time waits for no one.<br>I’d like to remember that <a href="https://medium.com/@jonwestenberg/destinations-7285416ea7ed#.5xoguwmrv">we’re all going to end up the same way, and the only thing that makes us different is the way we spend our moments</a>.</p><p><em>P.S Ironically, I received the reminder from a Whatsapp chat :p</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf5fdb0b685b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Problem Solvers to Trouble Makers]]></title>
            <link>https://medium.com/@taufans/from-problem-solvers-to-trouble-makers-7977fa8ca7aa?source=rss-3714f35f558c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7977fa8ca7aa</guid>
            <category><![CDATA[thoughts]]></category>
            <category><![CDATA[opinion]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Taufan Satrio]]></dc:creator>
            <pubDate>Fri, 25 Mar 2016 17:09:25 GMT</pubDate>
            <atom:updated>2016-03-25T17:09:25.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqNMNL4yJqQPE_ex70CZzw.jpeg" /></figure><p>Countless times I have told myself that I am a problem solver. And other people also tend to expect that I am capable of solving problems and — perhaps—ignite changes. “Agent of change” so they say. Usually I just chuckled and tried my best to live up to such expectation. But along the way, as I looked back and sideways (figuratively of course), I noticed something: an irony if I may. And maybe you’ve seen it too.</p><p>Oddly enough, every now and then I found myself at the other end of the spectrum. I forgot to wash the dishes, too lazy to take out the trash, and too busy to help with house chores. I’ve seen it happen to others too. We create inventions, craft tools, build startups, and join organizations to solve everyday problems but sometimes we’re blinded by that goal.</p><p>Suddenly house chores is not our responsibility, hanging out with family is a waste of time, feeding pets can be done later, too exhausted to give our seat to the elderly on our way home from work, and we litter irresponsibly because someone else whom I paid will take care of it. <strong>We transformed from problem solvers to trouble makers. </strong>What’s worse is when those seemingly small matters accumulate into larger issue without us realizing.</p><p>Don’t get me wrong, solving a real life problem IS a noble cause, but let us not take for granted the mundane things we encounter in our journey there. This is a reminder for myself mostly. And if you agree with me, you can remind yourself and others around you. The world could use more problem solvers and less trouble makers.</p><blockquote>At the end of the day, the easiest way to solve a problem, is to not make one.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7977fa8ca7aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>