<?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 Samreen Malla on Medium]]></title>
        <description><![CDATA[Stories by Samreen Malla on Medium]]></description>
        <link>https://medium.com/@samreenmalla?source=rss-e7b200bb96fa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*i4oMjeMLLTbug9EaeCGX9w.png</url>
            <title>Stories by Samreen Malla on Medium</title>
            <link>https://medium.com/@samreenmalla?source=rss-e7b200bb96fa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:41:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@samreenmalla/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[Why You Need To Know About Cloud As A Manager]]></title>
            <link>https://samreenmalla.medium.com/why-you-need-to-know-about-cloud-as-a-manager-7948f03c651e?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/7948f03c651e</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Wed, 13 Nov 2024 17:36:02 GMT</pubDate>
            <atom:updated>2024-11-13T17:37:39.093Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5dztovPWQuswlaDIpI-MUA.jpeg" /></figure><p>Management roles are getting more and more technical these days and making it through this job market is a job in itself. Having a skillset that can help you stand out among the “100 applicants applied already” is crucial.</p><p>Businesses are now all cloud based. Deploying products to cloud and using cloud services to reach to more audience has been the go to strategy for most companies. So, one of the most useful skills in a manager would be having the cloud knowledge.</p><p>Now, talking about the cloud services, I am more inclined towards AWS. Why?</p><ol><li>According to a <a href="https://survey.stackoverflow.co/2024/technology/">Stack overflow survey</a> 2024, AWS dominates the cloud market by holding 48% the global market share.</li><li>There are over 200 AWS services. Any requirement you have, there is a tool or service built to deliver already.</li><li>From Netflix to Twitter, any platform you use is being built on top of AWS. A lot of modern Generative AI workloads are also being hosted on this platform.</li></ol><p>This has to mean its good right?</p><p>Now let’s also understand why<strong> YOU </strong>need to know about cloud.</p><p>As a Manager you are working to create value be it through a product or a project. You understand the customers, the business, and the product. But do you understand how your product is being built? Or how your product is reaching your customers? When you understand your product from discovery to delivery, you can create more value throughout those steps.</p><p>And like I mentioned above, having the technical skills actually helps.</p><p>Better yet, let’s look at the top 5 reasons, why you need to know AWS as a Manager:</p><h4><strong>Become an informed decision maker:</strong></h4><p>Understanding AWS enables us, to make informed decisions regarding product architecture, resource allocation, and cost management. Tools like <strong>AWS Compute Optimizer </strong>can recommend optimal resource configurations based on usage patterns, while <strong>AWS Trusted Advisor</strong> provides recommendations for cost efficiency by highlighting unused resources or suboptimal configurations. This knowledge helps us to analyze technical feasibility and align product features with business goals.</p><h4><strong>Save on bucks, while providing more value:</strong></h4><p>Understanding how cloud works allows us to effectively manage budgets and optimize costs associated with cloud services. Tools such as <strong>AWS Cost Explorer and AWS Budgets</strong> provide insights into spending patterns and help in setting financial limits, facilitating better decision-making and smart financial commitments. By knowing how to leverage various pricing models and support plans, we can make strategic decisions that enhance profitability while ensuring that the product remains scalable and efficient.</p><h4><strong>Be a better collaborator:</strong></h4><p>A solid grasp of cloud technology fosters better communication and collaboration with engineering and development teams. We can engage more meaningfully in discussions about technical requirements, constraints, and innovation, which is crucial for a successful product development. Utilizing services like<strong> AWS Step Functions</strong> for orchestrating workflows can help us understand how different components interact, making it easier to manage complex processes and collaborate more effectively.</p><h4><strong>Keep your product Customer oriented:</strong></h4><p>AWS provides tools that can help us gather and analyze customer data effectively. For instance, using <strong>Amazon QuickSight</strong> for data visualization allows us to derive actionable insights from user interactions. By leveraging cloud capabilities, we can better understand user needs, iterate on products quickly, and enhance customer satisfaction through data-driven decisions.</p><h4><strong>Keep up with the market trends:</strong></h4><p>Cloud computing is a dominant force in the tech industry, with AWS being a leader. Knowledge of cloud services like <strong>Amazon EC2</strong> for scalable computing, and <strong>Amazon S3</strong> for storage, allows us to stay competitive and relevant in a market that increasingly relies on cloud solutions, and not to miss the career enhancement opportunities this skill brings.</p><p>To sum it up, learning about AWS not only equips us, with vital skills for our current roles but also helps us be more hands on with all the capabilities that Cloud and Gen AI brings.</p><p><em>I have talked about this in more detail in this video. Do check it out!</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9BqN9e-JaHQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9BqN9e-JaHQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9BqN9e-JaHQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/27cfe6bb3f1ba312ab25cb346521ea96/href">https://medium.com/media/27cfe6bb3f1ba312ab25cb346521ea96/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7948f03c651e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Kindled story of Kindle — A Case Study]]></title>
            <link>https://samreenmalla.medium.com/the-kindled-story-of-kindle-a-case-study-e9c4b3ae1812?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9c4b3ae1812</guid>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Tue, 07 May 2024 19:28:14 GMT</pubDate>
            <atom:updated>2024-05-07T19:28:14.243Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Kindled story of Kindle — A Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x2M3ACJq6lOSDPBjRsHxqg.jpeg" /><figcaption>The Kindled story of Kindle — A Case Study</figcaption></figure><p>As an avid reader, having a Kindle has been a game changer. The power of carrying thousands of books on your bag, and being able to read any time of the day or night, is has been a dream come true. <br>So, I wanted to understand, how this amazing invention came to be.</p><p>Kindle was first launched on November 19, 2007. However, the concept was developed way ahead.</p><p>2003 was a great year for both Apple and Amazon. Apple had made a huge disruption in music with iPods, while Amazon had just made their first profitable quarter. It is said that one night, Jobs invited Bezos to a dinner where he demoed Apple’s first windows application — iTunes. Through the demo, Jobs wanted to give a message to Bezos that everything was moving online, and the CDs and Cassettes that were high sellers in Amazon, could disappear in the coming days.</p><p>Bezos knew he had to do something about it. Either be a fast follower and do something similar to Apple in Music or be an inventor.</p><p>In the early 2004, Bezos made Steve Kessel, the lead of company’s digital business. This decision was confusing to a lot of people since Kessel was the VP of media retail, looking after the sales of books, music, video, and more. He would now be supervising the digital media business which consisted of an e-books team of roughly five people and no real prospects of growth.</p><p>Although there were proposals that Kessel could oversee both digital and the physical media, Bezos made sure, that the two should be completely separate from one another. He wasn’t focused on what to build, rather on who and how. And he knew Kessel would be the perfect leader.</p><p>Since Amazon was already working with Music, Books, and Videos, something along these domains were reachable and practical. Bezos made it clear that Amazon had to be the inventor, so Music was out of the picture.</p><p>With videos, in the 2004s, video had not gone digital, which seemed like an opportunity, but the barriers were just too high. With no fast internet to stream the video files, and the legalities with the studios, it was a lot of work.</p><p>Books were still the single largest category at Amazon. Although there were some companies working with e-books, the business was tiny; and most importantly, there was no good way to read books. PC was an only option, and everyone who loves reading know it is not a good experience.</p><p>So, this started the market research.</p><blockquote>Customers wanted something equivalent to iPods for books.</blockquote><p>Beginning with this concept, they moved forward.</p><p>In September 2004, they hired Greg Zehr who had been a VP of hardware engineering at Palm Computing and Apple. A separate office was setup for him in Silicon Valley so that Amazon could tap into the Talent pool. Simultaneously, an engineering team was being formed in the Seattle office for cloud and backend functions.</p><p>Then, in April 2005, Amazon acquired Mobipocket. Mobipocket was a small company based in France that had built a software application for viewing and reading books on PCs and mobile devices.</p><p>They first identified the core of the product: <br>1. Single purpose device only meant for book lovers to dive into books, not a multipurpose device with distractions.<br>2. Accessibility of books without the need of a cable or computer download to access books from anywhere and anytime.</p><p>The ideation started in early 2004, and by early 2007s, the team already had a working prototype. Bezos would call the team to an unsolicited location where they would each read books with the prototype and then gather around to share experiences to improve it.</p><blockquote>In November 19, 2007 Kindle became the first e-book reader with 90,000 books available for purchase. It got sold out in less than 6 hours.</blockquote><p>In their first launch, they gave users a way to send them feedback. Kessel and the team would personally look into those feedback, which later birthed Kindle 2 in 2009.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWFBor8f9sFBy9mDYWWoDA.png" /><figcaption>Kindle 1 VS Kindle 2</figcaption></figure><p>Kindle 2 incorporated a lot of user’s feedback: a sleeker design, 25% longer battery life, faster page turns, memory expansion up to 2 GB, Read-to-me feature, and 230,000 books for purchase.</p><p>They continued the improvement, and iteration throughout the year, and by 2012, Kindle had been the world’s best-selling e-reader for five years straight. The 5th iteration of Kindle, <strong>Paperwhite</strong> was launched in 2012 which even in 2024 is the best-selling Kindle.<br>Throughout the years, Kindle has evolved and become better for people everywhere around the world.</p><h3>Takeaways</h3><p>Through this amazing case study of Kindle, here are the five key takeaways, we, as Product Managers must look into:</p><h4><strong>1. Identify the value chain:</strong></h4><p>Amazon was already working with Books. Although it was physical, they knew the supply chain by being on the middle of everything — the writers, publications, and retailers to the customers. Through Kindle, they were no longer the ones in the middle, but in everywhere. So, if you are trying to reinvent a wheel, identify what you already have, and start with it.</p><h4>2. Working Backwards:</h4><p>Had Amazon thought what they were just an e-commerce platform, not a hardware company, the world might never have a Kindle. They identified what the customers needed, and then gathered resources after it. Most times in Product management, you ought to think out of the box.</p><h4>3. Make your product ever evolving:</h4><p>Launched in 2007, Kindle has successfully been the best-selling ebook reader till date. This is because it is evolving, with new technologies, and with its customers.</p><h4><strong>4. Believe in the Product you are working for:</strong></h4><p>Bezos and the team were faced with multiple concerns, and criticism when they were working on Kindle. However, Bezos knew what disruption would look like. He believed in this team, and his vision of the Product.</p><p>And lastly, a simple yet critical takeaway:</p><h4>5. Your estimated time and resources mean nothing:</h4><p>Humans are biased creatures, and usually we tend to overestimate ourselves. As a leader, we must be flexible to these estimates, because those are just that — Estimates.</p><h3>Conclusion</h3><p>In the ever-evolving landscape of innovation, the journey of Kindle stands as a beacon of inspiration. It reminds us that greatness often lies on the other side of uncertainty. In the face of doubt and skepticism, it was the unwavering belief of visionary leaders, the relentless dedication of a talented team, and the synergy born from collaboration that propelled Kindle from concept to revolution. So, let this case study serve as a reminder that no challenge is insurmountable. For when we dare to dream, and work together to turn those dreams into actions, we unlock the potential to create wonders that shape the future.</p><p><em>I have also talked about this in detail in this </em><a href="https://youtu.be/8XakGB0rXXo"><em>video</em></a><em>, if you are into that kind of stuff ;)</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8XakGB0rXXo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8XakGB0rXXo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8XakGB0rXXo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0df99f852490a793b92cfe7d26b01952/href">https://medium.com/media/0df99f852490a793b92cfe7d26b01952/href</a></iframe><h4>References:</h4><p><a href="https://commons.wikimedia.org/w/index.php?curid=11375546">https://commons.wikimedia.org/w/index.php?curid=11375546</a></p><p><a href="https://www.entrepreneur.com/growing-a-business/why-and-how-amazon-created-the-kindle-and-changed-the/363311">https://www.entrepreneur.com/growing-a-business/why-and-how-amazon-created-the-kindle-and-changed-the/363311</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9c4b3ae1812" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shifting Gears: From Feature Factory to Outcome-Driven Product Management]]></title>
            <link>https://samreenmalla.medium.com/shifting-gears-from-feature-factory-to-outcome-driven-product-management-f25a4ead304b?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/f25a4ead304b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Thu, 23 Nov 2023 07:20:58 GMT</pubDate>
            <atom:updated>2023-11-23T07:20:58.992Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*38V21bxCQAkVtfXyuy-yMw.png" /></figure><p>The term “Outcome Driven” gets thrown around a lot these days. This is something you might have heard from the leadership of your team one to many times when working on a product. But are you really working with an outcome-driven team? Is your business actually focused on outcomes?</p><p>There have been many instances where although people are talking about becoming outcome-driven, they are still performing as a “Feature Factory”.</p><p>In Product Management, being called a feature factory is rather derogatory and is used as a way of indicating that the business is moving in the wrong direction. Before looking into how we can avoid becoming a feature factory, first, we need to understand what it is, and how we might fall into this trap.</p><h3>What is?</h3><blockquote>When we call a Product Team a Feature factory, it means that the team is releasing features after features without adding any value to the product.</blockquote><p>It refers to a business that is focused on <strong>delivering output rather than outcomes</strong>.</p><p>The businesses that measure success by how much and how often new feature is shipped without measuring the Return of Investment makes them a feature factory.</p><p>Sounds familiar? Now, no team wants to go down this path. But we fall into this trap unintentionally when,</p><blockquote>We do not validate the idea before building and take no feedback from the users after releasing.</blockquote><p>It’s like the team is jumping from one feature to another without looking back at what impact they just delivered. For these teams, getting the features out means they are successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OaexrnDGbeH_SreVWEBJCQ.jpeg" /><figcaption>What feature factories do</figcaption></figure><p>What leads to becoming a feature factory:</p><h4>Intuitive Leadership:</h4><p>Leadership demands features based on what they “think” is valuable. When the leadership is over-confident in their intuition without gathering any information or evidence, Product Managers become less confident about delivering value. The team then delivers what the leadership wants to see, not what is actually valuable.</p><h4>Lack of a clear Product Strategy:</h4><p>The teams that do not have a clear goal as to why they are doing what they are doing, are focused on only delivering what is asked to them. These types of teams do not have a clear vision, and strategy which makes them output oriented. They don’t think about how they can make the product better. They are only focused on developing the feature and meeting the deadline.</p><h4>Un-measured feature impact:</h4><p>After a product team delivers a feature, it must be measured with respect to user adoption, retention, and how it has or has not played a role in revenue generation. When product teams do not measure these metrics and focus on new features one after another without taking a buffer time for proper research and analytics, they end up losing the bigger picture.</p><h3>Moving on…</h3><p>Now that we know what the feature factories are doing, let’s get into what we must actually do.</p><p>Becoming outcome driven does not happen overnight. It happens when teams put effort to build systems for feedback and analysis. We must work on the process, people, and much more.</p><p>Here are some steps we can take as product managers to make create a culture of delivering outcomes:</p><h4>Collaborate</h4><p>When an idea is brought up by the leadership, try to analyze it with respect to the current state of the product. Collaborate with the stakeholders to take a design thinking approach and come up with creative and strategic ways to bring the idea to life.</p><h4>Work on the Product Strategy, Vision, and Objectives</h4><p>For the product strategy and Vision, you would want to work closely with the leadership to understand their aspirations and vision. Try to build your northstar metric and align your short-term goals with the broad strategy. Outline the objectives of each feature and their impact to the Product strategy.<a href="https://samreenmalla.medium.com/paving-a-way-for-your-product-the-product-roadmap-2a8089b03e51"> Create milestones for the product</a> as well as the team.</p><h4>Listen and Analyze</h4><p>Listen to the customers but do your research. Sometimes the users’ feedback can be overwhelming which can drive Product Managers to go along with the requests without necessary research. The goal is to spend time with your users and try to find the underlying pain points, not just build their feature requests.</p><blockquote>Deliver value, not just requests.</blockquote><p>Another important thing we can do as a Product Manager is to change the way we communicate. Instead of communicating about features, try providing updates about the value you are targeting to provide. Do not just talk about the features, talk about the impact. Talk about why we are doing what we are doing.</p><p>Understand what the lifecycle should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zAnxMnnePSDrOS_V8sM_0Q.jpeg" /><figcaption>Fig: What Outcome Driven teams do</figcaption></figure><h4>Conclusion</h4><p>The first step toward solving a problem is knowing that there is a problem. Not validating an idea before building it is a problem, not analyzing the impact of that idea is a problem. Wearing a product manager’s hat means you have to focus on outcomes rather than outputs.</p><p>Hope this has helped you in creating a mind map of how you can transition from being output driven to outcome driven.</p><p>Keep building awesome things!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f25a4ead304b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Paving a way for your Product: The Product Roadmap]]></title>
            <link>https://samreenmalla.medium.com/paving-a-way-for-your-product-the-product-roadmap-2a8089b03e51?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a8089b03e51</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[product-roadmap]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Tue, 03 Oct 2023 04:54:20 GMT</pubDate>
            <atom:updated>2023-10-03T04:54:20.541Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xXWlZPTpxwrNN0Bqtqcmkw.png" /></figure><p>In Product Management, one of the most important documents you will prepare is the Product Roadmap. This piece of information is crucial in identifying how a product will be developed and evaluated.</p><blockquote>Working only with intuition is dangerous. So, we need a long-term <strong>product development plan</strong> that gives all the <strong>product stakeholders</strong> the information they need to <strong>co-ordinate their planning</strong>.</blockquote><p>Let’s decode this definition. We have three things here, development plan, product stakeholders, and co-ordinating the plan.</p><h4>Product Development Plan</h4><p>A product from discovery to launch, goes through several planning, research, and testing. This is the overall developmental cycle which involves evaluation and iteration at every step. A plan in this case must be dynamic and is prone to change with respect to relevance and priorities.</p><blockquote>When we say a “long-term” development plan, we are not saying this is “carved in stone”. It is an ever-evolving, dynamic piece of information which streamlines the efforts for the overall product development.</blockquote><h4>Product Stakeholders</h4><p>One of the most essential parts of following a product roadmap is that it needs to be <strong>accepted and owned</strong> by the stakeholders. Let’s identify our stakeholders first and look into what level of ownership they need to hold.</p><p>First and foremost, the <strong>Most important stakeholder.</strong></p><p>The Business Leader (CEO, General Manager, anyone who leads the business functions other than Product development, sales, marketing, and support).</p><blockquote>A product manager, although may be the creator, but the business leader, must feel complete ownership of the roadmap.</blockquote><p><strong>Why?</strong> The business leader needs to be at the top of the roadmap, in order to allocate the resources, the headcount, to remind each of the stakeholders to prioritize tasks necessary for the roadmap success.</p><p><strong>When?</strong> They must be involved as early and often in the process of roadmap development. So, to say, we create the roadmap, with the business leader.</p><p>Then comes, <strong>Other Stakeholders:</strong></p><ol><li>Sales leader: VP of sales, Chief Revenue Officer. <br>They have to hit the sales targets based on the roadmap.</li><li>Product Development Leader: CTO, VP of Engineering. <br>They are responsible for organizing and motivating their team to hit developmental milestones.</li></ol><p>We can also add other stakeholders if necessary but always remember:</p><blockquote><em>Whomever you choose to include, they must add value to the process, not create distractions.</em></blockquote><p>Now, let’s talk about another most important stakeholder of the product. <strong>The customers.</strong></p><p>Understanding our customers is the most important and the primary currency of any product manager. Through collaboration with the customer success teams, surveys, and direct communication, we can know a lot about the customers, their pain points, their usage, and their expectations with the product.</p><h4>Coordinate Planning</h4><p>Like a map, a product roadmap gives us a predictability on where our product is heading and how we must align our future activities in that direction. It forces leadership to clearly articulate their business goals and make strategies to achieves those outcomes.</p><p>Now that we know what a roadmap is, why we need it and who we should include, let’s look at:</p><h3>How to make it successful?</h3><p>There are three things, we need to be mindful about if we want our roadmap to be successful.</p><h4>Sound Strategy</h4><p>A Product Strategy is a representation of the way we are trying to achieve a business outcome. It is the description of how the business is trying to achieve its goals with the product. A sound product strategy includes:</p><p>Business goals, measurement of success, target customers, competitors, and key differentiators.</p><p>When we start with a sound product strategy, it becomes easier for us to determine what milestones we need to achieve, and when. The first step is articulating the product strategy as clearly as possible.</p><h4>Realistic</h4><p>A product roadmap consists of milestones that the team needs to achieve in each quarter, month, or Sprint. Milestones help us to identify and address the pain points of the customers which can reduce or even prevent churn.</p><p>Some milestones may not directly impact our customers, but they would be beneficial in other strategic objective, like optimization of the application, opening new channel for sales, lowering costs, and so on.</p><p>We need to think of milestones at the right level of granularity. These are not backlog tasks, these are big features that will impact the business.</p><h4>Fully supported by key stakeholders</h4><p>We have identified our stakeholders above. For our roadmap to be successful, the stakeholder at all levels, must take ownership of it. They must align their business tasks, to reinforce and meet the roadmap goals.</p><p>We must never create a roadmap, based on “someone’s” intuition and gut feel.</p><p>Intuitions can be faulty, and most common mistakes that we make is when leaders are intuitive and persuasive. It can lead to faulty and unrealistic expectations, not fully supported by other stakeholders.</p><blockquote>The purpose of the roadmap is not the document itself, but the alignment of the different stakeholders around the development plan that the roadmap represents.</blockquote><h4>Hands-On</h4><p>These are the groundwork we just did. Now, let’s create a first draft.</p><p>Remember, the first draft is likely to change before it is accepted. Nothing to be disheartened about. It is a living document, prone to change.</p><p>Some things to keep in mind while creating the first draft:</p><ol><li>Roughly sequence your milestones in terms of their value in supporting your product strategy.</li><li>Prioritize each of them one by one, based on the rationale. It might give you the first mover benefit or might have a major impact on user retention, based on what the business’s goal is, prioritize the milestones.</li><li>Schedule the milestones into your roadmap. (Basic approach: Highest priority first)</li><li>Use the effort estimate provided by your product development leader, as well as the development capacity of the team to figure out when you could expect it to be delivered. You can do this collaboratively with the development teams.</li><li>Pick up the second highest priority milestone and assuming that the first one is completed on time, schedule that one in the same manner.</li></ol><p>Let’s take an example of an E-commerce Platform. Let’s say we are building the overall website for the business. The first draft may look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wd3Itb8ZESdeWpDuPaPrsQ.jpeg" /><figcaption>Product Roadmap for an E-commerce Platform</figcaption></figure><p>In the above roadmap, we have the milestones listed for each quarter. Each of these milestones target to meet the Product Strategy of the business to:</p><ol><li>Be Easily accessible.</li><li>Provide Frictionless experience.</li><li>Retain customers.</li></ol><p>In any case, we have to be mindful of the development capacity of the team in each quarter or period.</p><p>The first draft may go through a number of iterations, and it will change over time. You need to ask yourself, if it implements the product strategy, and if it is feasible from development perspective. If you have doubts, you need to make adjustments so that both these things are well maintained.</p><h4>End Remarks</h4><p>There is no fixed format that fits all organizations: Format is less important than the support of the stakeholders. Once you present it to them, they must support and believe in it.</p><p>The key to building this alignment is the process you go through, not the final format or even the contents of the product roadmap.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a8089b03e51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One-on-One: making thembetter]]></title>
            <link>https://samreenmalla.medium.com/one-on-one-making-thembetter-f76a7b6ee7f5?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/f76a7b6ee7f5</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 12:26:18 GMT</pubDate>
            <atom:updated>2023-07-26T16:41:38.789Z</atom:updated>
            <content:encoded><![CDATA[<h3>One-on-One: making them better</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WgG305GxFj0MEg8oadQdfg.png" /></figure><p>We conduct several meetings in a day as managers. They range from product, progress, team check-ins, planning for the future, and whatnot. But, How many times do we set up meetings to connect with our colleagues individually? How sure can we be to say that we know our team members better? How much have we focused on THE PEOPLE?</p><p>So many times, I have seen managers push one on ones and never get back to it. It&#39;s obvious that too many meetings sometimes drain all of our social batteries, but hey, it is what we do. Right?</p><p>What we intend to forget ever so often is that these one on ones are not just any other meetings. It is our time, off of the monotonous work, to connect with each other, to know each other better, and if we do it right, to build friendships.</p><p>Although it&#39;s very people-specific and yes, not all my 20 team members think, or feel the same way. Having been on both ends, attending one on one as a report and a manager<em>,</em> I have had an abundant chance of knowing the Dos and Don’ts.</p><p>If you are a manager who has lost touch with why to conduct one on ones, or if you are a manager trying to conduct your very first one on one, here is a list of things we can do to make one on ones better for us: the managers, and our teammates.</p><h3>Go Prepared</h3><p>It is recommended that you and your report discuss ahead of schedule the agenda of the one on one. While this might be ideal, the everyday meetings and the hustles give us little to no time whatsoever. Writing down some talking points in the notes, or jotting them in bullets on a piece of paper might be a more realistic approach. However, be prepared on the most critical items you want to discuss with them. You can ask them to do the same. When you have the most critical things listed, you can make them a priority and discuss other things later, or in the next one on one.</p><h3>Ask Questions</h3><p>It might be the first one on one you are having with this person, or maybe the 10th, it is always better to go prepared. Learn a little about them, and remove every judgment you have of them. Let this be the first time you connect with them on a personal level. Let this be the time to actually get to know them better. Make a list of questions you think would allow you to know them better. From the simple: How are you feeling about this project? to the more complex ones: What do you consider your biggest strengths? make sure you have some questions prepared.</p><blockquote>During one of my one on ones, I asked my colleague to list out three of her biggest strengths and weaknesses. She listed her weaknesses easily, but when it came to strengths, she was blank. I had to give her points on what she had accomplished so far, and how she had done them. After the conversation, she told me she had been feeling unconfident throughout the week, and now that we listed her strengths together, she felt much empowered.</blockquote><p>You see, asking valuable, intentional questions can sometimes make people think, of themselves, of certain situations, and more.</p><h3>Connect</h3><p>Many a time, we are accustomed to showing our team the happy days. We confidently handle clients and have answers to most questions. But the reality is not just all that. One on one is a time when you can open up about so many things, beyond the regular work stuff. Share your vulnerabilities with them, share your failures, share your ideas with no filter. This will open them up with you, and help them connect with you on a personal level.</p><blockquote>One time, one of my team mate seemed to be having a really low day. I had scheduled a one on one with him prior, so when we went in, I started by sharing my personal struggle. I told him that the week was getting too hectic and I needed to manage my stress. As I was sharing my struggles, he opened up and shared with me his personal hardship. He was going through a tough time with his girlfriend which was impacting his day. When he shared this, I asked him if wanted to talk about it. After he said yes, we talked about relationships in general, I gave him some advice, and we continued our session like any other. The next day, he was back, re-energized. He thanked me for the suggestion and was back being his motivated self.</blockquote><p>At the end of the day, we are only humans. And humans have feelings. Let’s not forget that.</p><h3>Be Present</h3><p>Be fully present. Oftentimes, it&#39;s easy for us to drift away and think about the message you had to send to the client, or the email that needs your response, the Slack message that you just got.</p><p>Mute those for a second! 🤫</p><p>When we are distracted by other things, we cannot connect with them. It gives an impression that we are not interested. No one wants to feel ignored, right?</p><p>Although there might be pressing issues, this meeting is about them, so make it about them.</p><h3>Feedback Loop</h3><p>Make a habit of giving and receiving honest feedback. And “honest” is the key here.</p><p>Initiate a feedback session where you give them all the good things they did, and also some areas of improvement that can actually help them be better. Then you ask for their genuine feedback for you. This way, you both help each other become better.</p><p>When you are both giving each other constructive feedback, you give them a space where you can tell each other uncomfortable things. In some ways or the other, you are both uplifting each other in spirits and in career.</p><h3>Support</h3><p>When you give them an open space where they can share something with you, it is necessary that you don’t cross the line. If they have shared something personal or professional: a detail about themselves, make sure you support them. Give them their space and ask if you can be of any help to them. Don’t give them solutions right away. Sometimes, all a person needs is ears. Listen, and help them where they ask for it.</p><blockquote>One of my colleagues shared with me that he had received an offer from another company. He told me that he was considering it given he felt he was stuck here. I asked him to do his analysis, and list out the pros and cons. <strong>In fact, we did it together.</strong> By the end of it, we found out that he only needed a change in project. He was happy with the office culture, and what he was getting. He just needed a more challenging project. I told him, I would talk to the engineering manager and got him into a new project 2 days after.</blockquote><blockquote>Fun fact: He is still with the company. 🙌</blockquote><h3>Do more</h3><p>Although you may be meeting each other regularly and having conversations on a daily basis, make it a habit to conduct one on ones every end of Sprint, or every month. I have read most people say you should conduct it every week, but honestly, it’s not feasible for me. So do what floats your boat, but do it!</p><p>You might think that this is just another meeting, but it’s not. It is a chance for you to connect with them and build a stronger relationship.</p><p>In her book, “<a href="https://www.amazon.com/Making-Manager-What-Everyone-Looks/dp/0735219567">The Making of a Manager</a>”, <a href="https://medium.com/u/b8a4e5ae7490">Julie Zhuo</a> writes,</p><blockquote>“A manager’s work is to turn one person’s particular talent into performance.”</blockquote><p>And one on ones is a special opening where you identify their talents, and plan together how you can transform it into performance.</p><h3>Clarity</h3><p>We should never intend to confuse our team members. After you conduct the one on one, do not leave them guessing why we talked about what we talked about. Let your intentions be very clear in terms of the meeting and let them have their ideas poured out to you.</p><p>If they have shared something personal, let them know that it is okay. Be a safe space where they can share things and not get into trouble about it later.</p><p>After the meeting, make sure they are not puzzled, but rather feel empowered and happy to have had the conversation.</p><h3>Making it something you both look forward to</h3><p>One-on-ones although may take a significant amount of your time, they are one of the most essential meetings you conduct. It is a valuable time for you to connect with your teammates and discuss all sorts of things: their personal achievements, their workload, their future plans, what’s bothering them, what’s getting them excited, everything and more.</p><p>Always remember, when you take care of your people, they take care of everything else.</p><p>— --</p><p>Come and Say Hi on my <a href="https://linkedin.com/samreenmalla">LinkedIn</a> 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f76a7b6ee7f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drifting through the 7 Cs of communication]]></title>
            <link>https://samreenmalla.medium.com/drifting-through-the-7-cs-of-communication-6b5e11cc4bcd?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b5e11cc4bcd</guid>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Mon, 26 Jun 2023 05:58:59 GMT</pubDate>
            <atom:updated>2023-06-26T05:58:59.651Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QorPMsFF2-Vq66c9qwpvpQ.png" /></figure><p>Communication, although is the most essential part of work, it is also one of the main reasons for misunderstanding.</p><p>Effective communication is not easy and takes practice, so here are 7 tips to improve your communication skills also called the <strong>seven Cs of communication.</strong></p><h3>Completeness</h3><p>The message must be complete. You need to provide all necessary information and convey all the facts that are needed for the receiver to understand what you are trying to do.</p><p><strong>For example: </strong><br>If you want your colleague to send an email about her work progress, you say:</p><blockquote>“Hey Sherry, send an email to the client at the end of the day today, okay?”</blockquote><p>Now, your colleague is extremely confused since she does not know what email you are talking about. The message you gave her was incomplete and she will not be able to do what exactly you want her to do. Instead you could have said:</p><blockquote>“Hey Sherry, could you send an email to the clients about your tasks update including the ones that are still work in progress? Let me know if you want me to review before sending. Is that okay with you?”</blockquote><p>This gets the message across properly without any confusion.</p><h3>Conciseness</h3><p>Conciseness means wordiness.</p><blockquote>Convey what you want to say in least possible words.</blockquote><p>This does not mean give them an incomplete message, but keep your message as concise as possible. This is a time saving and cost effective way of communicating. Do not keep repeating the same thing over and over again or don’t add any irrelevant information.</p><p><strong>For example:</strong></p><p>We need to send out a message to our remote team, emphasizing that we need to follow certain rules and communicate efficiently with each other. If we write something like this:</p><blockquote>“In order to achieve the desired outcome of this project, it is imperative that we adhere to the established guidelines and protocols that have been set forth by the relevant authorities and stakeholders, and that we communicate effectively and efficiently with each other and with our clients throughout the duration of the project.”</blockquote><p>This sentence is way too long, has too many words. It is unclear about what we need to do and why. Instead:</p><blockquote>“To succeed in this project, we must follow certain rules like attending the daily scrum at 10am EST, communicate well with everyone in the team, and let everyone know if you are facing any blockers so that we can work collaboratively on solving it.”</blockquote><p>This sentence is short, simple, and clear. It tells the reader what we need to do and why in a few words.</p><h3>Consideration</h3><p><strong>Being considerate means stepping into someone else’s shoes</strong>, taking another person’s viewpoints and feelings into consideration. When working in a team, we communicate with several people. We need to understand their mindset, where they are coming from, and their current emotions.</p><p>Communication without thoughtfulness may sound rude and hinder the relationship between the sender and the receiver.</p><p><strong>For example:</strong></p><p>When we are in a meeting discussing about a major feature. A developer keeps constantly interrupting everyone which is making everyone else frustrated or angry. You don’t want to come across as rude and arrogant, but the person is disrupting the meeting decorum. What you can say here is:</p><blockquote>“Hey Dave, I understand that you are excited about this feature, so are we. Let’s make this discussion more interactive and allow everyone to keep their opinion out here as well. We can circle back to the details once everyone has put out their ideas. How would you like that?”</blockquote><p>This way, you do not hurt their feelings and keep the enthusiasm going while also keeping the meeting balanced.</p><h3>Concreteness</h3><blockquote>Concreteness refers to being particular.</blockquote><p>When you are discussing among your team, it is necessary that you give specific facts and figures. Similarly, when you are asking for help, your message should be straight, not fuzzy statements that might confuse your recipient. Concreteness in communication helps to reduce misinterpretation hence there is less room for misunderstanding.</p><p><strong>For Example:</strong></p><p>You need a document from a team member so that you can share it in a presentation the next day. You also want to review it and make necessary changes before the presentation. So, you tell her,</p><blockquote>“Emma, can you create a document about the feature you were working on last week? Share it with me soon.”</blockquote><p>Now, Emma does not know what soon is: an hour, a day, a week or a month? She might not make it available for the next day. Also, she might have worked on multiple features last week. So, she is confused as to what you want and when you want it. To create a better understanding you should have said:</p><blockquote>“Emma, I need a document from you about the payment integration feature you worked on last week. Please make it ready in the next 1 hour. I want to review it and present it in the meeting tomorrow. Can you make it happen?”</blockquote><h3>Clarity</h3><p>When communicating with someone about something, the message must be clear.</p><blockquote>This implies emphasizing on a specific message rather than jumbling up several messages at a time.</blockquote><p>This makes understanding clear and easier while also making you a good communicator. Unclear messages are the root causes of misunderstandings and chaos.</p><p><strong>For Example:</strong></p><p>Suppose you send your boss an email saying:</p><blockquote>Hello Roy,</blockquote><blockquote>I’m sorry for the delay, I was busy with the project, but I have some questions, can you please answer them, also I need your feedback on the report, and can you please approve my request, thank you.”</blockquote><p>This email will confuse him since it has no structure or clarity. The boss might not know what to focus on and might miss some important action items. Instead you can write:</p><blockquote>Hello Roy,</blockquote><blockquote>Thank you for waiting for my response. I was occupied with the project, hence the delay. I have some queries that would require your attention as soon as possible. I will forward it to you right away. I also needed you feedback on the report. We can discuss this when you have time.</blockquote><blockquote>Thank you</blockquote><p>Now, the boss can prioritize the information and create less delays in the work process.</p><h3>Courtesy</h3><blockquote>Courtesy as we know is about showing someone respect.</blockquote><p>When communicating in a professional setting, it is essential to show respect and sincerity to your colleagues, be it, seniors, juniors or any stakeholders. Your language must be polite, judicious, and reflective. Like the saying goes “When you give respect, you get respected.” This stands true during every type of communication.</p><p>When you speak with someone, the tone of your voice, how you address them, your body language is visible. But when you are working with a remote team, messages may not be received as intended.</p><p><strong>For Example:</strong></p><p>You need your team member to prioritize a certain task. So you ask them,</p><blockquote>Hey, I want you to work on Sticky note feature before anything else. If you need anything, let me know.</blockquote><p>This message, although written with good intentions, may be received as rude and arrogant. You can sound kinder by saying:</p><blockquote>Hey Max, I hope you are not very occupied right now. We needed to prioritize the sticky notes feature before any other tasks this sprint. I am sure would be the right person to work on it given your experience. Let me know if you have any concerns. I am always here.</blockquote><p>The person now feels valued and appreciated. You get the message across without offending anyone.</p><h3>Correctness</h3><p>Correctness is essential in all types of communication, but more so in written format. Your messages and emails should not have grammatical errors. The message must be exact, and well-timed. Also, when speaking, it is important to have precision in the things you speak about. Correctness helps to build greater impact on the audience and also builds credibility for the speaker.</p><p><strong>For Example:</strong></p><p>You need to add more resources on your team to meet the deadline. You are asking your engineering manager to provide you a senior developer.</p><blockquote>I need a senior developer to complete the module of the application. My deadline is approaching and we have only completed so much. If we don’t add a resource right now, I don’t think we will be able to meet the deadline.</blockquote><p>This message, although gives the information out loud, does not make sure it is based on facts. The engineering manager, may or may not take your request seriously. While you can say:</p><blockquote>My project is in need of a senior mobile developer. The deadline is in next 2 months, and with all the junior resources on the team, we have only been able to complete 40% of the work. Major modules are still a work in progress. Please look into this matter and provide me with an answer by the end of day today.</blockquote><p>Now, with the facts provided, they can look into what type of resource would fit best. They would also be able to prioritize the action item with the given deadline.</p><h4>End Remarks</h4><p>Communication is essential in every aspects of our life, and even more so in a professional setting. <strong>Being able to present idea across is a super power! </strong>With these Seven C’s of communication you can be effective among your team and stake holders who are right next to you or seven seas across.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b5e11cc4bcd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum: The Three Pillars]]></title>
            <link>https://samreenmalla.medium.com/scrum-the-three-pillars-6dfd222eeb09?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dfd222eeb09</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Sun, 25 Jun 2023 08:30:44 GMT</pubDate>
            <atom:updated>2023-06-25T08:30:44.980Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HDCBCy03ji0tXkW-i5cOQQ.png" /></figure><p>When trying to implement Scrum in project teams, one is constantly reminded that Scrum must be embedded at the core of the team. Although it is mostly used to optimize predictability, it also helps team members know about each other’s competencies and make better use of it for the product.</p><p>Based on empiricism and lean thinking, Scrum focuses on continuous improvement, value for experience, and observability.</p><p>As goes for any framework, Scrum stands tall due to its three pillars. Similar to when hit by an earthquake, a building with strong pillars is less impacted - when anything goes off in a process, we should first look into the three pillars of Scrum. So let’s dive deep into these three pillars of Scrum:</p><ol><li>Transparency</li><li>Inspection</li><li>Adaptation</li></ol><h3>Transparency</h3><p>Transparency in Scrum says <em>All the work that is done and is being done must be visible to everyone</em>. <strong>Everyone </strong>— the ones doing the work and the ones getting the done work. In Scrum, decisions are based on the state of the artifacts:</p><ul><li>The Product backlog</li><li>The Sprint backlog</li><li>The Sprint increment</li></ul><p>If the state of these artifacts are not transparent, the decisions may be biased and sometimes even risky for the product.</p><p>As a product manager, we must always remember that when a team is not transparent about the work being done, or the progress of a certain unit, say tasks, features, or even a module, it creates confusion and a lack of trust. Everyone involved should be known to the facts about the vision they are working for.</p><p>Transparency enables inspection, and inspection is necessary to keep the product and the team in track.</p><h3>Inspection</h3><p>The progress of the product and the state of the Scrum artifacts must be frequently inspected. Inspection is necessary so that we can prevent any kind of deviation from the process. Inspection is enabled in Scrum through its five events:</p><ul><li>Sprint</li><li>Daily Scrum</li><li>Sprint Planning</li><li>Sprint Review</li><li>Sprint Retrospective</li></ul><p>These events must be carried out efficiently to provoke positive changes in the product and the team.</p><p>As a product manager, we must be able to carry out inspection to bring everyone in the team on the same page. A slight deviation may also create a huge impact to the team and the product. Carrying out these Scrum events regularly and effectively is key to inspecting each scrum artifacts.</p><p>No matter what we are doing, it is necessary to make sure that we are all working towards the same product goal.</p><h3>Adaptation</h3><p>Now, inspection without adaptation would be pointless, wouldn’t it?</p><p>If any aspects of the product and process is deviating outside the acceptable limits, the process and the resources used must be adjusted. When should we make those adjustments? you ask, as soon as the deviations are identified so that further variance can be prevented.</p><p>Let’s all face it, adaptation and adjustment are not easy. Adaptation is possible only when all the members of the team are empowered and self-organizing. Adaptation is done by the team. If your scrum team is strong, adaptation is just another task to create a healthier environment for the work to be done.</p><p>As a product manager, we should reinforce the needs and benefits of adaptation. If something is deviating from the anticipated path, we need to adapt a process that guides it correctly, which is possible only through adaptation.</p><p>Work on making your team more self-managed, and they will start adapting on their own.</p><h3><strong>End Remarks</strong></h3><p>Scrum works when these three pillars are efficiently implemented. Make the work transparent to the team members and stakeholders → Create a culture of diligently inspecting work and increment → Adapt to new and necessary processes if a deviation is identified during inspection.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dfd222eeb09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life long Leadership: Getting Started]]></title>
            <link>https://samreenmalla.medium.com/life-long-leadership-getting-started-b7caa230d2ee?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7caa230d2ee</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Sat, 13 Nov 2021 14:31:30 GMT</pubDate>
            <atom:updated>2021-11-13T14:31:30.583Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*hzdoyfM9VI5A_1LmgT7FJw.png" /></figure><p>Leadership is a skill that is necessary in almost every aspect of professional and personal life. It is something that shows our confidence, and our ability to do things. Most of us think that leaders are the amazing breed of humans that do things differently, think of things differently, and live a life we cannot imagine. However, leadership is not something that is unattainable. It’s not rocket science (though many people do rocket science :P). It’s not a trait people are born with, it is something that comes with practice, and commitment. From taking a small initiative, to doing things that can change the world, all leaders do, are find a vision, and commit themselves towards achieving it. It is an art that can be learned and practiced through dedication and commitment. <strong>Everyone can be a leader.</strong></p><p>There is no such hard-and-fast rule of learning leadership. There is no formula of becoming a leader. But we can learn from the already established world leaders. By learning what their process of becoming a leader was, we can make our process better. Because aren’t we all in the process of becoming something? So why not be a leader?</p><p>Through this article, I have tried to highlight the most common practices of leadership that can assist us on the journey of becoming a great leader.</p><p>According to the book “<a href="https://www.amazon.com/Truth-about-Leadership-Heart-Matter/dp/0470633549/ref=sr_1_1?keywords=The+Truth+about+Leadership&amp;qid=1636812804&amp;qsid=145-5468023-3494233&amp;sr=8-1&amp;sres=0470633549%2C1578603021%2CB0032COUMC%2C111923798X%2C1119144280%2CB07DKHH1GC%2C1119430275%2C1984878107%2C0140280197%2C1523000627%2C059323152X%2C1250192455%2C1119592275%2C1736624903%2CB098RQP754%2C1785042149&amp;srpt=ABIS_BOOK">The Truth about Leadership</a>”, there are five most common practices that leaders engage in while accomplishing extraordinary things. Let’s dig deeper into what those five practices are:</p><h3><strong>Modeling the way</strong></h3><p>Exemplary leaders know that if they want commitment from their team, they need to be the models first. In order to model the way, a leader must be able to identify the core values. <br>Values are beliefs that serve as guides for any actions. Aligning the values and performing actions accordingly sets an example for the people who look up to you.</p><blockquote>Modeling the way is essential because people follow a leader’s actions before following a plan.</blockquote><h3><strong>Inspiring a shared vision</strong></h3><p>A vision helps to set a goal. A shared vision is vital in bringing people together for a common goal.</p><p>Inspiring a shared vision can be accomplished by envisioning the future and enlisting others. A leader must be able to determine the new heights the team can attain after achieving a goal. Every team members must realize what they are working for and be aligned with it. Understanding the goal of doing certain things is essential for motivation.</p><h3><strong>Challenging the Process</strong></h3><p>Challenging the process simply means changing or improving the status quo. It demonstrates the fact that an exemplary leader is continuously trying to innovate, experiment, and take risks.</p><blockquote>Leaders do not question themselves or their team; they question the ideas and doubt the default. — Grant (2019)</blockquote><p>Challenging the traditions and bringing new ideas help leaders and their teams to innovate and seek creative and new ways to improve.</p><h3><strong>Enabling others to act</strong></h3><p>Leadership is a team effort. An exemplary leader fosters collaboration and builds trust to enable others to act. S/he frequently uses the term “We” rather than “I”. Fostering teamwork and sharing the accomplishments are the two most common ways a leader enables others. By sharing a vision and making it possible for others to act, a leader expects good results, and shares shares all wins and losses with the team, so that there is sense of ownership for everyone.</p><blockquote>Through enabling others to act, experiment, and change the process, a good leader creates leaders.</blockquote><h3><strong>Encouraging the heart</strong></h3><p>Tremendous achievements come through hard work and much determination. It is not easy to stay motivated and determined all the time. When an effort fails, it is more difficult to stay intact and work harder. One of the most critical actions of a leader is to motivate and encourage others. Keeping the pace going and making everyone in the team feel accomplished even in a difficult situation.</p><blockquote>An exemplary leader encourages the heart by recognizing the efforts of the team members and celebrating the victories and values.</blockquote><h4>Ending Notes</h4><p>Let me repeat again, leadership is not an in-born trait, it comes with practice and determination. Through small steps we can take a bigger leap, and I hope these small steps can help you become a leader in your area of life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7caa230d2ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feedbacks made easy: The Seven Step Feedback Model]]></title>
            <link>https://samreenmalla.medium.com/feedbacks-made-easy-the-seven-step-feedback-model-8ac66d2f5a4b?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ac66d2f5a4b</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Fri, 15 Oct 2021 14:31:20 GMT</pubDate>
            <atom:updated>2021-10-15T14:31:20.524Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AYO0v4VePj7Oesah5YarXg.jpeg" /></figure><p>Dealing with people can sometimes be tiring, especially when the people we work with are difficult. In a workspace, where we have to deal and interact with people, it is necessary that we know how to properly communicate. We don’t want any misunderstandings there, do we?</p><p>Effective and proper communication is crucial if you are leading a team or part of one. You can do both without coming out as rude or inconsiderate. This is where the <strong>Seven-Step Feedback Model</strong> comes in. In a workspace, where we work with varieties of people, it is unavoidable that there are certain people, who just don’t know when to stop, or how to react. We don’t want to be too direct and confront them, but we also want them to improve, and make the situation better for themselves and the team..</p><p>To deal with people like these and not come out as an asshole, we have the seven-step feedback model. Let’s understand this model through some examples we can all relate to.</p><h3><strong>Scenario 1</strong></h3><p>There is a team meeting going on about how we want the team to move forward with a certain client requirement. There is one person, who keeps interrupting other team members and only puts his opinions. As a project manager, what you do is, after the meeting is over, you call aside from the team member and have the following conversation:</p><blockquote>“ During the team meeting, <strong>when you</strong> interrupt other team members, <strong>I feel like</strong> it demotivates them to put forward their thoughts <strong>because</strong> only your ideas are being heard<strong>…</strong> <strong>What I would like</strong> is for you to wait and listen to others’ ideas as well and add to them, <strong>so that</strong> every member’s opinions are considered. <strong>Do you think we can do it? </strong>”</blockquote><h3><strong>Scenario 2</strong></h3><p>During client calls, there is a team member who is constantly on his phone, not paying attention to what the client is saying. Later on, when the tasks are assigned, he asks why those changes are being made which was discussed in the meetings earlier. Using the model, we can have this conversation with the team member:</p><blockquote>“ <strong>When you</strong> are constantly using the phone during our calls, <strong>I feel like </strong>you miss out on the details of what we discussed with the clients <strong>because </strong>you are not able to focus on the meeting<strong>… What I would like is </strong>for you to put your cell phone aside during the calls <strong>because </strong>it would help you concentrate on the call and understand the tasks that will be assigned later. <strong>What do you think about that? </strong>”</blockquote><p>Hence, according to the seven-step feedback model when dealing with people we can forward the conversation in the following way:</p><ol><li><strong>When you…</strong><br><em>Explain the issue briefly, whether it’s something your colleague has done or said.</em></li><li><strong>I feel…</strong><br><em>Make it personal! Speak as a friend, not a manager. Explain what issue/s will arise or has arrived from their action/s. You describe the impact of this on your team and the project.</em></li><li><strong>Because…</strong><br><em>Here you describe the impact of his/her action on themselves. Explain the impact in detail.</em></li><li><strong>Pause for a response.</strong></li><li><strong>What I would like is…</strong><br><em>What they could do better so that the impact can be decreased.</em></li><li><strong>Because…</strong><br><em>Explain how they can create a positive impact on the team.</em></li><li><strong>What do you think about that?</strong><br><em>Let them agree or disagree.</em></li></ol><p>This model has helped me deal with people and also go through effective communication with the team members. Use these steps and find out if you can sort out the differences with your team members.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ac66d2f5a4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writer’s Unblock: Defeating Writer’s Block Inside Out]]></title>
            <link>https://samreenmalla.medium.com/writers-unblock-defeating-writer-s-block-inside-out-754fe98fb4fd?source=rss-e7b200bb96fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/754fe98fb4fd</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Samreen Malla]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 06:48:42 GMT</pubDate>
            <atom:updated>2020-09-01T06:48:42.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WoYmZLIsaaO3pp2A33vg5Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@m15ky?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mike Tinnion</a> on <a href="https://unsplash.com/s/photos/writing?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Writing is one of the essential forms of communication. Written communication can be in various forms like technical writing, blogs, articles, emails, letters, proposals, etc. When writing any content, it is crucial to have a free flow of thoughts and ideas. Any obstruction in the thought process can effect the writing process and the writer may not be able to comprehend their thoughts to words.</p><p>Have you had a hard time continuing something you wrote or even starting a fresh blog? You know what you want to write about but you feel like you have lost the words. Sometimes you start panicking and start thinking less of yourself? Get some fresh air, breathe and read this article :P</p><p>When you can’t start or continue a piece of writing, its not that you can’t write, or you are not creative enough. What you are going through is called “The Writer’s Block”, and most writers go through this unpleasant experience.</p><p>So what is this villainous thing that keeps us from writing? Let’s take a look,</p><blockquote>Writer’s block is a condition in which the author loses the ability to produce new work, or experiences creative slowdown. The difficulty may occur when producing new ideas or even during the continuation of an incomplete work. Writer’s block mostly occurs due to the conflict between the goal of writing well, and the fear of writing poorly. Between these two forces, the creative flow gets blocked.</blockquote><p>Also known as the blank screen syndrome, this phenomenon causes a paralysis on the flow of thoughts and ideas and deprives a writer to produce a new creation. Why its called the blank screen syndrome? Because sometimes, it becomes terrifying for the writer to face a blank screen.</p><p>So, what causes this to happen? Is it that my right brain has stopped functioning? Was I never creative enough? Should I give up writing and go back to the bank job, I had left to start my writing career?</p><p>Wooooaaahhhh hold on!</p><p>We all know writing is a challenging mental process. It requires utter focus, dedication, and time. There are many psychological and external factors affecting the state of mind of a writer, causing the blockage in his/her cognitive capabilities. Moreover, these factors can be anything from distraction, procrastination, and even fear of getting ridiculed. Some of the most common causes of writer’s block are:</p><h3>Causes</h3><p><strong>Perfectionism</strong></p><p>Most people use perfectionism as a protection mechanism to protect themselves from harsh critique or failure. Unfortunately, trying to write the perfect sentence, paragraph, or novel will lead most writers never to write a single word.</p><blockquote>Perfect is the enemy of the good; if we always strive for perfection, we will not even reach the level of “good.”</blockquote><p><strong>Self-criticism</strong></p><p>Most writers compare their work with the works of other, more successful writers. Creative writing is a daunting task. It is a skill that ripens with time and the amount of effort we pour in. Most writers criticize themselves way early on the process. Unrealistic expectations of oneself make us criticize our work. While we end up comparing out prototype 1 with prototype 10 of others, we won’t even be able to reach prototype 2.</p><p><strong>Anxiety</strong></p><p>Being anxious about one’s writing capability or the outcome of the writing itself can result in writer’s block. Whenever we are anxious, it makes us lose focus and interest in the thing we are doing and focuses on the worry instead. Fearing rejection, or setting a high expectation of oneself can lead to anxious behavior which can block the creative flow and hampers the writing process.</p><p><strong>Distraction</strong></p><p>In an era where we are connected all the time, it has become almost impossible for people to concentrate on their work. Writing is a cognition-heavy task, and when distracted frequently, it is difficult to put our thoughts together and write. If I am checking my phone every 5 minutes while I am seated down to complete an assignment, I won’t be able to write a single sentence in even an hour. Distraction is never a friend of creativity.</p><p><strong>Lack of research</strong></p><p>Whenever we are writing on a topic, we must research thoroughly on that topic. The more we know, the more we are confident in what we are delivering to our audience. Research always provides us with new topics to write and content to update. It always keeps the writer in a flow. After a thorough research, we can prepare an outline and structure the writing process. We can always benefit from research and planning ahead of time.</p><p>Now that we know what causes this obstruction, let’s find out how we can overcome this block and let out creativity take a never ending flow.</p><h3><strong>Overcoming the block</strong></h3><p>Some useful strategies that can be helpful are explained below:</p><p><strong>Confidence - you have something important to say:</strong></p><p>One of the major stressors for writers is the misconception that they do not have anything important or unique to offer. For any writer, it is essential to understand that they have a great deal to offer.</p><blockquote>Confidence is an incremental sequence of experiencing success in writing and developing the ability to write about abstract concepts.</blockquote><p>Confidence musters up ideas and makes writers able to write it down when necessary. Most of the time, having the confidence that we have something valuable to offer and delivering it, is the best way to avoid writer’s block.</p><p><strong>Stop delaying - “now” is the time:</strong></p><p>Most of the time, writers get indulged in a vast topic and get confused as to where to start. Writers need to identify and prioritize the topics. Also, delaying the writing and shifting it from time to time is a way to avoid writing. We should briefly plan on what we want to write about, create an outline, and then start writing there and then. When you sit down to write, there is no better time than “now’ to start.</p><p><strong>Comfort - find yourself a comfortable time, place, topic to write about:</strong></p><p>Comfort is one of the most critical factors that affect a writer’s writing habits. Finding the right place and time is very important for productive writing. Writing during the peak hour of productivity, in a setting with minimal distractions is one of the most effective ways to reduce writer’s block and foster productivity.</p><p><strong>Recognize yourself - reward yourself after each step of the process:</strong></p><p>Writing is hard work, and in order to make it fun, we should recognize and reward ourselves for writing. When we are writing for the sake of our task, it becomes monotonous and boring. When we include prizes and small appreciation by rewarding, we are more likely to continue writing. A pat on the back for writing or completing a significant part of the article, can boost a writer’s confidence.</p><p><strong>Take breaks -give yourself some time:</strong></p><p>Writing should not be monotonous and dreary. If and when we feel like we are running out of ideas, take breaks. Going for a walk, listening to music, a change of environment, or even sleeping it off can help to continue writing or completing it.</p><p><strong>Start writing -now is the right time:</strong></p><p>The most effective way to avoid writer’s block is by starting to write. Writing a few lines can be a huge help to restrain from writer’s block. Create a manuscript, make an ordered outline of what you want to include in your writing. The first paragraph can be the hardest, but after you finish the first paragraph, it will get easier as it goes.</p><p>Honestly, I was having a writer’s block before I started writing this blog. I was confused if I could deliver what I wanted to say. But here I am, writing the concluding lines of this article.</p><p>Writing should not be taken as a task or a monotonous activity. It should be fun. Experiencing writer’s block is common, let’s not try to run away from it. Now that we know how we can overcome this villain, let’s start making our creations the heroes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=754fe98fb4fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>