<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jorge Gómez Sancha on Medium]]></title>
        <description><![CDATA[Stories by Jorge Gómez Sancha on Medium]]></description>
        <link>https://medium.com/@jorgesancha?source=rss-1a963afbe914------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*pi4HkjCeJmUAHi6nvSmA9Q.jpeg</url>
            <title>Stories by Jorge Gómez Sancha on Medium</title>
            <link>https://medium.com/@jorgesancha?source=rss-1a963afbe914------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:10:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jorgesancha/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[You reap what you sow, specially as a Product Manager]]></title>
            <link>https://medium.com/@jorgesancha/you-reap-what-you-sow-specially-as-a-product-manager-3a234d6ee81d?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a234d6ee81d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Thu, 04 Apr 2024 23:38:45 GMT</pubDate>
            <atom:updated>2024-04-04T23:38:45.479Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*YLV2WsrMPxYGrnP9.jpg" /><figcaption>You reap what you sow</figcaption></figure><p>As a Product Manager joining an organisation, you may fall straight into project management mode: the team is probably feeling they have too many competing priorities and need someone to organise and prioritise the work.</p><p>So if you are any good at it, project managing whatever developments are ongoing can be a safe haven for a newly hired Product Manager such as yourself: it is an area where you can add value quickly and win the confidence of the team.</p><p>At the same time, the rest of the organisation will be feeling that they need more visibility on when things are coming out, so you will timidly start to produce a roadmap together with the CEO and/or the CTO, based on a number of inputs (mostly internal at this point).</p><p>Everybody will be happy with your work: you’ve come in and cleaned house, you’ve started building and sharing a roadmap and communicating what is ongoing. Feels like progress!</p><p>Meanwhile, without realising it, you will probably have done yourself and the company a huge disservice.</p><p>Wait… What?! Why??</p><p>They say that actions speak louder than words and, specially in companies without much product culture or experience, by taking on project management as your primary duty you will be relaying precisely the message that project management is what you do.</p><p>But you are a <strong>Product Manager</strong>, and your job is not about <em>building things</em>: is about ensuring the <em>right things are built</em>. Project Management might be part of your job at times and something you will no doubt need to help out with, but it shouldn’t be <em>your main job</em>.</p><p>If you start by project managing and become indispensable in that arena, you will have a hard time freeing time to work your way through to the other end of the spectrum of your responsibilities: researching and understanding customers’ needs, coming up with solutions together with the team, validating the usefulness of what you build, and using all of that to help inform and evolve the company’s purpose and longer term vision.</p><blockquote>At the end of the day, as a Product Manager you should judge yourself (and sooner or later your CEO will too) by how successful your company is thanks to the products you manage.</blockquote><p>If what your team builds is not what the customers want, if it doesn’t sell, no one will care about how well you project managed the whole thing, or how much the team loves you because you prioritise their tasks and spec them out beautifully. On the contrary: they will eventually wonder (and rightfully so) why did you build those things in the first place.</p><p>I speak from experience: in CARTO I took over Product in a very delicate moment and, for the first 6 months, I was on pure execution mode: pretty much all I did was to execute on someone else’s roadmap. When I eventually looked up, we had built and fixed and improved loads of things: but were those the <em>right</em> things? The things that would really move the needle? Most of them probably weren’t, if I’m totally honest. And although I hadn’t really chosen those things, I was still held responsible for the outcomes (or lack thereof).</p><p>James Clear, the author of “Atomic Habits”, argues in <a href="https://fizzle.co/sparkline/james-clear-fs359?utm_source=jorgesancha&amp;utm_medium=email&amp;utm_campaign=you-reap-what-you-sow-specially-as-a-product">this interview</a> that pretty much everything that happens to you is a “lag measure” (a reflection, let’s say) of your habits: how fit your are is a reflection of your eating, sleeping and exercising habits over time; if you make enough money, how much money you save is a reflection of your spending and financial habits; how clean your desk is after a while is a reflection of your organisational habits, etc. And these habits have a compounding effect over time, for better or worse.</p><p>So, as a Product Manager, you should think about that eventual “lag measure” you want to accomplish and commit as soon as possible to keeping the habits that will contribute to it. Ask yourself questions like these:</p><p>Over time, what will have more impact?</p><ul><li>Being part of every single development discussion <em>or</em> reading and answering customer support emails (so that you see first hand what problems they are suffering)?</li><li>Attending every stand-up meeting <em>or</em> attending more sales calls (so you can understand use-cases and gauge reactions to features and demos)?</li><li>Making every single product decision for the developers and designers <em>or</em> spending more time explaining what outcome you are trying to achieve and why (so that they can take those decisions themselves)?</li></ul><p>Something worth considering, wouldn’t you agree?</p><p>I wrote this back in 2020 as part of a newsletter I no longer write. But I just read it and thought it had stood the test of time reasonably well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a234d6ee81d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You reap what you sow, specially as a Product Manager]]></title>
            <link>https://medium.com/@jorgesancha/you-reap-what-you-sow-specially-as-a-product-manager-535caee841bb?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/535caee841bb</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Thu, 09 Jan 2020 19:04:55 GMT</pubDate>
            <atom:updated>2020-01-09T22:12:45.189Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*a_8DhIJtrtAsfH-g.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@jbrinkhorst?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jonathan Brinkhorst</a> on <a href="https://unsplash.com/s/photos/wheat?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As a Product Manager joining an organisation, you may fall straight into project management mode: the team is probably feeling they have too many competing priorities and need someone to organise and prioritise the work.</p><p>So if you are any good at it, project managing whatever developments are ongoing can be a safe haven for a newly hired Product Manager such as yourself: it is an area where you can add value quickly and win the confidence of the team.</p><p>At the same time, the rest of the organisation will be feeling that they need more visibility on when things are coming out. So you will timidly start to produce a roadmap together with the CEO and/or the CTO, based on a number of inputs (mostly internal at this point).</p><p>Everybody will be happy with your work: you’ve come in and cleaned house, you’ve started building and sharing a roadmap and communicating what is ongoing. Feels like progress!</p><p>Meanwhile, without realising it, you will probably have done yourself and the company a huge disservice.</p><p>Wait… What?! Why??</p><p>They say that actions speak louder than words and, specially in companies without much product culture or experience, by taking on project management as your primary duty you will be relaying precisely the message that project management is what you do.</p><blockquote>But you are a <strong>Product Manager</strong>, and your job is not about <em>building things</em>: is about ensuring the <em>right things are built</em>.</blockquote><p>Project Management might be part of your job at times and something you will no doubt need to help out with, but it shouldn’t be <em>your main job</em>.</p><p>If you start by project managing and become indispensable in that arena, <strong>you will have a hard time freeing time to work your way through to the other end of the spectrum of your responsibilities</strong>: researching and understanding customers’ needs, coming up with solutions together with the team, validating the usefulness of what you build, and using all of that to help inform and evolve the company’s purpose and longer term vision.</p><blockquote><em>At the end of the day, as a Product Manager you should judge yourself (and sooner or later your CEO will too) by how successful your company is thanks to the products you manage.</em></blockquote><p>If what your team builds is not what the customers want, if it doesn’t <em>sell</em>, no one will care about how well you project managed the whole thing, or how much the team loves you because you prioritise their tasks and spec them out beautifully. On the contrary: they will eventually wonder (and rightfully so) why did you build those things in the first place.</p><p>I speak from experience: in CARTO I took over Product in a very delicate moment. For the first 6 months, I was on pure execution mode: pretty much all I did was to execute on someone else’s roadmap. When I eventually looked up, we had built and fixed and improved loads of things: but were those the <em>right</em> things? The things that would really move the needle? Most of them probably weren’t, if I’m totally honest. And although I hadn’t really chosen those things, I was still held responsible for the outcomes (or lack thereof).</p><p>James Clear, the author of “Atomic Habits”, argues in <a href="https://fizzle.co/sparkline/james-clear-fs359?utm_source=jorgesancha&amp;utm_medium=email&amp;utm_campaign=you-reap-what-you-sow-specially-as-a-product">this interview</a> that pretty much everything that happens to you is a “lag measure” (a reflection, let’s say) of your habits: how fit your are is a reflection of your eating, sleeping and exercising habits over time; if you make enough money, how much money you save is a reflection of your spending and financial habits; how clean your desk is after a while is a reflection of your organisational habits, etc. And these habits have a compounding effect over time, for better or worse.</p><blockquote>So, as a Product Manager, you should think about that eventual “lag measure” you want to accomplish and commit as soon as possible to keeping the habits that will contribute to it.</blockquote><p>Ask yourself questions like these:</p><p>Over time, what will have more impact?</p><ul><li>Being part of every single development discussion? Or reading and answering customer support emails (so that you see first hand what problems they are suffering)?</li><li>Attending every stand-up meeting? Or attending more sales calls (so you can understand use-cases and gauge reactions to features and demos)?</li><li>Making every single product decision for the developers and designers? Or spending more time explaining what outcome you are trying to achieve and why (so that they can take those decisions themselves)?</li></ul><p>Something worth considering, wouldn’t you agree?</p><p><a href="https://buttondown.email/jorgesancha"><em>Subscribe to my mailing list</em></a><em> if you want to get a post about Product, People and Startups in your inbox every two weeks</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=535caee841bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[VP of Delivery]]></title>
            <link>https://medium.com/@jorgesancha/vp-of-delivery-3c8cbfeeb2a0?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c8cbfeeb2a0</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 17:31:05 GMT</pubDate>
            <atom:updated>2019-08-02T17:31:05.333Z</atom:updated>
            <content:encoded><![CDATA[<p>A question I hear a lot is <em>what does a VP of Engineering do</em>?</p><p>I think part of the confusion comes from the title itself: <strong>VP of Engineering.</strong></p><p>It doesn’t convey much, does it? The combination of ‘VP’ (<em>Vice President? wait, reports to the President? I didn’t know we had one!</em>) and ‘engineering’ confuses even the sharpest engineers. And they too, when one joins their company — usually as their new boss — often wonder whether they need one at all.</p><p>It is made more confusing by the other Technology leadership title in startups: <strong>Chief Technology Officer</strong>.</p><p>This one is clearer for engineers and non-engineers alike (<em>clearly, the Chief of Technology must be the Chief of all Technology thingies!)</em> However, it doesn’t help the case of the VP of Engineering title.</p><p>This is because “<em>Technology</em>” is a big word under which many things can fall, including <strong>people</strong>, <strong>organisation</strong> and <strong>process</strong>, areas where often a VP of Engineering can make the difference.</p><p>When I joined CARTO in 2016 it was as VP of Engineering. Folks were understandably confused:<em> “sounds important! what does it mean?”.</em> At the time, my go-to soundbite to explain my job simply was:<em> “the CTO makes the technical calls, I look after the people and the processes”</em></p><p>That’s not how I define it anymore.</p><blockquote>A<strong>s important people are</strong> within an organisation and <strong>as effective as the right processes can be</strong>, they are not why CEOs hire VP of Engineers.</blockquote><p>CEOs hire VP of Engineers for three reasons, often in this order:</p><ol><li><strong>to give the CTO space</strong> and time to think and work on the technology</li><li>to make sure <strong>“shit gets done quickly and well”</strong></li><li>to make sure everything is in place <strong>to continue to “get shit done quickly and well” at a sustainable and predictable pace.</strong></li></ol><p>It is on the 3rd point where the “people and processes” bit falls squarely in.</p><p>Everybody wants the technical team to be happy and motivated, to have great sourcing and recruiting processes in place, great test coverage, great laptops to work on, career paths; but none of that matters unless it contributes to your developers being more effective at doing important, purposeful work that gets used by an increasing number of customers.</p><blockquote>To put it differently, rather than trying to bend the world around developers to make them happier, bend it to make them more effective, because that will make them happier.</blockquote><p>At the end of the day and as time goes by, if that team is not delivering product consistently and successfully, no one will be happy: not the CEO, not the CPO, not the Sales organisation, not even your technical team for which you may have so conscientiously setup career paths.</p><p>So when someone asks me nowadays “what do VPs of Engineering do?” my answer is now <strong>“They make sure shit gets done quickly, predictably and well. They are the VPs of Delivery”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68fPZL6QCXC19wgqi32-MA.jpeg" /></figure><blockquote>DISCLAIMER! Nothing in this post is meant to imply that career paths, time to work on side-projects or go to conferences, learning resources, technical chats, or many other things are not important: they absolutely <em>can</em> be. It implies that none of that will matter in the long run <em>unless</em> it contributes to making them more productive and effective.</blockquote><p>If you are starting out as a manager, you might find these other posts useful:</p><ul><li><a href="https://medium.com/@jorgesancha/competent-manager-helpless-employees-fa2ce5807b0">Competent Manager, Helpless Employees</a>, on how to avoid micro-management while still taking making use of your unique skills</li><li><a href="https://medium.com/@jorgesancha/the-bad-and-the-ugly-yes-but-also-the-good-450afeaee6ef">The bad and the ugly, yes; but also the good</a>, on giving negative feedback</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c8cbfeeb2a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The bad and the ugly, yes. But also the good]]></title>
            <link>https://medium.com/@jorgesancha/the-bad-and-the-ugly-yes-but-also-the-good-450afeaee6ef?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/450afeaee6ef</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Mon, 28 Jan 2019 11:05:04 GMT</pubDate>
            <atom:updated>2019-01-29T19:09:48.558Z</atom:updated>
            <content:encoded><![CDATA[<p>Take your feedback and shove it!</p><p>I don’t know about you, but that’s what I think whenever I get negative feedback from people that <strong>never ever give me positive feedback.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eaYrOTQfGIawWOCT.jpg" /><figcaption>Tell me something nice, kid… I have a heart too, you know.</figcaption></figure><p>Don’t get me wrong: I love feedback. The positive, the negative and the down right ugly. There is no progress without feedback, so I not only want it, I demand it! Long live <a href="https://twitter.com/jorgesancha/status/1064840092190195712">360 evaluations</a> and <a href="https://twitter.com/luisico/status/1088846097362178049">weekly 1 to 1s</a>.</p><p>But if you are never ever going to give me the positive stuff, if you are not willing to point at something I’ve done and say <em>“that really worked! You miracle worker, you…”</em> or <em>“hey! really good presentation! It really resonated because…”</em> or <em>“you were right about that thing”</em> or simply <em>“good job with that”</em>, then really don’t bother with the negative stuff, because after receiving only negative feedback for a while, I just don’t care what you think.</p><p>Maybe you have seen <a href="https://www.youtube.com/watch?v=WN_IzDeBdRM">Whiplash</a> too many times and you buy that “good job” are the two most harmful words in the english language. But you are not <a href="https://www.imdb.com/title/tt2582802/characters/nm0799777?ref_=tt_cl_t2">Fletcher</a>, dear manager. You are not trying to train the new <a href="https://en.wikipedia.org/wiki/Charlie_Parker">Bird</a>. You are trying to run an organization, hopefully one that goes on to achieve whatever you are aiming for. If you limit yourself to providing just the negative feedback, one of three things (and sometimes all of them) usually happen with folks:</p><p>- they start losing their self-confidence<br>- they don’t feel valued<br>- they burn out and, eventually, move on</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U-3KCtYdv7_md2bk.jpg" /><figcaption>Don’t be that guy</figcaption></figure><p>People in your organization need to grow in a healthy, motivating way, so that they are willing to stick around for a long time, so that they progressively get better and readier to deal with the also progressively heftier challenges your organization will undoubtedly face.</p><p>And I’m not talking about hiding negative feedback between chunks of good feedback with the <a href="https://www.forbes.com/sites/alisacohn/2017/06/20/please-stop-using-the-feedback-sandwich/">infamous feedback sandwich</a>; you can give it to me straight. But only as long as I know that, whenever I get things right, you will also (or at least, sometimes) point them out.</p><blockquote>Here is the secret: if you want to be able to provide negative feedback in a constructive way, you need to earn it.</blockquote><p>And you earn it by establishing a relationship of trust and respect with that person. They need to know that, beyond whatever your personal agenda and alongside with whatever’s best for the company, you also have their best interest at heart. They need to know you are looking out for them as well as for the company; that what you tell them will not just be good for the company, it will make them better too.</p><p>And no one can feel that unless you tell them BOTH the positive and the negative.</p><p>So be honest, manager. Be authentic! Go out of your way to praise someone if you believe they have done something right. You’ll positive-reinforce the hell out of their behavior and in the process, you will not only earn the right to point out those things that they can do better, you will ensure that it will be listened to intently and acted on swiftly when you do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=450afeaee6ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Competent Manager, Helpless Employees]]></title>
            <link>https://medium.com/@jorgesancha/competent-manager-helpless-employees-fa2ce5807b0?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa2ce5807b0</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Wed, 21 Nov 2018 07:17:58 GMT</pubDate>
            <atom:updated>2018-11-21T07:21:19.580Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>In the novel <a href="https://amzn.to/2DraLqu">Today will be different</a> from Maria Semple, there is a wonderful paragraph where the protagonist explains the nature of her relationship with her husband:</p><blockquote>There’s a phenomenon I call the Helpless Traveler. If you’re traveling with someone who’s confident, organized and decisive you become the Helpless Traveler: “Are we there yet?” “My bags are too heavy.” “My feet are getting blisters.” “This isn’t what I ordered.” We’ve all been that person. But if the person you’re traveling with is helpless, then you become the one able to decipher train schedules, spend five hours walking on marble museum floors without complaint, order fearlessly from foreign menus, and haggle with crooked cabdrivers. Every person has it in him to be either the Competent Traveler or the Helpless Traveler. Because Joe is so clearheaded and sharp, I’ve been able to go through life as the Helpless Traveler. Which, now that I think about it, might not be such a good thing.</blockquote><p>I loved that paragraph and the comparison because I too have been the Competent or Helpless Traveler many times, when traveling and in many other contexts as well.</p><p>It made me think about management and how easy it is as a manager to get into the Competent Traveller role, dictating to the members of your team how to go about any and all things.</p><p>I have the good fortune at <a href="https://medium.com/u/bad1a3c5dd60">CARTO</a> of working with a team that knows more about everything than I do (and I’m not being coy — this is true!), so my opportunities to dictate stuff are few and far between. But even with a highly specialised team, I still fall in that trap sometimes. And I see this happening a lot to others as well and at all levels of management.</p><blockquote>In the spirit of getting things done, in the name of achievement, in trying to ensure a particular outcome or in trying to get there faster, it is very easy to become the dictator.</blockquote><p>And sometimes it might be necessary and it might work for a time, but it is not sustainable. Here’s, in my experience, why:</p><h4>Passivity</h4><p>If you consistently tell people what to do and how, you are essentially training your team to wait for your instructions. And that’s what they’ll do. “Let’s wait and see what he says…” will become their modus operandi. They will essentially become those Helpless Travelers, always waiting for you to sort out the tickets for them and to tell them what train to get on, instead of starting to work on problems and coming up with potentially exciting alternatives; because, why would they if in the end is going to be what you say no matter what?</p><h4>Demotivation</h4><p>Everyone has their own ideas and opinions and, even if you are the expert and the person you are managing recognises you as so, there will come a time when their own experience and ideas don’t match yours; <strong>if they can never see their own ideas realised, eventually they will want to go somewhere where they’ll let them</strong>.</p><h4>Unaccountability</h4><p>Not their fault, right? If things go wrong but they have limited themselves to following your orders to the letter, they won’t feel responsible if the initiative fails or things turn out badly.</p><h4>Mediocrity</h4><p>No matter how much you know about a given subject or how sure you are about the way forward, it is impossible to know how your team would fare on their own unless you let them.</p><p>And in not letting them, you will be limiting yourself (and your company) to the solutions you are able to conjure up on your own. You will be missing out on the combined creativity locked-up within the brains of your team members. Their likely different, potentially surprising and maybe better approach to tackling whatever problems you are trying to solve will never see the light of day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4XuzA72YHSjYDWI6sNrk2g.jpeg" /><figcaption>Your helpless team tagging along while you competently do everything for them. Photo by <a href="https://unsplash.com/photos/6U5AEmQIajg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jehyun Sung</a> on <a href="https://unsplash.com/search/photos/leader?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>None of the above means that you need to abdicate your responsibilities and let your team do whatever they want. Your expertise is probably essential and it should not be wasted! On the contrary, you <em>have</em> to leverage it; but it is probably better to use it to guide people, not to drag them around; to <strong>illustrate important points and ask difficult questions</strong>, not to work through the whole problem; you should use it to try to <strong>edit their work and provide feedback to make sure it is all that it can be</strong>, rather than trying to lay it all out for them.</p><blockquote>Most importantly, use your expertise to explain <em>why</em> certain things are important, <em>why</em> you are asking them to do one particular thing or other, <em>why</em> it is important for the company to go in a certain direction.</blockquote><p>Because if you succeed in conveying the <em>why</em> of things, their ideas should start matching yours, or at least, aligning perfectly with yours; and that’s when things start to flow, when people feel free and encouraged to suggest ideas, when projects seem to breeze without needing constant oversight and when the outcome of their work is as good or better than you expect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b4Sj7A6RM5V1NKHC" /><figcaption>You and your team in (ehem) perfect alignment. Photo by <a href="https://unsplash.com/@adspedia?utm_source=medium&amp;utm_medium=referral">Val Vesa</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>And if you are not an expert on the subject? Well, all the more reason to listen and let them show the way…</p><blockquote>“Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity.”</blockquote><p>Is the old quote attributed to <a href="https://www.businessinsider.com/11-quotes-that-show-the-great-leadership-of-general-george-patton-2015-11?IR=T#1-a-pint-of-sweat-will-save-a-gallon-of-blood-1">General Patton</a>, that although somewhat abused, perfectly captures this.</p><p>But let’s be honest too: all of this is easier said than done. <strong>Unfortunately one doesn’t turn into General Patton overnight</strong>, inspiring action through eloquently described visions of product and company, gaining respect through flawless and steady-handed leadership; and one often doesn’t have (well, never really) teams of military trained operatives to carry out one’s orders, but rather diverse members with wildly different seniority, background and skills.</p><p>So knowing what to delegate and how much and when and to whom is a key part of getting all of this right¹. People have different skills, seniority and motivations and you can’t delegate equally with each of them.</p><p>Just like you wouldn’t tell your 7 year old daughter “We need to get to Brugge, kid: go sort it out for the whole family!” you probably shouldn’t ask your newly hired junior developer to rethink your whole infrastructure so that you can better scale horizontally. Mind you, they might figure it out! But it could be you find your way in Brugge via Sidney, or that you find a big Google Cloud bill in your inbox.</p><p>However, I do ask my 7 year old to help us figure out what our boarding gate is when at the airport; and to guide the whole family there. Just like anybody else she loves a challenge, and I encourage her to be the Competent Traveller even though it would be much easier to have her follow me. It works wonders, just like it does at work.</p><ol><li>This post started as a humongous one that also included practical tips as to how and when to delegate, but I decided to split it in two. Those practical tips on delegation are coming in my next post. Follow me here or on <a href="https://twitter.com/jorgesancha">twitter</a> if you are interested in reading that one too.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*TgTS3oovPCoJQ-mDFAcwPQ.gif" /><figcaption>Thanks to Iván Malagón and François Chabat for their comments on the draft.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa2ce5807b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should learn to say NO to your clients]]></title>
            <link>https://medium.com/@jorgesancha/why-you-should-learn-to-say-no-to-your-clients-2a6e6d765592?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a6e6d765592</guid>
            <category><![CDATA[client-relationship]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Thu, 18 Oct 2018 02:21:05 GMT</pubDate>
            <atom:updated>2018-10-23T01:08:21.135Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why you should say NO to your clients</h3><p>My colleague Bastian (with whom I co-founded BeBanjo) often tells me that he learnt from me how to say No. Not sure I’m <em>that</em> good at it, to be honest, but I did learn from the best!</p><p>Many years ago him and I asked <a href="https://twitter.com/javiercanada">Javier Cañada</a> (designer and teacher extraordinaire, now founder of <a href="http://www.tramontana.co/">Tramontana</a>) to help us design our product <a href="https://bebanjo.com/products/sequence/">“Sequence” at BeBanjo</a>. He was the first Designer we ever hired (and the first one I personally ever had to manage) and his capacity to unequivocally say “No” blew me away.</p><p>It stung a bit at first every time he told me “No”. I suppose that, in my inexperience, I was expecting some level of abidance whenever I said “we should change this” or “this should work differently” (after all, I was paying!), but Javier had no problem saying things like “No, that makes no sense” if my suggestion was crap. He would even laugh out loud at my (very likely) stupid design/ux related suggestion and come back with a comically distorted version of it… the bastard!</p><p>He didn’t say no to everything, though: he accepted good suggestions and listened carefully to the business problems we were trying to solve.</p><p>But I realised something: every time he said “NO” and defended his position, <strong>he was cementing his place as the Design expert in the room</strong> and <strong>he was gaining my trust</strong>. It made me feel that I was in good hands, that I should follow his advice and that I could trust him because he had no reason to lie: he would just tell me things as they were.</p><blockquote>Saying NO to your clients is an empowering tool. And anyone can do it; we are just not used to it after years of “the customer is always right” nonsense.</blockquote><p><strong>Experts can say NO</strong>. In fact, they are expected to say NO. Intelligent people often surround themselves with straight-shooters, with those that won’t be afraid to confront them or point out when they are wrong; as opposed to egotistical maniacs, who surround themselves with malleable people and sycophants who will agree with everything they say (and you can look at my LinkedIn and try to figure out who I’m talking about)</p><p>So if you consider yourself an Expert in any field and you want to work with intelligent people, <em>don’t be a YES man</em>, because saying YES to everything will only erode their perception of you as an Expert.</p><p><strong>Beginners can also say NO</strong>… but it might require some bargaining. If you are a beginner, you may not yet have the track record or credentials to say NO, but that shouldn’t stop you! Argue your compelling reasons and, if need be, you can resort to things like “Please, trust me on this. Let me give it a try my way first, we can always go back to your way if it doesn’t work”</p><blockquote>If your client or boss is worth their salt, they will know that letting you get away with what you want will motivate you incredibly to getting it right and that you will happily own the outcome (or fallout) of your decision.</blockquote><h3><strong>Ok, But Why Say No?</strong></h3><p>After all, nobody likes naysayers…</p><p>Saying NO to your clients (and when I say clients, I mean anyone you work for — an actual client, a boss, a user, etc…) will get you <em>three things you really want</em>:</p><p><strong>1.Trust and credibility</strong><br>Your clients come to you for help. They have a problem or an idea for a project and they come to you. Helping them is not about saying yes to whatever they ask; helping them is about applying your skills and experience to steer them in the right direction, and your skills and experience will often tell you: “My client is wrong”.</p><p>If you only say YES, you are not helping them; but if you say NO and you show them a better way, <strong>you will earn their trust</strong>.</p><p><strong>2. Happiness</strong><br>Or at least, self-preservation.</p><p>If you say YES to things you should say NO to, you will be disappointed. And the more you fail to stand your ground by saying YES when you should say NO, the more disappointed you will be. You will lose motivation. You will loathe that project and day-dream of better projects and clients.</p><blockquote>You can’t expect dream projects to fall on your lap, but you can try to make every project you work on a DREAM PROJECT. Learning to say NO will help with that.</blockquote><p><strong>3. Freedom to choose</strong><br>Once you learn to say NO and realise how valuable it is, you will not be afraid of losing customers or prospects through saying NO. In fact, you will feel the opposite.</p><h3><strong>How to say NO</strong></h3><p>One thing is knowing you should say NO, another thing is to do it; and another entirely different thing is to do it in such a way that you actually reap the benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*7L13zwtniKxeEwtWf-D5tw.gif" /><figcaption>These are not the droids you are looking for…</figcaption></figure><p>Here are some tips:</p><ol><li><strong>Say NO early</strong><br>Early on the project, choose something important you disagree on and push back firmly on it. It will set the tone of your relationship and you will learn how your client breathes.</li><li><strong>Offer a better alternative<br></strong>You cannot say NO unless you have compelling reasons to do so; explain them calmly, try not to get excited… be cool.</li><li><strong>Excel at delivering your alternative</strong><br>Once you’ve fought back on something, you must absolutely rock at delivering the alternative. It will help build TRUST (“he was right!”) and it will make it easier to say NO again when you have to.</li><li><strong>Don’t say NO as a general rule</strong><br>Clients and bosses have little hearts too, you know… If you always say NO, they will be the ones that lose motivation and eventually, they won’t want to work with you. So if one of the times you are not sure about who is right (your client or you), go with the client’s option and earn some good will.</li><li><strong>Be nice</strong><br>NO can be a hard word, don’t be a jerk when you say it. There are many ways to say NO that are still firm and don’t burn bridges: “I don’t agree with that”, “That’s not the case”, “I’m thinking there is a better way…”</li><li><strong>When you say YES, be enthusiastic</strong><br>Whenever customers are right, don’t hold back on saying… “YOU ARE SO RIGHT!” This will put you and your customer at the same level. You will be a team working towards a common goal. And you will go on to rule the world together.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*-Yr5a0sxVt3X6k143EFMrQ.png" /><figcaption>You and your client, getting ready to rule the world together</figcaption></figure><p>Some people don’t like to be told NO: they prefer being RIGHT rather than being EFFECTIVE, and you don’t want to work for them. Choose another client more worthy of your skills and time: they are out there.</p><p><strong>If you have enjoyed reading this story, please give it a 👏 so other people will see it here on Medium.</strong></p><p>I’ve just started writing on Medium and I’m keen to understand what interests you; your claps, comments and follows mean a lot.</p><p><strong>This story is published in </strong><a href="http://blog.usejournal.com/"><strong>Noteworthy</strong></a><strong>, where 10,000+ readers come every day to learn about the people &amp; ideas shaping the products we love.</strong></p><p><a href="http://blog.usejournal.com/"><strong>Follow our publication</strong></a><strong> to see more product &amp; design stories featured by the </strong><a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post"><strong>Journal</strong></a><strong> team.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a6e6d765592" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I've learnt about Sponsored Features in Product Management]]></title>
            <link>https://medium.com/@jorgesancha/what-ive-learnt-about-sponsored-features-in-product-management-3d5d2e7d2612?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d5d2e7d2612</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-features]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Mon, 28 May 2018 08:29:04 GMT</pubDate>
            <atom:updated>2018-05-28T09:10:30.651Z</atom:updated>
            <content:encoded><![CDATA[<h3>What I’ve learnt about Sponsored Features in Product Management</h3><p>Should you build features in your product if a customer is willing to pay for them? Short answer: <strong>No</strong>.</p><p>But what if that key customer won’t renew? What if you are at a point where you cannot afford to lose certain customers? Hmmm… Ok, read on.</p><p>A while ago a friend asked me about my experience with “Sponsored Features”. Are they a good idea? How do I introduce them to our customers? Will they jeopardise my roadmap? Will they turn us into a consulting company rather than a product company?</p><p>I wrote this blog post back then but I didn’t publish it because I h̶a̶v̶e̶ ̶a̶ ̶m̶a̶s̶s̶i̶v̶e̶ ̶ ̶i̶m̶p̶o̶s̶t̶o̶r̶ ̶s̶y̶n̶d̶r̶o̶m̶e̶ ̶was really busy at the time. Recently, however, the nice folks at <a href="https://medium.com/u/2be38458200b">Wise Athena</a> came to <a href="https://medium.com/u/bad1a3c5dd60">CARTO</a> to talk about engineering and product, and the concept of “Sponsored Features” came up again, so I thought I’d dig this up and publish it.</p><p>Sponsored Features are relevant to B2B software products and they often come up early in the life of those products, when there is not yet a clear market fit or when you are entering a new phase (e.g. “going for the “enterprise” customers”). Sponsored Features <strong>might make sense </strong>at a certain point in time <strong>but they are also extremely dangerous</strong>… so what follows is a quick primer about them and the pitfalls to look out for.</p><h3>What is a “Sponsored Feature”?</h3><p>I don’t know where the actual term comes from, but it refers to a product feature that:</p><ul><li>you would eventually build into your product as part of your roadmap, <em>and</em>,</li><li>a customer covers the cost of developing it (in part or in total) in exchange for having it delivered earlier</li></ul><p>That is, rather than waiting for the feature to be built as part of your normal development process, they pay for you to build it sooner. In essence, <strong>the customer is buying “priority” for a feature</strong> that would (in theory) otherwise be built sometime in the future.</p><p>Wow! That sounds great, right? Hmmm… <em>not so fast</em>. The customer could be buying much more than priority in the process. Let’s look at what’s great and what isn’t so great about them.</p><h3>The ‘good’ things</h3><h4>Sponsored features can be a powerful tool to close deals.</h4><p>Oftentimes a customer is enamoured by your product but there are those two or three things that <em>they absolutely must have</em> in order to get started. The more ‟enterprisey” your customers are, the more adamant they will be about certain requirements that your product must absolutely have; common features to any SaaS product are things like security requirements, authentication mechanisms, granular permissions or others, but there will also always be things relevant to your specific industry. If <em>what they want really is aligned with what you want</em> for your product, then it is a perfect outcome: the customers get what they want and you get paid to build something that you are going to be able to sell to other customers.</p><h4>Easy cash</h4><p>Cash is important, specially when you are starting, and the difference between just selling a license to use your product or getting the license fee <em>plus</em> your development financed, can be the difference between life or death. A good sponsored feature at the right time could turn an interesting deal into a life saver.</p><h4>Extra hands</h4><p>If you are getting extra funds for a feature, in theory you should have the capacity to hire extra hands to deliver it. And thus (at least on paper) you are not necessarily delaying the rest of your roadmap.<strong> This is an important selling point but often not a very realistic one</strong>; depending on how specialised your stack and how steep the learning curve for a new developer to be productive on your product, it might be more or less realistic.</p><h4>Priorities</h4><p>Sponsored features can greatly help clarify your priorities when it comes to your roadmap. Once you’ve agreed to deliver them, well… you have to. This can be good or bad, depending mainly on how useful this feature will be to your future customers.</p><h3>The pitfalls</h3><h4>Remember: YAGNI</h4><p>You Ain’t Gonna Need It. The biggest pitfall is that the whole premise of <em>sponsored features being those that would (normally) otherwise be built sometime in the future could be totally flawed</em>.</p><blockquote>The reality is that, even if you think your product will need that feature in the future, there is no way of knowing whether you would add it or not if you weren’t getting paid for it.</blockquote><h4>No going back</h4><p>As the Basecamp folks say in Getting Real, <a href="https://gettingreal.37signals.com/ch05_Start_With_No.php">each time you say yes to a feature, you are a adopting a child</a>. In the case of Sponsored Features, this particular child will never find a job and will never leave your home: once a customer has paid for a feature, you will never get rid of it; there is no going back. So it is extra important that you are convinced the feature is right for your product.</p><h4>Your roadmap, at stake</h4><p>If you are not careful, Sponsored Features can become your Roadmap. When you open that door, you are in a way relaying to your customers that, as long as they are willing to pay, it is OK for them to change your Roadmap. And there are surprisingly deep-pocketed companies out there!</p><blockquote>In a way, you are relaying to your customers that, as long as they are willing to pay, it is OK for them to change your Roadmap</blockquote><h4>You must own the definition and IP</h4><p>Even if customers are paying for it, they would need to be crystal clear on two things:</p><ul><li>this is a product feature and as such, <strong>you have the final say on the final solution</strong>. Otherwise you can find yourself introducing a bespoke customer solution into your product</li><li>again, this is a product feature and as such, the rest of the customers will benefit from it and <strong>you will keep IP for the work</strong></li></ul><h3>Should I offer them and, if so, how to go about them?</h3><p>My advice? <strong>Don’t do it.</strong> Think of alternatives, offer workarounds, find a way to do it via APIs or outside of the core product. They come with too many strings attached, so they should be a last resort.</p><p>In general it would be much better to use all of your customer’s input and the market needs to prioritise what you do next, not a specific customer’s cash.</p><p>So my personal suggestions are as follows:</p><p>1) <strong>As always and in general, start with NO</strong>. You don’t add a feature to your product if just one customer wants it (there is ample literature about why you should do this, from 37 Signals to Seth Godin)</p><p>2) <strong>Wait until you see no other option</strong>. Having a particular feature in your roadmap is not a sufficient reason to turn it into a Sponsored one. Sometimes when saying <em>“our product doesn’t do this, but it is in our roadmap”</em>, your customer will say <em>“OK”</em>, and that is really the best outcome, because then you will still have control over your roadmap (remember, this is probably not your only customer and having control of your roadmap allows you to satisfy more than one customer at once!)</p><p>However, if the customer keeps insisting, you see no other option (could this be built outside of your product using your APIs, maybe?), you absolutely need the customer and the feature is worth it (see point 3), turning it into a Sponsored Feature can become a reasonable solution to the conundrum for everybody.</p><p>3) <strong>Be honest with yourself</strong>. <em>Do you really think this feature will be absolutely essential to your product?</em> Oftentimes you end up developing Sponsored Features that “don’t hurt” rather than those that will make the difference. And over time, they do hurt. Also, developing SFs that are not great additions to your product can have a demoralising effect in your team.</p><p>4) Before committing, <strong>make sure you understand in detail what problem they are trying to solve</strong> and then <strong>get sign-off on the solution <em>you</em> devise </strong>before starting development.</p><p>5) <strong>Protect your future roadmap by positioning it as a special case</strong>. Something along these lines: “Look, on rare occasions we do something we call Sponsored Features, which are &lt;explain the concept here&gt;. Because this is a feature we absolutely think that makes sense but we would not prioritise it right now if it weren’t for you, it could be a good candidate. It would allows us to hire additional help so that we can prioritise it without abandoning our current commitments”.</p><p>6) <strong>Protect your relationship by having a roadmap at the ready</strong> — it doesn’t matter if you like detailed roadmaps or not (I personally don’t as my fellow CARTO members know - :trollface: - and I go for very high level ones). Not the same to say “It is in our roadmap” than to actually show where in your roadmap.</p><p>So there you have it. Use sparingly, use with caution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d5d2e7d2612" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Análisis de la desviación de los presupuestos municipales y el gasto real]]></title>
            <link>https://medium.com/gobierto-herramientas/an%C3%A1lisis-de-la-desviaci%C3%B3n-de-los-presupuestos-municipales-y-el-gasto-real-94f968905915?source=rss-1a963afbe914------2</link>
            <guid isPermaLink="false">https://medium.com/p/94f968905915</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[transparencia]]></category>
            <dc:creator><![CDATA[Jorge Gómez Sancha]]></dc:creator>
            <pubDate>Thu, 19 May 2016 15:52:59 GMT</pubDate>
            <atom:updated>2016-05-19T15:52:59.523Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Presupuesto vs. Ejecución: Análisis de la desviación de los presupuestos municipales y el gasto real</h3><h4>Un ejercicio de comparación entre lo que presupuestan los municipios de España y lo que realmente acaban gastando</h4><p>¿Qué te parecería si descubrieras que tu municipio gasta un 621% más de lo que presupuesta? ¿O si por el contrario descubrieras que gasta tan sólo un 8% de su presupuesto anual? Porque esto es lo que pasó en el 2014 con los municipios de <a href="https://presupuestos.gobierto.es/places/tollos/2014">Tollos, Alicante</a> y <a href="https://presupuestos.gobierto.es/places/galbarros/2014">Galbarros, Burgos</a> respectivamente.</p><p>Aunque esos números suenan fatal, esas cifras pueden llevar a engaño porque se trata de algunos de los municipios más pequeños de España, con un total de 59 y 28 habitantes respectivamente y presupuestos totales de aproximadamente €45.000 y 120.000€. Cualquier pequeño cambio en este tipo de municipios puede hacer que el gasto por habitante se dispare o se quede corto, y a pesar de lo espectacular de las desviaciones, a menudo las cantidades son pequeñas y fácilmente explicables.</p><p>Es por ejemplo el caso de <a href="https://presupuestos.gobierto.es/places/galbarros/2014">Galbarros</a> donde, si exploramos las partidas presupuestarias en <a href="https://presupuestos.gobierto.es/">Gobierto</a>, se ve que aproximadamente 85% del presupuesto <a href="https://presupuestos.gobierto.es/budget_lines/galbarros/2014/453/G/functional">iba destinado a “carreteras”</a>; trabajos que seguramente no se hicieron en el 2014 ya que la partida <a href="https://presupuestos.gobierto.es/budget_lines/galbarros/2015/453/G/functional">vuelve a estar presente en el presupuesto del 2015</a>. Lo sabremos en cuanto el Ministerio de Hacienda y Administraciones Públicas publique los datos de ejecución presupuestaria municipal del 2015, que se esperan para Junio.</p><p>Sin embargo, hay muchos otros municipios con grandes desviaciones de presupuesto y en Gobierto, mientras esperamos a los datos del 2015, hemos estado jugando con los datos del 2014 y hemos hecho una pequeña herramienta de visualización de los mismos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rt424hIMjFLzagxxw-KZWQ.gif" /><figcaption>Herramienta de comparación de Presupuestos y Ejecución</figcaption></figure><p>Con ella hemos podido descubrir cosas como que, de todos aquellos municipios con datos presupuestarios (6426 de 8192):</p><ul><li>un 42% (2716 municipios) cumplen con su presupuesto con una desviación igual o menor al 10% (son la franja de puntos azules claros en medio del gráfico), un 31% (2008 municipios) incrementa su ejecución en más del 10% y el ~26% de municipios restantes no llegan a ejecutar el 90% de su presupuesto</li><li>un 25% (1612 municipios) se desvían del presupuesto más de un 25% (950 lo superan y 662 ejecutan el 75% de su presupuesto o menos)</li><li>un 1,1% (73 municipios) se desvía un 100% o más de su presupuesto!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*hmbPeO10ZTmGFwT5J2gvYQ.png" /><figcaption>73 municipios superan su presupuesto en un 100% o más</figcaption></figure><p>Curiosamente, estos porcentajes de desviación no se mantienen cuando dividimos los datos por Comunidad Autónoma. Teniendo en cuenta que no hay datos presupuestarios para Navarra, País Vasco, Ceuta y Melilla, y tomando el 10% de desviación como referencia, tendríamos a Madrid, Asturias y Murcia como las comunidades autónomas con mayor número de municipios que se ciñen a su presupuesto (aprox. un 67% de los municipios de esas comunidades dentro de esa desviación).</p><p>En el otro extremo, estaría la Rioja, donde solamente un 24% de los municipios se ciñe a su presupuesto con una desviación del 10% o menos. Curiosamente, la gran mayoría (el 72%) de los municipios de la Rioja no llegan a ejecutar ni el 90% de su presupuesto.</p><p>La comunidad autónoma cuyos municipios más exceden sus presupuestos es Extremadura, dónde un 55% se desvía por encima del 10%. En su defensa habría que decir que no tiene prácticamente municipios que superen los 10.000 habitantes, lo cual, como decíamos al principio, hace que las desviaciones sean bastante más visibles.</p><p><em>Este post se publicó originalmente en el </em><a href="http://gobierto.es/blog/20160518-presupuesto_vs_ejecucion.html"><em>blog de Gobierto.es</em></a><em> y allí puedes encontrar una herramienta interactiva de visualización para que puedas sacar tus propias conclusiones sobre la ejecución de los presupuestos municipales.</em></p><p><em>Gobierto crea herramientas para que los datos públicos de municipios y otras organizaciones sean más usables, y puedas conectar mejor con tus vecinos. Si eres un municipio, </em><a href="https://presupuestos.gobierto.es/users/new?pro=true"><em>regístrate y te montamos una demo con tus datos</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94f968905915" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gobierto-herramientas/an%C3%A1lisis-de-la-desviaci%C3%B3n-de-los-presupuestos-municipales-y-el-gasto-real-94f968905915">Análisis de la desviación de los presupuestos municipales y el gasto real</a> was originally published in <a href="https://medium.com/gobierto-herramientas">El blog de Gobierto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>