<?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 Chris Bartolo on Medium]]></title>
        <description><![CDATA[Stories by Chris Bartolo on Medium]]></description>
        <link>https://medium.com/@chrisbartolo?source=rss-b797fc8b8eea------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*m_gmSVqhgVCvB-QeNJg_Ww.jpeg</url>
            <title>Stories by Chris Bartolo on Medium</title>
            <link>https://medium.com/@chrisbartolo?source=rss-b797fc8b8eea------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:14:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisbartolo/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[Beyond the Daily Grind: Finding Fulfilment in Your Career]]></title>
            <link>https://medium.com/beyond-agile-leadership/beyond-the-daily-grind-finding-fulfilment-in-your-career-57433a2483fb?source=rss-b797fc8b8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/57433a2483fb</guid>
            <category><![CDATA[coaching-and-consulting]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ctotalk]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Chris Bartolo]]></dc:creator>
            <pubDate>Tue, 16 Jul 2024 22:13:46 GMT</pubDate>
            <atom:updated>2024-07-16T22:13:46.503Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J2KPpWbV843G0wkE6l8cHQ.png" /></figure><p>In a <a href="https://medium.com/@chrisbartolo/redefining-leadership-the-power-of-collective-success-b35e5516c160">previous article</a>, I explored how transforming an “I” culture into a “we” culture led to collective success and better results for the company as a whole. While that learning was significant, it didn’t capture the full scope of my experience and growth. Reflecting on my journey, I’ve realised there are more nuanced lessons that are often overlooked by others in similar situations.</p><h3>The Initial Struggle</h3><p>When I joined the startup, I was filled with disappointment and anger. The company was in a dire state — no budgets for growth, numerous vacant roles, and a general lack of motivation among the staff. It was a challenging environment, to say the least. As a young, ambitious, and highly motivated individual, I found myself stuck in tasks that didn’t excite me. I felt like I could do my job with my eyes closed, which left me frustrated and unfulfilled.</p><h3>Internal Conflict</h3><p>I struggled internally with the business decisions and directions that didn’t make sense to me. Why were certain people still part of the team? Why was the company content with the status quo? These questions plagued me as I tried to implement changes. I built teams, set up the technical structure, introduced agile methodologies, and more, yet I still felt something was missing.</p><h3>A Shift in Perspective</h3><p>In my frustration, I vented to peers and former colleagues, seeking validation for my feelings. It wasn’t until I combined their calm, measured advice that my perspective began to shift. Here are the key lessons I learned:</p><h4>Lesson 1: Filling the Gaps</h4><p><strong>Problem:</strong> Why keep someone if we end up doing their job?</p><p><strong>Answers:</strong></p><ol><li>If we don’t do it, it won’t get done, so we just have to do it.</li><li>When we fill gaps, it masks the issue from the business, making it our problem, not theirs.</li></ol><p><strong>Solutions:</strong></p><ol><li>Do the work, bring up the issue, and hope it gets addressed.</li><li>Don’t do the work, let the business feel the gap, and force them to act on it, accepting the interim consequences.</li></ol><h4>Lesson 2: Recognising Growth Opportunities</h4><p><strong>Problem:</strong> I’m not learning anything new; I can do this with my eyes closed.</p><p><strong>Answers:</strong></p><ol><li>It’s egotistical to think you know it all. Keep a journal to reflect on your day and identify areas for growth.</li><li>Reflect on past experiences where you had to learn by doing, even when it wasn’t part of your expected role. One of my peers reminded me of the diverse challenges I faced in a previous job, where I had to set up enterprise-level physical infrastructure, design a server room, create and manage a team from scratch, and even handle office logistics like choosing the coffee machine.</li></ol><p><strong>Combined Insight:</strong> There are always gaps in a company. By filling these gaps, we prevent the business from recognising and addressing its own issues. It’s tough, but sometimes we have to do the work to ensure the team doesn’t suffer, while also recognising the hidden growth opportunities in seemingly mundane tasks.</p><h3>Embracing Unseen Opportunities</h3><p>Realising I was learning in unexpected ways was a turning point. I never anticipated managing tight budgets, handling HR policies, juggling office management, and navigating compliance and regulation. These experiences were invaluable, teaching me skills I hadn’t set out to learn but were crucial for my personal and professional growth.</p><p>I was learning a lot, and it was these experiences that truly broadened my capabilities. The fact that I could manage my primary job easily actually freed up time for me to delve into other areas like information security, obtaining iGaming licenses in various jurisdictions, budgeting, and office management.</p><h3>The Trap of Stagnation</h3><p>We all fall into cycles where we feel stuck, doing the same things repeatedly. When this happens, it’s important to take a step back, change our focus, and find value in the tasks we overlook. Each task, no matter how trivial it seems, contributes to our growth. By learning to do them well, we drive our personal development and make the experience worthwhile.</p><h3>Paying It Forward: Helping Others See the Value</h3><p>A few months ago, a manager who I had worked with in the past as a junior developer came to me for advice. He was in a tough spot, feeling like he was stagnating. He felt he had nothing left to learn in his job and had become an expert in his technical area.</p><p>I shared my story with him and started by saying, “Stop looking at your job as just a developer’s job.” Before this role, he had never managed people, given guidance, mentored, or motivated others. When I asked if he was doing that now, he admitted he wasn’t. He had become so focused on being a strong developer that he hadn’t transitioned into his new role as a manager effectively.</p><p>By shifting his focus and gaining a new perspective, he realised the value he was missing and the gap he was creating within his team. He began to work on mentoring and guiding his team, focusing on motivation and leadership. This new approach re-energised him, and he started to see his role in a new light, finding fulfilment in helping his team grow and succeed.</p><h3>Final Thoughts</h3><p>This journey has taught me to embrace every challenge as an opportunity for growth. When we change our perspective and find value in the mundane, we transform frustration into fulfilment. So, next time you feel stuck, remember to squint your eyes, shift your focus, and discover the hidden lessons in your daily tasks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57433a2483fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-agile-leadership/beyond-the-daily-grind-finding-fulfilment-in-your-career-57433a2483fb">Beyond the Daily Grind: Finding Fulfilment in Your Career</a> was originally published in <a href="https://medium.com/beyond-agile-leadership">Beyond Agile Leadership</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Avoid Getting Lost: The Power of Sharing Your Vision with Your Team]]></title>
            <link>https://chrisbartolo.medium.com/avoid-getting-lost-the-power-of-sharing-your-vision-with-your-team-b13147644564?source=rss-b797fc8b8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/b13147644564</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[ctotalk]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <dc:creator><![CDATA[Chris Bartolo]]></dc:creator>
            <pubDate>Sat, 13 Jul 2024 16:48:08 GMT</pubDate>
            <atom:updated>2024-07-13T20:38:46.007Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*d4lVbdOdD6bVqEW8XlLSUw.jpeg" /></figure><h3>Can You Relate?</h3><p>Imagine this scenario: You’re driving behind your friends to a place you’ve never been before. They keep flooring it randomly, then suddenly take a left turn, then a right, and then another right. You’re struggling to keep up. Eventually, you lose them and decide to turn back home.</p><p>Start planning ahead. Share your route and destination ahead of time, and use those turn signals.</p><p>It saves friendships 😃</p><p>—</p><p>Now, think about how this applies to your team. Clear communication and planning can prevent confusion and keep everyone on the same path. Sharing the destination ensures everyone is working towards the same goal and gets there together! Increase your chances for success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b13147644564" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redefining Leadership: The Power of Collective Success]]></title>
            <link>https://chrisbartolo.medium.com/redefining-leadership-the-power-of-collective-success-b35e5516c160?source=rss-b797fc8b8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/b35e5516c160</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organisational-culture]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[ctotalk]]></category>
            <dc:creator><![CDATA[Chris Bartolo]]></dc:creator>
            <pubDate>Sat, 13 Jul 2024 05:30:23 GMT</pubDate>
            <atom:updated>2024-07-13T05:30:23.873Z</atom:updated>
            <content:encoded><![CDATA[<p>In the high-stakes world of startups, leadership missteps can make or break a company. I learned this the hard way during my first stint as a CTO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sIGWIE7M-0qgJeBXTJzSfA.png" /></figure><p>Looking back to my first time as a CTO within a startup, I remember one particular event that drove a significant yet simple change in how I speak and represent every person within the organisation.</p><h4>Here’s what what happened</h4><p>Upon joining the startup, I quickly learned that what was sold to me about the business was not entirely true; many issues seemed to have been omitted. Looking back now, I don’t believe it was intentional but rather a lack of understanding of the company’s reality. Initially, I felt blindsided and set up for failure. This mix of frustration and determination fuelled my journey to navigate the unforeseen challenges.</p><p><em>I think we all start out with a lack of empathy towards founders and the assumption that they know exactly what they are doing.</em></p><p>I was given what felt like an impossible goal: take over from the existing technical leadership, understand or replace the team, with basically no budget. The previous leadership, upon learning of my arrival, committed to a three-month launch timeframe.</p><p>The reality was that the application built was not scalable, was constructed with no understanding of architecture, and would crash after five minutes of starting up the backend server application.</p><p>Just painting a picture here, <em>or maybe</em> I’m trying to justify my approach.</p><p>Long story short, I did not manage to get it launched in three months; there was too much to do. But we launched live beta a few months after that, and it was successful. I was filled with pride, and here is when it went wrong.</p><p>During the live successful beta, we organised an office event, gathered around a large screen, opened some beers, and enjoyed watching clients test it and live stream it. The teams started congratulating each other and then turned to me and thanked me. At that point, I proudly stated:</p><p><em>“I did it!”</em></p><h4>The problem <em>I</em> started</h4><p>After that, it became the most prominent thing, even in casual discussions; people would automatically latch on to every time I would say “I.”</p><p>I started to feel it became an individual effort, where everyone was against me. They’d argue for the sake of arguing, and my influence on the teams started to lack and fall back.</p><p><strong>It was a <em>ME</em> versus <em>THEM</em> at that point.</strong></p><p>There were many events that made me start to obsess, feeling that I did not belong anymore and that the teams and my peers were no longer on my side. I felt unappreciated, and everything was an uphill battle.</p><p><strong><em>The problem was THEM … </em></strong><em>I was wrong..?</em></p><h3>I made it worse</h3><p>I was new to the project and the codebase, and as a startup with a low budget, it’s good to mention there was no documentation. This only meant that I had to be onboarded and, every step of the way, be hand-held throughout the code and any code changes I made.</p><p>While writing this, I’m just thinking I’m making myself sound terrible. However, I think it’s beneficial to explain in a crude way to slightly amplify the importance of what I learned through this experience.</p><p>I remember one particular scenario. A specific issue/bug was being said as “impossible to fix” by a team lead. I made sure I was the one to fix it in the shortest timeframe possible. I wanted to prove that I knew what I was doing and that it could be done. While I was successful, instead of being a leader and showing the team how to get there themselves, to improve and grow the team, I think it’s fair to say I failed. I took all the credit and slammed it in their faces.</p><blockquote>When a critical bug was deemed ‘impossible to fix,’ I tackled it myself to prove my capabilities. Though I succeeded, I missed a crucial opportunity to empower my team and foster their growth.</blockquote><p>At that point, I think it’s fair to say I lost any respect or trust from many team members.</p><h3>The Realisation</h3><p>A couple of weeks after that, a peer sat me down and pointed it out, going as far as explaining that it demotivated people and took away any benefit or positivity around the success of what we had accomplished, even if there was credit to give to me.</p><p>Reality is, I didn’t do it alone. I steered the ship, I drove the teams and the people, and while I had worked hard and late nights and was hands-on in the codebase, I still did not do it alone.</p><p>Any learning opportunity, mentoring/coaching of the teams, or even growth of the team, was lost and missed.</p><p><strong>They</strong> didn’t make it a <strong>ME</strong> versus <strong>THEM</strong>. I managed to achieve that all on my own. I can take credit for that.</p><blockquote>This experience underscored the importance of collective success in leadership. Effective leaders elevate their teams, share victories, and create an environment where everyone thrives.</blockquote><h3>Now, how to fix it?</h3><p>As with everything done so far, I couldn’t fix it alone, and that was one of my most important learnings. My peer wanted to work on it with me, and while he may not know it, I stuck through that startup mostly because of him. He helped me with my personal growth.</p><p>I was open to change and self-improvement. One important factor: I went back to my mentor from a previous company I worked at, and he had a lot to say about it as well.</p><p>I think having the support and willingness from others to help and support you is one of the most crucial parts of our leadership journey. It was also a sudden realisation:</p><p><strong><em>The Power of “We” and “Us”</em></strong></p><p>Within our leadership roles, we need to work on having level heads and putting our own ego and pride aside.</p><p>Every time I said “I,” my peer would immediately subtly signal me, bang on his desk, and make sure I rephrased. In scenarios where it was “a bit too much,” he’d interject and ensure we smoothed it out, making the other person and team members feel good and accomplished.</p><p>It wasn’t easy, especially when it had become very natural to say “I.”</p><p>My peers became my team; we became a team.</p><p>We solidified our mission, our values, and how we managed the company and organisation together. My success became their success and the teams’ success. The team’s success became our success. My peers’ success became our success.</p><p>We broke down the silos and the idea of the “individual effort,” removing, in some cases, conceit. The distance between us as leaders and our teams dissolved.</p><p>My point is, I couldn’t do it alone. It took an active effort, not just from myself but from others too, and not just from my peers but from the teams.</p><p>After all, it was the teams that I had hurt.</p><p>The teams had to be open for us to mend the relationship and work better together.</p><h3>The Fine Line</h3><p>I can’t not mention where there is a fine line when using <em>US</em> and <em>WE</em>. As we program ourselves to think and speak in this way, it’s easy to fall into some traps.</p><p>As leaders, we constantly need to give feedback. It’s very easy to cower behind the use of “we,” creating a group and a gang-up effect on the person, sometimes to add amplification and justification to the negative feedback we’re giving.</p><p>Keep in mind, when doing this, you’re setting a very bad culture and ripple effect.</p><p>Some people take this hard, feeling they’ve been singled out and are the bad sheep amongst their team and colleagues, creating the I vs. THEM. They may cower away, feel unwanted, and no longer feel part of the team, while others may decide to be more confrontational and attack their peers.</p><p>You lost trust and respect while successfully creating a toxic culture.</p><p>When giving feedback, it’s important you are direct, and in cases where it’s negative, use phrases like “I feel,” not “we feel,” or “the team feels.”</p><p>I personally like adding the “we” and “the team” when I’m giving positive feedback. This also tends to have a very positive ripple effect. Usually, the person I say that to would start giving positive compliments and feedback directly to others, as they feel confident, motivated, and thankful to others for praising them.</p><h3>Our Responsibility</h3><p>As leaders, we have a responsibility to cultivate a culture of inclusivity, support, and shared success. This means recognising the contributions of everyone involved and ensuring that each team member feels valued and part of the collective achievement.</p><p>Using “we” and “us” fosters a sense of unity and shared purpose, but it must be done thoughtfully. Positive reinforcement should always highlight the collective effort, while constructive feedback should be individualized to avoid alienation and maintain trust.</p><p>Ultimately, our responsibility is to lead by example, showing humility, empathy, and a genuine commitment to the growth and well-being of our teams. By doing so, we not only enhance our leadership effectiveness but also build a stronger, more cohesive organisation where everyone thrives.</p><p><strong>Our responsibility as leaders extends beyond individual achievements. It’s about fostering a culture where every team member feels valued and integral to the collective success. By embracing ‘we’ over ‘I,’ we pave the way for a more inclusive and resilient organisation. Let’s lead with empathy, humility, and a genuine commitment to our teams’ growth and well-being.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b35e5516c160" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating the Challenges of Leadership in a Fast-Paced Environment]]></title>
            <link>https://chrisbartolo.medium.com/navigating-the-challenges-of-leadership-in-a-fast-paced-environment-fd288239f2ad?source=rss-b797fc8b8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd288239f2ad</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organisational-culture]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Chris Bartolo]]></dc:creator>
            <pubDate>Tue, 09 Jul 2024 16:54:32 GMT</pubDate>
            <atom:updated>2024-07-09T18:03:13.206Z</atom:updated>
            <content:encoded><![CDATA[<p>In a world that feels perpetually short-staffed and rushed, it’s easy to overlook the importance of kindness and understanding in our professional interactions. The image below, which I recently came across, highlights a crucial point:</p><blockquote>We need to appreciate those who show up, even when the going gets tough.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*Xh0vqJPjjsU6q_aF.jpeg" /><figcaption><a href="https://kkapczynski.medium.com/the-whole-world-is-short-staffed-be-kind-to-those-that-showed-up-7d21c06b8b4d">https://kkapczynski.medium.com/the-whole-world-is-short-staffed-be-kind-to-those-that-showed-up-7d21c06b8b4d</a></figcaption></figure><p>As a CTO with over a decade of experience, I’ve found myself often caught between the demands of shareholders and the needs of my team. This balancing act can be challenging, particularly in high-pressure environments where the stakes are high. Our natural tendency might be to react quickly and sometimes harshly when things don’t go as planned. However, it’s precisely in these moments that our role as mentors and coaches becomes most critical.</p><h3>The Dual Perspectives on Being Short-Staffed</h3><p>The image conveys a message that can be interpreted in multiple ways. On one hand, it’s a call for empathy towards employees dealing with a tough work environment and demanding clients. On the other, it might seem like a critique of management, suggesting that staffing issues are a result of deeper organizational problems. The reality is often somewhere in between.</p><p>In a <a href="https://kkapczynski.medium.com/the-whole-world-is-short-staffed-be-kind-to-those-that-showed-up-7d21c06b8b4d">recent article by Kasia Kapczynski</a>, this duality is explored. While some argue that kindness is essential, others believe that the need for such reminders points to systemic issues within workplaces. However, it’s crucial to recognize that it’s not always about poor management. Business profitability, targets, and other external factors also play significant roles.</p><h3>Finding Meaning and Motivation</h3><p>Taj Pelc, in a thought-provoking <a href="https://www.linkedin.com/posts/tajpelc_people-need-a-sense-of-meaning-in-their-work-activity-7212067028264718337-96j0?utm_source=combined_share_message&amp;utm_medium=member_desktop">LinkedIn post</a>, underscores the importance of purpose in driving team performance. He states, “On teams where we got shit done, we had a strong reason to do so. We knew what was at stake. We were hungry for the outcome. If your team is asleep, try giving them a reason to get out of bed first.”</p><p>This sentiment highlights the critical role of communication in leadership. Yet, we often forget that effective communication is not an innate skill for everyone. Many founders and business leaders are not formally trained in management, which can lead to misunderstandings and frustrations. Recognising this can help us approach our roles with more empathy and patience.</p><h3>Reflecting on Our Leadership Style</h3><p>The phrase “The whole world is short staffed. Be kind to those that showed up.” made me reflect on how easily we can forget our responsibilities in leading and nurturing our teams. Instead of reacting harshly to setbacks, we should focus on understanding the underlying issues and working collaboratively to address them.</p><p>As a CTO, my approach involves two key strategies:</p><ol><li><strong>Retrospective Analysis</strong>: This involves looking back at what went well, what didn’t, and how we can improve. It’s a systematic way of learning from our experiences.</li><li><strong>Risk Assessment</strong>: Encouraging teams to think proactively about potential issues and develop contingency plans.</li></ol><h3>Implementing Risk Assessment: The ROAM Approach</h3><p>Risk assessment is a powerful tool for supporting teams, particularly in high-stakes scenarios like product releases. By anticipating potential problems and preparing solutions, we can manage crises more effectively. Moreover, it nurtures a supportive environment where team members feel prepared and backed by a structured process.</p><p>I use the ROAM approach for risk assessment:</p><ul><li><strong>Resolved</strong>: Identify risks that are not immediate threats and set them aside.</li><li><strong>Owned</strong>: Assign ownership of a risk to a team member responsible for managing it.</li><li><strong>Accepted</strong>: Acknowledge risks that cannot be resolved and plan to deal with them.</li><li><strong>Mitigated</strong>: Develop strategies to reduce the impact of potential risks.</li></ul><p><em>(Additionally, understanding the probability of risks helps in prioritising actions.)</em></p><p>By incorporating these practices, we not only enhance our team’s resilience but also foster a culture of continuous improvement and mutual support.</p><p>This approach ensures that team members are not left to face uncertainties alone but are equipped with the tools and support they need to succeed.</p><p>This is an adaptation of the ROAMing technique from the SAFe Framework. <a href="https://scaledagileframework.com/planning-interval/">https://scaledagileframework.com/planning-interval/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fbdxqWqBfHKJiNG_vHq9Cg.png" /></figure><p>The key to successful leadership in fast-paced environments lies in our ability to balance empathy with accountability. By investing in our teams, understanding their challenges, and providing clear guidance and support, we can navigate the pressures of our roles more effectively. Let’s remember to be kind to those who show up, and together, we can achieve remarkable outcomes.</p><p><em>Sidenote: I decided to not go into too much detail on breaking down the ROAMing technique, as there are other articles out there, which do a better job than me! Such as this one:<br></em><a href="https://deeprojectmanager.com/roam-risk-management/"><em>https://deeprojectmanager.com/roam-risk-management/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd288239f2ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Achieving Success Through Clear Goals and Aligned Objectives]]></title>
            <link>https://chrisbartolo.medium.com/achieving-success-through-clear-goals-and-aligned-objectives-e644b8b5a6be?source=rss-b797fc8b8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/e644b8b5a6be</guid>
            <category><![CDATA[ctotalk]]></category>
            <category><![CDATA[saas-okrs]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Chris Bartolo]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 10:25:51 GMT</pubDate>
            <atom:updated>2024-07-07T17:28:59.159Z</atom:updated>
            <content:encoded><![CDATA[<p>Setting clear and comprehensive business goals, maintaining focus, and effectively communicating them sets a direction, vision, and mission for every team member to work towards. Aligned goals between teams and departments contribute to a culture of follow-through and accountability, supporting your business’s success and profitability.</p><p>Success demands following through, supporting your teams, and measuring your ROI against the mission.</p><p>On multiple occasions, I compare many startups and businesses to the idea of grabbing a packet of ham and throwing slices against a glass wall, hoping that one of them sticks.</p><p>I’ve implemented different Agile methodologies depending on the size and form of the business. One of the most important implementations, though, is the use of OKRs with quarterly roadmapping and increments. This gives cross-functional teams enough room to focus and work towards a goal — short enough not to require a considerable investment but long enough to support your experts in wireframing, spec’ing out, and building.</p><p>Aligning the objectives also means that all your stakeholders — hr, marketing, sales, finance, legal — know what they need to focus on and work towards making those objectives a success. It’s useless developing 50 half-baked features under pressure and rush, only to end up using five things that aren’t mature enough to be as successful as they could have been.</p><p>Think about it… Focus on those five key features, assign resources, and allocate time for them to be marketable and sellable. Ensure each of the roles are also aligned and following through with the set objectives to meet the ROI based on the chosen features and functionality. It’s counterproductive if development builds 50 things, but then marketing decides to promote something new instead of what has been built.</p><h4>Quick cheat-sheet:</h4><ol><li>Set your business objectives</li><li>Workshop around the objectives, with different experts in your team</li><li>Define Key Results and Key Actions for each Objective</li><li>Use the WSJF method for prioritising based on Business Value, Time Criticality, Risk Reduction and Opportunity Enablement, Cost of Delay, and Job Size</li><li>Communicate, Document and promote the objectives internally, making sure every person is onboard and working towards the same goal</li><li>Shield teams and goals, Achieve!</li></ol><h4>Maintain your defined path</h4><p>Keep in mind, adjusting or making changes to what’s been defined, comes at a cost!</p><p>Anything invested on what has been worked on so far, can potentially be lost, and result in no value delivery. Consider the consequences vs the opportunity when making adjustments. In many cases, it’s not worth disrupting efforts, but rather wait until delivery, and re-run the exercise for setting/updating objectives, workshopping and prioritisation.</p><p>Maintaining focus, and your team’s current path, gives a lot of positive growth within your business. Sustainability, drive, motivation, and establishes a culture of <strong>follow-through</strong>. The end-result of delivery and meeting Key Results and even part of the set objectives, also sets a feeling of accomplishment within the teams and business.</p><p>The effect is contrary when redefining objectives along the way, or even inserting new goals and adjusting goal posts. You can’t create a culture of follow-through and delivery, if you’re not following-through with your set objectives. This lack of focus results in low-quality work, demotivation, and lack of cultural rewards through sense of accomplishment within the teams and workforce.</p><p>Keeping a focused approach ensures that you meet your ROI goals. Quality over quantity leads to sustainable success.</p><p>#BusinessGoals #AgileMethodologies #SuccessStrategies #OKRs #TeamAlignment #Productivity #Leadership #Management</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e644b8b5a6be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Rules of 3, applying to decision-making, as a CTO]]></title>
            <link>https://chrisbartolo.medium.com/my-rules-of-3-applying-to-decision-making-as-a-cto-31241464e3fc?source=rss-b797fc8b8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/31241464e3fc</guid>
            <category><![CDATA[cto-as-a-service]]></category>
            <category><![CDATA[ctotalk]]></category>
            <category><![CDATA[rule-of-three]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[flow]]></category>
            <dc:creator><![CDATA[Chris Bartolo]]></dc:creator>
            <pubDate>Tue, 02 Jul 2024 17:32:07 GMT</pubDate>
            <atom:updated>2024-07-02T17:32:07.546Z</atom:updated>
            <content:encoded><![CDATA[<p>“I don’t trust them to get things done; I need to know everything and they need to seek my approval before they do anything!”</p><p>As a CTO, I used to struggle with this mindset, but I realized it was hindering productivity and blocking team flow. Enabling and facilitating flow within a company is crucial for maintaining efficiency.</p><p>The &lt; 3 minute rule, from my previous post, isn’t just for tasks — it can be applied to decisions as well.</p><p>Many “micro-decisions” are asked constantly. While they can feel like a nuisance, answering them quickly enables flow, unblocking work and preventing bottlenecks.</p><p>We all become bottlenecks at some point, disrupting flow. Decentralizing decision-making is key. Here’s how I achieve this:<br>1) Set Clear Roles and Responsibilities: Avoid grey areas in hierarchy and responsibilities to prevent conflicts. Establish a formal communication path. Instead of giving directions in silos, set goals within a group context, ensuring everyone understands their role and the collective objective.<br>2) Communicate Expectations: Use clear examples based on existing practices and real-world scenarios. For new initiatives, participate in planning stages, articulating the vision and desired outcomes. This ensures decisions align with overall goals.<br>3) Educate and Empower: Break down decisions by outlining possible options, evaluating outcomes and risks, and considering previous decisions or goals. Encourage gathering necessary information to make informed decisions. This helps in making decisions with the lowest risk and highest value. For decisions with equal risk and value, the deciding factor becomes job size.</p><h4>Decentralizing Decision-Making</h4><p>To maintain flow and avoid bottlenecks, I delegate:<br>1) Recurrent and Frequent Decisions with limited impact<br>2) Time-Critical Decisions with high cost of delay<br>3) Decisions Requiring Specific Knowledge and context</p><h4>Balancing Speed and Quality in Decision-Making</h4><p>Communication between management levels can limit flow and block work. However, rushing decisions can have negative consequences. To balance this, I:<br>1) Prioritize Decisions: Make quick decisions for low-impact issues while taking time to deliberate on high-impact decisions.<br>2) Clarify Decision Criteria: Establish clear criteria for decision-making based on impact, urgency, and context.</p><h4>Not all decisions can be decentralized. For those requiring higher management involvement:</h4><p>1) Delay Decision Making When Necessary: Gather input and avoid poorly-informed choices.<br>2) Simplify and Break Down Decisions: Break down complex decisions into simpler components to facilitate input from higher management. Structure work to avoid being blocked by pending decisions beyond your control.</p><p>By implementing these strategies, I ensure many decisions are made swiftly and effectively when possible, while knowing when to delay and simplify decisions to maintain flow and productivity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31241464e3fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A spin on the rule of 3, as a CTO]]></title>
            <link>https://chrisbartolo.medium.com/a-spin-on-the-rule-of-3-as-a-cto-35738e93d13b?source=rss-b797fc8b8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/35738e93d13b</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ctotalk]]></category>
            <category><![CDATA[rule-of-three]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Chris Bartolo]]></dc:creator>
            <pubDate>Tue, 02 Jul 2024 17:29:45 GMT</pubDate>
            <atom:updated>2024-07-02T17:29:45.180Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The Rule of 3:</strong> Break tasks into three components to make them manageable, memorable, and actionable. 🛠️</p><p>As a CTO, I’ve found the Rule of 3 to be incredibly effective in managing my workload and maintaining productivity. However I tend to use my own “personalised” rule of 3.</p><h3>Here are my Rules of 3:</h3><p>1️⃣ Ad-hoc tasks &lt; 3 minutes? Do immediately. <br>Throughout the day, many small tasks arise that can feel annoying and distracting due to context-switching. However, these tasks often block others and, if left undone, accumulate and create stress by the end of the day. This can snowball into the next day, adding to the list of ad-hoc tasks. By handling them immediately, you not only unblock others and keep things moving but also prevent a backlog of small tasks, reducing stress and keeping your mind uncluttered.</p><p>2️⃣ Can’t do it in 3 days? Delegate it. <br>This ensures timely decision-making and avoids creating unnecessary blockers. In a dynamic environment where new priorities and events arise daily, it’s easy for tasks to be deprioritized. When the third day comes and you can’t get to a task because something more important demands your attention, it disrupts the flow of work for your team and other dependencies. Delegating at this point ensures the task gets done, maintaining workflow continuity and preventing disruptions.</p><p>3️⃣ Something flagged 3 times? Act NOW. <br>This rule sets a clear threshold for action, ensuring recurring issues are addressed promptly and don’t escalate. It’s crucial for maintaining operational efficiency and resolving problems quickly.</p><h4>The Rule of 3 in GTD</h4><p>David Allen’s GTD (Getting Things Done) method also emphasizes breaking down tasks into manageable components. The “two-minute rule” is part of this methodology:<br>If a task takes less than two minutes, do it immediately. This approach reduces the cognitive load of tracking numerous small tasks and helps maintain focus on larger projects.</p><p>By integrating these rules into my daily routine, I’ve been able to streamline my workflow and improve overall productivity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35738e93d13b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>