<?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 Rully Indra Laelaningrum on Medium]]></title>
        <description><![CDATA[Stories by Rully Indra Laelaningrum on Medium]]></description>
        <link>https://medium.com/@ullyindr?source=rss-76626a7360e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hmBi5lt8uVMywvVNEz_GUg.png</url>
            <title>Stories by Rully Indra Laelaningrum on Medium</title>
            <link>https://medium.com/@ullyindr?source=rss-76626a7360e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:47:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ullyindr/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[What I Learned from Leadership Training by Dale Carnegie]]></title>
            <link>https://ullyindr.medium.com/what-i-learned-from-leadership-training-by-dale-carnegie-73c482318cd8?source=rss-76626a7360e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/73c482318cd8</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[dale-carnegie]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Rully Indra Laelaningrum]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 04:16:19 GMT</pubDate>
            <atom:updated>2025-09-30T04:16:19.154Z</atom:updated>
            <content:encoded><![CDATA[<p>Last June, I joined a three-day workshop based on Dale Carnegie’s <em>Leadership Training</em>. Short in duration, yes, but packed with lessons that stayed with me.</p><p>Leadership, I realized, isn’t something you master in a weekend (or even in a lifetime). It’s not a single skill you can check off, but a continuous practice: a mix of habits, perspectives, and small daily choices.</p><p>This workshop didn’t hand me all the answers, but it did offer valuable reminders. Here are the key takeaways I carried home.</p><h3>1. Leading Starts with the Self</h3><p>The first lesson was about self-leadership: before you can influence others, you need to manage yourself. It sounds cliché, but I’ve seen how true it is in day-to-day work.</p><p>The training broke it down into four foundations:</p><ul><li><strong>Self-Acceptance</strong>: knowing your strengths and weaknesses without judgment.</li><li><strong>Self-Respect</strong>: holding onto your values and boundaries.</li><li><strong>Self-Confidence</strong>: trusting your ability to act even when the outcome is uncertain.</li><li><strong>Self-Direction</strong>: having clarity about where you’re heading.</li></ul><p>As a manager, I notice how my own state affects the team. On weeks when I lack clarity, the team feels it. When I lead with confidence, they mirror it. This section reminded me that leadership isn’t just about setting tasks or goals, it starts with how I carry myself every day.</p><h3>2. Leadership vs. Management</h3><p>Another distinction that hit home was the difference between leadership and management:</p><ul><li><strong>Leadership</strong> is about people: creating an environment where others feel inspired to move toward a shared goal.</li><li><strong>Management</strong> is about process: making sure systems, plans, and structures actually work.</li></ul><p>In practice, I often find myself switching between the two. Some days, I need to be the “manager” who checks details, aligns processes, and makes sure deadlines don’t slip. Other days, I need to be the “leader” who paints the bigger picture, injects energy, and keeps morale alive.</p><p>The hard part is balance. I’ve had weeks where everything was on track, but the team energy felt flat. On the flip side, there were times when the team was buzzing with motivation, but tasks were lagging behind. Both extremes don’t work.</p><p>The real craft of leadership, I realized, lies in holding these two roles at once.</p><h3>3. Personality Styles Matter</h3><p>Not everyone leads, or responds in the same way. The workshop described four personality styles:</p><ul><li><strong>Driver</strong>: focused on results, decisive, straight to the point.</li><li><strong>Influencer</strong>: focused on people, energetic, persuasive.</li><li><strong>Analyzer</strong>: focused on data, logical, detail-oriented.</li><li><strong>Sympathizer</strong>: focused on harmony, supportive, loyal.</li></ul><p>The point isn’t to box people in, but to recognize differences. I can see these patterns in my own team. There are teammates who always push for fast results (Drivers), some who love rallying others with enthusiasm (Influencers), those who won’t move without data (Analyzers), and those who make sure no one feels left out (Sympathizers).</p><p>The tricky part? Many people don’t fit neatly into just one box. I’ve worked with colleagues who are both analytical and empathetic. That makes it impossible to apply a one-size-fits-all leadership style.</p><p>This made me reflect on my own approach: am I leading in the way my team <em>needs</em>, or just in the way that feels natural to me? It’s a question I’ve started asking myself more often since the workshop.</p><h3>4. Listening is More Than Hearing</h3><p>We also covered the <strong>five levels of listening</strong>:</p><ol><li>Ignoring</li><li>Pretend listening</li><li>Selective listening</li><li>Attentive listening</li><li>Empathic listening</li></ol><p>When I first heard this, I immediately thought about my 1:1s with team members. Honestly, I often hover between levels 3 and 4. I catch the main points, ask clarifying questions, and nod along. But <em>empathic listening, </em>where you’re not just understanding the words, but also the feelings behind them — is harder.</p><p>There were moments when a teammate shared frustration or doubt, and I jumped too quickly into “problem-solving mode.” Looking back, they didn’t always need solutions; sometimes, they just needed to feel heard. That’s the shift I want to practice more: listening with both the mind <em>and</em> the heart.5. Creativity Needs Both Green and Red Lights</p><h3>5. Creativity Needs Both Green and Red Lights</h3><p>We also talked about <em>Green Light</em> and <em>Red Light</em> thinking:</p><ul><li><strong>Green Light</strong>: free flow of ideas, no judgment, creativity encouraged.</li><li><strong>Red Light</strong>: critical evaluation, identifying risks, selecting the best option.</li></ul><p>It sounded simple, but it hit me because I realized I often mix the two. In brainstorming sessions, I sometimes jump into “red light mode” too fast, shooting down ideas before they have space to breathe.</p><p>I remember one project where a teammate suggested something that felt unrealistic at first. My instinct was to dismiss it. But when we explored it further, parts of that idea actually became the foundation of a feature we later shipped. If I had gone full red light too soon, we would have lost it.</p><p>Leadership, in this sense, is about knowing <em>when</em> to switch lights. First, let ideas grow freely. Then, when the time is right, bring in structure and evaluation.</p><h3>6. Delegation is Not Distribution</h3><p>This was a big reminder for me. Assigning tasks ≠ delegation.</p><ul><li><strong>Distribution</strong>: giving tasks so the work gets done.</li><li><strong>Delegation</strong>: giving ownership so someone can learn and grow.</li></ul><p>In the past, I’ve been guilty of doing the first. When deadlines are tight, it feels easier to just distribute tasks like checkboxes. Things get finished, but the team doesn’t grow much from it.</p><p>True delegation takes more time and patience, because mistakes will happen. But I’ve seen how powerful it is. When I delegate with trust, people step up. They may struggle at first, but they often surprise me with solutions I wouldn’t have thought of.</p><p>It’s slower in the short term, but it builds confidence and skills that make the whole team stronger in the long run.</p><h3>7. Appreciation is a Leadership Skill</h3><p>The last reminder was about something so simple, yet so often overlooked: appreciation.</p><p>Being an <strong>appreciative leader</strong> means:</p><ul><li>Recognizing contributions.</li><li>Expressing appreciation authentically (not just “good job” but <em>why</em> it mattered).</li><li>Building a culture of trust and gratitude.</li></ul><p>I used to underestimate this. I thought appreciation was just a “nice to have,” something you sprinkle on top after the real work is done. But I’ve seen how it changes the energy in a team.</p><p>A genuine “thank you for staying late to fix that issue, it saved us from a bigger problem” does more than boost morale. It tells people their work matters. It builds trust. And over time, it shapes a culture where people want to give their best.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZGdnuUf9QXIMdT4T" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Three days of training can’t turn anyone into a perfect leader. But for me, it planted seeds.</p><p>It reminded me that leadership is not about titles or authority. It’s about how we show up: how we listen, how we delegate, how we balance process with people, and how we appreciate those around us.</p><p>It’s a practice. And like any practice, it grows with intention, reflection, and consistency.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73c482318cd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Radical Candor: Being a Kick-Ass Boss Without Losing Your Humanity]]></title>
            <link>https://ullyindr.medium.com/radical-candor-being-a-kick-ass-boss-without-losing-your-humanity-226de1131062?source=rss-76626a7360e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/226de1131062</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[radical-candor]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Rully Indra Laelaningrum]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 03:33:58 GMT</pubDate>
            <atom:updated>2025-09-30T03:50:19.274Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first became a manager, I thought my job was to keep everyone happy. I avoided tough conversations in 1:1s because I didn’t want to make things “awkward.” The result? Small problems piled up into big ones, and I carried the stress alone.</p><p>On the flip side, I’ve also had moments where frustration made me too blunt. I’d point out mistakes without enough empathy, and later realized I had left people feeling discouraged instead of motivated.</p><p>Kim Scott calls this balance <strong>Radical Candor</strong>: caring deeply about your people <em>while also</em> being brave enough to challenge them directly.</p><h3>Care Personally, Challenge Directly</h3><p>Caring personally doesn’t mean remembering birthdays or sending cupcakes. It’s about <em>real conversations</em>. For me, that looks like asking my team what excites them outside of work, or why they joined this company in the first place. Those stories often reveal what motivates them at work.</p><p>But care alone isn’t enough. You also have to <strong>challenge directly</strong>. That means saying the uncomfortable thing when someone misses a deadline or isn’t stepping up. I still struggle here, I sometimes hesitate in 1:1s when I need to bring up tough feedback. But every time I <em>do</em> say it, my team appreciates the honesty.</p><p>Feedback may sting in the moment, but it prevents resentment from festering. And when resentment doesn’t fester, people actually start to <em>enjoy</em> working together.</p><h3>The Traps I’ve Fallen Into</h3><p>Reading Scott’s framework was like holding up a mirror. I saw myself in these traps:</p><ul><li><strong>Ruinous Empathy</strong> — avoiding hard feedback because I didn’t want to hurt feelings. This left people confused about what needed to improve.</li><li><strong>Obnoxious Aggression</strong> — being too direct without enough context, especially when deadlines were tight. I learned the hard way that bluntness without care just shuts people down.</li><li><strong>Manipulative Insincerity</strong> — luckily rarer for me, but I’ve caught myself sugarcoating when I was simply too tired to argue.</li></ul><p>We all slip into these modes. The goal isn’t perfection: it’s awareness, and course correction.</p><h3>Rock Stars and Superstars</h3><p>One thing I’ve learned is that not everyone on my team has the same trajectory. Some are <strong>rock stars</strong> — steady, reliable, and happy where they are. Others are <strong>superstars</strong> — hungry, ambitious, and climbing fast.</p><p>Early on, I made the mistake of expecting everyone to “grow fast.” But not everyone wants that, and that’s okay. A healthy team needs both stability <em>and</em> ambition. Now, I try to understand where each person is in their journey and create opportunities that fit.</p><h3>Collaboration Over Command</h3><p>Telling people what to do doesn’t work.</p><p>What works better is collaboration: listening to ideas, debating openly, and then deciding together. I like Scott’s reminder that debates should be about the <em>best answer</em>, not about ego. It takes time, but the outcome sticks longer because the team owns the decision.</p><p>And when it’s time to execute, I’ve learned not to step too far back. Staying close to the work — while still giving people ownership — builds trust.</p><h3>Don’t Forget Yourself</h3><p>“You can’t give a damn about others if you don’t give a damn about yourself.”</p><p>This one hit me hard. There were weeks when I was juggling too many projects and felt I couldn’t “own” any of them fully. I burned myself out trying to keep everyone afloat.</p><p>Now, I’m learning to protect my energy through doing my hobbies or simply disconnecting after work. When I show up centered, I can give more to my team.</p><h3>My Go-To Feedback Practices</h3><p>Here are a few practices that have worked for me (even though I still fail at them sometimes):</p><ul><li>Give feedback immediately, not weeks later.</li><li>Praise in public, criticize in private.</li><li>Say “this approach doesn’t work” instead of “you’re wrong.”</li><li>Listen first, respond later.</li><li>Embrace the discomfort — it gets easier with repetition.</li></ul><h3>Building a Team That Loves Their Work</h3><p>One of the most rewarding moments as a manager is watching a team genuinely <em>enjoy</em> working together. And no, it doesn’t come from free meals or flashy outings.</p><p>It comes from the small things: thoughtful 1:1s, challenges, and casual sharing sessions where we talk not only about code or projects, but also about who we are outside of work. Those conversations build trust in ways no team-building budget ever could.</p><p>Most of all, it comes from shifting how I see my role. Not as “the boss” who has all the answers, but as a <em>partner</em> walking alongside the team. That, to me, is the essence of Radical Candor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oNnaFx14CswFbV19" /><figcaption>Photo by <a href="https://unsplash.com/@etienneblg?utm_source=medium&amp;utm_medium=referral">Etienne Boulanger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Radical Candor isn’t about being nice or being harsh, it’s about being honest <em>and</em> human.</p><p>I’m still learning to practice it daily. But every time I manage to care personally and challenge directly, I see my team grow stronger — and myself grow a little more into the kind of leader I want to be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=226de1131062" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned from My Twenties]]></title>
            <link>https://ullyindr.medium.com/what-i-learned-from-my-twenties-b2c97af147de?source=rss-76626a7360e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2c97af147de</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[self-acceptance]]></category>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[life-in-your-20s]]></category>
            <category><![CDATA[storytelling]]></category>
            <dc:creator><![CDATA[Rully Indra Laelaningrum]]></dc:creator>
            <pubDate>Thu, 28 Aug 2025 06:01:52 GMT</pubDate>
            <atom:updated>2025-08-28T06:07:12.669Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Reflections on growth, mistakes, and everything in between.</em></p><p>This year marks the closing chapter of my twenties. Before entering a new decade, I’ve reflected on what the past ten years have taught me. My twenties were marked by challenges, uncertainties, countless first experiences, meaningful encounters and painful goodbyes, as well as a deeper journey toward knowing myself and God. It was a decade of growth that has shaped the person I am still becoming.</p><p>Here are the lessons I carry from that journey.</p><h3>1. Self-Mastery</h3><p>The path to self-mastery is shaped by each experience: pleasant, painful, and deeply uncomfortable. Each one whispered something about who I was, if only I paused long enough to listen. By turning inward and asking myself the hard questions, I began to see more clearly. Journaling became both a mirror and a compass, teaching me awareness, honesty, and patience with myself.</p><blockquote>“Journaling doesn’t just record life; it reveals it.”</blockquote><h3>2. Recognize the Patterns</h3><p>Life moves in rhythms: habits, reactions, relationships. Often, it’s not the situation that traps us, but the patterns we replay without seeing.<br>Maybe overthinking leads to endless scrolling, deepening anxiety. Maybe guilt from unrepentant mistakes can make prayer feel heavier, which in turn feeds avoidance — and the cycle repeats.</p><p>So, what patterns keep returning in your life?</p><h3>3. Focus on What You Can Control</h3><p>I learned to focus on what I could control. I chose to focus on myself, on personal growth, and on the journey of “me versus my past self,” instead of constantly comparing myself to others. By doing so, I gained more clarity on what truly matters and how I can make a meaningful contribution to others.</p><h3>4. Feeling Content</h3><p>Back then, I was always hungry for validation — and perhaps that was natural, since I hadn’t yet felt enough within myself. But slowly, I learned to find wholeness within, to feel that I was enough without needing constant approval from others. Contentment became less about chasing recognition and more about embracing peace.</p><blockquote>“What we seek is no longer recognition, but peace.”</blockquote><h3>5. Wisdom Needs Knowledge</h3><p>I once thought wisdom simply came with age, but I learned it also requires knowledge. The more I studied, the more I realized how little I actually knew. And as one teacher reminded me, knowledge is meant to measure ourselves, not to judge others.</p><blockquote>“How dare we judge others, when what we truly lack may be knowledge?”</blockquote><h3>6. Learn to Unlearn or Re-Learn</h3><p>Growth often requires courage: the courage to question values, perspectives, and habits we once believed were absolute. Not everything we learned as children remains relevant today. The ability to unlearn and re-learn is what keeps us alive, curious, and evolving.</p><h3>7. Effort in Relationships</h3><p>Every relationship asks something of us: love, family, friendship. It takes effort, time, patience, and often the softening of our egos. Healthy connections don’t just happen; they grow when both sides choose to show up and make life easier for each other.</p><h3>8. The Power of Acceptance</h3><p>Acceptance is not passive surrender; it is the strength to acknowledge what lies beyond our control. To accept reality, the process, and even ourselves. It is where healing begins, and where peace quietly enters.</p><blockquote>“Acceptance is where healing begins, and peace finds its way in.”</blockquote><h3>9. Letting Go with Surrender</h3><p>Letting go is not giving up, but returning things to where they truly belong. Over time I learned that nothing is truly “ours”: people, moments, feelings, even life itself. We are only entrusted with them for a while. Surrender teaches us peace, trust, and a deeper faith.</p><blockquote>“Letting go is a form of returning — to peace, to trust, to Him.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1Ij1tA9AovqrfAGJ" /><figcaption>Photo by <a href="https://unsplash.com/@kubliz?utm_source=medium&amp;utm_medium=referral">kub liz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Looking back, I realize that learning never stops. None of us have it all figured out — we are all still finding our way.</p><p>If you’re in your twenties now, which lesson are you learning the hard way?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2c97af147de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blameless Culture]]></title>
            <link>https://medium.com/product-monday/blameless-culture-8003bccb2047?source=rss-76626a7360e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8003bccb2047</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[blameless]]></category>
            <dc:creator><![CDATA[Rully Indra Laelaningrum]]></dc:creator>
            <pubDate>Mon, 19 Dec 2022 02:25:18 GMT</pubDate>
            <atom:updated>2022-12-19T03:21:48.161Z</atom:updated>
            <content:encoded><![CDATA[<p>Back to 3 years ago, when I was a new engineer on this team. I made a mistake by using the production environment while running the local test. It caused several emails to be sent and some tweets posted. It was noticed by one of the members who see dummy tweets posted on my company&#39;s Twitter account. And also the admin received +100 emails from the platform simultaneously. Fortunately, the emails were only sent to the company team email, not to all of our users.</p><p><strong>“Good experience Rully!”</strong>, said senior engineers to me. It was quite heartwarming and relieve my guilt at that time. Back then, I was a fresh graduate and the only female engineer on the team.</p><p>After the incident, our action item is to mend the onboarding process to avoid the same mistake. The senior engineer doesn’t blame both the new member and others. Yet, we reflected on what was wrong with our system. Yes, my team is adopted Blameless Culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_k7kLbPDIIPZmUGJ" /><figcaption>Photo by <a href="https://unsplash.com/@matscha?utm_source=medium&amp;utm_medium=referral">Daniela Holzer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Humans will fail. Humans always make mistakes. Blameless culture’s goal is to accept that failure is normal. Rather than focus on the person, we focus on the system.</p><p>Here is the blameless culture practice in my Product &amp; Engineering team:</p><h4>1. Assume people are doing their best</h4><p>We set our mind to assume that each company member is doing the best they can to achieve our target. Based on the information they have, or the knowledge they have learned, they want to give their best to the company. It’s impossible there is a member who wants the company to fail or be unsuccessful. So we can conclude that they do not make mistakes on purpose.</p><h4>2. Usecase documentation and acceptance scenario</h4><p>Before making a feature, we used to write the documentation which contains all of the possibilities that will happen if the feature is already implemented in the platform. Each engineer can share their approach to developing the feature. So that other engineer can give their perspective on whether the approach is effective or not.</p><p>The documentation also should contain the negative flow which could happen to prevent it happen in the future.</p><h4>3. Automate</h4><p>With automation, we can find errors as early as possible. From the negative flow we wrote on the documentation earlier, we transform them into tests to prevent human errors. We always run the test before we deploy the new code to the production environment.</p><h4>4. Give positive feedback</h4><p>Replace negative language with more positive and knowledge-sharing language. This is implemented in our PR review practice. We tend to focus on what can be improved, instead of pointing out what might be wrong. We put forward another idea and provide some references to help the contributor understand better.</p><h4>5. Watch the language</h4><p>Avoiding language that could be considered blameful. Instead of asking <strong>“Who caused this to happen?”</strong>, we can ask, <strong>“How could this happen?”</strong>. Instead of saying <strong>“X deployed a change to production”</strong>, we can say, “<strong>A commit was deployed to production”.</strong></p><p>We can’t say that it’s already perfectly implemented in my team or my company. But we always learning to make it better.</p><p>Let’s share your thoughts and experiences in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8003bccb2047" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-monday/blameless-culture-8003bccb2047">Blameless Culture</a> was originally published in <a href="https://medium.com/product-monday">Product Monday</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>