<?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[manas.tech - Medium]]></title>
        <description><![CDATA[We build unconventional software, and here we talk all about it - Medium]]></description>
        <link>https://medium.com/manas-tech?source=rss----af888569068a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>manas.tech - Medium</title>
            <link>https://medium.com/manas-tech?source=rss----af888569068a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:29:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/manas-tech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What can you envision yourself doing for 20 years?]]></title>
            <link>https://medium.com/manas-tech/what-can-you-envision-yourself-doing-for-20-years-4122a9752f53?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/4122a9752f53</guid>
            <category><![CDATA[teal-organizations]]></category>
            <category><![CDATA[long-term-thinking]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[systemic-design]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 19:51:56 GMT</pubDate>
            <atom:updated>2023-07-07T19:51:40.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo by Greg Rakozy on Unsplash" src="https://cdn-images-1.medium.com/max/1000/0*_ChDz1VaQ0ODahZI" /><figcaption>Photo by <a href="https://unsplash.com/@grakozy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Greg Rakozy</a> on <a href="https://unsplash.com/photos/oMpAz-DN-9I?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Many coaches, motivational speakers and advisors go on and on about questions like “<em>where do you see yourself in 5 or 10 years?</em>”, about the need to think long-term, and about the importance of playing the long game. But twenty years is a long, long time. For most people, it’s half of their entire work life. Very few are willing to commit that much time to a project.</p><p>This article aims at two simultaneous targets: on one hand, it aims to serve as <strong>a praise for vision, commitment and evolution</strong>; on the other hand, it aims to serve as <strong>an invitation to explore</strong> what can be achieved when we really go full-on into the long term.</p><h3>The praise</h3><p>This past month, <a href="https://manas.tech/"><strong>Manas.Tech</strong></a> turned 20. That’s two whole decades of leveraging all kinds of technology tools to solve problems. And two whole decades of carefully and dutifully laying a foundation and setting up scaffolding to <strong>enable people to build whatever they want, however they want</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PiB-4eJ-jcHHLXvCN0MdLg.jpeg" /></figure><p>To mark the 20th anniversary, the entire company flew to a resort in Brazil, to spend 5 days connecting to each other without technologic mediation. Some of us actually met for the first time in person, or met again after some <strong><em>years of almost exclusively working together remotely</em></strong>.</p><p>That last sentence sounds simple enough, but there is quite a lot going on there. There is a significant amount of work behind a team’s capability to work remotely while maintaining the quality of what they deliver and the quality of the interactions that foster good collaboration. That is part of what you get when an organization has been operative for two decades.</p><p>But not only the passing of time makes this possible: leaders need to invest heavily, consciously and consistently in creating, maintaining and updating the mechanisms that enable efficient collaboration.</p><p>Let’s look at some of those.</p><h4>Communication tools</h4><p>The single greatest communication tool is <strong>making agreements</strong>. Different people call it by different names, such as protocols, rules, guidelines or even tips. They all mean the same thing: there needs to be agreement on how we will use each thing, so that everyone knows how to play the game and we get better at playing it over time.</p><h4>Management tools</h4><p>Whatever it is that you do, as long as you keep doing it, two things are likely to happen:</p><ol><li>you’re going to get better at it, and</li><li>you will start doing more of it.</li></ol><p>To do #2 without letting go of #1, you need to find ways to <strong>manage your work</strong>. Management done right is a delicate alchemy of methodology and tools. The seal of truly great management is the design of one’s own flavor of methodology and a bespoke set of tools. We have developed many tools that align with our specific needs and wants, and with the particular way in which our organization works.</p><p>We have our own tools for billing and finance management, tools to keep track of tasks, projects and responsibilities, tools that help us keep records of important things in a way that doesn’t demand constant up keeping.</p><h4>Human tools</h4><p>Organizations are groups of humans who come together to achieve something greater than themselves. Taking care of those humans is the best way to enable them to build things far greater than you can imagine. Human tools involve the creation of safe, transparent and sustainable practices that help people feel they can do their best work, express their views and opinions, and build meaningful relationships with both peers and clients.</p><h3>The invitation</h3><p>If you’ve been reading attentively, you surely noticed that these tools are much more than a way of working remotely: they are the basis for working. Period.</p><p>These three systemic units (communication, management and human) make up the larger system that is the organization, which will function only as well as these three systems do.</p><p>During our retreat in Brazil, the main goal was to relax, celebrate 20 years of doing what we love to do, and connect with the team. And we fulfilled those goals. But we also made time to reflect on how these three systems impact us on the day to day.</p><p>And this is also an invitation to you. To look into your organization and systems, to map out what it is you want to achieve and, most importantly, what happiness looks like to you.</p><p>For guidance, this is how we approached this, and some of the decisions we’ve made over the years, which got us here.</p><h4>No-objectives &gt; Guided by principles</h4><p>Management by objectives only works well if you are positive about what the objectives you want to accomplish are, and <a href="https://www.techtarget.com/whatis/definition/Results-Only-Work-Environment-ROWE#:~:text=A%20Results%2DOnly%20Work%20Environment,personal%20days%20or%20vacation%20days."><strong>ROWE</strong></a> is a great approach if you have those specific objectives and can define corresponding metrics, but <strong>when you are optimizing for happiness, there is no such thing as clear objective/goals</strong>.</p><blockquote>So, why would a company want to optimize for happiness?</blockquote><p>Well, for starters, to survive and thrive for more than 20 years. Somehow, people spend most of their time approaching problems in terms of finding solutions, but surprisingly little pondering how happy they would be if they succeed.</p><p>Optimizing for happiness, then, sounds laughable for most leaders at first sight. It would seem that happiness and business have nothing to do with each other, and anyone who optimizes for anything other than profits is simply mad. But organizations are made of people, and people stay where they are happy.</p><p>What most leaders don’t reflect so much upon is that investing in happiness is <a href="https://manas.tech/blog/2022/03/07/virtuous-cycle/">a very good way –probably the best– of building long-term revenue</a>. Over time, teams develop mechanics which make them faster, more efficient, and help them build trust.</p><p>Aligning incentives to achieve business results creates an environment of fierce competition, an obsession with metrics and information hiding. Optimizing for happiness, on the other hand, shifts focus away from reaching a goal no matter what, towards the motivation behind people’s actions, and makes it quite pointless to compete, measure obsessively. and hide information, by creating an environment where people collaborate, share and are open with each other.</p><h4>Dropping ancient artifacts</h4><p>Another key factor in the creation of sustainable organizations is changing mindsets. Some of these are kind of an invisible and unwanted inheritance: we tend to build organizations more or less intuitively and fall into patterns that others have created, without thinking too much about how accurate or appropriate they are, and they are such subtle traits that it can be difficult to point at them when they are causing problems.</p><p>So, a dedicated effort to creating awareness about our systems is the first step in the direction of sustainability. Our <a href="http://What most leaders don&#39;t reflect upon so much is that investing in happiness is not only beneficial for the well-being of individuals but also a crucial factor in building long-term revenue and success. Organizations are comprised of people, and people tend to stay where they are happy.  At first glance, optimizing for happiness may seem laughable to most leaders. Happiness and business are often perceived as separate entities, and those who prioritize anything other than profits might be deemed as irrational. However, when individuals within a company are happy, they become more engaged, motivated, and productive.  Over time, teams develop internal mechanics that make them faster, more efficient, and adaptable. Trust and long-term collaboration allow for open and free-flowing communication, fostering innovation and problem-solving. When employees are satisfied and feel valued, they are more likely to go above and beyond to achieve shared goals.  Investing in happiness goes beyond providing superficial perks or short-term incentives. It involves creating a work environment that prioritizes the well-being and growth of employees. This can be achieved through transparent and sustainable practices that empower individuals to do their best work, express their ideas, and foster meaningful relationships with both peers and clients.  One key aspect of building a successful organization is developing effective communication tools. Establishing clear agreements, protocols, and guidelines ensures that everyone understands how to collaborate efficiently and promotes continuous improvement over time. When individuals are aligned in their understanding of how to work together, they can focus on driving progress and delivering high-quality results.  Additionally, implementing robust management tools is crucial to managing workloads effectively while maintaining and improving performance. As companies grow, it becomes essential to find methodologies and tools that align with their unique needs and processes. By designing customized approaches and utilizing tailored tools, organizations can strike a balance between scaling their operations and maintaining the high standards they&#39;ve established.  Celebrating milestones, such as the 20th anniversary of a company, provides an opportunity for reflection and connection. Gathering the entire team in a setting away from technological distractions allows individuals to forge stronger relationships and deepen their bonds. It highlights the importance of investing in both technological infrastructure and human interactions to create a harmonious work environment.  In conclusion, the ability to envision and commit to long-term goals is essential for building a successful and thriving organization. By investing in effective communication, management systems, and human-centered practices, companies can foster an environment that promotes collaboration, innovation, and happiness. Prioritizing the well-being of employees not only cultivates a positive work culture but also serves as a catalyst for long-term revenue generation and sustainable growth.">handbook</a> contains a beautiful quote by Eduardo Galeano that points directly to this:</p><blockquote>We are what we do to change who we are</blockquote><p>A lot of things at Manas work very differently than anywhere else, and were originated by a consistent effort to make space for introspection. That is how we find, rethink and recreate artifacts and methods that were installed by use, but not conscious choice. Making time to look inwards as an organization, thinking about and discussing how we want Manas to be, is a core pillar of our culture.</p><h4>Test, measure, iterate</h4><p>The most important thing about all of that introspection is translating it into <strong>experiments</strong>. Quickly. We believe in testing things out and seeing what works and how, instead of endlessly discussing what might happen.</p><p>Over the years, we’ve had plenty of people reach out to us and ask about our internal systems, how they work and how to implement them. What most of them imagine is that you can implement one thing or another and then sit back and watch the magic happen.</p><p>Few imagine what it really goes into spearheading things under complete uncertainty, measuring with less data than one would hope, and correcting course on the run. Experiments on organizational dynamics, especially, involve a systemic ripple effect: anything you modify leads to subsequent modifications that become necessary when a part of the system changes.</p><p>What makes systems work, though, is precisely the awareness of how much they will –<em>need to</em>– evolve over time, adapting to the context and to their own evolution. Phil Stutz expresses it hardly and straightforwardly:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/0*rII1oGD2voEj7pkH.jpg" /></figure><h3>Something to think about</h3><p>When I first came in contact with Manas, it just seemed impossible. I knew of no other organization that worked like this one did.</p><p>A bunch of years later, I still know of no other organization that has no hierarchies and no rigid role structures, yet runs a smooth operation. I know of no other organization that decentralizes decisions about salaries, projects, budgets, hiring –<em>and pretty much everything else</em>–, and that has remained profitable for over 20 years. I know of no other organization that spends so much time reflecting upon what they do, how they do it and why, without seeing productivity go down, but the opposite.</p><p>When I first came in contact with Manas, it just seemed impossible. The more I think about it, though, the more it makes perfect sense. Also, the more I come to be convinced that the company has survived and thrived for more than two decades, not in spite of, but <strong><em>thanks to</em></strong> a stubborn will to challenge things that are presented as a given.</p><p>As Daniel H. Pink says</p><blockquote>“asking ‘why’ can lead to understanding; asking ‘why not’ can lead to breakthroughs.”</blockquote><p>Here’s to twenty more years of challenging the world around us. And to you doing the same with the world around you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4122a9752f53" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/what-can-you-envision-yourself-doing-for-20-years-4122a9752f53">What can you envision yourself doing for 20 years?</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What ‘high quality code’ means]]></title>
            <link>https://medium.com/manas-tech/what-high-quality-code-means-5b3ec1cfb763?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/5b3ec1cfb763</guid>
            <category><![CDATA[high-quality-code]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Fri, 26 Nov 2021 20:39:24 GMT</pubDate>
            <atom:updated>2021-11-26T20:39:23.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h4TLlisFk7XvtREAsS7C7Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cgower?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Christopher Gower</a> on <a href="https://unsplash.com/s/photos/code?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Philosophy, praxis and examples</h4><p>Imagine you knew the materials destined to build homes and vehicles were flawed. Would you still build with them? Or if you knew that the ingredients that will go in your food were spoiled. Would you still eat them?</p><blockquote><strong>The quality of the building blocks that make the lives we live determines the quality of our lives.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*7_-LQojqpsbTbiLX.jpeg" /></figure><p>Software has also become a core element of what makes up our daily livelihoods, which means that the quality of the software we code (and use) will significantly influence the quality of our future.</p><p>Humanity has made that mistake in the past: fossil fuels, plastic, greenhouse gases, pouring waste into potable water sources, and the list goes on.</p><blockquote><strong>Short-term benefit often hides mid- and long-term loss</strong>.</blockquote><p>A lot of articles can be found on high quality code. Pretty much all of them are structured as a step-by-step guide to write good code, but no one can actually believe that an article can teach someone how to do that. This is not one of those.</p><p><a href="https://manas.tech/"><strong>Manas.Tech</strong></a> is an organization known for the quality of the code it produces, with nearly two decades of developing high performing software tools. So, instead of trying to write yet another impossible tutorial, we want to focus on gathering the combined knowledge of our engineers to find some insightful criteria that points us in the direction of how good quality code is conceived, designed and built.</p><h3>How to know when we got there</h3><p>A quick online search throws a bunch of different perspectives and definitions about this topic, but if we read carefully into them, they all end up sounding more and more like opinions. Sometimes, they even come across as an attempt at SEO, aiming for positioning at the expense of clarity and insight. But we’re not trying to find the best answer to a prototypical user’s search terms, we’re trying to come up with useful, applicable guidelines that shape the way we approach building sustainable, maintainable and efficient code.</p><p>So, why do we want a good definition of high quality code? Because we need a methodical and objective way to determine that we’ve created code that is high quality. Why? Because, as we said, software is now a core element of most of the products and services that our lives are built upon. Uniform criteria to determine the quality of the systems that make up our world becomes a requirement.</p><p>So, having a good sample of experienced software engineers at hand, we decided to <strong>survey our team</strong> to try and come up with a solid, functional definition of high quality code.</p><h3>Survey</h3><p>The questionnaire was brief by design. We wanted to get meaningful answers, but not take a significant amount of time from our engineers. The goal was to ask ourselves how we create and deliver high quality code, which could also serve as the foundation for building a document that reflects how we think about code and our everyday practice. Also, we didn’t want respondents to lose interest and lower the quality of their answers just to get it over with.</p><p>One of the items in the survey was <em>«What is the first question you try to answer when evaluating the quality of code?»</em>, a question aimed to surface the respondents point of entry to code review. Across the board, the answer was <em>«What does the code do?»</em>. It sounds common-sensical, yes. But it points to a very functional-oriented evaluation, which starts to say something quite interesting when we look at other questions in the survey.</p><p>For instance, when asked what attributes our engineers rank the highest as a symptom of good quality code, the first response was <strong>clarity</strong>, followed by <strong>effectiveness</strong> and <strong>simplicity</strong>.</p><blockquote><strong>Good quality code is clear about what it does, it does it well, and it does so simply.</strong></blockquote><p>A nice complement to this view is that, on the opposite end, most of the surveyed engineers pointed that <strong><em>a symptom of bad quality code is high complexity</em></strong>. This reminds me of Ozzy Osbourne saying:</p><blockquote>«I don’t want you to play me a riff that’s going to impress Joe Satriani; give me a riff that makes a kid want to go out and buy a guitar and learn to play.»</blockquote><p>But I digress.</p><p>Aside from high complexity, other high ranking indicators of bad code were :</p><ol><li><em>«another developer’s difficulty or incapacity to explain or understand what the code does»</em></li><li><em>«a lack of clarity»,</em> and</li><li><em>«a lack of post-reflection»</em>.</li></ol><p>Basically, <strong>bad code looks like a mess</strong>. Not only it is less efficient, sometimes even inefficient. It looks messy to other developers. It gives them a hard time understanding what it is and what it does. And that points towards a developer who has difficulty with creating good abstractions. Which is another way of saying that they haven’t taken the time to fully understand the nature and complexity of the problem they’re trying to solve. As Einstein said, <em>«If you can’t explain it simply, you don’t understand it well enough.»</em></p><h3>What it all means</h3><p>This survey gives us a glimpse into what high end software engineers think when designing, building and reviewing code. We did our best here to boil all of that down to a summary of indispensable attributes that make for good quality code, and something more like a rule of thumb to identify bad quality code.</p><p>This is not enough, though. Building high quality software doesn’t necessarily take more time or even cost more, but it does require a careful and methodical approach that usually means that the engineers behind it have spent more time thinking about the problem (and have previously spent more time thinking about <em>other</em> problems), exercising their craft and polishing their skills.</p><p>The problem is that, most often than not, we don’t know when building materials are of poor quality or that the food we eat was prepared with less than ideal ingredients. And, more often than not, we notice the quality of the code because it is bad, precisely because of the negative consequences it brings. As Nassim Taleb puts it:</p><blockquote><strong>We see the obvious and visible consequences, not the invisible and less obvious ones. Yet those unseen consequences can be — nay, generally are — more meaningful.</strong></blockquote><p>Good quality software is kind of like running water: we open the tap and expect it to flow. And as long as it does, we don’t really reflect on how that came to be. We only notice it when it doesn’t, when our expectations are missed.</p><h3>So, what does «high quality code» mean?</h3><p>It means that someone put in their time, effort and long term developed skills into designing, building and expressing the solution to a problem in a way that works and creates a good base for continued evolution. As mentioned earlier, that quality translates into the quality of the life we can expect to build on top of it. So, any way we want to look at it, good quality software is a smarter investment than the alternative.</p><p>We want to strive for good quality code because the nature of business is to constantly change, and that makes requirements change, which leads to changes in functionality. So, then code needs to be modified, in order to adapt to the new business requirements.</p><p>What if we build architectures that <strong><em>expect</em></strong> change? That is the very question asked by Neal Ford, Rebecca Parsons and Patrick Kua, in their book <em>Building Evolutionary Architectures</em>. What if, instead of aiming to build something that fights off change, we built systems that flow with it. After all, change is the only constant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cmq9C9Lp9zJPS3uK.png" /></figure><p>From that point of view, <strong>high quality code is code that any developer can easily understand what it is doing, how it is doing it and how to change it so that it does something else</strong>.</p><p>High quality code and evolutionary architectures go hand in hand, and that should be the primary indicator of a successful software endeavour.</p><p>First and foremost, because software is the language spoken by most of the things and systems that make up our everyday lives: we are way more dependent on software than we realize, and a lot of the situations we regularly identify as unfair, impractical or frustrating, are the product of not understanding the situation with enough clarity, which leads to poorly designed systems and mixed and matched code that keeps growing in complexity in a futile attempt to get those poorly designed systems to fix the reality they don’t fully grasp.</p><p>Second, because the attributes of clarity, effectiveness and simplicity are not merely a whim, or a stubborn quest for elegance, but a fundamental way to build robust solutions that can stand the test of time, adapt to an evolving technological landscape, and serve as the foundation for future developments.</p><p>And last but not least, because any corners we cut today will create headaches, turmoil and even catastrophe for the future. As creators, as contractors, as clients and even as consumers, we should own up to that responsibility.</p><p>Wherever in the ecosystem you are, you can step up and demand high quality code. It makes a real difference.</p><p><em>Originally published in the </em><a href="https://manas.tech/blog/2021/11/05/high-quality-code/"><strong><em>Manas.Tech blog</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b3ec1cfb763" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/what-high-quality-code-means-5b3ec1cfb763">What ‘high quality code’ means</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product Marketing Engineer]]></title>
            <link>https://medium.com/manas-tech/the-product-marketing-engineer-2eb2f59f0ac1?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/2eb2f59f0ac1</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[product-engineering]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[product-marketing]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Wed, 17 Nov 2021 19:43:16 GMT</pubDate>
            <atom:updated>2021-11-17T19:43:15.964Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0ST1H2rhR4dX6t-w5GMdg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@lazizli?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Lala Azizli</a> on <a href="https://unsplash.com/s/photos/product%20engineer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Birth of a new kind of software engineering</h4><p>This article stems from a conversation that we come back to from time to time. A conversation around the idea that software engineering is changing, and it increasingly requires that teams have a deep understanding of the business side of things as much as they do the technical aspects.</p><p>This happens because software development is no longer an isolated practice. What was once a self-contained, somewhat obscure discipline that occupied a select group of initiates, is now a core pillar of our modern lives and is rapidly becoming the most sought-after talent in the world. So much so, that virtually every business, in some way or another, relies on software and information technologies to exist and operate.</p><p>Nowadays, technological products and services originate on both sides: engineers create and offer them to businesses, and businesses actively generate demand for software products to address their specific needs. This situation gives birth to a communication problem: engineers and businesses speak different languages, aim for different goals, and often have different views on what is important when it comes to designing and building software tools.</p><h3>Middle ground to be claimed</h3><p>A useful framework to get into this conversation is the one proposed by <strong>Kenton Kivetsku</strong>, former Googler and founder of <a href="https://www.rocketblocks.me/">RocketBlocks</a>, who <a href="https://www.youtube.com/watch?v=KkZP2EMa3k8">in this video</a> explains the difference between the role of a Product Manager (PM) and a Product Marketing Manager (PMM).</p><p>For the purposes of this article, let’s get rid of the names he uses for these two roles, and explore the general idea of product management tasks and responsibilities that range from being more customer-focused or rather more engineering-focused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SvTfe8CbrhI_WRUe.png" /></figure><p>Kivetsku lays out a spectrum where Customers and Engineers sit at opposite ends. As we near either one of those ends, we find that tasks and responsibilities get more tactical in nature, into the specific realm we approach. On one end, tactical action focuses on the engineering side of things (building an infrastructure, developing features, deploying services), while on the other end, they progressively focus on the customer-facing side of the business (understanding customer behavior, designing experiences, spreading the word).</p><p>The interesting part, as you can see, is right in the middle. Strategic efforts are not something that can be carried out by an isolated team or manager, but are rather a joint venture that can only be successful when it aligns the goals of each team and the organization, drawing a line that ties the hardcore technical aspects directly with customer needs.</p><p>This is key: <strong>whenever strategic decisions are made leaning too heavily to one side or the other, products suffer.</strong></p><h3>A graveyard for apps</h3><p>Back in 2009, Apple debuted a <a href="https://www.youtube.com/watch?v=szrsfeyLzyg">TV commercial for the iPhone</a> with the catchphrase <em>“</em><strong><em>There’s an app for that</em></strong><em>”</em>. There was such buzz around the idea, they were even <a href="https://trademarks.justia.com/779/80/there-s-an-app-for-77980556.html">granted the trademark</a> for it a year later. And everyone jumped on that train.</p><p>Not long after, though, it became apparent that, unless you had some sort of leverage that made your app indispensable, there was a slim chance that anyone was going to download it. That is how we found out that the lesson from the dot.com bubble was not properly learned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d3151qEUhijs68SQ.jpeg" /></figure><p>Have you ever visited the App Burial Grounds? My guess is you haven’t. Firstly, because it is not a real place, and secondly because no one ever goes there. That’s why the very idea of an App Burial Grounds exists in the first place: there lie the apps that no one ever visits.</p><p>The majority of the apps that were conceived during the ‘there’s-an-app-for-that-fever’ now rest in the App Burial Grounds. Why? Because they were ill-conceived, created with the wrong thing in mind. Those apps that now forever rest unvisited, were <strong>conceived as solutions in search of a problem</strong>.</p><p>We’ve all heard stories of engineers who fall in love with a technical feature that no customer resonates with, or product marketers who envision dreamlike experiences for customers that are either technically non-viable or impossibly expensive.</p><p>This is what happens when strategic decisions are made on tactical premises.</p><h3>Rise of the Product Marketing Engineer</h3><p>To address these strategic decisions around technological products, a new figure arises.</p><p>Where Product Engineering is responsible for developing the product and keeping it operating, and Product Marketing is responsible for representing the customers interests within the product team, <strong>the Product Marketing Engineer (PME)</strong> is responsible for providing a comprehensive and strategic view of the relationship between product and customer that encompasses the full arc: their function is that of seeking balance between feasibility, viability and desirability.</p><blockquote>The Product Marketing Engineer combines long-term business vision, a deep understanding of user experience and empathy for end customer needs with a solid understanding of the principles of software architecture, an operational knowledge of every stage in the development process and a basic grip on the math behind effort estimations.</blockquote><p>Most teams (the good ones, at least) already bring all of these skills to the table and perform the bulk of the PME’s responsibilities as a whole. But something always gets lost in translation.</p><p>Instead of relying on different people, with different pieces of a puzzle, who have to assemble it each time, a Product Marketing Engineer has the skills to form a complete view of the puzzle in their mind, and can act as a natural interpreter. They ease the back and forth of ideas, reduce communication noise and make sure there are no inconsistencies or blind spots in the team’s conception of the problem to be solved and the array of potential solutions to be developed. Of course, this needs careful follow-through and lots of communication in order to scale.</p><h3>The road ahead</h3><p>Software is not what it used to be. While the <a href="https://manas.tech/blog/2021/11/05/high-quality-code/"><strong>quality of the code</strong></a> and the elegance of the solution is still a hallmark of a good engineer, the context in which they operate is very different. Design, UX and accommodation to customer needs are now an integral part of software development, and pivotal to its success.</p><p>The best way to make sure our endeavours steer clear of the App Burial Grounds is to invest in strengthening the link between engineering and customer satisfaction. Or, put in other terms, the link between our tools and our goals.</p><p>Until not too long ago, development teams fulfilled these functions as a collaborative effort: some of the people in the team took care of the engineering, and others took care of the customers. They met halfway, discussed and agreed on how to move forward, and organized the work around those agreements.</p><p>Today, a Product Marketing Engineer takes over <strong>the responsibility of orchestrating the efforts of a whole team</strong>, covering the full span of devising technically robust products that delight customers, and facilitating collaboration during the product development process, freeing everyone else to focus on their specific roles.</p><p>In the near future, most members of the product team will have the PME’s skillset, as it will be hard to overlook the relevance of incorporating a new role that is capable of orchestrating strategic decisions around the product.</p><p>Why not get a head start today?</p><p><em>Originally published in the </em><a href="https://manas.tech/blog/2021/11/05/product-marketing-engineer/"><strong><em>Manas.Tech blog</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2eb2f59f0ac1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/the-product-marketing-engineer-2eb2f59f0ac1">The Product Marketing Engineer</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How can we design software to handle complexity?]]></title>
            <link>https://medium.com/manas-tech/how-can-we-design-software-to-handle-complexity-eecadcd4f85a?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/eecadcd4f85a</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Mon, 26 Jul 2021 18:14:58 GMT</pubDate>
            <atom:updated>2021-07-26T18:14:44.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YBTM4fB81Gc6wubk_luyLA.png" /></figure><h4>A tale of spreadsheets, complexity and human nature</h4><p>You’ve probably heard about the so-called “blame game” unleashed in the UK after news surfaced that the <strong>authorities failed to report nearly 16,000 positive COVID-19 cases</strong>. You’ve probably also heard that this was “<a href="https://www.dailymail.co.uk/news/article-8805697/Furious-blame-game-16-000-Covid-cases-missed-Excel-glitch.html">caused by an Excel spreadsheet containing lab results reaching its maximum size</a>”.</p><h3>Matt Parker on Twitter: &quot;When I first heard that cases were missing I thought &quot;can&#39;t be an Excel problem, the rows run out at 1,048,576 which is bigger than even total cases&quot;.I never thought they&#39;d have a case per COLUMN. Unbelievable. And yes: Excel columns end at 16,384 aka &quot;XFD&quot;. https://t.co/To9b4qIuzD / Twitter&quot;</h3><p>When I first heard that cases were missing I thought &quot;can&#39;t be an Excel problem, the rows run out at 1,048,576 which is bigger than even total cases&quot;.I never thought they&#39;d have a case per COLUMN. Unbelievable. And yes: Excel columns end at 16,384 aka &quot;XFD&quot;. https://t.co/To9b4qIuzD</p><p>There are a couple of things (<em>at least</em>) to be said about this.</p><p>First, it is interesting to notice that the episode was referred to as “an Excel glitch”. No mention of things that can easily be read between the lines: no one updated the spreadsheet, no one bothered to check if it needed to be updated, and no one said anything about the way the data was being logged, or even if Excel was the right tool to begin with. As if the authorities were talking about rain, the whole thing was described as something that just happened. The issue of human responsibility went completely unmentioned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-FuibdE4AxeuZDhfcfxXg.jpeg" /></figure><p>A case like this one is interesting because it is so clear that Excel is not to blame, that it lets us see beyond. It lets us pose the question:</p><blockquote><strong><em>Why is it that tools and systems get blamed for human miscalculation, failure to apply said tools as they were intended, or addressing a problem with the wrong system?</em></strong></blockquote><h3>Designing systems to handle complexity</h3><p>While most innovations over the course of History multiplied human capabilities (harder, better, faster, stronger, as <a href="https://www.youtube.com/watch?v=gAjR4_CbPpQ">Daft Punk</a> put it), software introduces the groundbreaking possibility to create things that would be impossible to build without software.</p><blockquote><strong>Software is not a scalar upgrade of capabilities, but an exponential one.</strong></blockquote><p>When capabilities can grow exponentially, however, so can complexity. And that introduces a design problem: we need to learn how to design a whole new category of things, unlike any other. And that requires that we think differently, that we approach problems differently.</p><p>Here, it’s useful to discern between the design of systems and the design of software. Systems make up a larger class that includes software, but exceeds it. This can sound trivial, but it’s actually key: while problems that are thought of as ‘solvable with software’ are usually approached with a design thinking mentality, problems that are not thought of as involving software (but are very much a systemic problem) tend to be approached unsystematically and without much regard for design. That is likely how we end up with Excel being used to count COVID-19 cases.</p><p>John Ousterhout proposes that the main idea underlying all of computer science is <strong>Problem Decomposition: the capacity to take a complex problem and break it down into pieces so that each piece can be built more or less independently</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yGGHF8qPP4GYRrPk" /></figure><p>The idea behind software design, Ousterhout says, is that <strong>we are doing things for the future</strong>. That, in turn, comes with an inherent problem, which is that humans can’t visualize the future very well.</p><h3>Explaining complexity</h3><p>In the hours after the news broke out about this case, two main hypotheses were presented to explain the loss of data:</p><ul><li>The first one said that the positive cases data was stored in Excel using columns for the data points instead of rows.</li><li>The second one said that the data was stored in rows, but using an old version of Excel, which uses an .xls file format and supports a much smaller amount of rows, instead of the newer version which uses an .xlsx file format and supports a larger number of rows.</li></ul><p>The first explanation points to a misuse of the tool. As such, it is misleading. By focusing on the rows-columns dichotomy, it implies that, had the cases been logged using rows, things would’ve been fine.</p><p>The second one focuses on a failure to update the tool, and some sources suggest that the decision to stay in an older version (pre-2007) was driven by the need to use macros in order to automate part of the process, which is not possible in the new version. This explanation is a bit more elaborate, but still somehow approves the use of Excel as a database for positive COVID-19 cases.</p><p>In both cases, there is a deeper issue of myopia: a system design that failed to prepare for the future.</p><h3>Tools to help us think</h3><p>The COVID-19 pandemic made it clear that our inability to predict the future can have serious consequences. This is only made worse by the fact that, the longer into the future we go, the more inaccurate our vision becomes.</p><p>This is the difference between tactical and strategic programming: the former prioritizes getting the system to work and leaves fixing it for later, while the latter focuses on figuring out how to reduce complexity –and avoid it entirely when possible– before building.</p><h3>Inherent complexity vs. accidental complexity</h3><p><a href="https://www.jbrains.ca/">J. B. Rainsberger</a> reminds us that <strong>inherent complexity</strong> is related to a problem being hard in essence and can’t be removed, only dealt with; while <strong>accidental complexity</strong> comes from people mis-approaching a problem, regardless of that problem being intrinsically hard or not, and as it’s manmade, can be eliminated or fixed. Since we’re doing things for the future, this distinction is paramount:</p><blockquote><strong>Inherent complexity can’t be avoided, only managed;</strong> <br><strong>accidental</strong> <strong>complexity is a mistake that replicates itself</strong>.</blockquote><p>To approach inherently complex problems, we need to experiment, evaluate, and gather more knowledge. That doesn’t mean that we can’t do anything until we gain clarity; but it does mean that whatever decisions we make with high uncertainty will need to be revisited once we clear some of that uncertainty away.</p><p>Doing things for the future is a complex problem. The practice of software design consists, then, in building the scaffolding that our future selves can lean on to make better decisions, reduce bias and avoid falling for the trap of urgency.</p><p>In his book <a href="https://doc.lagout.org/science/0_Computer%20Science/4_Theory%20of%20Computation/Design/The%20Design%20of%20Design%20-%20Essays%20from%20a%20Computer%20Scientist.pdf"><em>The Design of Design: Essays from a Computer Scientist</em></a>, Frederick P. Brooks Jr. mentions that, “As tool complexity grows, the need for explicit use models increases. Even for a shovel, it is important to be explicit as to whether it is for coal, dirt, grain, snow, or some mix; whether for child, woman, or man; whether for the casual user or the manual laborer. How much greater is the need for explicit use models for a truck, a spreadsheet, an academic building!”</p><h3>Getting out of our own way</h3><p>So we get to the heart of the problem: <strong>the goal of software design is to remove us from the accidental complexity of a problem</strong>. To do so, system designers need to create an abstraction for the solution at a higher level. The main goal of abstraction is to handle complexity by hiding unnecessary details from the user.</p><p>The more flexible a solution needs to be, however, the less it will be able to abstract, because it needs to give users some manipulation access. Therefore, the higher the risk of introducing accidental complexity. And more accidental complexity means that it gets increasingly harder to verify correctness, that applications are more prone to errors, and that their usage will be more likely to allow for –<em>you guessed it</em>– accidents.</p><p>Excel is a super flexible tool. The invention of the spreadsheet is arguably one of the most powerful and, at the same time, most accessible inventions in all of computing. The very same spreadsheet used in the UK to count COVID cases can be easily modified to <a href="https://www.popularmechanics.com/technology/a22353/super-mario-bros-in-microsoft-excel/">run Mario Bros</a>.</p><p>A global-scale pandemic is definitely a hard problem, inherently complex. Certainly something one does not want to take any chances with. But high-end, efficient and tested systems that are specially designed to tackle that particular problem, take time to develop and implement, and viral outbreaks don’t regularly give people a heads-up.</p><p>A COVID-19 case-counter built with Excel bears much more accidental complexity than a custom tool, and therefore is a lot more prone to the types of errors we’ve seen. But in emergency situations, humans default into the domains and tools that are familiar to them, and that is another thing that can be said about MS Excel: it is a very familiar tool. This is the window through which accidental complexity can get in, and add to the inherent complexity of the problem.</p><p>Our best approach, then, is to design our systems, not to help us do a particular task better or faster, but to <strong>help us make better decisions.</strong></p><p><em>Originally published in the </em><a href="https://manas.tech/blog/2021/05/26/software-to-handle-complexity/"><em>Manas.Tech blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eecadcd4f85a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/how-can-we-design-software-to-handle-complexity-eecadcd4f85a">How can we design software to handle complexity?</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You are asking for the wrong thing]]></title>
            <link>https://medium.com/manas-tech/you-are-asking-for-the-wrong-thing-6f52fea89d99?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f52fea89d99</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tech-proposal]]></category>
            <category><![CDATA[proposal-writing]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[outsourcing]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Wed, 02 Jun 2021 15:03:49 GMT</pubDate>
            <atom:updated>2021-06-02T15:03:36.130Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i24PpJSUoU7P2SQz.jpeg" /></figure><h4>A different way of thinking about tech proposals.</h4><p>Most proposals for a tech project share a problem: they consist of a few introductory sections dropping credentials, a list of scope gathered from conversations with the customer, a table with budget, a timeline with deliveries. The problem is that they focus on the wrong thing, and create conditions for a mismatch in expectations:</p><blockquote><strong>Businesses evaluate potential providers, not in terms of how well they can do the work, but on how capable they are of putting together an attractive proposal.</strong></blockquote><p>If we aim for better outcomes and better relationships, this needs to change. We hope this article will start that conversation.</p><p>In this article, we will walk you through what was probably the most innovative and forward thinking proposal-writing experience of our 2020: a startup came up with an experiment where two contractors compete head to head, to find the best suited one for their project.</p><p>By the end of this article, it will be clear that there is an alternative approach to thinking about tech proposals, one that works because it underscores what actually matters to a customer looking for a contractor, and because it focuses on the provider’s actual capacity to deliver what’s needed.</p><h3>Origin story</h3><p>At the end of 2019, we came in contact with <a href="http://mimic.com.br/"><strong>Mimic</strong></a>, a startup on the look for a tech partner who would help them bring a new idea to market. Their core business was flourishing, they had recently finished a great round of funding, and they were determined to spend that money wisely.</p><p>Mimic specializes in producing food at scale and selling through online channels. Being a very competitive market, they meant to install a completely new way to conceive a customer’s interaction with the food they want to eat. Blow people’s minds and blow up the market, all in one stroke. We will explore how five key changes in the framing of an innovation project had a big impact on the results.</p><p>To make it easier and more pleasurable for you to read, we’re going to break it down into sections, each focusing on one key element of why their approach was so radical: transparency, expectations, communication, prototyping, remuneration.</p><h3>Transparency</h3><p>The first element of this experiment, and a cornerstone of this entire approach, is <strong>transparency</strong>.</p><p>Perhaps inherited from four and a half decades of Cold War, up until not too long ago, secrecy was widely considered to go hand in hand with innovation. Sayings like “secret sauce” and “secret ingredient” crystallized this vision: keep your cards close to your chest. Slowly but steadily, however, transparency has been gaining ground. And perhaps a lesson learned from those four and a half decades of Cold War, is that keeping secrets is simply too costly -and not necessarily advantageous.</p><p>We know that transparency enables trust, which is necessary when you want to get the most out of a collaboration. A provider that doesn’t trust you holds back on what they can do: no one wants to throw their best ideas on the table for free, so that the competition can then execute on them for less money.</p><p>But what if the competition was also sitting at the table? That changes things, doesn’t it? Well, it did. The client came forward with a conundrum: we’ve got two suitors and both have merit and experience, would you be willing to participate in an experiment to help us decide?</p><p>While it was definitely a rare event, the fact that the client was so transparent about having more than one simultaneous proponent had a trust-generating effect. It was a bit strange, but it raised the stakes and everyone knew what was going on. <strong>They were trusting us, and inviting us to trust them</strong>.</p><h3>Expectations</h3><p>The second relevant component in this experiment, and one that is often the seed of future displeasure, concerns <strong>expectations</strong>. Entering the competition, all participants knew what we were dealing with.</p><p>The client set up an all-hands kickoff meeting and explained, in detail, what their expectations were: they went over their business goals, market, customer base, challenges, lessons learned, trends noticed, and their vision about the future. Then, they presented the results of their market research, how they intended to act on it, and the role they envisioned technology could play in those plans.</p><p>They shared the slide deck with everyone, so we had their expectations and evaluation criteria in writing. At this point, the possibility of having doubts about what they were looking for was tiny. <strong>They knew what our expectations were, so they were very clear about theirs</strong>.</p><h3>Communication</h3><p>Just to be extra sure they weren’t taking any chances, the client decided to tackle one of the structural weaknesses of the traditional contracting scheme: <strong>communication</strong></p><p>Usually, communication during the proposal elaboration takes the form of Q&amp;A, rather than a collaboration and iteration on the actual work being done. For this project, interaction was built into the process from the beginning, by design.</p><p>Within the four-week span of the competition, we had a weekly meeting scheduled, to show progress, bring up doubts, give and get feedback. <strong>They were spearheading collaboration, and inviting us to partner on the making of the proposal</strong>.</p><h3>Prototyping</h3><p>Almost every company looking for a provider, in almost every field, conducts their search by looking at the wrong thing. They ask for proposals, portfolios and marketing materials, instead of actual work.</p><p>This is a hard problem to spot, because it is a common feature of the human experience. This is how we evaluate consumer product brands, potential employees, presidential candidates, you name it. The fact that it is a widespread practice doesn’t make it a good one, though. We all fall into this trap one time or another, but there is something we can do. <strong>We can <em>-and should-</em> ask better questions</strong>.</p><ul><li>Wouldn’t it be much more effective to evaluate the ability to do good work, by asking for good work?</li><li>Are you looking for innovative solutions? Have them show you they can innovate.</li><li>Are you looking for speedy delivery? Have them deliver something fast.</li><li>Are you looking for good proposal writing skills?? Doubtful.</li></ul><p>Someone’s ability to deliver good products is best measured by their ability to deliver good products. It sounds tautological, but it is the best approach you can take. What should be under evaluation is actual work done, representative of the same kind of service you expect to get from your provider, should you hire them.</p><p>If you are on the path of innovation, the single best course of action you can take is to allocate a small percentage of your total budget for that project to see if your idea holds water. Spend a little time and money to understand if it makes sense, and you will have saved a lot of time and money.</p><p>If you are evaluating a partnership with a provider for a project, isn’t it also the single best course of action to allocate a small percentage of your total budget to see what they can achieve with it? <strong>Nothing</strong> will give you a better sense of the value they can create, as giving them a chance to create value.</p><p>For this project, the client’s end goal was to tackle an <strong>USD 8 billion industry</strong>, starting with a very focused niche market, that could rapidly grow into a business serving over 20 million customers.</p><blockquote><strong>For such an ambitious projection, wouldn’t you want some kind of proof that your tech partner can deliver on their promises?</strong></blockquote><h3>Remuneration</h3><p>Last but not least, the element that ties everything together and makes this crazy experiment work is <strong>remuneration</strong>. Paying people for the work they do always makes sense, but especially when you are asking them to bet on you.</p><p>Think about it: providers don’t know for sure that the proposal will get them hired. For them, it’s a gamble. Sure, an open and transparent competition scenario raises the stakes. But there is a point along the curve where investing becomes over-investing. And that point isn’t always easy to determine If providers are competing for free. The quality of the proposal will be a compromise between how much they care to get your business -their expectation of how much they stand to win if they do a good job-, and how much time and effort they can afford to spend on something that might not pay off.</p><p>It’s analog to how quickly you will be serviced when walking into a restaurant: if the place is crowded, you won’t be the priority; and if there aren’t that many people there, the wait will be shorter. But who wants to eat at the empty restaurant, after all?</p><blockquote><em>The quality of the proposals you get is in direct proportion to the amount of time and effort your providers can dedicate to them.</em></blockquote><p>As a client, you can influence that. You can acknowledge the work that goes into designing a proposal and pay for it. It is like any freemium model: whatever you get for free, is marketing for the company behind it; the features that will really make a difference for you and your business are likely behind a paywall.</p><p>Funding a proposal guarantees that your provider is going to be fully invested into it. And it sends a clear message that you value their time and their work.</p><p>This startup decided to take this path. <strong>They were letting us know that they valued our time, and that let us know that they value their own</strong>.</p><h3>Takeaways</h3><p>Innovation is usually thought of as the outcome of a process, but it can -and perhaps should- also be applied to the process itself.</p><p>Understanding that there was a lot of uncertainty to be dealt with, this startup opted for maximizing their chances of <strong>creating a truly innovative product by investing in a truly innovative proposal design process</strong>.</p><p>Understanding that collaboration yields better results than speculation, this startup opted for minimizing their risk by creating a transparent, open and hands-on experiment, where providers developed a proposal with them, and not just for them.</p><p>Understanding that communication is pivotal in reducing the chances of building the wrong thing, they built fluid interaction channels, not as an addition to the experiment, but as part of its underlying infrastructure.</p><p>Understanding that the work speaks louder than any deck ever could, they created an opportunity to show up and do the work.</p><p>And understanding that a good proposal is a sound investment, they invested in creating an opportunity for their providers to invest the time and effort that go into creating great proposals.</p><p>As <a href="https://medium.com/u/945d128497b6">David Grandes</a>, Mimic’s CTO puts it:</p><blockquote><em>“I think the biggest issue for other firms adopting this approach is not that they don’t know </em><strong><em>how</em></strong><em> to do it. It’s that they don’t think paying for more proposals in parallel actually makes sense in the bottom line. In other words, they disregard the value of information. What made it super clear to me that in the end this was a solid investment, was seeing the difference in the proposals. It made me realize that the gap was so large that paying 2X for proposals was worth it.”</em></blockquote><p>Innovation is about understanding, and taking action on that understanding. In this case, it was about understanding that <strong>the conditions in which great proposals are created are not a random and natural occurrence, but something that can be designed</strong>. And then acting upon that understanding. That is how you know a company is serious about innovation.</p><p>So, in order to get the best proposal for your tech innovation project, it’s fundamental to change the questions you’re asking about the process. Otherwise, you will get a very neat set of right answers that are of no use.</p><p>Don’t focus on the content: instead, create a context that enables and drives the rise of interesting questions and tiny, discrete experiments to test those questions. Not only will this give you a better tool for measuring your providers’ competencies; you will also learn valuable information in the process. It’s a win-win.</p><p><strong><em>Originally published at </em></strong><a href="https://manas.tech/blog/2021/04/20/asking-for-the-wrong-thing/"><strong><em>Manas.Tech</em></strong></a><strong><em> on April 20, 2021.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f52fea89d99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/you-are-asking-for-the-wrong-thing-6f52fea89d99">You are asking for the wrong thing</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Speed and sustainability: will your go-kart pass the test?]]></title>
            <link>https://medium.com/manas-tech/speed-and-sustainability-will-your-go-kart-pass-the-test-9caead630fd0?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/9caead630fd0</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Tue, 11 May 2021 12:34:12 GMT</pubDate>
            <atom:updated>2021-05-11T12:34:12.767Z</atom:updated>
            <content:encoded><![CDATA[<h4>What it takes to take a startup from inception to scale</h4><p>A go-kart is a type of open-wheel car or quadracycle. They come in all shapes and sizes, from very simple models often made with scrap wood and ball-bearings, all the way to high-powered racing machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pECi4Vi_NUlp5orI" /></figure><p>While the simpler go-karts are gravity propelled, the higher-end ones are motorized and reach speeds of 40 or 50mph. One could argue that the main difference between one and the other are the control skills required to drive them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n5dCsxZrHtqQIB36" /></figure><p>One could also argue that the difference between leading a startup in its early days and leading it during the scale up phase, is exactly the same.</p><blockquote>In essence, when building a business, you are building a go-kart. Your very own go-kart. And when you launch it to market, you are betting (often all you have) on the idea that, as it picks up speed, it will not fall apart. With you sitting on it.</blockquote><p>The inevitable question then is, how can we build a robust enough framework for the go-kart, so that it can stand the test of time and evolve with the business as needed?</p><h3>Go-Kart essentials</h3><p>This elemental vehicle is sufficiently simple and sufficiently familiar to provide us good grounds for analogy. The bare essentials of a go-kart are:</p><ol><li>A <strong>platform</strong>, which is a fixed structure that <strong>keeps every other element in place</strong>, as well as sustains the weight of the person driving. Fixed elements provide structure, and create a frame of reference for everyday activities and decision making. In a startup, this category contains things like the <strong>purpose of your organization, the promises you make to your customers, the shape and operative system of the organization.</strong></li><li>A <strong>propulsion system</strong>, which is a mechanical element consisting of two parts: a <strong>source of power</strong>, like an engine or gravity, that generates energy, and a <strong>propulsor</strong>, which is a means of converting power into propulsive force. In a startup, the people are the element that generates energy, while other moving parts like the organization’s strategy, its products or services, the office, and the array of tools used to carry out its day to day activities, are a propulsor, the way that energy reaches the end customers.</li><li>A <strong>steering system</strong>, which is a way to control the direction of the vehicle. No go-kart or organization exists in a vacuum: their evolution is deeply connected to the evolution of its customer base, and maintaining that balance is all about steering. In a startup, the steering system is the Founder, and later the CEO: they are the ones who provide direction for the business and are in charge of navigating.</li></ol><p>Every one of these is equally important: without a fixed element in place, our go-kart would be a spaghetti bowl of parts, but without any moving parts it wouldn’t move, and without the capacity for steering, the whole experience would be a speedy and danger-ridden ride to injury or worse.</p><h3>Your go-kart’s dashboard</h3><p><a href="https://www.youtube.com/watch?v=ii1jcLg-eIQ&amp;t=317s">Paul Graham</a>, co-founder of <a href="https://www.ycombinator.com/">Y Combinator</a>, says that startups work in counter-intuitive ways and that, if we don’t incorporate mechanisms to keep us on the right path, our intuition can lead us astray, and our go-kart will inevitably fall apart. As any pilot knows, we need to learn to trust our instruments more than we trust our senses, because our senses can be deceitful. A dashboard with clear, objective, easy-to-measure metrics is our best friend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*MPFL99Vdn3zOurXr" /></figure><p>Over years of contributing to go-kart projects, we’ve learned that, while no one has the right answers, there are some key ideas that, when arrayed as a dashboard, can help us approach this problem. We put together a small go-kart building kit with a few of those ideas, to get our wheels on and, most importantly, <em>keep</em> them on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*bPNcpHERbaCR0RdoBCoilQ.jpeg" /></figure><h3>1. Build with the user in mind</h3><p>If we think about it, no one needs you to build a startup. What people need are solutions to their everyday problems. Sometimes to obvious problems they are fed up with, and sometimes to not so obvious problems, that we can uncover and solve in one motion. If we can help with that, we’re on to something. In any case, <a href="https://medium.com/manas-tech/where-to-start-with-ux-design-dfc4dda40120"><strong>we build with the user in mind</strong></a>.</p><p>Another useful idea from Paul Graham: what we need to succeed in building a startup is not expertise in building startups, but expertise in our users. So, before investing in the actual development, it pays off to <strong>invest in understanding your customer base</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uu03Z4TxcBDz0AeaFSlGYQ.png" /></figure><h3>2. Understand what kind of go-kart we are dealing with</h3><p>Conventional problems are just as imaginable as conventional solutions. Most of them are already solved. But <a href="https://manas.tech/blog/2020/06/12/unconventional-blogpost/">unconventional</a> problems, which span beyond the border of the familiar and into the unknown, present us with problems that are not yet fully understood, and thus can’t be solved in a predictable, straightforward way. Understanding what kind of go-kart we are dealing with makes decisions easier along the way.</p><p>Dave Snowden’s Cynefin framework is a useful tool to map the complexity of the domain we’re operating in. From the simple and the obvious to outright disorder and chaos, it provides <a href="https://medium.com/manas-tech/the-4-stages-of-fixing-the-customer-experience-gap-5ced20d6b1e4">a way to navigate complexity</a> in a counter-intuitive space like the startup world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhlzXdkHiyHn5-voBcwjig.jpeg" /></figure><h3>3. Build speed into the process</h3><p>Speed is important because it’s not optional. Not for go-karts, and not for startups. Your go-kart’s best shot at staying in one piece comes from its capacity to endure speed. Also, the faster you build a vehicle and test it, the faster you will know how to build a vehicle that does what you want it to do.</p><p>But speed shouldn’t come at the expense of performance: some components are best bought, while some need a degree of customization to give us an edge. Knowing when to <a href="https://manas.tech/blog/2020/10/06/screwed-up/">build, buy or adapt</a> goes a long way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*BNc0dofWZjQrZ8JSAxerqg.jpeg" /></figure><h3>4. Gaming the system is a bad idea</h3><p>Most domains in life allow some degree of gaming: people get ahead by lying about how much they know or how much work they’ve put in, or by being someone’s son/daughter, niece/nephew, or by turning marketing efforts <a href="https://www.youtube.com/watch?v=4xgx4k83zzc">all the way up to 11</a> and creating <a href="https://en.wikipedia.org/wiki/Potemkin_village">Potemkin villages</a> to give the appearance of success.</p><p>But there is no amount of gaming the system that can keep our go-kart in one piece as it gains speed. Cutting corners plays directly against us in this scenario. Same goes for any startup: if a shortcut existed, why isn’t it the main road?</p><p>Startups demand we put in the work and, since no single individual can do all the work, finding the right allies can make it or break it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*f2ToOxL0E6aL7nAhFXidJw.jpeg" /></figure><h3>5. Fuel and metrics</h3><p>A company needs money like a go-kart needs gas or inertia, to keep its wheels rolling. But we don’t build it in order to buy gas or accumulate inertia, and we also don’t build companies in order to make money. At least, we shouldn’t. Not because of some moral imperative, but because it makes no sense to do so.</p><p>Customers don’t buy the idea that we make money; why would they? They buy whatever value they perceive we offer them. And they keep buying if we deliver that value. A sale makes the wheels turn, a customer relationship keeps them turning.</p><p>Making money is not the goal of a startup. Money has a double function of keeping the wheels in motion whilst serving as a rudimentary metric: if we’re making money, it is a sign that we’re doing something for our customers. But, like a go-kart with no solid platform, a startup that only exists for the money has no structure to hold it in place.</p><p>On the other hand, when refining what our metrics are, and how we use them to steer our business: <a href="https://manas.tech/blog/2019/12/13/automated-financial-modeling/">What if we could have a real-time, easy-to-understand, but formal model of the whole organization?</a> And what if it was fed with real-time information?</p><h3>Ready to drive</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*U-eQug4uIbcgkFswRRaVwg.jpeg" /></figure><p>We began by arguing that, when speed increases, be it in a go-kart or in a startup’s growth, it becomes more and more relevant to have steering and control skills, in order to drive them.</p><p>But, as we began to break it down, it became evident that the skills of the driver are only a part of it. As it turns out, the other part concerns the quality of the materials we use, and the way we build it: keeping in mind that our work needs to endure time and high speeds.</p><p>In the end, though, we shouldn’t overlook the fact that it’s supposed to be fun. And that it’s much easier to have fun when we don’t need to worry about our go-kart breaking apart.</p><p><a href="https://manas.tech/blog/2021/04/14/go-karts/"><em>Originally posted at Manas.Tech’s blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9caead630fd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/speed-and-sustainability-will-your-go-kart-pass-the-test-9caead630fd0">Speed and sustainability: will your go-kart pass the test?</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building bridges: our approach at product design]]></title>
            <link>https://medium.com/manas-tech/building-bridges-our-approach-at-product-design-8e827ae4da4b?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e827ae4da4b</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Thu, 29 Apr 2021 18:34:32 GMT</pubDate>
            <atom:updated>2021-05-07T18:27:37.440Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZK98SvF17PdUVWyRaFZWfQ.jpeg" /></figure><p>The design of a product can be thought of as building a bridge: our initial problem is that we need to get from point A to point B, and there is something in the way that prevents us from simply walking to the other side.</p><p>However, it is important to note that there is at least one major difference to take into consideration: the <a href="https://digitalcommons.usu.edu/cgi/viewcontent.cgi?referer=&amp;httpsredir=1&amp;article=3187&amp;context=etd">expected bridge failure rate is 1 out of 4,700 annually</a>, while on average 68% of IT projects fail, according to <a href="https://www.zdnet.com/article/study-68-percent-of-it-projects-fail/">a report issued by IAG Consulting</a>.</p><p>That same report indicates that these projects fail most often due to poor business analysis capabilities. This means that we can’t simply pile stuff up and hope it turns into a bridge along the way. We find that the most efficient way to design a product is to work simultaneously from both banks, and meet halfway:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*4w42y7-XDdwWNDOkHn9z-w.jpeg" /></figure><p>a) on one side, we start out with an <strong>analytical and constructive</strong> approach: understand what we know and what we don’t, lay out every piece of the puzzle we have, figure out how they might combine, etc.</p><p>b) on the other side, we start out with a <strong>narrative approach</strong>, with the goal in mind, on a qualitative and visionary note.</p><p>Let’s take a look at how this works.</p><p>We begin with research, exploration and idea mapping, and then divide progress along two paths: from an analytical perspective, we use the Jobs To Be Done framework to capture and organize our customers’ needs into an actionable scheme and, from a narrative point of view, we use a narrative structures to encapsulate concepts that can go along our customers in their journey from problem to fix.</p><h3>Research, exploration and idea mapping</h3><blockquote><em>The secret to doing good research is always to be a little underemployed. You waste years by not being able to waste hours.</em> –<strong>Amos Tversky</strong></blockquote><p>Desk research is a process that enables us to find out our status of knowledge. We use <a href="https://melvintercan.com/blog/the-rumsfeld-matrix-uncertainty.html">the Rumsfeld Matrix</a>, because it’s simple and powerful: it lets us map what we know (<em>knowns</em>), what we know but aren’t aware that we know (<em>unknown knowns</em>), what we don’t know (<em>unknowns</em>), and be aware that there are things we don’t even know we don’t know:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gaiFiYKBzs472M1WlQOQGw.png" /></figure><p>For almost every problem one can think of, there is a series of previous attempts at solving it. We need to find them, and understand what worked well and what didn’t, to avoid reinventing the wheel and to find inconvenients that we may encounter down the road.</p><p>We conduct our research in two stages, starting with an <strong>exploration phase</strong>: the goal here is to gather as much information as possible about the client, their customers, their partners, ourselves as providers, the competition, the market. We dive deep into scientific publications, studies and articles, which in turn lead to perusing other tools that compete with our product and tools that solve a neighboring problem.</p><p>During this phase, we seek to collect a large volume of information to expand on our knowledge. We aren’t trying to find the answer, only gathering information to know what questions we’ll need to formulate.</p><p>Then we move on to an <strong>analytical phase</strong>: depending on the problem, we might use different techniques, but the goal here is to see if we can find ways to put together all the pieces of the problem in a way that makes sense as a whole. Ideally, we like to get a visual expression of all the information we’ve gathered. We use <a href="https://www.mindmapping.com/mind-map">mind mapping</a>, cluster diagramming (also known as <a href="https://www.lifehack.org/articles/featured/rico-clusters-an-alternative-to-mind-mapping.html">Rico clustering</a>), combinatorial matrices, or a combination of all those to find insights into a plausible solution.</p><p>From that point on, our roads fork. One path goes down into the requirements analysis, while the other takes a step back to try and see the full picture form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AAtwrwYF_Lb_amhiGi6kSw.jpeg" /></figure><h3>The near shore: Jobs To Be Done</h3><blockquote><em>To design is to devise courses of action aimed at changing existing situations into preferred ones. — Herbert A. Simon</em></blockquote><p>The initial exploration phase generates a large volume of data points. We then need to narrow the arch of ideas and focus on those that have the most in common with our project.</p><p>Like many product design teams, we used to start out by outlining <a href="https://www.nngroup.com/courses/personas/">Personas</a>: constructed but realistic representations of target users, based on data captured during market and user research. We now prefer to start with <a href="https://youtu.be/sfGtw2C95Ms">Jobs To Be Done</a>:</p><blockquote><strong>Customers often buy things because they find themselves with a problem they would like to solve. That’s the Job To Be Done.</strong></blockquote><p>Before creating Personas, we need to leverage the data we gathered about our target audience to understand their mission and motivation. The Jobs to be Done framework gives us a practical way to narrow down our results and weed out potential solutions that don’t make sense.</p><p>Paraphrasing Theodore Levitt, people don’t want to buy a quarter-inch drill; their job is to make a quarter-inch hole. We don’t really need to know what Alice or Bob like to do on their weekends to help them get their job done. We do need to understand what that job is and why they need to do it. Personas come in handy at a later stage, where we need to empathize with target users to design the user experience.</p><p>Once we have gathered enough data to figure out what job our customers need to get done, we can begin to look for patterns, which give shape to customer clusters.</p><h3>The other shore: Building around a narrative</h3><blockquote><em>No word matters. But man forgets reality and remembers words. –Roger Zelazny</em></blockquote><p>Customers don’t make decisions in terms of abstractions such as features. Too many companies get stuck in the weeds of ‘how it works’, but customers never buy ‘just a product’, they buy the value that the product offers them and the function it performs: they mostly want to know “<em>why should I care?</em>”, and the answer should point them in the direction of getting their job done. In this second path, our actions are guided by the question:</p><blockquote><strong>What is the story we want to be able to tell once the product is built?</strong></blockquote><p>Customers buy products because of a story they tell themselves about who they are and what those products do for them. Our best shot at creating successful products is to find those stories and align our design efforts with them.</p><p>From this second shore, we build a narrative that goes hand in hand with our discoveries about our customers. <strong>This narrative is not a fixed thing; it should be fluid and constantly adjusting to incorporate new facts and hypotheses we formulate</strong>. It’s also not something vague and fictional: our narrative is the resulting image of connecting the dots we put together during our research.</p><p>While the initial research stage was an expansive moment of accumulation, and the first path of thorough analysis was of a descriptive nature, this narrative instance is an attempt to synthesize and explain our customers decisions and actions. <a href="https://pressbooks.bccampus.ca/jibcresearchmethods/chapter/3-2-exploration-description-explanation/">Exploration, description, explanation</a>.</p><p>Knowing what our users will attempt to solve with our product makes most decisions easier. Endless arguments about whether we should make it look great or make it run fast no longer make sense when we can understand our customers’ actions. (<em>No one wants it to run slow, if you were on the fence with that one</em>). When in doubt, we err on the side of the customer’s benefit.</p><p>In the fever of the ‘<em>move fast and break stuff</em>’ mindset that populates the technology industry lately, most product design projects start prototyping right away and miss this point. They become too focused on things like technology stack, features and specs. This dramatically increases the possibility of building the wrong thing. A narrative helps us incorporate new knowledge into an ecological whole, that keeps the customer front and center, and focuses our efforts towards solving their problem.</p><h3>User Experience Design</h3><blockquote><em>People ignore design that ignores people. –Frank Chimero</em></blockquote><p>Having conducted this analysis, we have a multilateral understanding of the narratives our customers’ are immersed in, and we can take actions to solve their problems by helping them get their jobs done. We need to have done this work to grasp what it is that our customers need, and why they want it. <em>How</em> that will become a reality is the <strong>user experience</strong>, and it is the corollary of our exploration, description and explanation design process.</p><p>Now, the term “user experience” probably ranks among the most misunderstood terms in recent history. It is taken to mean that focus should be on the user or customer. This is a misconception: what it really means is that you should focus on the user <em>from a business perspective</em>.</p><p>UX is better understood as a set of business decisions aligned towards what you want your users or customers to <em>experience</em>: it is about creating an environment or context that moves your customers to act in a certain way; not <em>any</em> way, but a way that aligns their needs with your business goals. In simpler terms:</p><blockquote>Product design is about finding balance between user experience and business convenience.</blockquote><p>Designing the flow of experience is a delicate mix of science and art, one that aims to balance the needs and wants of both customers and business. During this phase of the product design process, we focus on understanding when, where and how our customers will interact with the product. Each interaction should be meaningful by design and result in a positive experience that also drives the business forward.</p><p>The key concepts here are alignment and balance. Between customer satisfaction and business success. A meticulous analytical approach and an encompassing narrative serve as a caliber to find that balance.</p><h3>Putting it all together</h3><p>We began by saying that product design can be thought of as building bridges. The purpose of these products we design is, precisely, to bridge the gap between our customers’ current situation and the one we envision for them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TDjtkQzG8AmlJP4Z" /></figure><p>Over the course of our years helping others build their bridges, we have come to a method that does a few things well: it presents our customers with an original way to see what they do for <em>their</em> customers, it gives our team a better grasp on the problem and our imagined solutions, and it provides a checking mechanism to ensure we’re on the right track.</p><p>If both ends meet, it means we’re on to something. It means the narrative can hold every piece of the puzzle in place, and that every piece individually contributes to the overarching narrative. It makes sense.</p><p>In a way, this can also be thought of as a bridge. Between user experience and business convenience. Between meticulous analysis and an overarching narrative.</p><p>The best way to build bridges, it would seem, is to build bridges.</p><p><a href="https://manas.tech/blog/2021/02/10/building-bridges/"><em>Originally posted at Manas.Tech’s blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e827ae4da4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/building-bridges-our-approach-at-product-design-8e827ae4da4b">Building bridges: our approach at product design</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tools to forecast fire spreading behavior]]></title>
            <link>https://medium.com/manas-tech/tools-to-forecast-fire-spreading-behavior-67cbfc7b922d?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/67cbfc7b922d</guid>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[mathematical-modeling]]></category>
            <category><![CDATA[environmental-impact]]></category>
            <category><![CDATA[forest-fires]]></category>
            <dc:creator><![CDATA[Franco Nicolas Bellomo]]></dc:creator>
            <pubDate>Thu, 03 Dec 2020 16:12:39 GMT</pubDate>
            <atom:updated>2020-12-04T14:47:29.515Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hour-by-hour machine learning assisted forecast of forest fires shape and area</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xp5332Qy5_LSbDIS9_hO1w.jpeg" /><figcaption><em>Okanagan Drone — OpenAir UAV Flight Training Partner</em></figcaption></figure><p>In the past year alone, the world has been witness to a worrying burst of forest fires: bushfires in Australia and the Amazon gained notoriety in late 2019, but other areas like Central Africa and Patagonia have large forest fires every year. Most recently, wild fires have been raving throughout almost every region of the world: <a href="https://news.mongabay.com/2020/11/a-million-hectares-ablaze-as-forest-fires-sweep-through-bolivia/">Bolivia</a>, <a href="https://www.aa.com.tr/en/africa/forest-fires-kill-2-in-algeria/2035376">Algeria</a>, <a href="https://www.cbc.ca/news/canada/sudbury/forest-fires-statistics-climate-change-1.5806432">Canada</a>, <a href="https://www.aljazeera.com/news/2020/11/2/fires-in-brazils-amazon-rainforest-jump-in-october">Brazil and North-eastern Argentina</a>, most of <a href="https://europeansting.com/2020/11/02/commission-report-europes-nature-under-threat-as-world-suffers-worst-year-on-record-for-forest-fires/%5C">Western Europe</a>, <a href="https://eng.belta.by/society/view/another-belarusian-helicopter-comes-home-after-fighting-forest-fires-in-turkey-135354-2020/">Turkey</a>, <a href="https://www.cbsnews.com/news/wildfires-sibera-russia-burned-area-larger-than-greece-heat-wave/">Russia</a> and the list sadly goes on and on.</p><p>Forest fires are sadly here to stay, and the best and only thing we can do is figure out how to fight them.</p><p>Developed between November 2019 and February 2020, <a href="https://forestfires.tools/"><strong>ForestFires.tools</strong></a> combines UAVs, embedded computing boards, visible spectrum imagery, machine learning classification of vegetation types and fire-frontier detection, in a mobile frontier mathematical model to give first responders the resources they need to fight large scale forest fires at an affordable cost.</p><h3>An unusual solution</h3><p>This set of fire-fighting tools was developed for the <a href="https://unusualsolutions.org/">Unusual Solutions Competition</a>, a global competition organized by <a href="https://werobotics.org/">WeRobotics</a>, that invites individuals and teams from all over the planet to submit solutions on how to best tackle social, environmental and scientific challenges with technology.</p><p>The goal of the project was to aid fire responders in the planning of their efforts. But also, considering that many of the countries with the largest forest areas are in the global south, and are collectively less wealthy than their northern counterparts, we focused on putting together a solution that has a cost of around <strong>600 USD</strong>, making it affordable to as many groups as possible.</p><p>In future iterations, we plan to work with local UAV groups and maker-spaces in all countries, so that the product, training and support can be offered at an even lower cost.</p><h3>How it works</h3><p>There are 5 key elements that make this solution different to anything else out there:</p><ol><li>Multispectral imagery updated often with the use of UAVs</li><li>Machine learning algorithms: one to classify the terrain according to vegetation, and one to detect the frontier of the fire</li><li>A small, purpose built, portable weather station</li><li>Mathematical modeling of the fire</li><li>The solution works offline, generating near real-time forecast</li></ol><p>All of these components combined enable us to build an accurate, local and almost real-time forecast of wildfire spreading.</p><p>By combining multispectral aerial images collected by drones with meteorological variables obtained by the portable station, like temperature, humidity, wind speed and direction, <a href="https://forestfires.tools/">ForestFires.tools</a> can create a more accurate, local, near real-time fires forecast, that allows firefighters to better understand and respond to forest fires.</p><p>The data sources gathered by the UAVs are then processed by an inexpensive, portable computer that doesn’t require an Internet connection to prepare a fast fire model capable of forecasting the spread of the fire. This is a key feature of the product: it works locally and offline to give fire responders maximum value with minimum constraints.</p><p>Applying machine learning algorithms to the imagery, the model classifies vegetation according to type (grass, trees, water) and to current state of dryness/humidity. With this classification plus experimental data from other researchers, we were able to gather the necessary data to integrate evaluations such as conductivity, thermal diffusion or vegetation density into our model. This imagery also allows us to detect the coordinates of the fire sources that will later become our initial conditions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*uwcZQfm04mVH18pxQZld2Q.png" /></figure><p>Combining all of that data in a finite element model with a moving boundary of the heat equation, we can forecast the fire spreading in the short term, which provides responders with more accurate and real-time information for decision-making. This gives firefighters autonomy on the field, without losing access to accurate, timely information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*YPRmyDPtsC3fJb7UAXJ5gw.png" /><figcaption><em>Equation used for fire modeling, where each term (p, k, T) corresponds to a matrix obtained from the image processing, modified by climate conditions (w)</em></figcaption></figure><h3>Approach &amp; components</h3><p>The<strong> </strong>toolset allows first responders to better understand where and how fast fire will spread, and use that information to make better decisions on resource allocation.</p><p>Planning for firefighting is based on a triangular model: <strong>topography - fuel -weather</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2fweHkwFia4gmvUfotxWQ.jpeg" /></figure><p>After validating the need and approach with potential users, we focused on reducing uncertainty around the technical feasibility of the solution. For that we built several small prototypes of the key components:</p><ol><li><strong>Fire boundary detection</strong>: We used <a href="https://www.tensorflow.org/lite/models/object_detection/overview">TensorFlow Object Detection API</a> to train a machine learning model that detects the coordinates of fire spots. We obtained training and validation images from multiple videos of forest fires captured by drones. With only 30 images in the training set (which we tagged manually), we obtained an 83% average precision on fire coordinates detection. As the basis for the model, we used a pre-trained <a href="https://github.com/tensorpack/tensorpack/tree/master/examples/FasterRCNN">COCO-faster-rcnn</a> and ran the training on a <a href="https://www.nvidia.com/en-gb/data-center/tesla-k80/">Nvidia Tesla K80</a>.</li><li><strong>Classification of ground coverage</strong>: we applied <a href="https://gisgeography.com/ndvi-normalized-difference-vegetation-index/">NDVI</a>, an algorithm that enables the detection of vegetated areas and other types of surfaces, such as rock, water and soil. More importantly, NDVI allows us to classify how green or dry the vegetation is, which improves the accuracy of the fire spreading forecasts. Running an NDVI analysis requires aerial imagery captured with an infrared camera.</li><li><strong>Spread forecasting</strong>: we started from the basic <a href="https://en.wikipedia.org/wiki/Heat_equation">heat equation in 2D</a> and iterated to incorporate additional parameters into it: <br><strong>a.</strong> Initial coordinates of fire spots.<br><strong>b.</strong> A map of underlying types of ground cover that determine the combustibility of the material.<br><strong>c.</strong> Weather conditions<br>That model enabled us to forecast the action of the wind in the fire spreading and how the materials burn, predicting the final shape and area of a fire over specific periods of time.<br>We also optimized the model to be run on a GPU (we are planning on using an <a href="https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-nano/">Nvidia Jetson</a>), so that we can provide an offline, affordable and portable platform to run the forecast.</li><li><strong>Components for the weather station</strong>: we researched and evaluated different components for the weather station and optimization box, and came up with a minimum viable budget for it. The alternatives are quite promising, with viable options starting at a cost of 240 USD.</li></ol><p>We leaned towards using Raspberry PIs in combination with the <a href="https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-nano/">Nvidia Jetson</a> to run offline imagery processing. The imagery processed using a lightweight optimized AI algorithm for <a href="https://pdfs.semanticscholar.org/0306/b969b9b4666c90776857d14966e5f7b6c401.pdf">shadow analysis</a> can be used to build a <a href="https://www.usgs.gov/faqs/what-are-digital-elevation-models-dems?qt-news_science_products=0#">Digital Elevation Model</a>, a key component in the analysis of the spread of forest fires. Assessment of fuel moisture could also be done with similar methods.</p><p>In addition to that, information from a portable weather station provides temperature readings, humidity and wind speed and direction. That component is essential, partly because lack of connectivity means no access to remote weather stations, but also because fires create their own nearby weather conditions. A fire propagation model would then use that input data to forecast potential scenarios. The Jetson board is a perfect fit for all these tasks and comes at an extremely reasonable cost of 99 USD.</p><p>For image processing purposes, we based our code on an integration or extension of <a href="https://www.opendronemap.org/">OpenDroneMap</a>. For the Weather Station we think the best approach is using and interconnecting with the <a href="https://projects.raspberrypi.org/en/projects/build-your-own-weather-station">Raspberry PI Weather Station</a>, These guarantee we build on existing open source and open hardware efforts, significantly reducing development costs and increasing long-term sustainability.</p><h3>The resulting toolset</h3><p>These wildfire behavior forecasting tools deliver an hour-by-hour machine learning assisted forecast of forest fires shape and area. The outcome is precise and timely knowledge in the hands of firefighters, which significantly improves their ability to allocate resources and make decisions, as efficiently as possible.</p><p>The potential impact of this project is a more focused and efficient use of resources during forest fires response efforts. If responders have a better understanding of the likelihood of the fire spreading in certain directions and at certain speeds, efforts can be better focused, and evacuations –if necessary– could be planned with more time.</p><h3>Next steps</h3><p><a href="https://forestfires.tools/">ForestFires.tools</a> was developed as a concept for the Unusual Solutions Competition, and has not yet been deployed in a real setting. However, it is as close to completion as possible without financing.</p><p>Our roadmap to a complete and successful implementation is as follows:</p><ol><li><strong>NDVI expansion</strong><br>The NDVI analysis provides a good basis to understand the type of ground coverage and is widely used to assess crop health in agriculture and forest coverage from satellite remote sensing. In order to provide more accurate fire behavior forecasts, we need to expand on that and use machine learning to classify types of vegetation. The input to such a machine learning classifier is the multispectral imagery (both infrared and visible imagery).</li><li><strong>Real-world testing</strong><br>Testing the spreading model, first without weather input. Using real imagery captured from past fire events, both aerial or satellite, and infrared spectrum, we can run our model and compare its predictions with the actual spreading. Those cases can be used to iterate and improve the model until the results are accurate enough.</li><li><strong>Portable weather station development</strong><br>The portable, local weather station needs further development and testing, and to incorporate the output to the model. While this whole solution can be used with an off-the-shelf weather station, that single component is what increases the total cost the most. To improve on affordability, we have researched a few alternatives of wind sensors that can be integrated into a small, portable and affordable weather station that can be connected to the proposed solution.</li><li><strong>NDVI testing on well-known terrain</strong><br>Run further tests on NDVI analysis using multispectral imagery captured with UAVs and the subsequent machine learning classification on well known terrain. We want to evaluate and compare lower-end infrared cameras against more expensive ones to determine the most affordable feasible option.</li><li><strong>Contrasting accuracy in real setting</strong><br>Join a fire event response and test the whole solution, without acting on the forecasts, but contrasting them with the actual progress of the fire. We have already got clearance to do this in Patagonia.</li></ol><p>We are very confident about the potential of this project and the value these tools can deliver to fire responders all over the world. As forest fires keep decimating key resources in our ecosystems, there is much we can do, and this feels like a good place to start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67cbfc7b922d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/tools-to-forecast-fire-spreading-behavior-67cbfc7b922d">Tools to forecast fire spreading behavior</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On the meaning of unconventional]]></title>
            <link>https://medium.com/manas-tech/on-the-meaning-of-unconventional-ba250685d5b1?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/ba250685d5b1</guid>
            <category><![CDATA[wicked-problem]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[unconventional]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 15:21:36 GMT</pubDate>
            <atom:updated>2020-06-12T15:21:46.850Z</atom:updated>
            <content:encoded><![CDATA[<h4>A new kind of approach to tackle new kinds of problems</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WhiuAJpKGMpVT6od" /></figure><p>If you go to<a href="https://manas.tech/"> Manas.Tech</a>, you can find an<a href="https://en.wikipedia.org/wiki/Easter_egg_%28media%29"> easter egg</a> by hovering on the word ‘unconventional’. That word is a big influence on everything we do, including but not limited to, a hidden wink to curious visitors.</p><blockquote><strong>Unconventional<br></strong>/ʌnkənˈvɛnʃ(ə)n(ə)l/<br><em>adj. </em>not based on or conforming to what is generally believed.</blockquote><p>The dictionary definition of the term <strong><em>unconventional</em></strong> is as illustrative as its counterpart:</p><blockquote><strong>Conventional<br></strong>/kənˈvɛnʃ(ə)n(ə)l/<br><em>adj. </em>based on or conforming to what is generally believed.</blockquote><p>The true meaning, however, does not lay in definitions. What’s behind this is the fact that all<strong> the easy problems are already solved</strong>. Humans have learned to solve most of their easy, straightforward problems, and have done a pretty good job at it. The remaining things to be fixed, solved and improved are the tough ones. <strong><em>The wicked problems</em></strong>.</p><p>But it is often difficult to see this. In fact, many along the years have claimed the end of History, only to be shortly after disclaimed by, well… History.</p><blockquote>“<em>Everything that can be invented has been invented.</em>”<br>–Charles H. Duell, 1899, U.S. Commissioner of Patents</blockquote><p>Read that quote again, but this time, take a look at the year. Right at the end of the 19th century, a man in charge of patenting inventions, claimed his job was about to disappear. Mind you, some of the inventions that have become an integral part of our daily lives hadn’t been patented yet when Mr. Duell uttered these words: both Tesla and Marconi applied for patents on radio in 1900, air conditioning systems were patented in 1902, the airplane would be patented in 1906, and television wasn’t around until 1930.</p><p>So, what led Mr. Duell to believe that everything had already been invented?</p><h3>Wicked Problems</h3><p>Well, the thing is, in a complex world where simple, straightforward problems have already been solved, the only way you can create value is by taking a shot at solving the hard problems. The complex problems that arise from complex systems.</p><p>These are what we call <a href="https://www.wickedproblems.com/1_wicked_problems.php"><strong>wicked problems</strong></a>: social or cultural problems that are difficult or impossible to solve for as many as four reasons: incomplete or contradictory knowledge, the number of people and opinions involved, the large economic burden, and the interconnected nature of these problems with other problems. <em>Sounds oddly familiar, doesn’t it?</em></p><p>There is another substantial difficulty that comes with complexity: it is hard for us humans to wrap our minds around it.</p><blockquote>“<strong><em>Any sufficiently advanced technology is indistinguishable from magic</em></strong>”<br>–Arthur C. Clarke</blockquote><p>It’s fair to say that <strong>any sufficiently complex problem is indistinguishable from an impossible to solve enigma</strong>. And that is why, when the solution is presented to us, it seems magical.</p><p>However, as impossible as these kinds of problems may seem, they can be mitigated through the process of design, which is <strong>an intellectual approach that emphasizes empathy, abductive reasoning, and rapid prototyping</strong>.</p><h3>Putting the solution ahead of the problem</h3><p>In 2001, almost exactly a century after Duell, Steve Jobs introduced the iPod to the world, and everything about that tiny device seemed absolutely magical. If I had been the Commissioner of Patents at the time, the very next day I would have said that everything that can be invented had been invented. That’s what it felt like at the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*1ZMtZbei-nTTs3LE" /></figure><p>But fast forward to 2007, only 6 years later than the iPod, and not that long ago, Steve Jobs did it again: he introduced the iPhone, and everything about it seemed even more magical than the iPod.</p><p>If I had been the Commissioner of Patents in 2007, the very next day I would have published a retraction on my 2001 statement because now, oh yeah, now everything that can be invented has been invented. But I would also have been wrong, wouldn’t I?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iqb8EZAnwlQbIF9x" /></figure><p>When these magical innovations are first presented to us, they truly are the closest thing to magic. <strong>They solve a problem that we didn’t even realize we had</strong>, in a way that is just mesmerizing. We didn’t even know that there was a problem with our phones having a physical keyboard, or that there was a void in our lives that had to be filled with apps.</p><p>But then, after a short time goes by, the shine starts to fade, and it seems like that magic was there the whole time. Not only the solution seems obvious, the problem does too. And yet, the majority of us didn’t see it before, exactly like Mr. Duell believed everything had already been invented back in 1899.</p><p>This brings a lot of headaches because, next time we face a complex problem, we will be tempted to believe that the solution should be the obvious one. Just as the last great solution seemed obvious once we became familiar with it. <strong>But that problem wasn’t obvious, and neither was the solution</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Ry_2Nb0ZHneAZWeBK0HIw.jpeg" /></figure><p><strong>Conventional problems are just as imaginable as conventional solutions</strong>. That is why –and how– humans have learned how to solve most of them.</p><p>But the <strong><em>unconventional</em></strong>, which spans beyond the border of the familiar and into the unknown, presents problems that can’t yet be completely understood, and thus can’t be solved in a predictable, straightforward way. Paraphrasing George Bernard Shaw,</p><blockquote><em>“Conventional people adapt themselves to the world. <br>Unconventional people attempt to adapt the world to themselves. <br>All progress, therefore, depends on unconventional people”.</em></blockquote><p>Unconventional problems can’t be solved with a conventional approach.</p><p>Anything you can successfully predict is not the outcome of a complex system. And anything you can’t successfully predict is not a conventional problem to be dealt with in a conventional way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cO53Rw-i-2I9mkEB" /></figure><p>Things like a global pandemic put this in perspective with a clarity that is rare in our human experience. Dealing with it required understanding a complex system, with complex elements such as the behavior of a deadly virus, human behavior, and human behavior when faced with a deadly virus. There are too many variables, behaving too erratically.</p><p>Most of the approaches we saw in the early days of the outbreak approached it too simplistically. And they simply failed. We weren’t realizing that there was incomplete or contradictory knowledge, a lot of people and opinions involved, a large economic burden, and the interconnected nature of these problems with other problems. The recipe for a wicked problem was right before our eyes, yet we were suffering from Duell’s nearsightedness syndrome.</p><p>Things started to shift when we started addressing this problem seriously. When we understood that this was a wicked, unconventional problem, in dire need of unconventional solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q8OCWut7TkkGUKlh" /></figure><p>So this is where we stand: at the border, and headed for uncharted territory. From this point on, the kinds of problems that humanity will face, will increasingly look more and more like handling a pandemic: a lot of different variables, interacting in a complex system, with a degree of uncertainty that makes any linear prediction both laughable and dangerous.</p><p>All we can rely on, if we want to innovate successfully, is going to be found on the fringes. <a href="https://medium.com/u/f9ac9806e153">Seth Godin</a> said it almost 20 years ago, but it still rings true today:</p><blockquote>“<em>Safe is risky. Risky is safe.</em>”<br>–Purple Cow, 2003.</blockquote><p>That is the true meaning of <strong>unconventional</strong>. For us, at least. It’s about doing the hard, irregular, dynamic work that goes into designing possible solutions for problems that are currently difficult to imagine, with empathy, abductive reasoning, and rapid prototyping.</p><p>It’s about knowing how to go to the fringes, and how to come back. The work that we need to learn consists of a systematic approach to complexity and the skill to craft that which is not based on, or conforming to, what is generally believed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba250685d5b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/on-the-meaning-of-unconventional-ba250685d5b1">On the meaning of unconventional</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 4 stages of fixing the customer experience gap]]></title>
            <link>https://medium.com/manas-tech/the-4-stages-of-fixing-the-customer-experience-gap-5ced20d6b1e4?source=rss----af888569068a---4</link>
            <guid isPermaLink="false">https://medium.com/p/5ced20d6b1e4</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Martín Pettinati]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 16:49:20 GMT</pubDate>
            <atom:updated>2020-01-21T18:03:54.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>Fixing the customer experience gap: a 4-staged journey</h3><h4>Ideas on how to power your marketing strategy using technology</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8E8p3m_xkDa7uE-m9tOmNw.png" /></figure><p>I’ve been working in the intersection between <strong>marketing and tech</strong> for a few years now, and lately I’ve been thinking about some interesting things that happen in that space. I think there is a gap (<em>or 3, actually</em>) between marketing needs/efforts and customer needs/efforts, and the way technology is used to bridge that gap (<em>or gaps</em>) is understood as necessary, but not really understood all too well. So this article is an exercise: I wanted to lay it all out and see what useful ideas come up.</p><p>Designing a marketing strategy is an endeavor that points towards a universal goal: maximizing customer satisfaction. And in that endeavor, marketers and marketing teams tend to go through 4 stages. Each of these stages is defined by a main question or course of action that resonates in our heads constantly like a mosquito on a hot summer night, until we manage to somehow solve it, and then we can move on to the next stage, where another premise is waiting to do the mosquito night dance in our mind.</p><h3>First stage: chasing after the category leaders</h3><p>If you work in Marketing (or in any kind of business that has to deal with real people, face-to-face, in real time), I’m willing to bet you have spent some time turning some of these questions -<em>or all of them</em>- in your head:</p><ul><li>Is it better to have a brick &amp; mortar store, or to go full digital?</li><li>If we choose to do both, how can we find a good balance between the two?</li><li>Why do people come to the store, look around, and then go home and buy online?</li><li>If they’re going to buy online, why do we bother having stores?</li><li>If we get rid of the physical stores, will customers still find our products online?</li><li>Is ecommerce a way to kill the business or a way to help it survive?</li><li>Are Amazon, ebay and the rest friends or foes?</li></ul><p>Usually, the answer most businesses and organizations come up with, to deal with the bulk of these questions, is: <strong><em>do whatever is working for the guys who are doing well</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*f6VgbMkpKNmBGCHk" /></figure><p>This is also referred to as ‘<strong>Best Practices</strong>’, and it’s what took businesses on a breakneck ride from investing in banner advertising, to SEO, to paid search, to social media marketing, to influencer marketing, to account-based marketing, and so on and so forth, over the past couple of decades.</p><p>During this stage, your mind will bend over backwards trying to find out what these best practices are, and you and your team will spend hours upon hours <a href="https://www.youtube.com/watch?v=g4OBUupicWg">combing the desert</a> until you find them. Eventually, you will leave this stage behind when the nerve racking question is brought forward:</p><h3>Second stage: are there even ‘Best practices’ where you operate?</h3><p>It’s now become a part of the common-sensical jargon, but you probably never stopped to think about what ‘Best practice’ means and entails, and that’s fine. Let us travel back in time, right before the turn of the century, to a time called “<strong>the 90s</strong>”, when <a href="https://cognitive-edge.com/our-people/dave-snowden/">Dave Snowden</a> created the <a href="https://en.wikipedia.org/wiki/Cynefin_framework"><strong>Cynefin framework</strong></a>, a tool for decision-making that offers five decision-making contexts or “domains”:</p><ol><li><strong>Simple / Obvious / Clear</strong>: this domain represents the “<strong>known knowns</strong>”. This means that there are rules in place (or <strong><em>best practices</em></strong>), the situation is stable, and the relationship between cause and effect is clear: <em>if you do X, expect Y</em>.</li><li><strong>Complicated</strong>: this domain consists of the “<strong>known unknowns</strong>”. The relationship between cause and effect requires analysis or expertise; there is a range of right answers.</li><li><strong>Complex</strong>: this domain represents the “<strong>unknown unknowns</strong>”. Cause and effect can only be deduced in retrospect, and there are no right answers.</li><li><strong>Chaotic</strong>: in this domain, cause and effect are unclear. Events in this domain are too confusing to wait for a knowledge-based response. Action — any action — is the first and only way to respond appropriately.</li><li><strong>Disorder</strong>: this domain represents situations where there is no clarity about which of the other domains apply. By definition, it is hard to see when this domain applies. The way out of this realm is to break down the situation into constituent parts and assign each to one of the other four realms.</li></ol><p>So, <em>why are we going through the pain of unpacking a framework?</em>, you may be wondering. <strong>To make a point.</strong> <em>And what is the point?</em> That doing whatever is working for the guys who are doing well is a valid approach <strong><em>only</em></strong> in a situation we can define as part of the Simple / Obvious / Clear domain.</p><p>Most people who own businesses and run organizations haven’t heard about the Cynefin framework, so it takes them a heartbreaking amount of time to exit this stage. You have probably lived through something like this, trying out stuff that doesn’t work, and wondering if anything ever will. Eventually, you reach a point where you decide that trying to find the recipe for success just doesn’t make sense, and then you move on. Knowing about this framework could have saved you a bunch of time. But now you know, and knowledge is power. Or at least it gives you the power to move out from these murky waters onto the next stage:</p><h3>Third stage: figuring out what your context looks (and behaves) like</h3><p>When there are clear rules in place, when the situation is stable, and when the relationship between cause and effect is clear, you can -and probably should- apply best practices. But I’m pretty sure your current state of affairs doesn’t have all those qualities at once, and most likely none of them. That being said, it is my duty to inform you that <strong><em>no,</em></strong> <strong><em>you do not qualify for best practices</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*EnnbfOHkdOkSMToajbQ6LQ.jpeg" /></figure><p><strong>What to do, then?</strong> Well, during this stage you need to work on understanding what realm or domain you’re operating in, and what that means, in order to act accordingly.</p><p>Businesses — and marketers working for said businesses — struggle to find ways to connect all the disperse experiences their customers go through when interacting with their brand: what goes on in the physical stores is usually far and disconnected from what takes place on the website, or on social media, and we’re all pretty convinced that word-of-mouth comes into this equation at some point, but we are not really sure where, or how. And on the customers’ side, they want to solve their problems, fulfill their desires, satisfy their needs, and all we marketers and businesses seem to be doing is getting in their way. It’s frustrating for everyone.</p><p>If everything we’ve talked about so far resonates with you, and I bet it does if you got to this point, we can start to heal this broken process by agreeing that we don’t have clear rules in place, that the situation is not too stable, and <em>certainly</em> the relationship between cause and effect is, to say the least, unclear. Acceptance is freeing.</p><p><strong>First conclusion</strong>: there is room for best practices, yes, but it’s getting smaller and smaller.</p><p><strong>Second conclusion</strong>: if you want to apply what “the guys who are doing well” are doing, you need to realize that just because a few things are working well for them <strong>now</strong>, it does not mean that is how they got there. Not only that, but you need to check as well if they are operating in the domain of the Simple, the Obvious and the Clear and, if so, proceed to check if you are also in that domain or not.</p><p>This is a tricky question and, to answer it, maybe we could approach it at an angle, and <strong>ask a different question</strong>, one that also helps us figure out how to make your customers happy (or at least happier) and while doing that, gather some valuable insight to tackle some or all of the questions that we started out with in the first stage.</p><p>To do that, a big question we should be asking revolves around <strong>integration</strong>:</p><blockquote><strong><em>Is there a way to integrate all these scattered experiences into a seamless one that makes our operation almost transparent to our customers?</em></strong></blockquote><h3>Fourth stage: Jekyll &amp; Hyde’s gaps</h3><p>In this stage, you will begin to tackle the ugly side of the relationship between your business and your customers. We have been talking about this gap in a <em>matter-of-fact</em> way, and that can make it sound like something natural, almost inevitable. But when you take a closer look, you can see what the gap is really made of: advertising that doesn’t match what goes on at the store, an in-store experience that doesn’t correlate with the online experience, and a wide array of customer care interactions alternating and overlapping between phones, online chats, in person attention, email and (<em>yes, still</em>) physical mail, and it all points us in the direction of the same ugly monster: <strong>Dr. Jekyll and Mr. Hyde</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0uJsM1me5dTBi0-q.jpg" /></figure><p>The problem with Jekyll and Hyde is the same problem most businesses deal with: they each do their own thing, while ignoring what their counterpart is doing. The ugly gap between what businesses want and what customers want is actually made of 3 gaps: first of all, <strong>a gap in knowledge</strong>; second, <strong>a gap in understanding</strong> regarding that knowledge; and third, <strong>a gap in action</strong> based on the understanding of that knowledge. And in this stage, you will try to find a way to bridge these 3 gaps, in order to realign customer and business needs.</p><h4>The gap in Knowledge</h4><p>The gap in knowledge consists of a divide between data that businesses gather in their online portals and data that they gather at their physical stores. If you have a bank account, a cable TV account or almost any other kind of account, and at one point you had a problem and needed assistance, which made you reach out to the company behind it, you most certainly have come in close contact with this gap:</p><blockquote>On your first interaction, you are required to provide some personal information like your ID, date of birth, account number (maybe some, maybe all, maybe a combination of those), only to reach a second instance of interaction, where (<em>no suspense</em>) you are required to provide some or all of that information once more. Are we supposed to believe that they don’t already have all that information, and possibly much more? Not in 2020, if I had to guess. But the Knowledge in gap is a real thing, and this is how she manifests.</blockquote><p>If you are rolling your eyes at this, reminiscing of past encounters with these services providers, I’d like to invite you to look inwards at your own business: Is the information you’re gathering on different outlets integrated? Are you leveraging that information to drive and improve customer interactions? Do you have systems in place to keep track of everything you know and can know about your customers?</p><p>You can probably make an educated guess about the nature and quality of that experience, but chances are you don’t know for a fact. It’s not your fault: the larger your business gets, the harder it is to keep a pulse on it. Furthermore, it’s quite possible that this disconnect between what you know, what you think you know and reality, also happens at the level of your customer care / customer service team, and that’s a bit more worrying. Again, not your fault; but definitely something you can work on.</p><h4>The gap in Understanding</h4><p>Some businesses do have systems in place to gather information about their customers and their experience. These are the companies who do know your client ID, where you live, what you are subscribed to, etc., and their problem is one step further along the customer experience pathway: they’re not really sure what all that information amounts to.</p><p>The bigger the business, the bigger the dataset. Does that mean that we know more? Or does it simply mean that we have a bigger mess to make sense of? It’s not unusual to find leaders and businesses who are sitting on an incredible pile of information, some of them without a clue that they actually have access to it, and others without a clue where to begin making sense of it all. They have so much data on you that they should know who you are, what you like and dislike, and how to leverage that to their own commercial advantage. But they don’t.</p><p>Having the data is nowhere near as important as making sense of that data. The world around us is constantly giving us valuable information, and the better we understand what that information means, the better our decisions will be and, ergo, the better and more efficient our actions.</p><h4>The gap in Action</h4><p>Last, but certainly not least, some businesses have the information, they have taken the trouble to organize it, they have the visualization tools to help them make sense of it all at a glance, and they understand their customers with clarity. They seem to be doing everything right. <em>Yay!</em> And yet, they don’t seem to be <em>acting</em> on it.</p><blockquote>This may ring a bell: you go into a meeting, issues get thrown around, people discuss, and (after a considerable amount of time, of course) the thing ends, and everyone seems to be (kind of) on the same page. People do that thing where they slap their thighs, say “<em>well..!</em>” and head for the door. You leave with a sense of accomplishment after getting everyone to agree on a course of action. But then, a week goes by, and then another.. and nothing seems to have changed. You don’t get it… What happened?</blockquote><p>It may sound counterintuitive, even illogical, but <strong>having all the information and making sense of it isn’t enough</strong>; it is necessary, yes, but not sufficient to actually make change happen. To make change happen, the stakes need to be raised: either something really good is to be gained from action, or something really bad is going to happen unless we take action.</p><p>Things that we agree on don’t translate into action when there is nothing to lose, or when it isn’t clear who gets the blamed it doesn’t, or when the benefit of acting on it isn’t seductive enough. To put it harshly, people ask themselves, “<em>who cares?</em>”, and when no urgent answer comes to mind, the thing probably won’t go any further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*bnmNJMmGVp1p7SV_svi1-g.gif" /></figure><p>So, if we read this right:</p><ul><li><strong>Some organizations don’t know what information they already have</strong>: they are gathering data for sure, but they lack systems to do so in an orderly fashion</li><li><strong>Some organizations do know what information they have, but aren’t sure how to use it</strong>: they lack systems to comprehensively understand their information in a way that makes it easier for them to make decisions</li><li><strong>Some organizations have the information, have systems in place to understand it, and have even come to make comprehensive decisions on it, but aren’t moving into action</strong>: the stakes aren’t high enough.</li></ul><h3>What to do with these conclusions</h3><p>Having reached this point, you might be thinking that <strong>the solution will come from technology</strong>. After all, it’s what Amazon (<em>“the guys who are doing well”</em>) did. They took a decent shot at this whole thing with <a href="https://www.amazon.com/b?ie=UTF8&amp;node=16008589011">Amazon Go!</a>, a brick and mortar store with no employees and no check-out lines, that relies on a combo of computer vision, deep learning algorithms and sensor fusion to make magic happen as customers go in the store, pick up whatever they want and leave, as everything gets automatically billed to their Amazon account.</p><p>Even if you aren’t Amazon, chances are you are still right: <strong>technology might bring the solution to some — or all— of your marketing problems</strong>. But before you embark on such a journey, that noise in your head telling you to incorporate technology needs to be fine tuned, until you can hear some kind of melody in it.</p><blockquote><strong>Nothing is worse than being successful in solving the wrong problem.</strong></blockquote><p>The question, of course, isn’t whether or not technology can save us all. It probably can. The question is <em>what kind</em> of technology is that, how should you approach it, and what implementation strategy better fits your situation. And all of this hinges on a previous step: <strong>clearly defining <em>what kind</em> of problem you’re trying to solve</strong>.</p><p>Coming towards the end of this journey, you probably guessed it: <strong>there is no foolproof recipe to bridge this gap </strong>and make things magically better at the tip of your fingers. Each business, each market, each context and each domain has its own particularities, and the combinations are, if not endless, definitely too many to be solved by a single, straightforward approach. However, since every organization goes through these stages during the development of their marketing strategy, you <strong><em>can</em></strong> use this model to organize that process, and to determine what to focus at every point along the way.</p><p>You can use this knowledge, first and foremost, to understand what stage you are going through. But you can also use it to decide whether or not to chase the category leader and, if so, how; or to figure out if best practices apply or not; or to get a clear definition of the context you are operating in, and adjust accordingly.</p><p>Most importantly, I think you can use this model to acknowledge and work on bridging your Jekyll &amp; Hyde gaps. And that will have a direct and immediate impact on your customers and their experience.</p><p><em>about </em><a href="https://medium.com/u/9b03e30b2b33"><em>Martín Pettinati</em></a><em>:</em></p><p>I want you to communicate better. When I’m not communicating the awesome stuff that gets done at <a href="https://manas.tech/"><strong>Manas.Tech</strong></a>, I write, talk, design and execute trainings on communication, marketing, presentations, public speaking, leading teams, and several other things, always within the field of communication, always focused on doing, and with the purpose of creating and sharing useful and applicable things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ced20d6b1e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manas-tech/the-4-stages-of-fixing-the-customer-experience-gap-5ced20d6b1e4">The 4 stages of fixing the customer experience gap</a> was originally published in <a href="https://medium.com/manas-tech">manas.tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>