<?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 Yip YM on Medium]]></title>
        <description><![CDATA[Stories by Yip YM on Medium]]></description>
        <link>https://medium.com/@yipym03?source=rss-6b3c37d051ff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*F79qAbxy1k5ULW01.jpg</url>
            <title>Stories by Yip YM on Medium</title>
            <link>https://medium.com/@yipym03?source=rss-6b3c37d051ff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:10:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yipym03/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[Empower Teams and Individuals through OKRs]]></title>
            <link>https://medium.com/@yipym03/empower-teams-and-individuals-through-okrs-a9ab3df46f82?source=rss-6b3c37d051ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9ab3df46f82</guid>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[management30]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[okr-framework]]></category>
            <dc:creator><![CDATA[Yip YM]]></dc:creator>
            <pubDate>Tue, 10 Aug 2021 07:05:51 GMT</pubDate>
            <atom:updated>2021-08-11T10:43:57.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*znKeZ66mOdHG2tZFXc9nJA.png" /></figure><p>My first experience with goal-setting in organisations went like this:</p><ol><li>Here’s a stack of lists</li><li>Choose the list which fits your role</li><li>Load the priorities given into the career tool we will use to assess you with</li></ol><p>Nothing much to it. But in the long run…</p><p>Pro: I didn’t need to think about my priorities until the yearly assessment season arrived</p><p>Con: I didn’t need to think about my priorities until the yearly assessment season arrived</p><p>I could never really tell the difference as the goal-setting muscle never needed to be exercised until I was asked to work with Objectives and Key Results (OKRs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rCUn-XLl6w96f4paS8YeEQ.png" /></figure><p>OKRs actually stem from a line of thought that leads back to Peter Drucker who introduced Management by Objectives (MBOs). Andy Grove felt that the next evolution was to refine MBOs with knowing how we are making our way towards our objective. He then unleashed it upon Intel back when they were growing and aiming for world domination. As luck might have it, John Doerr was exposed to the power of OKRs through his work in Intel. He eventually left Intel and met up with Google’s founders who were building stuff in a garage and the rest is history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6HVR_6p1kbdb_-bqLmsGZg.png" /></figure><p>OKRs are made up of (1) purpose — what we want to complete or achieve and, (2) direction — how we are going to make our way there. It is a communication framework: We state our purpose and direction to the public and request that they provide feedback through conversations with us to help refine our statements.</p><p>In detail, the Objectives have these characteristics:</p><ol><li>Meaningful — What is desirable and relevant to how we want to shift our current reality?</li><li>Action-oriented — What can we say to encourage us to actually do something?</li><li>Practical — What is feasible and viable with respect to the future we want to create?</li><li>Inspirational — What is innovative and significant to us that ignites our passion?</li></ol><p>While Key Results follow the SMART (Specific, Measurable, Attainable, Realistic, Time-bound) acronym, <em>‘A’</em> leans more towards being Aggressive, Audacious and Aspirational in accomplishing the tasks, measuring where we are and using our output or outcomes as guidance towards meeting our objective.</p><p>In short, OKRs are declarations: “I/We will (Objective to accomplish) as measured by (this set of Key Results).”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kv7joagimfOfLaNT79vcfA.png" /></figure><p>Taking a big picture view of the OKR ecosystem, we have this example from <a href="https://www.whatmatters.com/the-book/">Measure What Matters</a>. Typically, a top-down approach is taken as the OKRs are derived from the organization’s vision, mission and strategy.</p><p>The great cascade starts when I adopt my direct manager’s KRs and make them my objective(s). I would then create my KRs and engage my team by selling the story of why my KRs matter to the organization. They would each then adopt one or more KRs as their objective(s). This process continues until we reach the person nearest to the ground.</p><p>Right after receiving the objective(s), I have an option to ask clarifying questions and align my perception of what I am committing to. If I accept those objective(s), I also have the opportunity to align my KRs with my direct manager. In the midst of working out or even, working on my KRs, I could have conversations with peers in different departments. If we find synergy, we can always solidify it through a joint KR.</p><p>This is the power of OKRs as a communication framework. It sounds like a huge amount of work but imagine practising this as part of creating your working ecosystem. It will get easier day-by-day. To start off, we can ask ourselves: What is the significance of taking the time and effort to cascade the OKRs and, the time and effort to align the OKRs? What is the long-term cost of practising this versus the benefit of enacting behaviour change?</p><p>When we say “People are the heart of any organisation”, what we mean is that the basic structure of an organisation is just people grouped together in a logical fashion so that we can deliver the promises made to our customers. OKRs make these promises clear at every level.</p><p><em>Side note…This does not mean we start and end with top-down OKRs. Here is some guidance on the culture we eventually want to develop through using OKRs: </em><a href="https://www.whatmatters.com/faqs/bottom-up-okrs-definition-examples/"><em>Bottom-up OKRs: What are some examples?</em></a></p><p>From experience, I find that once a proper objective has been set, it can last for years. Whereas, key results can change or be completed every quarter or less. Hence, it is worth exploring guidelines for key results before looking at the overall idea of OKR superpowers.</p><h4>Guideline #1: Pair quantity with quality</h4><p>Every key result you write down has a story behind it. Can you tell anyone what it is without speaking to them? One way to approach this is ask yourself:</p><ul><li>What is the ultimate result I am aiming for?</li><li>What is the domain I will be measuring success in? (e.g. programming skills, realised sales, potential clients, etc.)</li><li>How can I measure the domain to show that I am achieving the results?</li><li>How can I know that my actions act as proof for the results I want to achieve?</li></ul><p>Pairing quantity key results with quality key results strengthens OKRs as a communication framework and allows everyone to get onto the same page earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C3JcTpP7g4a2e2hcJHoCNw.png" /></figure><h4>Guideline #2: Mix outputs and inputs</h4><p>This guideline is closely related to the previous guideline. In the example provided below, a mechanic can tune the engine to increase average lap speed. Whether the 2 percent increase has been met depends on tests at wind tunnel.</p><p>You could also treat tests as wind tunnel as a quantity key result and increase average lap as a quality key result.</p><p>The main point here is that you can weave your quantity and quantity key results as a mixture of outputs and inputs to meet your objective. Weaving them will enhance your story and the resulting actions you would take to achieve those key results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NrG1r4odAGz6VvCs89aF9A.png" /></figure><h4>Guideline #3: Less is more</h4><p>One purpose of setting a key result is to enact some change, get some result and measure whether that result is desired. Having 3–5 key results for each objective pushes us to employ laser-focus in completing the actions needed to reach the output or outcome.</p><p>If you feel the tendency to create too little or too many key results, ask yourself: Would having all these key results allow me to have more focus or less focus in achieving my objective?</p><p>Put it another way: You decide on the level of focus you want to have for all your objectives.</p><h4>The OKR Superpowers</h4><blockquote>Andy Grove created a system for goal setting that was deceptively simple. Objectives are the what. Key results are the how. If I achieve those hows, those key results, I will provably get to the objective. Objectives are significant, concrete, action oriented, and (ideally) inspirational. They are typically longer lived. They’re bold. When properly designed and deployed, they’re a vaccine against fuzzy thinking — and fuzzy execution. The key results are aggressive, but always measurable, time-bound, and limited in number. They’re aggressive but realistic, but most of all, they’re measurable and verifiable. It’s not a key result unless it has a number. How do we set meaningful audacious goals?</blockquote><p>When you enter the world of OKRs, what you need to unlock are the following superpowers. This section sums up what you have read in the articles thus far and why they are important elements of OKRs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dTqlMb0dPXMJQhWH5xE7mQ.png" /></figure><h4>Superpower #1: Focus &amp; Commit to Priorities</h4><p>Have you experienced doing many things which end up with little impact? Similar to a vector moving in a positive and subsequently negative direction, bringing you back to zero. What if you could cut those many things down to 2 or 3 items? Would that change what you can achieve then? Would that allow you to look at the bigger picture and evaluate how effective you are in achieving your organisation’s vision? Focus brings clarity to what you want to communicate and how you communicate your priorities. Focus allows you to influence and engage others in what you commit to changing.</p><h4>Superpower #2: Align &amp; Connect for Teamwork</h4><p>Expanding on the great cascade of OKRs, you can identify numerous opportunities for top-down and bottom-up functional alignment and connection. While this allows you to deliver to expectations, you do not work in a vacuum. Everyday, things change and what can make it more likely for you to meet your end goals is the OKR framework’s potential for cross-functional coordination. When you start to communicate using the OKR framework, you gain the ability to leverage on others who can help you manage your risk and dependencies. Explore using the OKR framework as a communication tool for gathering like-minded individuals to your cause.</p><h4>Superpower #3: Track for Accountability</h4><p>At the beginning of this article, I mentioned how I didn’t need to think about my priorities until the yearly assessment season arrived. What happened in between? Are priorities just a way to measure how much we are reimbursed? If priorities are so important, why not pay more attention to them? In short, regular tracking enables you to change your behaviour towards reaching the end goal. When you look at how you are progressing you either give yourself a pat on the back and feel motivated by the path you are taking or trigger an internal reflection to decide on actions which would orientate you towards your intent. The earlier you notice that you are straying from the path, the faster you can pivot. OKRs are not absolutes, they are meant to be guardrails.</p><p>Additionally, at the end of the OKR cycle, you will need to score and provide an assessment of the score. This is where subjectivity meets the facts and puts your team network to the test. A general guide for scoring involves a scale of 0 to 10 and follows these rules:</p><ul><li>7 to 10 means the OKR was delivered to satisfaction</li><li>4 to 6 means there was progress but the OKR was not completed</li><li>0 to 3 means there was no real progress at all for the OKR</li></ul><p>Once everything is done, an additional step you can take is to reflect on the quality of your OKR. Could a goal achieved in full be changed? What did you learn to alter your approach to next cycle’s OKRs?</p><h4>Superpower #4: Stretch for Amazing</h4><p>There are many kinds of goals, ranging from the simple one to the most unattainable legacy you could create. In the end, you set the level. A key characteristic is for OKRs to be inspirational and aspirational. You will be amazed how much can be done even for aspirational goals, that is, as long as you start to set them.</p><p>Aspirational goals spark creativity and passion. OKRs allow you to disrupt the market, as long as you balance the institutional nature of it with a varied-range of goals. Also, it is alright to have more undelivered goals. As Bono from U2 once said “<em>The OKR framework cultivates the madness, the chemistry contained inside it. It gives us an environment for risk, for trust, where failing is not a fireable offense — you know, a safe place to be yourself. And when you have that sort of structure and environment, and the right people, magic is around the corner.</em>”</p><p>This article details all areas I covered with my teams when we embark on setting and maintaining OKRs. Here is a snippet from an enjoyable moment with one of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_DoYmUAhFw5LV1_evWtGQ.png" /></figure><h4>Want more inspiration? Head on over to <a href="https://management30.com/practice/okrs/">https://management30.com/practice/okrs/</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9ab3df46f82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s time for the Celebration Grid]]></title>
            <link>https://medium.com/@yipym03/its-time-for-the-celebration-grid-d67e90ab1c97?source=rss-6b3c37d051ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/d67e90ab1c97</guid>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[management30]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <dc:creator><![CDATA[Yip YM]]></dc:creator>
            <pubDate>Wed, 09 Dec 2020 10:02:21 GMT</pubDate>
            <atom:updated>2020-12-12T03:10:20.307Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Donald G. Reinertsen argues that when we run experiments, we do that because we want to learn something and when we have a 50/50 chance of success or failure, we learn the most.</blockquote><p>When I heard that <a href="https://jurgenappelo.com/">Jurgen Appelo</a> created the Celebration Grid based on <a href="https://www.amazon.com/Principles-Product-Development-Flow-Generation-ebook/dp/B00K7OWG7O">Don Reinertsen’s ‘The Principles of Product Development Flow’</a>, I was ecstatic. This is such an amazing way to mould knowledge into a model I can carry everywhere or spin up for reflective work. Here’s how the Celebration Grid works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*_pOjjLJfjcUiKie2b6IvMw.jpeg" /><figcaption>Celebration Grid in full glory</figcaption></figure><p>On the top and left perimeters, we see a way to map our behaviours (actions) to our outcomes (results).</p><p>Within the second layer, we have 3 grids for our mistakes, our experiments and our practices. These relate directly to our behaviours (actions). And they are further categorised into our failures or successes as our outcomes (results).</p><p>As we dive deeper into the respective grids, we notice how easy it has become to determine whether we are learning and growing.</p><p>Overall, the Celebration Grid gives us a way to take a step back and become our own observers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U4C7b7qVGmIaFvhBx_7P1Q.png" /><figcaption>Celebration Grid in action</figcaption></figure><p>This is the Celebration Grid in action. In our newly formed product team, we used this very early on in our release cycle to check how we were doing with our Discovery &amp; Delivery work. While this can be used anytime, anyplace, timeliness does matter. In our case, it has made us aware of our current reality from the beginning. Inspecting and adapting then became our focal point.</p><p>It is worth noting that we used a 3-step approach for our team retrospective:</p><ol><li>List down our mistakes, experiments and practices</li><li>Reveal, align and categorise our items into the 6 areas related to failure or success</li><li>Reveal and discuss how our actions translate into learnings and actionable items for our future</li></ol><p>Initially, I felt glad we even tried this out. I thought what we did was good enough until I watched a <a href="https://www.youtube.com/watch?v=l_uz5wqdImQ">2015 Management 3.0 video</a>.</p><ul><li>My first takeaway: we should also question “What about the white area?” and “What else should we have done to learn more?”</li><li>My second takeaway: There’s more to the Celebration Grid than what’s presented on the surface. Look below…</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*WQyWfASCNetmb8nBMjjuIg.png" /><figcaption>Celebration Grid on networks versus hierarchy</figcaption></figure><p>Networks of teams versus an hierarchical network feature here. For experimentation to take flight, we rely on network of teams with their ability to form and dissolve quickly. Practices (and standard processes) typically thrive in an hierarchy. When we have a successful experiment, it could turn into a successful practice. When we have a failed practice, it could turn into an experiment.</p><p>On the surface, the Celebration Grid looks busy. But at every turn, it gives us an opportunity for a deeper interpretation of the work we do.</p><h4><em>Want more inspiration? Head on over to </em><a href="https://management30.com/practice/celebration-grids/"><em>https://management30.com/practice/celebration-grids/</em></a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d67e90ab1c97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productivity Sweet Spot]]></title>
            <link>https://medium.com/@yipym03/productivity-sweet-spot-159ea884ebc1?source=rss-6b3c37d051ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/159ea884ebc1</guid>
            <dc:creator><![CDATA[Yip YM]]></dc:creator>
            <pubDate>Fri, 28 Aug 2020 06:59:19 GMT</pubDate>
            <atom:updated>2020-08-28T06:59:19.057Z</atom:updated>
            <content:encoded><![CDATA[<p>Two months ago, I found myself saying yes to more meetings than I could handle. I admit, they all had really compelling agendas.</p><p>Until I chanced upon a talk by a Product Manager who created focus time by blocking out time-slots within her working week. This started a slew of experiments.</p><h4>Experiment 1: Start blocking up all spaces in the work week</h4><p>(Except Mondays.) I chose to leave Mondays open so others could include me in meetings easily on Mondays. In short, funnel others to my chosen day of week for information gathering.</p><p>However, there were sporadic blocks of ‘Space’ in my calendar. On bad weeks, it was hard to find nice stretches of focus time. But it wasn’t a total failure.</p><h4>Experiment 2: Block all spaces for the work month!</h4><p>(Again, leaving Mondays open.)</p><p>A little extremity didn’t hurt anyone. And now I was able to move nice huge blocks around, occasionally allowing meetings to come in between them. Unfortunately, I didn’t always find myself doing productive work.</p><h4>Experiment 3: Create an organised list to manage backlog</h4><blockquote>“Does this spark joy?” – Marie Kondo</blockquote><p>There is a chunk of paper in front of me every day. Basically made up of scraps with random stuff: important information and snippets of conversations, or ideas from an article.</p><p>So everything was migrated to a nice online list. Throwing actionable ideas into a list, grouping them and linking sources of inspiration together was a good pre-requisite to actually getting a plan up.</p><h4>Experiment 4: Start planning for the week</h4><blockquote>“The danger of expecting nothing is that, in the end, it might be all we’ll get.” – Dan Ariely</blockquote><p>With my backlog of actionable ideas listed prioritised, I would spend Monday mornings planning the week. That got the work done but left me feeling anxious every time Monday came around. Having a preference for getting ready early and making small tweaks nearer the deadline meant planning had to be done earlier.</p><p>I also noticed ad-hoc meetings still dropped in on Tuesdays to Fridays. Some of them were simply unavoidable.</p><h4>Experiment 5: Plan even earlier!</h4><p>Every Friday at 5.30pm, I would pick up my backlog, grab the prioritised tasks and pump them into the following week. Of course, there is some buffer added to Fridays. (Some deem it the most productive day of the week.)</p><p>Coincidentally, having an OKR / goals evaluation slot right before planning helps me to cut off from work and enjoy the weekend.</p><h4>In conclusion…</h4><p>What started out as a way to create boundaries, grew into a practice I use to create focused, productive moments at work.</p><blockquote>“The most compassionate people are also the most boundaried.” – Brene Brown</blockquote><p>The lesson here: Regularly observe how you work, adjust appropriately and be kind to yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=159ea884ebc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drafting my WHY Statement]]></title>
            <link>https://medium.com/@yipym03/drafting-my-why-statement-2fdd0a66225?source=rss-6b3c37d051ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fdd0a66225</guid>
            <dc:creator><![CDATA[Yip YM]]></dc:creator>
            <pubDate>Sun, 03 May 2020 14:17:25 GMT</pubDate>
            <atom:updated>2020-05-03T14:17:25.592Z</atom:updated>
            <content:encoded><![CDATA[<p>After reading Start with Why, I was craving for more. How could I apply the concepts to help the people around me see its importance? That was a year ago. Not much has changed since then.</p><blockquote>It’s not about perfection but progress!</blockquote><p>1st May 2020, 9:00pm. I joined a 2-hour workshop with about 80 participants to jumpstart my WHY. Here’s my take on the process.</p><h3>Refresher on The Golden Circle</h3><p>Basically, we can have the same result which can be achieved through different means. This relates to having the same WHAT but different HOWs.</p><p>However, why we do something or act in a certain way, may not be entirely clear to us as this purpose resides in the realm of feelings. By identifying the patterns from our life’s stories, we can come closer to drafting our WHY.</p><h3>Have a Partner</h3><p>The workshop required me to be a partner first as well as the storyteller second.</p><p>Right from the start, it’s important to understand how to be a good partner. This is the equivalent of saying: “My partner’s life purpose is now in my hands too. I am equally responsible for crafting it with him or her.” The interesting bit here is that your partner should not be someone close to you so that your stories will not be tainted with your partner’s view of it, thus losing objectivity.</p><h3>Gather and Share Stories</h3><p>The main part of the workshop is to bring stories to the table where your partner will help you to draft your WHY. And you will do the same for him or her.</p><blockquote>I am the sum of my experiences.</blockquote><p>Choosing your story is the moment of self-reflection. What stories were meaningful in a good way and in a bad way? Which stories do you want to re-live and which stories do you not want to re-live but learnt the most from? What was the first story you recalled that was impactful to you?</p><p>Telling a story to your partner means helping them re-live that very moment with you. Set up the stage, then get into the facts and convey your feelings! Be open to questions from your partner. All he or she wants to do is to dive into that moment with you. Take this chance to be vulnerable and trust in your partner.</p><h3>Identify Themes</h3><p>Themes are recurring instances in a person’s life. It could be what you did or something which happened to you, that clearly shows what you care about. In short, what you value.</p><blockquote>What does the story say about who they are and what they value?</blockquote><p>Here’s where the data analysis starts. We convert all the raw data (facts and feelings) from the stories shared, into the impact they had on our partner’s life. Connecting the dots on what your partner values; even negative stories can show us what they felt was missing and that is clearly what they value.</p><p>Naturally, the more stories shared, the easier it would be to identify themes.</p><p>As you list the themes that stood out from your partner’s stories, there might be 1 theme or many themes. What helped was verbalising all those themes to your partner.</p><p>This is your litmus test for resonance. This is the first take on who your partner is, what he or she values. At this point, it is alright to mull it over together. After all, it’s a first take.</p><h3>Draft your WHY Statement</h3><p>Here it gets tricky as you put into a common format, the feelings and values your partner upholds. Don’t fret. Pick out 1 to 2 themes that were the most inspiring to you and go for it!</p><blockquote>Format: To (contribution), so that (impact).</blockquote><p>Bear in mind that it has to be simple and clear, contains verbs and affirmative language. This WHY will be your partner’s legacy – because of the impact, it can’t exactly be accomplished. But most of all, it has to feel right and inspires you.</p><p>When you’re done, share it. Give your partner options and commit to the drafting process by checking on which key words resonates with your partner. Use a thesaurus if need be. It has to feel right and inspire your partner too.</p><p>Right at the end, remember it’s not about perfection but progress.</p><h3>Discovering my WHY Statement</h3><blockquote>My WHY is what I value and believe. It is the change I want to make in the world.</blockquote><p>10 pieces of rough paper later, this is the first draft of my WHY and I attribute it to my fantastic partner who took the effort to dig deep and listen.</p><blockquote>To connect lives with others in order to reciprocate learnings, warmth and love with others.</blockquote><p>There’s definitely more to come in refining my WHY. After all, this is a discovery process about my purpose in life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fdd0a66225" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>