<?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 Bogdan Cirlig on Medium]]></title>
        <description><![CDATA[Stories by Bogdan Cirlig on Medium]]></description>
        <link>https://medium.com/@bogdancirlig?source=rss-be86a66caebe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*377ogc3Io3MgtTfC6uTggA.jpeg</url>
            <title>Stories by Bogdan Cirlig on Medium</title>
            <link>https://medium.com/@bogdancirlig?source=rss-be86a66caebe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:37:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bogdancirlig/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[Ensuring Software Quality: A Commitment to Excellence and the End User]]></title>
            <link>https://medium.com/@bogdancirlig/ensuring-software-quality-a-commitment-to-excellence-and-the-end-user-5ec1c7e1230e?source=rss-be86a66caebe------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ec1c7e1230e</guid>
            <category><![CDATA[software-quality-testing]]></category>
            <category><![CDATA[voice-of-the-customer]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Bogdan Cirlig]]></dc:creator>
            <pubDate>Thu, 24 Aug 2023 23:28:37 GMT</pubDate>
            <atom:updated>2023-08-24T23:28:37.161Z</atom:updated>
            <content:encoded><![CDATA[<p>In the dynamic landscape of software development, a central tenet remains unchanged: the quality of software is paramount. There’s a direct correlation between software quality and user satisfaction. We often say that our customers “vote” with their wallets and take their business somewhere else. However, the concept of ‘quality’ can be amorphous. Here, we’ll delve into why ensuring quality is indispensable and how engineering teams can effectively monitor and enhance the quality of the features they release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TAnBigsMwy0b6disLx9DyA.png" /></figure><h4>The Bedrock: Why Quality Matters</h4><p><strong>Trust &amp; Brand Image</strong>: High-quality software fosters trust. Users rely on applications to perform consistently and securely. Every bug or performance issue erodes this trust, impacting not just the software’s perception but the overarching brand image.</p><p><strong>Business Metrics</strong>: Quality isn’t just about aesthetics or smooth functioning. It directly influences business metrics. Crash rates, slow performance, or bugs can lead to user attrition, reduced engagement, and eventually, lost revenue.</p><p><strong>Efficiency &amp; Cost</strong>: Revisiting and rectifying mistakes is both time-consuming and expensive. By ensuring quality at the outset, teams can reduce the long-term costs associated with maintenance and troubleshooting.</p><h4>Quantitative Signals: The Tangible Metrics</h4><p>Engineering teams need a robust set of metrics to evaluate the quantitative aspects of software quality. These include:</p><p><strong>Error Rates</strong>: Monitor crash reports and error logs. An uptick can indicate problems with the latest release.</p><p><strong>Performance Metrics</strong>: Response times, load times, and other performance metrics can give insights into the software’s efficiency.</p><p><strong>Usage Metrics</strong>: If a new feature is rarely used or leads to a decrease in engagement, it might be misaligned with user needs or have usability issues.</p><p><strong>Automated Test Results</strong>: A comprehensive suite of automated tests — unit tests, integration tests, and end-to-end tests — should consistently pass. Failures here are a direct indicator of quality concerns.</p><h4>Qualitative Signals: The User’s Voice</h4><p>While quantitative metrics offer a tangible measure, qualitative feedback gives context and depth. They highlight the ‘why’ behind the numbers.</p><p><strong>User Feedback &amp; Reviews</strong>: Users are the best critics. Regularly solicit feedback and monitor reviews to understand the user experience.</p><p><strong>Usability Testing</strong>: Before fully releasing a feature, conduct usability tests to gather firsthand insights into its intuitiveness and usefulness.</p><p><strong>Internal Feedback</strong>: Often, your team knows the product best. Encourage internal feedback sessions where team members can voice concerns or suggestions about new features.</p><p><strong>Customer Support Interactions</strong>: Monitor the queries and complaints coming into your support channels. Are there recurrent issues? Is a particular feature repeatedly causing confusion?</p><h4>Ensuring Quality: Best Practices</h4><p><strong>Shift Left</strong>: The earlier you detect an issue, the cheaper and easier it is to fix. Implement rigorous testing early in the development cycle.</p><p><strong>Continuous Integration &amp; Continuous Deployment (CI/CD)</strong>: Automate testing and deployment to ensure that only thoroughly vetted code reaches the end user.</p><p><strong>Feedback Loops</strong>: Establish fast feedback loops with users. Tools like feature flags can help in rolling out features gradually and gathering feedback.</p><p><strong>Invest in Training</strong>: Regularly upskill your team. The better trained your engineers are, the higher the quality of the software they produce.</p><p><strong>Iterative Development</strong>: Accept that not every feature will be perfect initially. Instead, aim for continuous improvement, iterating based on both quantitative metrics and qualitative feedback.</p><p>In conclusion, ensuring software quality isn’t just a technical requirement; it’s a commitment to the end user. It’s about delivering value, fostering trust, and constantly striving for excellence. By effectively balancing quantitative and qualitative signals, engineering teams can pave the way for products that truly resonate with users and stand the test of time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ec1c7e1230e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maximizing Efficiency and Excellence: The Significance of Operational Metrics in Software…]]></title>
            <link>https://medium.com/@bogdancirlig/maximizing-efficiency-and-excellence-the-significance-of-operational-metrics-in-software-87569073ad45?source=rss-be86a66caebe------2</link>
            <guid isPermaLink="false">https://medium.com/p/87569073ad45</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[accountability]]></category>
            <category><![CDATA[operational-excellence]]></category>
            <category><![CDATA[efficiency]]></category>
            <category><![CDATA[results-oriented]]></category>
            <dc:creator><![CDATA[Bogdan Cirlig]]></dc:creator>
            <pubDate>Tue, 08 Aug 2023 17:42:27 GMT</pubDate>
            <atom:updated>2023-08-08T17:42:27.986Z</atom:updated>
            <content:encoded><![CDATA[<h3>Maximizing Efficiency and Excellence: The Significance of Operational Metrics in Software Engineering Teams</h3><p>In today’s rapidly evolving technological landscape, the success of any software engineering team hinges on their ability to not only ideate and innovate but to execute and deliver efficiently. The key to achieving this balance lies in the strategic utilization of operational metrics. These metrics serve as compass points guiding engineering teams towards their goals while enabling continuous improvement. In this article, we’ll delve into the importance of operational metrics and discuss why they are crucial for the successful execution and delivery of product engineering projects. We will also explore typical metrics for various categories that provide valuable insights into team performance and project progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*U9aryUtvK0RJESLymFlTxw.jpeg" /></figure><h3>Why Operational Metrics Matter</h3><p><strong>Performance Tracking</strong>: Operational metrics provide a quantifiable way to assess the performance of software engineering teams. They offer an objective view of how effectively teams are working towards their objectives and deadlines, aiding in identifying areas for improvement.</p><p><strong>Data-Driven Decision Making</strong>: Metrics empower engineering leaders with data-driven insights that allow them to make informed decisions. Instead of relying on gut feelings, decisions can be backed by concrete evidence, leading to better resource allocation and strategic planning.</p><p><strong>Continuous Improvement</strong>: By consistently monitoring operational metrics, teams can identify bottlenecks, process inefficiencies, and areas of suboptimal performance. This data-driven approach to improvement ensures that teams are always striving to enhance their processes.</p><p><strong>Transparency and Accountability</strong>: Metrics promote transparency within teams, enabling team members to understand their roles, contributions, and how their efforts align with broader goals. Moreover, metrics foster a culture of accountability, as progress is visible and can be tied directly to individual and team efforts.</p><h3>Key Operational Metric Categories and Their Importance</h3><p><strong>Velocity and Throughput</strong>:</p><ul><li>Metric: Sprint velocity (story points completed per iteration)</li><li>Importance: Measures the rate at which user stories or tasks are completed, providing insight into team efficiency and project progress. It also helps in predicting future delivery dates more accurately.</li><li>Caution: Teams are not goaled on how many sprint points they deliver, rather they use this metric to make better estimates of the workload and promises to deliver a certain volume of features. (will talk later about Say-Do ratios)</li></ul><p><strong>Goal / OKR tracking</strong>:</p><ul><li>Measures: How well the team deliveries are yielding the expected business goals (i.e. Revenue, Subscriptions, Daily Users, etc)</li><li>Importance: In results oriented teams that are empowered to choose to focus on most impactful problem statements, this metric tracks and predicts how well the shipped features are yielding the expected business result. This requires instrumentation of a real time analytics platform and A/B testing for every feature shipped.</li></ul><p><strong>Lead and Cycle Time</strong>:</p><ul><li>Metric: Lead time (time from task creation to completion)</li><li>Metric: Cycle time (time taken to complete a task)</li><li>Importance: These metrics highlight process efficiency, enabling teams to identify delays and streamline workflows. Shorter lead and cycle times result in faster delivery and more responsive teams. Use this to understand if User Stories take a long time to be ready for implementation, or if Design phase takes a long time or Compliance and Legal adds too much time. Work on reducing those times so teams can ship features quicker.</li></ul><p><strong>Deployment Frequency</strong>:</p><ul><li>Measures: How often code is deployed to production.</li><li>Importance: Reflects the frequency of releasing new features or updates, which can impact user satisfaction and business agility. Highly performing teams are able to deliver quick and often to enable them to measure customer impact and quickly test PMF hypothesis. Highly performing teams have achieved a continuous integration abd deployment (CI&amp;D) state where committed code is automatically deployed to production and made available to customers.</li></ul><p><strong>Quality and Defects</strong>:</p><ul><li>Metric: Defect density (number of defects per unit of work)</li><li>Importance: Demonstrates the quality of deliverables. Tracking defects helps in pinpointing code or process issues, allowing teams to focus on code quality and reducing the risk of post-release issues.</li></ul><p><strong>Test Coverage</strong>:</p><ul><li>Measures: Percentage of code covered by automated tests.</li><li>Importance: Evaluates the thoroughness of testing efforts and helps identify areas with insufficient test coverage. Automated testing enables teams to ship features quickly and have the safety net of not pushing out code breaking changes.</li></ul><p><strong>Mean Time to Recovery (MTTR)</strong>:</p><ul><li>Measures: Average time taken to recover from incidents or outages.</li><li>Importance: Reflects the team’s ability to identify and resolve issues promptly, minimizing downtime and user impact. Use a severity scale to categorize such incidents and work to define an acceptable SLA for them to be mitigated and then resolved. It’s important to focus on rapid mitigation to limit customer and company impact. To use an analogy, you have a pipe leak, how fast can you stop the leak and then focus on a permanent fix.</li></ul><p><strong>Technical Debt</strong>:</p><ul><li>Measures: Accumulated technical debt (e.g., overdue refactorings, postponed optimizations).</li><li>Importance: Helps manage and prioritize technical debt reduction efforts to maintain long-term codebase health. If ignored, the tech debt will have major side effects in how maintainable the codebase is and will add increased dissatisfaction in the engineering team which most likely will surface as a lagging indicator in yourPulse surveys.</li></ul><p><strong>Burnup and Burndown Charts</strong>:</p><ul><li>Measures: Progress of work completed (burnup) or remaining (burndown) over time.</li><li>Importance: Visualizes project progress and aids in predicting if the team will meet deadlines. Uses the moving average of the team velocity in predictions hence an honest estimate of sprint over sprint velocity will help the team make more accurate workload delivery predictions.</li></ul><p><strong>On-time Delivery (Say-Do ratio)</strong>:</p><ul><li>Measures: Percentage of projects or features delivered on schedule.</li><li>Importance: Ensures that the team is consistently meeting commitments and delivering value within the expected timeframe. Aim for 90% minimum for a well calibrated team. It is OK if teams slightly overpromise, that is on purpose to ensure optimal utilization of team capacity.</li></ul><p><strong>Employee Satisfaction and Turnover (Pulse surveys)</strong>:</p><ul><li>Measures: Employee engagement and retention rates.</li><li>Importance: Indicates the health of the engineering team and helps identify areas for improvement in team morale and management.</li></ul><p><strong>Infrastructure availability</strong>:</p><ul><li>Measures: The promise to the customers to be available</li><li>Importance: If you subscribe to the mantra that a customer hires a product to do a specific task for them then this metric measures how well the team is delivering on that promise to the customer. The usual metrics here look at API/Service uptime %, error rate per successful transactions, example failed payments rate for a payment API.</li></ul><p>In conclusion, operational metrics are the compass that guides product engineering teams towards successful execution and delivery. By utilizing metrics strategically, engineering leaders can make informed decisions, foster continuous improvement, and ensure transparency and accountability within teams. Whether it’s tracking velocity, assessing quality, or optimizing resource utilization, operational metrics empower teams to thrive in a dynamic and competitive environment. Through the regular analysis of these metrics, engineering teams can iterate on their processes, elevate their performance, and consistently deliver outstanding results.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87569073ad45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Holistic Product Ideation Framework: Empowering Voices and Driving Success]]></title>
            <link>https://medium.com/@bogdancirlig/a-holistic-product-ideation-framework-empowering-voices-and-driving-success-e4636e4a4194?source=rss-be86a66caebe------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4636e4a4194</guid>
            <category><![CDATA[product-market-fit]]></category>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[brainstorming]]></category>
            <category><![CDATA[product-ideation]]></category>
            <dc:creator><![CDATA[Bogdan Cirlig]]></dc:creator>
            <pubDate>Fri, 28 Jul 2023 04:19:38 GMT</pubDate>
            <atom:updated>2023-07-28T13:46:02.184Z</atom:updated>
            <content:encoded><![CDATA[<p>Innovation is the lifeblood of any successful business, fueling growth and enabling organizations to stay ahead of the curve. To achieve meaningful and impactful product innovation, businesses need a comprehensive framework that incorporates diverse perspectives, data-driven insights, and iterative testing. In this article, we will explore a robust product ideation framework designed to leverage collaborative tools, customer insights, and data science, culminating in a successful go-to-market strategy.</p><figure><img alt="Product Ideation" src="https://cdn-images-1.medium.com/max/1024/1*PY-RMgdZhZIQp2qSXtN3_w.jpeg" /></figure><h3>Phase 1: Defining the Goal of the Ideation Exercise</h3><p>The product ideation journey commences with a clear definition of the goal. Whether the aim is to enter a new market, attract a new customer segment, or address emerging needs, a well-defined goal sets the direction for subsequent phases.</p><h3>Phase 2: Leveraging Collaborative Tools for Inclusive Ideation</h3><p>Inclusive ideation is essential for cultivating a culture of innovation within the organization. Collaborative tools like Figma or Miro provide a digital canvas for remote teams, including product, engineering, user research, stakeholders, and on-ground personnel, to participate and contribute their valuable insights. By involving everyone with knowledge of the target customer and market, a rich pool of ideas emerges.</p><h3>Phase 3: Formulating Customer-Centric Problem Statements</h3><p>A common modern approach is Design Thinking, a human-centered approach to innovation that emphasizes understanding the needs and desires of users. It consists of five stages: Empathize, Define, Ideate, Prototype, and Test. During the ideation stage, team members generate a wide range of ideas to address the identified user needs. This process encourages creativity and collaboration and allows teams to explore multiple potential solutions before settling on a final concept. With a wealth of ideas at hand, the focus shifts to identifying patterns and common themes. Clustering similar ideas helps uncover potential opportunities that align with the overarching goal. These ideas are then translated into customer-centric problem statements, articulating the needs and challenges in a language that resonates with the target audience.</p><h3>Phase 4: Ranking Opportunities Based on Value to Customers and the Company</h3><p>To prioritize the problem statements effectively, teams must consider both customer value and business value together. Using data science, organizations can analyze the potential impact of each opportunity on customers and the company in terms of metrics that could be Revenue, Engagement, Subscriptions, etc. This data-driven approach ensures that the most valuable initiatives receive appropriate attention and resources. The end goal is to have a clear sense for each idea generated, why is it worth doing it.</p><h3>Phase 5: Pressure Testing Ideas with Target Customers</h3><p>Early validation of ideas with target customers is critical to success. Just because an idea seems viable from a business standpoint does not guarantee its acceptance by customers. Engaging with customers early on, gathering feedback, and validating assumptions helps avoid costly missteps and collects early product-market fit (PMF) signals.</p><h3>Phase 6: Assessing Feasibility and Risk</h3><p>Following validation, the next phase involves assessing the feasibility and associated risks of pursuing the proposed solutions. Evaluating technical constraints, resource availability, and potential challenges allows organizations to make informed decisions and manage potential hurdles proactively. In large organizations it’s very common to encounter dependencies on other parts of the company that might not have the same priorities as your team. In small companies its a function of funds and resource availability. there is always a maximum number of ideas you can pursue at any given time.</p><h3>Phase 7: Creating a Minimum Viable Product (MVP) for Rapid Testing</h3><p>To test assumptions quickly and effectively, developing an MVP or prototype is essential. By focusing on a small, statistically representative customer segment, businesses can obtain targeted feedback and iterate rapidly, refining the product based on real user insights. Define objective Go/No-Go milestones when the team assesses if they should pivot, persevere or deem that idea unfeasible.</p><h3>Phase 8: Measuring Success and Conducting A/B Tests</h3><p>Measuring the success of the product against predefined success criteria is crucial for continuous improvement. A/B testing can be employed to compare different features or versions, ensuring that each iteration is optimized for the best customer experience.</p><h3>Phase 9: Defining a Go-to-Market Strategy</h3><p>With a successful MVP in hand, it’s time to devise a well-defined go-to-market strategy. This comprehensive plan outlines how the product will be launched, marketed, and distributed to the target audience, ensuring a successful market entry.</p><h3>Conclusion:</h3><p>A robust product ideation framework that incorporates collaborative ideation, customer validation, data science, and iterative testing is paramount for teams seeking to drive meaningful growth and stay ahead of the competition. By leveraging diverse perspectives, involving on-ground personnel, and staying agile throughout the process, businesses can bring transformative products to the market and build lasting connections with their customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4636e4a4194" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Pursuit of Product-Market Fit: Lessons from the Lean Startup and Customer-Centric Approach]]></title>
            <link>https://medium.com/@bogdancirlig/the-pursuit-of-product-market-fit-lessons-from-the-lean-startup-and-customer-centric-approach-97f92ddc361d?source=rss-be86a66caebe------2</link>
            <guid isPermaLink="false">https://medium.com/p/97f92ddc361d</guid>
            <category><![CDATA[experimentation]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[product-market-fit]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Bogdan Cirlig]]></dc:creator>
            <pubDate>Mon, 24 Jul 2023 16:16:11 GMT</pubDate>
            <atom:updated>2023-07-24T16:16:11.848Z</atom:updated>
            <content:encoded><![CDATA[<p>Launching new products or features can be a daunting endeavor for tech focused teams. However, with the right approach, they can greatly increase their chances of success in finding product-market fit (PMF). Inspired by Eric Reis’ influential book, “<a href="https://www.amazon.com/The-Lean-Startup-Eric-Ries-audiobook/dp/B005MM7HY8/ref=sr_1_1">The Lean Startup</a>”, and drawing insights from my direct experience going through Y-Combinator and their emphasis on customer interactions, Customer Experience Design class from Stanford GSB, and “<a href="https://hbswk.hbs.edu/item/clay-christensen-the-theory-of-jobs-to-be-done">Jobs to Be Done</a>” theory by Clay Christensen, engineering teams can navigate the complex journey towards PMF more effectively. In this article, we will delve into the core principles of successful product launches and recommend “The Lean Startup” as essential reading for any aspiring entrepreneur.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZHDgqpRPzweoDbcKded6Q.jpeg" /></figure><h3>Talk to Your Customer: Understanding the “Jobs to Be Done”</h3><p>A key component of any successful product launch is understanding the needs and pain points of your target customers. Instead of solely relying on assumptions and hypotheses, successful product/engineering teams actively engage in regular conversations with potential customers. This approach, emphasized by Y-Combinator’s “talk to your customer” mantra, allows teams to uncover valuable insights about the “jobs to be done” — the core problems that customers seek to solve with your product.</p><p>By empathizing with the customer and gaining a deep understanding of their needs, teams can align their product development efforts with real-world demands. This customer-centric approach serves as a foundation for building products that genuinely address the pain points and deliver value.</p><h3>Decision-making at Inflection Points: Pivot or Persevere</h3><p>Throughout the product development journey, teams inevitably encounter inflection points where important decisions need to be made. These critical moments often present opportunities to either pivot or persevere. The Lean Startup methodology encourages a data-driven decision-making process during these junctures. Pivoting is an essential decision and a hard one to make but will save the agony of investing time and resources into a product or feature that is “ok” or “nice to have” but it does not catch fire and only serves the needs of a very small subset of your target customers.</p><p>Customer feedback and data gathered through interactions play a crucial role in determining the path forward. If the initial product hypothesis does not resonate with customers, a pivot may be necessary to adjust the product’s direction. On the other hand, if customer responses indicate a promising trajectory, the team can confidently persevere and continue refining their offering. The teams need to be ready to accept failure (lack of PMF) and continue to push forward to experiment and discover eventual PMF.</p><h3>Clear Metrics for Success: Measuring Progress Towards PMF</h3><p>To achieve PMF, teams must set clear and measurable success metrics. These metrics act as signposts, guiding the team towards their objectives and indicating when they’ve achieved PMF. Employing Customer Journey Maps with delighters and detractors help identify key touchpoints where success metrics can be effectively monitored.</p><p>By tracking these metrics, teams can objectively assess the impact of their product in the market and identify areas that require improvement. This data-driven approach helps teams remain focused on continuous improvement and enables them to make informed decisions throughout the product development lifecycle.</p><h3>Avoiding Feature Creeping and Shipping Timely: Embrace Minimum Viable Product (MVP)</h3><p>One common pitfall in product development is feature creeping, where a product accumulates unnecessary features that may not align with the core customer needs just because the team feels the product is missing one more feature that might bring the much needed PMF. The Lean Startup encourages a disciplined approach to product development through the concept of a Minimum Viable Product (MVP). MVP entails building the simplest version of the product that solves the customer’s primary problem.</p><p>By adhering to the MVP philosophy, engineering teams can avoid unnecessary complexity and focus on delivering value quickly. Rapid prototyping and launching MVPs enable teams to receive early feedback from customers, validate assumptions, and iterate faster. The combination of Mono repositories and automation, such as Continuous Integration and Delivery (CI/CD) pipelines, and test automation further accelerates the development process, leading to faster iterations and higher chances of achieving PMF.</p><h3>Conclusion</h3><p>Launching new products and finding PMF is a challenging process, but by applying principles from “<a href="https://www.amazon.com/The-Lean-Startup-Eric-Ries-audiobook/dp/B005MM7HY8/ref=sr_1_1">The Lean Startup</a>” book and incorporating customer-centric practices like Customer Experience Design and Jobs to Be Done theory, teams can greatly enhance their chances of success. Embrace a culture of constant customer interaction, data-driven decision-making, and clear success metrics to keep your product on the right track. By avoiding feature creeping and embracing MVP principles alongside the power of mono-repositories and automation, teams can rapidly prototype, launch, and measure success. For anyone aspiring to create innovative products and achieve PMF, “<a href="https://www.amazon.com/The-Lean-Startup-Eric-Ries-audiobook/dp/B005MM7HY8/ref=sr_1_1">The Lean Startup</a>” is a must-read guide on this exhilarating journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97f92ddc361d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Five Levels of Leadership: Securing Permission to Lead]]></title>
            <link>https://medium.com/@bogdancirlig/the-five-levels-of-leadership-securing-permission-to-lead-92a14a21d9cb?source=rss-be86a66caebe------2</link>
            <guid isPermaLink="false">https://medium.com/p/92a14a21d9cb</guid>
            <category><![CDATA[building-trust-at-work]]></category>
            <category><![CDATA[developing-people]]></category>
            <category><![CDATA[influence]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Bogdan Cirlig]]></dc:creator>
            <pubDate>Thu, 20 Jul 2023 17:02:44 GMT</pubDate>
            <atom:updated>2023-07-20T17:02:44.745Z</atom:updated>
            <content:encoded><![CDATA[<p>Leadership is not solely defined by a job title or a position of authority. True leadership goes beyond hierarchy; it requires the ability to secure permission from people who report into you or from stakeholders you want to influence. This concept is beautifully articulated in John Maxwell’s book, “<a href="https://www.amazon.com/Levels-Leadership-Proven-Maximize-Potential-ebook/dp/B004QZ9P7O">The Five Levels of Leadership</a>,” a transformative guide that emphasizes the importance of earning the trust and respect of your team. Inspired by my mentor, <a href="https://www.linkedin.com/in/srishivananda/">Sri Shivananda</a>, the CTO of PayPal, who recommended this book to me several years ago, I will delve into the significance of securing permission to lead and how it plays a vital role in establishing oneself and building a positive influence within a new organization. Way too often I hear of leaders coming into a new organization or taking over a new team and they go in “hot” before securing permission to lead.</p><figure><img alt="The Five Levels of Leadership: Securing Permission to Lead" src="https://cdn-images-1.medium.com/max/800/1*7tiFpZ8pKPWV7b3Jt9nxYQ.jpeg" /></figure><h3><strong>Level 1: Position</strong></h3><p>The lowest level of leadership is based solely on a person’s position or title within an organization. While this level grants some authority, it does not automatically instill trust or inspire others to follow. Leaders at this level often encounter resistance, skepticism, and limited influence. Merely holding a position does not guarantee success or create lasting impact. Many people fail by trying to lead from a position of apparent power.</p><h3><strong>Level 2: Permission</strong></h3><p>To move beyond the limitations of position-based leadership, leaders must secure permission from their team members to lead effectively. Permission is earned through building relationships, demonstrating competence, and fostering an environment of trust. Leaders who prioritize establishing meaningful connections with their teams gain the respect and commitment necessary to influence positive change. (see my article about Leading without Authority)</p><p><strong>Building Trust</strong>: Securing permission begins with building trust, a crucial foundation for leadership success. Trust is established by consistently delivering on promises, actively listening to team members, valuing their opinions, and demonstrating authenticity. When leaders cultivate trust, their teams become more willing to follow their guidance and embrace their vision.</p><p><strong>Demonstrating Competence</strong>: Competence is another key aspect of securing permission to lead. Leaders must possess the necessary skills and knowledge to guide their teams effectively. By continuously developing their expertise and staying up-to-date with industry trends, leaders demonstrate their commitment to personal and professional growth. Competence builds credibility and instills confidence in team members, further solidifying their permission to lead.</p><h3>Level 3: Production</h3><p>At this level, leaders prove their worth by consistently achieving results and fostering a productive work environment. By focusing on setting clear goals, empowering team members, and providing the necessary resources, leaders create a culture of high performance. Leaders who prioritize production not only earn the respect of their teams but also cultivate a positive influence that encourages others to go the extra mile.</p><h3>Level 4: People Development</h3><p>Leaders who reach level four understand the importance of investing in the growth and development of their team members. They recognize that by empowering and equipping their people, they multiply their impact and create a legacy of leadership. Through mentorship, coaching, and providing growth opportunities, leaders at this level inspire loyalty, nurture talent, and build a pipeline of future leaders.</p><h3>Level 5: Pinnacle</h3><p>The pinnacle of leadership is achieved when leaders develop other leaders. At this level, leaders have secured permission to lead at such a profound level that their influence extends beyond their immediate sphere of control. They have created a lasting legacy by building a culture of leadership, where others are empowered to make a positive impact and continue the cycle of securing permission to lead.</p><h3>Conclusion</h3><p>By focusing on building trust, demonstrating competence, and prioritizing people development, leaders can ascend through the levels, ultimately reaching the pinnacle of leadership, where their impact extends far beyond their immediate circle. Remember, true leadership is not about the position; it is about securing permission to lead and inspiring others to follow. What level are you at? Please share your experience by commenting on the article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92a14a21d9cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leading Without Authority: Harnessing Influence in the Workplace]]></title>
            <link>https://medium.com/@bogdancirlig/leading-without-authority-harnessing-influence-in-the-workplace-76b5d2d01d2b?source=rss-be86a66caebe------2</link>
            <guid isPermaLink="false">https://medium.com/p/76b5d2d01d2b</guid>
            <category><![CDATA[influence]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Bogdan Cirlig]]></dc:creator>
            <pubDate>Tue, 18 Jul 2023 19:04:35 GMT</pubDate>
            <atom:updated>2023-07-18T19:13:44.793Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s complex work environment, leadership is not limited to those with formal authority. The ability to lead without authority is a valuable skill that can drive collaboration, innovation, and success within organizations. <a href="https://www.keithferrazzi.com/">Keith Ferrazzi</a>, renowned author and expert in networking and leadership, explores this concept in his book “<a href="https://www.amazon.com/Leading-Without-Authority-Co-Elevation-Collaboration/dp/0525575669">Leading Without Authority</a>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C8PCVjdxFyaJqNAh4nUm2g.png" /></figure><p>I read this book few years ago and I truly enjoyed applying these principles at my last workplaces <a href="http://meta.com/">Meta</a> and <a href="http://paypal.com/">Paypal</a> and through my mentoring of upcoming leaders I found myself often referring back to Keith’s book and learnings when people worked on their influencing skills vs escalating to their VP to get alignment. In this article, I will delve into some key takeaways from Ferrazzi’s book and explore strategies for exerting influence in the workplace.</p><h3>Build relationships to drive influence</h3><p>One of the fundamental principles of leading without authority is building strong relationships. Take the time to cultivate genuine connections with your colleagues and stakeholders. By establishing trust and rapport, you can influence others and gain their support. Ferrazzi emphasizes the importance of investing in relationships as a foundation for effective leadership.</p><h3>Collaborate and create coalitions</h3><p>Leading without authority often necessitates collaboration and teamwork. Seek out opportunities to work together with others, leveraging their expertise and resources. By forming coalitions and aligning interests, you can amplify your impact and achieve shared goals.</p><h3>Proactive approach</h3><p>To lead without authority, it’s crucial to be proactive. Take the initiative to identify problems, propose solutions, and take action. Demonstrating initiative and a proactive mindset can inspire others to follow your lead and contribute to organizational success. Ferrazzi encourages individuals to seize opportunities and make a positive impact through proactive leadership.</p><h3>Effective communication</h3><p>Clear and effective communication is essential when leading without authority. Articulate your ideas, thoughts, and expectations with clarity. Actively listen to others and strive to understand their perspectives. Effective communication builds credibility and enables you to influence others.</p><h3>Demonstrate expertise and credibility</h3><p>Becoming a subject matter expert is crucial when leading without authority. Continuously develop your knowledge and skills to gain credibility among your peers. When others recognize your expertise, they are more likely to follow your lead, even in the absence of formal authority.</p><h3>Embrace accountability</h3><p>Accountability is a key aspect of leading without authority. Take ownership of your actions and outcomes. Holding yourself accountable for commitments and consistently delivering results fosters trust and respect from others. Ferrazzi stresses the significance of accountability as a foundation for leading without formal authority.</p><h3>Adaptability in a changing environment</h3><p>Adaptability is essential for successful leadership without authority. Embrace change and be willing to adjust your approach as circumstances evolve. Stay flexible and open-minded, encouraging others to do the same. Ferrazzi recognizes the dynamic nature of today’s work environment and underscores the importance of adaptability in effective leadership.</p><h3>Lead by example</h3><p>Setting a positive example is a powerful way to lead without authority. Demonstrate integrity, resilience, and a strong work ethic. Be a role model for others, inspiring them through your behavior and actions. Leading through influence requires being a positive influence yourself.</p><h3>Conclusion:</h3><p>Leading without authority is a skill that can elevate your impact within the workplace. You can harness influence and drive collaboration, innovation, and success. Building relationships, collaborating, being proactive, communicating effectively, demonstrating expertise, embracing accountability, adapting to change, and leading by example are key strategies for leading without formal authority. Embrace these principles, and become a catalyst for positive change in your organization.</p><p>Remember, leadership is not limited to a title or position — it is a mindset and a set of behaviors. With the right approach, anyone can lead without authority and make a significant impact. Keith Ferrazzi’s book <a href="https://www.amazon.com/Leading-Without-Authority-Co-Elevation-Collaboration/dp/0525575669">Leading Without Authority</a>, serves as a valuable guide on this journey to effective leadership. I encourage you to read it and share your opinions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76b5d2d01d2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>