<?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 Adán Gomezcoello on Medium]]></title>
        <description><![CDATA[Stories by Adán Gomezcoello on Medium]]></description>
        <link>https://medium.com/@adan.gomezcoello?source=rss-d46e70d150b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*83C7HXtPeTA65f5e7nDmdg.jpeg</url>
            <title>Stories by Adán Gomezcoello on Medium</title>
            <link>https://medium.com/@adan.gomezcoello?source=rss-d46e70d150b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:47:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adan.gomezcoello/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[AI Is Scaling Your Code. It’s Also Scaling Your Complexity]]></title>
            <link>https://medium.com/@adan.gomezcoello/ai-is-scaling-your-code-its-also-scaling-your-complexity-cedf539eefb9?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/cedf539eefb9</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 13:32:29 GMT</pubDate>
            <atom:updated>2026-04-28T13:32:29.514Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How using AI without control is creating hidden costs, fragile systems, and problems that only appear in production</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*K62hLUXaZ4SepVW0nLvfng.jpeg" /><figcaption>AI hidden problems</figcaption></figure><p>Over the past few months, my deep dive into building with AI models for both personal and enterprise projects has produced strong results. However, this journey has not been without challenges.</p><p>I identified critical patterns that, if left unaddressed, would have seriously compromised the success of these initiatives. In this article, I explain the main problems that arise when using Large Language Models (LLMs) without a clear methodology.</p><p>I started using AI tools intensively, especially for tasks that previously required a significant amount of time, such as code generation, refactoring, and deployments.</p><p>At first, the experience is impressive: everything moves faster, you produce more, and you solve in minutes what used to take hours. However, after several sessions, the first signs appeared that something was not quite right.</p><p><em>As an enterprise solutions architect, I have seen this pattern many times. Technologies change, but the same mistakes repeat. At the beginning, everything works and progress is fast, but without control, solid fundamentals, and clear judgment, the system begins to degrade. Complexity grows and costs scale.</em></p><p>These kinds of problems rarely end well.</p><h3>The illusion of productivity</h3><p>AI makes you feel productive very quickly. You generate code, test ideas, and iterate rapidly. Everything flows. However, when you look more closely, problematic patterns begin to appear:</p><ul><li>code that no one fully understands</li><li>decisions that are not questioned</li><li>solutions that are larger and more complex than necessary</li></ul><h3>Early warning signs</h3><p>We are building systems that appear to work but are not designed to survive. They do not fail today or tomorrow, but they are accumulating problems that will surface later. When they do, it will not be because of a single bug, but because control over the system was lost without anyone noticing.</p><p>This is not because the technology is flawed, but because it removes initial friction without removing complexity.</p><h3>Why this problem is not new</h3><p>Since the early days of software, complexity has always been present. Every layer, every abstraction, every solution and every line of code we create adds more complexity to the system.</p><p>In the past, that complexity came with friction in the form of time, effort, and deliberate decisions, which acted as a natural constraint. That is no longer the case.</p><p>AI removes that friction without removing complexity. We can build faster than ever, but we can also accumulate complexity faster than ever. Complexity does not disappear; it only shifts until it becomes unmanageable.</p><p><em>We saw it with cloud migration. Moving infrastructure off-premises promised speed, flexibility, and cost reduction. Early results were impressive. Teams moved faster, provisioning that took weeks happened in minutes. Then the bill arrived. What began as an efficiency play became a cost management crisis — sprawling resources, redundant services, and architectures that no one had fully designed because the platform made it too easy to just spin something up. The cloud did not create bad architecture. It removed the friction that used to slow it down.</em></p><h3>A real example</h3><p>This is not theoretical. I experienced it recently while working on a financial application. On the surface, everything looked fine. The application flowed well, the interfaces responded correctly, and the core functionalities were in place.</p><p>We progressed faster than usual. In fact, we progressed too fast.</p><p>However, when the time came to prepare a demo for potential investors, we began validating quality, reviewing full workflows, and testing different scenarios.</p><p>At that point, several issues started to emerge:</p><ul><li>duplicated logic</li><li>decisions without a clear rationale</li><li>parts of the code that worked but were not fully understood</li><li>deliberated fallbacks</li></ul><p>The AI had introduced these fallbacks deliberately to ensure that the system continued to operate. When something failed, it would return a default value or adjust the flow to avoid interruption.</p><p>At first glance, this made the application appear robust. However, when we validated the data in detail, the problem became clear. The results were not always consistent, and in some cases, they did not exist in the database.</p><p>This moment was critical because it confirmed something I had already sensed. We were not losing speed, but we were losing control.</p><p><em>To illustrate the impact, cleaning up this “ghost logic” in wealth management and goal modules required the equivalent of two full sprints of intensive refactoring. What initially appeared to be a one-week gain turned into nearly fifteen days of stabilization work. This was the direct cost of invisible rework: untangling code that seemed to function on the surface but lacked the structural integrity required to process real financial data.</em></p><h3>The six main problems</h3><p>These six problems rarely appear in isolation. They emerge gradually, overlap, and feed each other — which is precisely what makes them hard to catch. By the time one becomes visible, the others are already embedded in the system. Understanding them individually is useful, but what makes them dangerous is how they interact.</p><h4>1. Hidden AI costs</h4><p>It is easy to use AI without considering the real cost. Every interaction and iteration adds up. Initially, this is not noticeable, but as the system scales, the impact becomes significant.</p><p><strong>Consequence:</strong> Features that appeared viable become unsustainable. The cost per operation starts to erode margins. The business model does not fail; the implementation does.</p><h4>2. Ownership gap in generated code</h4><p>Parts of the system simply appear. No one fully wrote them, and no one fully understands them.</p><p><strong>Consequence:</strong> When something fails, no one knows exactly where to intervene. Debugging becomes slower, changes become riskier, and decisions become blocked. Teams begin to avoid certain areas of the system.</p><h4>3. AI-induced overengineering</h4><p>AI tends to provide complete solutions that are often unnecessary.</p><p><strong>Consequence:</strong> The system becomes more complex than required. Changes become slower and more expensive, and agility is reduced.</p><h4>4. Erosion of technical judgment</h4><p>There is a tendency to assume that if the AI suggests something, it must be correct.</p><p><strong>Consequence:</strong> The team’s ability to critically evaluate decisions weakens. AI does not understand the full context, and it can suggest solutions that work technically but should not exist within the system.</p><h4>5. Invisible rework</h4><p>There is a continuous cycle of generating, adjusting, and retrying, which is rarely measured.</p><p><strong>Consequence:</strong> Perceived productivity increases, but actual delivery speed decreases.</p><h4>6. Validation debt and loss of control</h4><p>AI generates code faster than it can be properly validated, and the system grows faster than it can be fully understood.</p><p><strong>Consequence:</strong> Errors surface in production. Changes become risky, and the system continues to function while becoming increasingly fragile.</p><h3>Vicious cycle</h3><p>The most dangerous aspect is that these problems are interconnected and reinforce each other.</p><p><strong>Stage 1 — Speed:</strong> AI removes initial friction, and everything appears to improve.<br><strong>Stage 2 — Disorder:</strong> The system continues to function but loses coherence as complexity grows unchecked.<br><strong>Stage 3 — Collapse:</strong> The system becomes fragile and unpredictable, and the problem shifts from technical to structural.</p><h3>The role of design and architecture</h3><p>AI is not the problem. The problem is using it without control.</p><p>Without design, architecture, and clear judgment, any system will degrade. AI simply accelerates that process.</p><p>For this reason, the role of architecture becomes even more critical. It is not just about generating code faster, but about defining what should be built, how responsibilities are structured, how outputs are validated, and how the system evolves while maintaining coherence.</p><p>AI can generate code, but it cannot determine whether that code fits within the broader system. It does not understand real constraints, business context, or prior decisions.</p><p>System coherence is not a technical issue; it is a design issue.</p><h3>Toward a more structured approach</h3><p>It is not enough to use AI more effectively. Its use must be structured.</p><p>The challenge is not only how code is generated, but under what rules it is generated, validated, and evolved. Without this structure, each interaction introduces variability.</p><p>The approaches I am exploring include:</p><ul><li><strong>Spec-Driven Development:</strong> defining requirements and acceptance criteria before generating code</li><li><strong>Agent-Driven Development:</strong> assigning clear roles and responsibilities to AI-assisted processes</li><li><strong>AI Operations:</strong> measuring usage, cost, and quality in production environments</li></ul><p>The objective is not to complicate the process, but to make it explicit.</p><p>To make this shift in mindset tangible, consider the difference between a generic prompt and a structured approach. It is not the same to ask a tool to “create an endpoint to register transactions,” where the model is left to infer architecture, validation, and error handling, as it is to apply Spec-Driven Development: “Implement this interface following these five strict acceptance criteria from our architecture document, and if you encounter an exception, do not use a fallback to hide it; propagate the error according to our standard.”</p><p>This represents a shift from using AI as a tool to assist development to using AI within a controlled system governed by clear rules.</p><p><strong><em>In the next article</em></strong><em>, I break down the structured approach I am applying to address these problems — Spec-Driven Development, Agent-Driven Development, and AI Operations — and what it actually looks like in practice.</em></p><h3>Conclusion</h3><p>The main limitation of AI is its lack of full context. It does not understand the reasons behind decisions, existing constraints, or past failures.</p><p>When its suggestions are implemented without validation or critical evaluation, the result is predictable:</p><ul><li>code that no one understands</li><li>escalating costs</li><li>fragile systems</li></ul><p>When these issues become visible, it is already too late. The challenge is no longer fixing errors, but regaining control of a system that was never fully under control.</p><p><strong><em>AI is not breaking your system. It is simply moving faster than your control over it. And speed without control is not progress — it is a countdown.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cedf539eefb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is better Product Management than Agile?]]></title>
            <link>https://medium.com/@adan.gomezcoello/is-better-product-management-than-agile-522e9c4668e8?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/522e9c4668e8</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agility]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 14:29:24 GMT</pubDate>
            <atom:updated>2024-04-27T14:30:18.139Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The quick answer is </em><strong><em>YES</em></strong><em>, but let’s delve deeper to fully grasp the reasons and clarify some aspects related to this response.</em></p><p><strong>Distinguishing Product Management from Agile Approaches</strong></p><p>Product management goes beyond the use of agility because it covers a wider range of aspects related to product management and business success. While agility has been widely adopted in the software development and project management industry, its focus is on rapid and flexible product delivery, sometimes leaving out broader strategic and commercial aspects. As for agility, it has experienced some loss of space in the industry due to several factors:</p><p><strong>Limitations in Scalability:</strong> While agility is effective for small teams and simple projects, it may face challenges in scalability when applied to larger projects or complex organizations.</p><p><strong>Limited Focus on Strategy:</strong> Agility tends to focus on rapid delivery of functionalities, sometimes overlooking broader strategic aspects such as product vision, portfolio management, and alignment with business strategy.</p><p><strong>Complexity in Implementation:</strong> Some companies have found that implementing agility can be complex and require significant cultural changes that are not always easy to achieve.</p><p><strong>Agile vs. Strategy: The Conflict of Philosophies</strong></p><p>Certainly, agile methodologies have been attempted to be extended beyond their original scope within companies. However, this often results in a transition back to a cumbersome framework, thereby losing the benefits that agile approaches can offer.</p><p>I understand the desire to adopt agility as a foundational principle or operational philosophy within a company. However, applying agile principles to complex definitions and overarching strategies can sometimes contradict its original intent of rapid execution.</p><p>Due to this conflict of ideas, product management has emerged as a more suitable methodology for strategic management within companies and their products. From its inception, product management emphasizes clear vision, strategy, and product roadmaps, making it a highly useful approach for companies with established products seeking to enhance efficiency and appeal to customers.</p><p>Agile principles, with their fundamental concepts of prompt and incremental action for rapid learning, are indeed well-suited for team management and daily operations or sprints.</p><p><strong>Clarification Note:</strong> It is important to mention that we are not against agility or devalue its importance in the daily management and software development. In fact, agility remains a valuable and effective practice in many business contexts. However, within the framework of new market trends and needs, agility has been integrated as one of the practices within the broader focus of product management, which covers strategic, commercial, and product lifecycle management aspects.</p><p>In certain scenarios, prioritizing an Agile framework over Product Management frameworks can be beneficial. For instance, when you don’t have a fully developed product and are simply testing the market, an Agile approach can accelerate development and gather early feedback from customers. However, in such cases, the Lean Startup methodology is more suitable. Apologies, but relying solely on Agile is not advisable, as it can easily lead to losing sight of your product’s vision.</p><p><strong>Product Management: More than a Methodology</strong></p><p>Unlike a specific methodology, product management encompasses multiple methodologies and approaches, such as Agile, Lean, Design Thinking, among others, adapting to the needs and characteristics of each organization. It is not just about following a set of predefined steps but adopting a strategic and flexible approach that allows for effective response to challenges and opportunities arising in product development and management.</p><p><strong>In conclusion</strong>, while Agile methodologies excel in rapid iteration and adaptability, Product Management offers a broader strategic framework that encompasses vision, strategy, and product lifecycle management. While Agile remains valuable, especially in team management and daily operations, integrating Agile practices within the strategic focus of Product Management can lead to a more comprehensive and effective approach to product development and management. Ultimately, organizations benefit from a flexible and adaptable strategy that leverages the strengths of both Agile and Product Management to navigate the complexities of today’s business landscape and drive long-term success.</p><figure><img alt="Product management as winner" src="https://cdn-images-1.medium.com/max/1024/1*heh73PKJhi235e5ilqpyZw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=522e9c4668e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Threat of Inadequate Data Analysis to Your Business]]></title>
            <link>https://medium.com/@adan.gomezcoello/the-threat-of-inadequate-data-analysis-to-your-business-335e11a50faa?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/335e11a50faa</guid>
            <category><![CDATA[survivorship-bias]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Sun, 21 Jan 2024 15:53:32 GMT</pubDate>
            <atom:updated>2024-01-21T15:53:32.008Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I watched a short video on assessing the impacts of bullets on warplanes. The soldiers’ initial instinct was the intuitive logic of reinforcing areas with more bullet impacts, a strategy that seemed sensible at first glance. However, this conventional approach was challenged by the clever insight of a mathematician.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*SpQ34QRKAMCPAo3AYSwbkQ.png" /></figure><p>This mathematician suggested that instead of strengthening areas that had already experienced impacts, it would be more prudent to reinforce the places where no shots had been recorded. The logic behind this idea stemmed from the observation that planes returning with shots in certain areas had failed to survive those impacts. Basing decisions solely on success cases can lead to erroneous conclusions. The initial intuition to reinforce impacted areas is driven by the survivorship bias.</p><p>Survivorship bias, a phenomenon manifesting when only available information from those who have succeeded is considered, can significantly distort decision-making. Applying this concept to the business world, we face the risk of making misguided decisions based on the analysis of survivors, instead of considering the whole picture.</p><p><strong>Survivorship Bias in the Business Context</strong></p><p>In business environments, survivorship bias can arise by solely focusing on success stories. Thriving companies capture attention, but what about those that haven’t managed to stand out? Ignoring these experiences can lead to a biased view of the business reality, distorting the perception of risks and opportunities. In practical terms, businesses relying on data plagued by survival bias might overestimate the viability of certain strategies, products, or initiatives. This misjudgment can result in faulty decision-making, hindering innovation and leading to suboptimal outcomes.</p><p><strong>Erroneous Decisions Driven by Survivorship Bias</strong></p><p>Basing decisions only on successful experiences risks adopting strategies that only worked for certain companies in specific circumstances.</p><p>Ignoring stories of initiatives that didn’t survive can lead to underestimating potential risks in future decisions.</p><p>Survivorship bias can hinder the identification of early warning signs by focusing solely on success cases.</p><p><strong>Example of Survivorship Bias in Business History</strong></p><p>An example of survivorship bias in the business world can be observed in the dot-com bubble of the late 1990s and early 2000s.</p><p>During that period, numerous emerging tech companies experienced rapid growth and seemingly spectacular success in the financial markets. Many investors and entrepreneurs were influenced by these success stories and rushed to invest in new tech companies based on the performance of those that had succeeded. However, survivorship bias was at play. The success stories of companies going public and experiencing significant increases in their stocks overshadowed the stories of many others that failed. Many dot-com companies that didn’t survive the burst of the dot-com bubble were not included in the dominant narrative.</p><p>The result was that investors, influenced by survivorship bias, made decisions based on a skewed sample of information. Many did not consider the possibility that the success of a few companies was not representative of the overall landscape and that many others were not thriving. This phenomenon led to misguided investments and the bankruptcy of numerous companies during the dot-com bubble collapse in 2000. Survivorship bias, by focusing exclusively on success stories, diverted attention from warning signs and contributed to misguided business decisions.</p><p><strong>Example of Survivorship Bias in a Digital Transformation</strong></p><p>In my experience in the business field, I faced a challenge that perfectly encapsulates the trap of survivorship bias. We were in the process of evaluating transactions for migration to digital channels, and the trend was to discard those showing a decline in physical channels. However, this initial assessment overlooked a crucial factor directly affecting the figures.</p><p>The decline in transactions through physical channels was not a direct indicator of their lack of relevance or unpopularity. These transactions were experiencing a decline precisely because conducting them through physical channels was cumbersome. Additionally, several competitors in the banking industry were already efficiently offering these transactions through digital channels.</p><p>The trap of survivorship bias had inadvertently been activated. By dismissing transactions based solely on their performance in physical channels, we were ignoring the evolution of the digital landscape. The decline did not indicate obsolescence; rather, it reflected a clear customer preference for more efficient and modern methods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*4NTxsT3XOd09avVdUCNeIw.png" /></figure><p><strong>Mitigating Survivorship Bias with Informed Approaches</strong></p><p><strong>Broadening Perspective</strong>: To counteract survivorship bias, it is essential to broaden perspective and not limit oneself to success stories only. This approach is based on the theory that informed decisions should consider both triumphs and failures to gain a more complete view of the business landscape.</p><p><strong>Example</strong>: In World War II, the analysis of warplanes illustrates this principle. Not only were planes returning with damage studied, but also those that did not return. Similarly, in the business realm, considering companies that haven’t succeeded can reveal crucial patterns and challenges for decision-making.</p><p><strong>Failure Analysis: </strong>Failure analysis involves scrutinizing the reasons behind business failures. This approach is grounded in the theory that understanding the underlying causes of failures provides valuable lessons and prevents decision-making based on incorrect assumptions.</p><p><strong>Example</strong>: During the dot-com bubble, many companies faced a sudden decline. Analyzing the reasons behind their failures would reveal, for example, how the lack of sustainable business models led to the downfall. This information can prevent similar decisions in the future.</p><p><strong>Diversification of Information Sources: </strong>Diversifying information sources aims to avoid relying exclusively on highlighted narratives. Theoretically, by seeking information from diverse sources, including less-known ones, a more balanced and accurate view of the business environment can be obtained.</p><p><strong>Example</strong>: In the context of unmigrated physical transactions, diversifying information sources could involve not only consulting trends in the Bank’s own transactions but also exploring global market trends. This approach can reveal opportunities that might be overlooked in conventional analysis.</p><p><strong>Conclusion</strong></p><p>In the business world, survivorship bias can be a significant obstacle to decision-making. Recognizing its influence and taking steps to mitigate it is necessary to avoid misguided decisions that could threaten long-term success. By learning from lessons of both successes and failures, businesses can build more robust strategies and make decisions that lead to success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=335e11a50faa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile is Not Dead, But…]]></title>
            <link>https://medium.com/@adan.gomezcoello/agile-is-not-dead-but-be3956eeedf8?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/be3956eeedf8</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Sat, 30 Dec 2023 01:38:41 GMT</pubDate>
            <atom:updated>2023-12-30T01:38:41.372Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been reading various articles proclaiming the decline or end of Agile. While some raise valid points, many seem to lack a comprehensive and objective view of the situation. This article aims to provide a thorough analysis, offering a balanced perspective on various Agile-related topics. Through this compilation, I intend to clarify the current state of Agile, allowing for a more complete and accurate understanding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4RfKTOqgWXbtX5KT" /></figure><h3><strong>Evolution of Agile</strong></h3><p>Agile is far from dead; instead, it has evolved to a point where, compared to its beginnings, it is almost unrecognizable — and that’s not necessarily a bad thing. Some of the most significant changes include:</p><p><strong>Agile Scalability</strong>: Initially focused on small teams and simple projects, Agile has evolved to be more scalable. Frameworks like SAFe (Scaled Agile Framework) and LeSS (Large-Scale Scrum) have gained popularity for scaling Agile principles across entire enterprises.</p><p><strong>Incorporation of DevOps</strong>: Recognizing the technological component of many projects, the integration of DevOps has become a key evolution. Collaboration between development and operations, along with process automation, is now integral to Agile practices.</p><p><strong>User Experience Focus</strong>: As user expectations have evolved, Agile has placed greater emphasis on user experience. Methods like Design Thinking and Lean UX are integrated to ensure that products developed are not only functional but also highly usable and user centric.</p><p><strong>Diversity of Practices</strong>: The diversity of Agile practices has grown considerably. From Kanban to Scrum, and from eXtreme Programming (XP) to hybrid approaches, teams can tailor their Agile approach to specific needs, allowing for adaptability to different organizational contexts.</p><p><strong>Holistic Approach to Digital Transformation</strong>: Agile has evolved to address not only specific software development aspects but also to play a more significant role in organizational digital transformation strategies. It is increasingly recognized as a key component for innovation and business competitiveness.</p><h3><strong>Agile in Complex Projects</strong></h3><p>In large projects, with or without Agile, implementation can be challenging. While Agile helps manage them in small, iterative parts, success is not guaranteed due to the intrinsic complexity of the project or product. Large-scale developments introduce challenges such as complex integration with multiple areas and systems, scalability management, and the need to address organizational changes globally. While Agile provides valuable tools, it does not guarantee absolute success in managing the intricate network of factors characterizing these projects.</p><h3><strong>The Greatest Mistake of Agile</strong></h3><p>Agile should not attempt to interfere with software engineering decisions; indeed, doing so would be its major flaw. Proper application of software engineering, along with adequate design, solid planning, and attention to code quality, is crucial to avoid costly issues in the future. Investing in a solid design from the beginning can save time and resources in the long run. This is further elaborated in this article: <a href="https://medium.com/@adan.gomezcoello/the-biggest-mistake-of-agile-0fe9906521d1">The Biggest Mistake of Agile.</a></p><h3><strong>The Greatest Achievement of Agile</strong></h3><p>The most significant achievement of Agile has been to enhance communication through techniques and ceremonies that enable continuous feedback and alignment with properly prioritized objectives to respond promptly to change and achieve continuous value delivery. The most significant contribution of Agile lies in its ability to enhance communication, foster collaboration, and enable teams to adapt quickly to potential changes. When understood and applied correctly, Agile becomes a valuable tool for any working team. This is discussed further in this article: <a href="https://medium.com/@adan.gomezcoello/discovering-the-true-value-of-agile-e15d8242787e">Discovering the True Value of Agile.</a></p><h3><strong>Ceremonies Disguised as Micromanagement</strong></h3><p>In highly mature teams where communication and alignment are intrinsic, Agile ceremonies may be perceived as unnecessary or even as a form of micromanagement. These teams, having reached an advanced level of collaboration, may find certain Agile practices, such as daily meetings and regular retrospectives, redundant. Agile should not become a rigid set of rules but rather a set of principles adaptable to each team’s specific dynamics. The key is to continually assess the effectiveness of ceremonies and adjust them as needed. Team maturity may require less formal structure to maintain agility and productivity. Avoiding micromanagement is emphasized in this article: <a href="https://medium.com/@adan.gomezcoello/daily-meetings-micromanagement-85bba5c7eb64">Daily Meetings: Micromanagement?</a></p><h3><strong>Conclusion</strong></h3><p>The Agile approach should be considered a valuable tool within a broad set of resources, used effectively in the right moment and context to solve specific problems. Its proper application can offer solutions, but when used incorrectly, it can generate unnecessary complications. Therefore, it becomes imperative to have a solid understanding of Agile principles and benefits, as well as a comprehensive understanding of the current state of the company or teams where it is intended to be implemented. Effectively integrating Agile practices requires a comprehensive evaluation and careful adaptation to specific circumstances, ensuring an implementation that truly adds value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be3956eeedf8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Daily Meetings: Micromanagement?]]></title>
            <link>https://medium.com/@adan.gomezcoello/daily-meetings-micromanagement-85bba5c7eb64?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/85bba5c7eb64</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Tue, 12 Dec 2023 02:38:03 GMT</pubDate>
            <atom:updated>2023-12-12T02:38:03.684Z</atom:updated>
            <content:encoded><![CDATA[<p>In my previous article <a href="https://medium.com/@adan.gomezcoello/discovering-the-true-value-of-agile-e15d8242787e">Discovering the True Value of Agile</a>, we discussed the true value generated by agility and its ceremonies. However, we left the question open: Are daily meetings a form of micromanagement? Daily meetings, also known as “daily stand-ups” or “daily scrums,” have evolved as an essential practice in agile and collaborative work environments. Beyond their fundamental role in communication and problem-solving, these sessions offer a powerful tool for addressing underlying behaviors that influence individual and collective productivity. However, it’s worth asking: Are daily meetings really a subtle guise for micromanagement?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*l21pfnggGrlECPLJtPG7yw.png" /></figure><p>In this article, we will question the nature of daily meetings and explore what lies behind this seemingly innocuous practice that has infiltrated our professional routines. In this analysis, we challenge established perceptions and explore less obvious situations within daily meetings, revealing both their potential benefits and uncomfortable questions they pose about contemporary work dynamics.</p><p><strong>Hawthorne Effect</strong></p><p>In the intricate fabric of labor productivity, the Hawthorne Effect stands out as an intriguing phenomenon that originated in the 1920s. The experiment at the Western Electric Hawthorne Works in Chicago, manipulating light, led to a perplexing conclusion: worker productivity showed a constant increase, regardless of light intensity.</p><p>This finding highlights the impactful influence of attention and special observation in boosting work efficiency. Exploring how this phenomenon intertwines with daily meetings, we delve into the intriguing possibility: the regular attention provided during these sessions can have a significant impact on team morale and motivation. This impact, enhanced by constant surveillance during meetings, opens the door to a substantial increase in productivity.</p><p>Thus, the Hawthorne Effect not only unveils mysteries of the past but also sheds light on contemporary work practices, challenging our perceptions and offering new insights into how attention and surveillance can drive excellence in today’s work environment.</p><p><strong>Beyond Communication</strong></p><p>Daily meetings also offer a powerful tool for addressing underlying behaviors that can influence individual and collective productivity.</p><p><strong>Shared Responsibility:</strong></p><p>Daily meetings foster shared responsibility by creating an environment where each team member shares transparent updates on their work. This constant exchange nurtures a collective sense of responsibility, driving individuals to fulfill their commitments.</p><p><strong>External Motivation:</strong></p><p>By establishing a regular pace of review and feedback, daily meetings act as a source of external motivation. The expectation of sharing daily progress can maintain high levels of motivation among team members, leveraging the inherent structure of these meetings.</p><p><strong>Fear of Failure or Judgment:</strong></p><p>Daily meetings provide a collaborative environment where the fear of failure or judgment can dissipate. Openness and willingness to discuss challenges in a team context can reduce anxiety, fostering a supportive environment and joint problem resolution.</p><p><strong>Clarity of Expectations:</strong></p><p>At the core of daily meetings is the opportunity to establish and clarify expectations. This daily focus on goals and objectives provides constant clarity, minimizing ambiguity, and optimizing the efficient execution of tasks.</p><p><strong>Rewards and Consequences:</strong></p><p>Linking daily meetings to performance evaluations and recognition offers a direct system of rewards and consequences. Achieving and celebrating daily milestones becomes a common practice, encouraging individual and collective performance.</p><p><strong>Lack of Self-Discipline:</strong></p><p>For those who may need a higher degree of structure, daily meetings serve as an external guide that contributes to focusing attention and maintaining the necessary discipline for constant progress.</p><p><strong>Conclusion</strong></p><p>In the contemporary work landscape, daily meetings, beyond their role in communication and problem-solving, emerge as an effective tool that addresses underlying behaviors and promotes productivity. Inspired by the 1920s Hawthorne Effect, where constant observation increased work efficiency, these sessions play a crucial role by offering strategic attention that boosts team motivation and responsibility. From clarity of expectations to the connection with rewards and consequences, daily meetings have not only integrated into professional routines but also challenge and transform work dynamics, contributing to an environment where productivity and performance are elevated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85bba5c7eb64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discovering the True Value of Agile]]></title>
            <link>https://medium.com/@adan.gomezcoello/discovering-the-true-value-of-agile-e15d8242787e?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e15d8242787e</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Sat, 21 Oct 2023 14:00:05 GMT</pubDate>
            <atom:updated>2023-10-21T14:00:05.911Z</atom:updated>
            <content:encoded><![CDATA[<p>Not long ago, I shared an article titled ‘<a href="https://medium.com/@adan.gomezcoello/the-biggest-mistake-of-agile-0fe9906521d1">The Biggest Mistake of Agile</a>,’ in which I explored some misconceptions surrounding Agile that have led to issues in software development. However, I want to emphasize that I don’t view Agile negatively. In fact, I consider it a powerful working philosophy when its fundamentals are understood and applied correctly.</p><p>Let’s imagine an experienced carpenter with a toolbox. They know when and how to use each tool according to their needs. The same principle applies to Agile and its various frameworks, which provide genuinely useful techniques and tools for project development. Success largely depends on how we employ these tools.</p><p>We understand that Agile facilitates early value generation through its agile dynamics. However, there are underlying factors that lead to these positive results. In this article, I aim to highlight one of the most significant achievements, if not the most significant, and explain how it can drive the success of projects and initiatives when comprehended and applied correctly.</p><p>One thing we immediately notice when implementing an Agile framework in a company is the execution of ceremonies such as the daily standup. But what’s the purpose behind this famous daily meeting? Perhaps there’s a degree of group micromanagement involved, but that’s not the focus of this article (we’ll address this in another article). The effectiveness of micromanagement can vary and depends on various factors. What I truly want to emphasize is the communication that occurs during this ceremony. If we have a leader (Scrum Master, Product Owner, etc.) who ensures that team members discuss relevant issues that are affecting or could affect their work, we can obtain early feedback and resolve issues collectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*AjBRbE7nPBlZ9p8ZCAxKAA.png" /></figure><p>Similarly, with other ceremonies like sprint planning and demo sessions, we generally enhance team communication regarding the overall vision and ongoing work, ensuring that everyone follows the same path. Feedback sessions, aimed at identifying both strengths and areas for improvement, are also valuable in terms of enhancing team dynamics. All of these ceremonies share the common purpose of conveying messages, ideas, suggestions, and improvements, which collectively contribute to effective communication.</p><p>The importance of communication for aligning and implementing a company’s objectives has always been emphasized. However, Agile frameworks have provided a more comprehensive approach to synchronized communication. This is achieved both verbally through ceremonies and visually through various planning and tracking boards, resulting in excellent outcomes.</p><p>As mentioned initially, these techniques should be considered tools that need to be used appropriately within the correct context. For instance, if we already have a mature, self-organizing team, one planning session and perhaps one alignment session may suffice for effective communication. In such cases, having daily meetings can become tedious and inefficient. Therefore, it’s essential to understand the underlying behaviors when addressing these working mechanisms.</p><p>In this scenario, it’s crucial to have a clear understanding of the team’s maturity to determine when it’s truly necessary to implement all ceremonies. Typically, newly formed teams require them. Evaluating maturity is not a straightforward task because there can be teams that follow all Agile ceremonies and board management routines but don’t necessarily achieve tangible results. Recognizing when a team is genuinely mature involves more than just sprint compliance metrics. It should be supplemented by periodic customer satisfaction evaluations, efficiency assessments, and assessments of their impact on organizational OKRs. This comprehensive approach allows us to determine when a team genuinely adds value and may not require as many ceremonies but should instead be allowed to work.</p><p>In conclusion, the most significant achievement of Agile lies in its ability to enhance communication, promote collaboration, and enable teams to adapt quickly to potential changes. When understood and applied correctly, Agile becomes a valuable tool for any working team. It’s essential to remember that it’s not just about following a set of practices but comprehending why they work and when to apply them to achieve the desired results.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e15d8242787e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Biggest Mistake of Agile]]></title>
            <link>https://medium.com/@adan.gomezcoello/the-biggest-mistake-of-agile-0fe9906521d1?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/0fe9906521d1</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Wed, 11 Oct 2023 00:49:57 GMT</pubDate>
            <atom:updated>2023-10-11T00:49:57.774Z</atom:updated>
            <content:encoded><![CDATA[<p>Agile, a framework for software project management that has gained immense popularity in recent years, has revolutionized the way companies approach the creation of applications and systems. Its manifesto, which emphasizes the importance of “working software over comprehensive documentation,” has been widely adopted as an industry standard. However, behind this focus on immediate functionality lies a mistake that has led many organizations down a path of issues, rework, and high costs.</p><p><strong>The Promise of Agile</strong></p><p>Agile promises fast software development that is adaptable to change, which sounds appealing in a constantly evolving business world. Its emphasis on collaboration, communication, and the early delivery of functional software has led to numerous successes. Agile teams can often develop basic features of an application in record time, allowing them to quickly respond to market needs.</p><p><strong>The Unfulfilled Promise</strong></p><p>However, the biggest mistake of Agile lies in how some organizations have interpreted the mantra of “working software over comprehensive documentation.” This has led to an unbalanced focus on rapid construction at the expense of proper design. The rush to have working software can cause teams to overlook critical design and planning processes with significant consequences.</p><p><strong>Problems Stemming from Misinterpretation</strong></p><p><strong>Poor Code Quality</strong>: The obsession with rapid construction often results in code solutions that work but are hard to maintain. Poor design and lack of planning can lead to low-quality code filled with errors and performance issues.</p><p><strong>Limited Scalability</strong>: Solutions built quickly tend to be less scalable. This means that when you need to add new features or adapt to market changes, the existing software may require significant revisions or even a complete rebuild.</p><p><strong>Hidden Costs</strong>: While initial development might be faster, the hidden costs associated with maintenance and subsequent updates can be substantial. The lack of a solid design can lead to an ongoing development cycle where more resources are spent fixing issues than were initially invested in construction.</p><p><strong>Constant Migration</strong>: Solutions built quickly without a solid design foundation often turn out to be “short-term fixes.” Organizations find themselves constantly migrating from one technology to another, erasing any initial time and resource advantages.</p><p><strong>Lack of Innovation:</strong> Focusing solely on immediate functionality can cause organizations to lose sight of long-term innovation. Inadequate design can limit the ability to create truly innovative and disruptive solutions.</p><p><strong>The Software Gurus in the Agile Manifesto</strong></p><p>To understand why there was such an emphasis on “working software over comprehensive documentation” in the Agile manifesto, we must consider its origin. The manifesto’s authors were true software gurus whose levels of experience and knowledge allowed them to design as they coded seamlessly and efficiently. For these experts, design and construction were one integrated activity.</p><p>However, this perspective doesn’t always align with the reality for most programmers. For the majority of developers, making software work effectively is a challenge in itself, and they often don’t possess the same level of experience and skills as the founders of the Agile movement.</p><p>It’s understandable that software experts might view comprehensive documentation as an unnecessary burden since their deep understanding of design is internalized. However, this doesn’t apply to most field programmers, for whom a lack of solid planning and design can lead to costly long-term consequences.</p><p><strong>Balancing Construction and Design</strong></p><p>The mistake of Agile isn’t in the methodology itself but in how it’s interpreted and implemented. The focus on “working software” shouldn’t be an excuse to neglect proper design. Instead, achieving a balance between construction and design is essential for long-term success.</p><p>Agile teams should remember that immediate functionality is only part of the equation. Proper design, solid planning, and attention to code quality are crucial for avoiding costly issues in the future. Investing in strong design from the beginning can save time and resources in the long run.</p><p>Agile isn’t the problem; it’s how it’s applied. When applied correctly, it can yield excellent results. The main pitfall lies in misinterpreting its focus on immediate functionality as a justification for neglecting proper design and planning. The true path to success involves finding a balance between construction and design to achieve high-quality, sustainable software in the long term.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*Dwyu_Y34WyWdFvYrRuArXw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0fe9906521d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should Companies Really Undertake Digital Transformation?]]></title>
            <link>https://medium.com/@adan.gomezcoello/should-companies-really-undertake-digital-transformation-c0728545a1ba?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0728545a1ba</guid>
            <category><![CDATA[customer]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Sat, 09 Sep 2023 13:43:27 GMT</pubDate>
            <atom:updated>2023-09-09T13:43:27.804Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s fast-paced business world, where new approaches and trends emerge daily, it’s entirely valid to question whether “digital transformation” is a passing fad or a true necessity. Due to the complexity of contemporary business challenges, ongoing technological advancements, and cultural shifts in the way we work, we can confidently say that it is indeed necessary. Digital transformation, although it may sometimes seem like a buzzword, has become an imperative for the survival and success of companies. It’s precisely these arguments about the need for transformation that hint at a synonymous concept that needs to be understood more clearly: <strong>adaptation</strong>.</p><p>Over the past centuries, we have witnessed businesses’ impressive ability to <strong>adapt </strong>and evolve in response to changes in the business landscape. However, what we are currently witnessing is an <strong>adaptation </strong>that surpasses in speed and scope any other period in history. This accelerated <strong>adaptation </strong>has become possible thanks to the digital revolution, which has driven the transformation of technology, communications, and business processes. Just as in past centuries when machines were the foundation of industrial revolutions, today, digital technology is the driving force behind businesses’ constant <strong>adaptation</strong>.</p><p><strong>Adaptation: The Cornerstone of Transformation</strong></p><p>As mentioned earlier, the key concept in digital transformation is <strong>adaptation</strong>. Transformation involves changing how work is approached and directed toward a constant quest to enhance customers’ lives through products and services. However, achieving this entails deeply understanding customers’ needs and precisely tailoring solutions to meet those needs within increasingly tight timeframes.</p><p>Generating real value for customers with an excellent “time to market” is no easy task. Many companies have operated with traditional approaches, project-driven structures, rigid hierarchies, and a focus on profitability, often leaving customers in the background, despite being the lifeblood of any business. Transformation involves <strong>adapting </strong>these outdated structures and operational models and redirecting the focus toward those who are the core reason for any business’s existence: customers.</p><p><strong>Key Approaches to Transformation</strong></p><p>During this transformation process, several necessary approaches are <strong>adopted </strong>to achieve the desired change. Two fundamental approaches are data-driven decision-making and agility. The former is based on making decisions supported by concrete data, allowing for a deep understanding of customer needs and more precise decision-making. On the other hand, agility, which emphasizes flexibility, collaboration, and rapid response to change, involves <strong>adopting </strong>methodologies that promote agility in communication and significantly accelerate “time to market.” These methodologies foster close collaboration among teams, faster decision-making, and incremental delivery of products or services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*fEoqsJctgJIsuS8-zKEUDw.png" /></figure><p><strong>The Digital Component’s Vital Role</strong></p><p>After placing the customer at the center of our decisions, guiding our steps with data, and establishing an agile operational model to create value, it’s time to introduce our star player: digital technology. This is why we refer to this process as “digital transformation.” At this stage, the goal is to <strong>adapt </strong>our value-generation chain to digital approaches that not only increase efficiency but also significantly aid decision-making and the creation of real value for customers, enabling an appropriate and competitive “time to market.”</p><p>In this context, we’re talking about a wide range of digital solutions, ranging from automating processes that were once manual to implementing digital channels that offer instant solutions to customers. Additionally, we can consider subscription models and other digital strategies that make customers’ lives considerably easier while making the company far more competitive in the market. These digital solutions not only enhance operational efficiency but also transform the way we interact with customers and deliver value at a constant pace.</p><p><strong>Conclusions</strong></p><p>Ultimately, digital transformation is about <strong>adaptation</strong>. It’s a process that seeks to restructure and <strong>adapt </strong>a company’s operations to remain agile and customer-focused. Without customer support, any company finds itself in a precarious position. Digital transformation is not a passing trend; it’s the key to survival and success in today’s business world.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0728545a1ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Programming: Art or Engineering?]]></title>
            <link>https://medium.com/@adan.gomezcoello/programming-art-or-engineering-4bea13db7511?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bea13db7511</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[art]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Thu, 07 Sep 2023 03:06:56 GMT</pubDate>
            <atom:updated>2023-09-07T03:06:56.876Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*E8jLwVWBgQYoRUhhNx3A5g.png" /></figure><p>Programming, that amalgamation of lines of code that brings modern technology to life, has been the subject of an ongoing debate regarding its essence. Is it a purely engineering discipline, or a field where creativity flows like an artistic expression? In this article, we will explore this duality that surrounds programming, and how, on certain occasions, this routine transforms into an artistic expression that challenges the traditional boundaries of engineering.</p><p><strong>Programming as Engineering</strong></p><p>At its core, programming is an engineering discipline. It requires meticulous planning, precise calculations, and rigorous analysis. Programmers, like software engineers, must build solid, efficient, and reliable systems. Databases must be designed with precision, algorithms must be optimized, and tests must be exhaustive. Here, programming resembles civil engineering, where every structural calculation must be perfect to ensure the solidity of a bridge.</p><p><strong>Transformation into Art</strong></p><p>However, there are moments when programming deviates from the path of engineering and ventures into the territory of art. It’s akin to the Japanese tea ceremony, once a daily routine, now a deeply rooted artistic expression in culture. The tea ceremony, or “chanoyu,” is a Japanese practice that combines the preparation and presentation of tea with an appreciation for aesthetics and simplicity. What was once a purely functional process evolved over time to become a highly ritualized art.</p><p><strong>The Art of Programming</strong></p><p>What makes code a work of art? Elegance. The ability to solve complex problems simply and beautifully. Programming, like art, is often subjectively judged. Code that is a marvel of engineering might be perceived as mediocre, while seemingly simple yet brilliant code can be admired as a masterpiece.</p><p><strong>Subjectivity in Code Aesthetics</strong></p><p>The subjectivity in appreciating code as art is fascinating. One programmer might look at a single-line function and marvel at its beauty and efficiency, while another might find the same line of code confusing and incomprehensible. This duality reflects the nature of art: its meaning and value can vary depending on the observer.</p><p><strong>Becoming an Artist from an Engineer</strong></p><p>So, how does one transform from an engineer into an artist in the realm of programming? It requires a deep understanding of programming techniques and patterns, combined with a dose of ingenuity and creativity. By merging the structured knowledge of engineering with the flexibility of artistic expression, a programmer can evolve from a mere coder into a true artist of code. This transition is where the boundaries blur, and lines of code become strokes of genius on the canvas of technology.</p><p><strong>The Perfect Balance</strong></p><p>Ultimately, programming is a unique discipline that resides at the intersection of engineering and art. Finding the perfect balance between rigorous functionality and creative aesthetics is the challenge that programmers face in their quest for excellence.</p><p>In conclusion, programming is both engineering and art. It depends on the perspective of the observer and the context in which it is used. Whether it’s like a steel structure supporting a building or a painting that captivates the soul, programming is ultimately an expression of human creativity and logic at its finest.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bea13db7511" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stay Focused on Your End Product]]></title>
            <link>https://medium.com/@adan.gomezcoello/stay-focused-on-your-end-product-33f5cada8daf?source=rss-d46e70d150b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/33f5cada8daf</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[customer-centric]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Adán Gomezcoello]]></dc:creator>
            <pubDate>Mon, 04 Sep 2023 01:17:20 GMT</pubDate>
            <atom:updated>2023-09-04T01:20:17.641Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*ByCS78vRlIQwbK1ldHKHFg.png" /></figure><p><strong>What is a product in the business context? </strong>This seemingly simple question can lead us down a labyrinth of definitions and approaches. I recently discovered this in my own workplace, where discussions about transitioning to a product-oriented company led us into unfamiliar territory.</p><p>At some point along the way, the lack of clarity about what constituted a product made the discussion confusing. We began to label applications, processes, and business capabilities as “products.” It seemed we had lost sight of the essential: a product is not merely a tool or a platform; it is the embodiment of an offer to the customer.</p><p><strong>The Misconception of Platforms and Applications</strong></p><p>In the world of business and technology, the term “product” is often misunderstood. For some, any platform or application is considered a product in itself. In the digital era, where platforms and applications seem to proliferate everywhere, it’s easy to confuse technology itself with the product. However, this perspective can lead to an incomplete understanding of what it truly means to create value for the customer.</p><p><strong>Painting as the Final Product</strong></p><p>To better grasp the concept of a “product,” let’s consider a painter. What is their end product? The answer is simple: the painting itself. This artwork is the tangible result of their creativity and skill. The brushstrokes, colors, composition, and technique are the capabilities the painter employs to bring their end product to life: the painting. This finished canvas is what is presented to the public, valued, and purchased.</p><p><strong>Product-Oriented Transformation</strong></p><p>Applying this analogy to the world of business and technology, a product-oriented transformation takes on new meaning. Instead of solely focusing on technology or the tools used, this perspective centers on the end product, on what genuinely satisfies customer needs and desires.</p><p><strong>An Example from Banking</strong></p><p>Take, for example, the world of banking. Banks are often considered to offer a wide range of digital services, from mobile applications to online platforms. However, from a product-oriented transformation perspective, the actual product a bank offers is a loan. It’s the loan that a customer seeks when they need financing to buy a house, a car, or start a business. Mobile applications and other digital channels are merely tools that support the delivery of this end product: the loan.</p><p><strong>The Customer as the Central Focus</strong></p><p>Product-oriented transformation places the customer at the heart of everything. Just as a painter strives to create artwork that connects with their audience, businesses must endeavor to provide products that solve problems and meet the needs of their customers. This involves thoroughly understanding who their customers are, what they desire, and how to provide them with genuine value.</p><p><strong>Capabilities as a Means, Not an End</strong></p><p>In this approach, technologies, tools, and capabilities are considered means to an end, not the end itself. They are the tools that support the process of creating value for the customer. Just as a painter carefully selects brushes and colors to create the perfect painting, businesses must strategically choose and utilize technologies to build products that genuinely positively impact their customers.</p><p><strong>Benefits of Product-Oriented Transformation</strong></p><p>Product-oriented transformation brings numerous benefits. By focusing on the end product and customer satisfaction, companies can:</p><p><strong>- Improve customer satisfaction:</strong> By offering products that genuinely meet customer needs, a loyal and satisfied customer base is created.<br><strong>- Drive innovation: </strong>By focusing on creating high-quality products, continuous innovation is fostered, constantly seeking ways to improve.<br><strong>- Optimize efficiency: </strong>By using technologies and tools strategically, companies can optimize processes and resources to deliver products more efficiently.</p><p><strong>Conclusion</strong></p><p>Product-oriented transformation reminds us that, ultimately, real value is created when a product satisfies customer needs. Just as a painter doesn’t fixate on brushes, color palettes, or canvases but on the final painting, businesses must focus on the end product they offer to the market. This involves understanding the customer, using technology strategically, and maintaining a constant focus on quality and customer satisfaction. Embracing this perspective allows companies to create genuine and lasting value in an ever-evolving business world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33f5cada8daf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>