<?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 José Fernando Costa on Medium]]></title>
        <description><![CDATA[Stories by José Fernando Costa on Medium]]></description>
        <link>https://medium.com/@villager1598?source=rss-14c6e677f21e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Iwrc5fCV6UPISN2y0bapvA.jpeg</url>
            <title>Stories by José Fernando Costa on Medium</title>
            <link>https://medium.com/@villager1598?source=rss-14c6e677f21e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:35:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@villager1598/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[Your proposal is missing a reason to defend it]]></title>
            <link>https://villager1598.medium.com/your-proposal-is-missing-a-reason-to-defend-it-eceedf638f3b?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eceedf638f3b</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 11:01:02 GMT</pubDate>
            <atom:updated>2026-11-16T11:01:02.417Z</atom:updated>
            <content:encoded><![CDATA[<p>The engineer showed her project manager why testing kept slipping. Developers and testers shared an environment, so each new deployment wiped out work the testers were checking. She asked for a separate test environment for the release and explained the cost. The manager agreed to take the request to the director.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cN4kFTv9-3OZZHlRH6lRmg.png" /></figure><p>At the budget meeting, he described it as a request for another server to help the engineers work faster. The director refused because the project was meant to use the infrastructure it already had without increasing cloud costs. Testing restarted after the next deployment, while the engineer prepared more technical detail for a director who never heard why she needed the environment.</p><p>When someone passes on your proposal, they decide which parts to repeat. The thing you want is easy to remember. The problem it solves, the cost of leaving that problem in place, and the limits of the request can disappear from the explanation. The next person ends up judging a proposal without knowing what it would change.</p><p>A longer presentation won’t fix that if the same person has to rebuild your argument from memory. Understanding you during a meeting isn’t the same as being able to explain your request to someone who wasn’t there.</p><p>Give your contact a short explanation they can forward or use in the decision meeting. Connect the problem to the action and state what needs approval. Keep supporting detail available, but make the request understandable without requiring another technical lesson.</p><p>For this engineer, the message needs to say that the development workflow is overlapping with the testing workflow, hence the need for separate environments to handle separate workloads independently. The director can question the expense or ask about other options while dealing with the problem the proposal is meant to solve.</p><p>Ask your contact what the decision maker is likely to challenge and adjust the explanation with them. Don’t make them guess which part of your meeting mattered. If they are going to argue your case, then clearly give them the case you need them to argue.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eceedf638f3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You made the improvement too big to try]]></title>
            <link>https://villager1598.medium.com/you-made-the-improvement-too-big-to-try-0b68d3277904?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b68d3277904</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-11-13T11:01:01.873Z</atom:updated>
            <content:encoded><![CDATA[<p>The support lead answered a night call about a failed service and found no instructions for restarting it. Tired of chasing developers after every handoff, she proposed a new portal for all project teams, with mandatory documentation and training before support accepted their work. Her director refused to introduce it during the current launches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bUVkA9RreU_czRX4Trjdww.png" /></figure><p>She put the proposal aside and accepted the next service with the same handoff email. When it failed, her team called the developer who built it and waited for him to wake up. The rejected portal became her reason to stop trying to improve things and everything stayed exactly the same.</p><p>You can make an improvement so big that you need permission from half the company before learning whether it helps. Once that version gets rejected, it’s tempting to conclude that management won’t let you fix anything. But rejection of the rollout doesn’t establish that every part of the idea is out of reach.</p><p>A new system asks people to spend money, change habits, and accept work before they’ve seen the benefit. If you can test the useful part on work you control, you have a smaller decision to make. You can find out what helps before asking everyone to adopt it.</p><p>Separate the problem you want to fix from the full solution you imagined. Choose one authorized test that can show how the change improves work. Agree on its limits and when to assess the results, so a test run doesn’t become the new way of doing things.</p><p>The support lead could ask one project team to prepare restart instructions and watch a support engineer use them in a test environment. If the engineer gets stuck, the handoff needs work. If the instructions help, she has something worth testing on another service, along with evidence of the effort involved.</p><p>One successful handoff won’t prove that a company-wide portal is worth buying, but it can establish whether the proposed handoff check deserves a wider trial. You don’t need the whole organization to change before you can learn that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b68d3277904" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your manager only has so much authority]]></title>
            <link>https://villager1598.medium.com/your-manager-only-has-so-much-authority-10026de6f93b?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/10026de6f93b</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 11:01:02 GMT</pubDate>
            <atom:updated>2026-11-11T11:01:02.183Z</atom:updated>
            <content:encoded><![CDATA[<p>The tech lead asked her manager to borrow an engineer from another team to rescue a client migration. He agreed the project needed help and told her to put a plan together. She rebuilt the schedule around that engineer, prepared all the onboarding materials, and told the client they could keep the release date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rXtMzzuRPug5b2ZGPTxloA.png" /></figure><p>When she sent the assignments, the engineer’s delivery manager refused to release him. She needed him for another client’s launch, and nobody asked her to change that commitment. The tech lead’s manager supported the recovery plan, but he couldn’t provide the person it depended on. She had to go back to the client and withdraw the date she confirmed.</p><p>Getting your manager to agree can feel like getting the company to agree. But their authority has limits. They can support a change without being able to spend the money, move the people, or accept the consequences on another team’s behalf.</p><p>If your plan depends on those decisions, you need the people who own them involved before you treat the plan as agreed. Their absence doesn’t make their commitments disappear. It means you’re making promises about resources you don’t control, based on a conversation with someone who doesn’t control them either.</p><p>Start with what the work requires and establish who can commit it. Ask your manager to help you reach those people and resolve the conflict. That keeps their support useful without pretending their approval covers the whole plan. A manager who can’t decide allocations may still help bring the two delivery owners together to decide which commitment takes priority.</p><p>For this migration, the engineer’s availability needed confirmation before the revised date went to the client. If both projects needed him, someone with authority over both had to choose, or the recovery plan had to change.</p><p>Don’t build a promise on someone else’s resources until the person responsible for them agrees to provide them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10026de6f93b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building proof without purpose is a waste of time]]></title>
            <link>https://villager1598.medium.com/building-proof-without-purpose-is-a-waste-of-time-1041ad75af04?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1041ad75af04</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-11-09T11:01:01.643Z</atom:updated>
            <content:encoded><![CDATA[<p>The sponsor blocked the new data architecture for lack of knowing whether it worked. The tech lead went ahead and built a demo to show it could handle the current reporting needs. The demo was praised, but the sponsor wanted to see it cover even more reports. Another round of praise came after with yet another set of reports to be tested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKSXL-K9KMguT811zbtvdA.png" /></figure><p>Proof has value when it reduces uncertainty to make a decision. Without that connection, a successful demo becomes another closed task with no consequence for what happens next.</p><p>Some objections emerge because a test reveals something people couldn’t see before. That’s useful learning. The problem is spending effort on iterations of proof without checking what it takes to for someone to make a decision. A better result won’t resolve a missing budget, an unsupported operating model, or a policy restriction.</p><p>You need to know what the proof is supposed to establish and what remains unresolved if it succeeds. Otherwise, you can keep winning the test while getting no closer to a decision.</p><p>Before building the next demo, ask which decision it will inform, who will make the decision, and what result would answer their question. Then ask whether anything else would prevent the work from proceeding. You’re not looking for someone to make the decision on blind faith, just asking for them to place fixed goalposts.</p><p>For this tech lead, the next task is to establish an owner and what they need to see in a demo to fund the new architecture, i.e., what proof the owner needs to make a decision. A working demo is not progress toward approval if its result doesn’t get him closer to a decision.</p><p>If the sponsor needs technical proof before asking for funding, that can be a valid next step. But the commitment is to a funding decision, not to adoption. If no one is prepared to own support under any result, another feature won’t settle that gap.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1041ad75af04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Praise is not support]]></title>
            <link>https://villager1598.medium.com/praise-is-not-support-4d96b2e126fb?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d96b2e126fb</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-11-06T11:01:01.822Z</atom:updated>
            <content:encoded><![CDATA[<p>The consultant showed his manager a proposal to replace a repeated manual check on their infrastructure deployments. The manager called it a great idea and said the team needed more initiative like that. The consultant took the encouragement as support and spent a couple of evenings building a tool around the proposal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ikql9KYii56cUx3OiLEvSg.png" /></figure><p>When he brought back a working version, the manager wouldn’t assign anyone to test it or approve time to introduce it. Client delivery took priority, and nobody agreed to own the tool. The consultant built something, on his personal team, that no one commited to using.</p><p>The manager might mean every positive word. But agreeing that a problem deserves attention doesn’t allocate the time, access, or authority needed to address it. Without a specific commitment, your enthusiasm becomes the resource plan.</p><p>That’s where the resentment begins. You think you’re advancing an agreed improvement, while the other person thinks you’re entertaining yourself. By the time you discover the difference, you have invested enough effort to feel owed a decision that nobody promised.</p><p>Before expanding the work, ask for support to back that encouragement. Ask which working hours you can use, who needs to be involved to validate the results, and who will decide whether to adopt it. The commitment can be small, but it needs to exist outside the compliment.</p><p>By all means continue doing things for your own personal growth. Just don’t let someone else’s “great idea” become an obligation to spend your evenings proving they meant it, or expecting to be rewarded for doing so.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d96b2e126fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your new ideas suffer from the promises you broke in the past]]></title>
            <link>https://villager1598.medium.com/your-new-ideas-suffer-from-the-promises-you-broke-in-the-past-bf91d7d80c96?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf91d7d80c96</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-11-04T11:01:01.900Z</atom:updated>
            <content:encoded><![CDATA[<p>The team lead asked his consultants to help with another onboarding improvement initiative. Last time, they were meant to create the training material in dedicated time, but those hours disappeared when delivery pressure increased. The material remained unfinished, and people had to explain why their client work was behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSNFRqCzmJcg1XdBty9Amw.png" /></figure><p>This time, nobody volunteered. The lead described the team as resistant to change and repeated how much easier onboarding would become. The consultants heard another request to accept work whose promised support could disappear before they finished it.</p><p>People don’t judge an initiative from its proposed benefits alone. They use what happened in the past as reference. A promise of support is weaker after watching support get taken back in the past.</p><p>That history doesn’t prove the new idea will fail, but it means enthusiasm is the wrong thing to ask for first. Another explanation of the benefits doesn’t answer whether people will have the time, access, or support needed to achieve them.</p><p>Before launching the next big idea, ask what made the previous one costly to join. In this case where an allowance for dedicated time disappear halfway through, address that possibility in the new arrangement. Show that you are doing something to prevent it, don’t tell people you’re aware of it.</p><p>Then keep that agreement through the first conflict. The team needs evidence that participation has different consequences this time. Calling them resistant won’t undo the lesson your previous decisions taught them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf91d7d80c96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You asked for initiative and punished the first decision]]></title>
            <link>https://villager1598.medium.com/you-asked-for-initiative-and-punished-the-first-decision-359c544a3049?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/359c544a3049</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-11-02T11:01:01.649Z</atom:updated>
            <content:encoded><![CDATA[<p>The project manager told the team lead she could change the sequence of the user stories as long as the release date and agreed scope stayed intact. She moved an internal report behind a client requirement that was blocking testing. When she presented the revised sequence at the team meeting, the manager asked to speak with her in private, where she faced a barrage of questions about the change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSNFRqCzmJcg1XdBty9Amw.png" /></figure><p>Before the next planning session, she sent him every proposed change for approval, holding up the work until he replied. He asked why she stopped taking initiative, but her last decision within the responsibility he gave became something she needed to defend. Getting his approval before acting seemed safer than finding out what he objected to after the work moved forward.</p><p>When you give someone authority, your response to their decisions teaches them what that authority means. You might think you’re checking their reasoning, but if every choice becomes an interrogation, they have to account for that cost. The next decision includes another consideration: whether acting without your approval is worth the trouble.</p><p>That’s how a team learns to ask permission for work you expect them to own. The agreed boundaries stop being enough because people must anticipate objections you haven’t explained. Sending the decision back to you removes that uncertainty, even if it delays the work. Asking for more initiative won’t help while your response makes seeking approval the sensible choice.</p><p>You can question a decision without questioning the person’s right to make it. Understanding their reasoning, identifying a missed requirement, and sharing information they didn’t have are part of helping them develop judgment. But the conversation needs to establish what needs attention. Your discomfort with a choice doesn’t make that choice a mistake.</p><p>Before challenging a decision, check whether it stayed within the agreed limits and made sense given the information available. If there’s a problem, name it and explain what it changes. If the decision was sound, acknowledge that the person was entitled to make it, even if you would have chosen another approach.</p><p>For this manager, that means addressing the reason for moving the report and its effect on the release. If he finds no conflict with the agreed scope or date, the lead doesn’t need an approval requirement added after the fact. He needs to make clear that decisions within those limits remain hers to make.</p><p>Review the decision in a way that helps the person make the next one, rather than teaching them to leave it with you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=359c544a3049" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop answering before they’ve had a chance to think]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://villager1598.medium.com/stop-answering-before-theyve-had-a-chance-to-think-ea2736fce2cb?source=rss-14c6e677f21e------2"><img src="https://cdn-images-1.medium.com/max/1254/1*TYLYmVgXJJRyaPw6w2OGRg.png" width="1254"></a></p><p class="medium-feed-snippet">The senior consultant answered every design question as soon as her colleague brought it to her. She knew which option would work and&#x2026;</p><p class="medium-feed-link"><a href="https://villager1598.medium.com/stop-answering-before-theyve-had-a-chance-to-think-ea2736fce2cb?source=rss-14c6e677f21e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://villager1598.medium.com/stop-answering-before-theyve-had-a-chance-to-think-ea2736fce2cb?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea2736fce2cb</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 11:01:02 GMT</pubDate>
            <atom:updated>2026-10-30T11:01:02.240Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[You fixed their work and now they don’t learn]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://villager1598.medium.com/you-fixed-their-work-and-now-they-dont-learn-63ee184100ad?source=rss-14c6e677f21e------2"><img src="https://cdn-images-1.medium.com/max/1254/1*Y_GLY_m8AkrVNuFRJixL7A.png" width="1254"></a></p><p class="medium-feed-snippet">The senior consultant found a gap in the junior&#x2019;s test plan before a client release. The tests covered records arriving as expected but&#x2026;</p><p class="medium-feed-link"><a href="https://villager1598.medium.com/you-fixed-their-work-and-now-they-dont-learn-63ee184100ad?source=rss-14c6e677f21e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://villager1598.medium.com/you-fixed-their-work-and-now-they-dont-learn-63ee184100ad?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/63ee184100ad</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 11:01:02 GMT</pubDate>
            <atom:updated>2026-10-28T11:01:02.237Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Being good at fixing problems shouldn’t become your entire job]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://villager1598.medium.com/being-good-at-fixing-problems-shouldnt-become-your-entire-job-f3646ba29400?source=rss-14c6e677f21e------2"><img src="https://cdn-images-1.medium.com/max/1254/1*P9bITwXhq3YN2hDS1ceeCA.png" width="1254"></a></p><p class="medium-feed-snippet">The delivery manager pulled his strongest consultant out of a design workshop to rescue a client release. She knew the system and could&#x2026;</p><p class="medium-feed-link"><a href="https://villager1598.medium.com/being-good-at-fixing-problems-shouldnt-become-your-entire-job-f3646ba29400?source=rss-14c6e677f21e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://villager1598.medium.com/being-good-at-fixing-problems-shouldnt-become-your-entire-job-f3646ba29400?source=rss-14c6e677f21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3646ba29400</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[José Fernando Costa]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 11:01:02 GMT</pubDate>
            <atom:updated>2026-10-26T11:01:02.035Z</atom:updated>
        </item>
    </channel>
</rss>