<?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 João Antunes on Medium]]></title>
        <description><![CDATA[Stories by João Antunes on Medium]]></description>
        <link>https://medium.com/@joao_antunes_?source=rss-68fe095ef711------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ka7zkXVsT4DS9w17.</url>
            <title>Stories by João Antunes on Medium</title>
            <link>https://medium.com/@joao_antunes_?source=rss-68fe095ef711------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:21:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joao_antunes_/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[Why You Should Make Everyone a Project Lead]]></title>
            <link>https://medium.com/entelo/why-you-should-make-everyone-a-project-lead-f167472b580d?source=rss-68fe095ef711------2</link>
            <guid isPermaLink="false">https://medium.com/p/f167472b580d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[João Antunes]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 15:51:49 GMT</pubDate>
            <atom:updated>2019-04-24T15:51:49.491Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jbVo1P763tm6cm3iswJnNw.jpeg" /><figcaption>Photo by <a href="https://www.flickr.com/photos/159535053@N06/">Christopher Mance</a> on <a href="https://www.flickr.com/">Flickr</a></figcaption></figure><p>In this blog post, I’ll describe my latest approach to improving morale and growing the team when facing a more challenging quarter. It is not a one-size-fits-all solution and it might not be well-suited to other teams or other types of roadmap, but it was successful for my team and could be for yours too.</p><p>Before we start, let me give a little bit of context. At the beginning of the last quarter (Q4), I took on the role of Engineering Manager (EM) of the team responsible for the two most prominent and user-facing Entelo products, Search and Envoy. Q4 is typically the most impactful quarter for the company because due to budget constraints and commitments, most prospects prefer to wait until the end of the fiscal year to sign high-dollar deals. This usually translates into a higher effort from product and engineering to accommodate minor (and sometimes major) requests from prospects or trial accounts.</p><h4>Morale</h4><p>Sales renewals are a huge challenge for many SaaS companies, even the most successful ones. Failure to do so, also known as customer churn, can affect not only Annual Recurring Revenue (ARR) but also team morale.</p><p>This is particularly true for startups, where limited resources restrict how many current, new, and future customers can be supported and kept happy. Sales teams, focused on reaching out to prospects and building pipeline, feel the pressure to rapidly replenish churning business with new deals. Customer Success (CS), on the other hand, is forced to prioritize larger customers over smaller ones, risking discontented customers who feel neglected. Even Engineering can become frustrated and disheartened that their efforts ultimately do not produce the expected results.</p><h4>Ambitious roadmap</h4><p>To reduce customer attrition, our CS and Data Science teams partnered up to identify the user actions most strongly correlated with user engagement and customer retention. We then devised a rather ambitious roadmap with several user-facing product enhancements as well as multiple experiments designed to increase user-engagement.</p><p>Some of these features required coordinated efforts between our team and the Infrastructure and Data Science teams to build services that would implement and execute new machine learning models. It’s fair to say that the roadmap called for both intra-team (backend, frontend) and cross-team collaboration (product, design, infrastructure, data science, CS).</p><h4>Communication</h4><p>With so many teams and stakeholders involved, one of the main challenges was keeping everyone (or at least the decision-makers) up-to-date on the status of the several roadmap items to anticipate any roadblocks as soon as possible. It was imperative that the overall status of any feature could be regularly determined in a quick and accurate manner to avoid unexpected delays that could jeopardize the execution of the roadmap.</p><h4>Quality</h4><p>Another challenge my team faced was improving our relationship with CS. Being an agile and high-performing team, we are used to ship fast and, sometimes, break fast. We typically rollout big features internally first, and then phase them out to the customers. With the goal of getting a Minimum Viable Product (MVP) out of the door quickly, we sometimes don’t spend as much time and resources as we’d like in thorough testing, in particular on our internal releases to CS users. As a consequence, our CS team grew frustrated when bugs popped up in newly rolled out features.</p><p>We had a challenging quarter ahead of us.</p><h3>Make everyone a leader</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fpIWJycDvG-w6Htx" /><figcaption>Photo by <a href="https://unsplash.com/@slelham?utm_source=medium&amp;utm_medium=referral">Steven Lelham</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There were many times I succeeded and there were also times I failed, but even in the face of failure I kept trying out new things until I finally found success. The times I learned the most, performed the best, and overall had the most fun, were when I was given extra responsibility and was pushed out of my comfort zone.</p><blockquote>“When people are given purpose (vision), autonomy (decision making and growth ownership) and mastery (functional ownership), they can reach decisions based on their expertise and what would fit best to the team’s values.”<br> — Oren Ellenbogen [<a href="https://leadingsnowflakes.com/">Leading Snowflakes</a>]</blockquote><p>Typically, we do this before promoting an individual: we put them in a position where they need to informally perform a new role with new responsibilities. Once they “prove” they can perform the new role at an acceptable level, they are officially promoted. This is a very common promotion approach designed to avoid the <a href="https://en.wikipedia.org/wiki/Peter_principle"><em>Peter Principle</em></a>, in which employees are continually promoted based on their success at previous roles and until they reach a level at which they are no longer competent. Promotions, and the extremely valuable growth opportunities that come with it, are, however, rare events (e.g., once a year or every two years) and as such they are given away very sparingly.</p><h4>Why not provide team members with increased responsibilities and growth opportunities more often?</h4><p>If your team is craving for growth, give them those opportunities. Don’t wait for promotion season to groom a few chosen ones, who are probably not the ones in greater need of learning opportunities. Push your team out of their comfort zone into roles of higher responsibility. Do it to <em>all of them</em>, so they can learn from their successes and failures together.</p><blockquote>Highly empowered employees showed engagement levels in the 79th percentile, whereas disempowered workers rated in the 24th percentile for engagement. [<a href="https://www.forbes.com/sites/joefolkman/2017/03/02/the-6-key-secrets-to-increasing-empowerment-in-your-team">Forbes</a>]</blockquote><h4>Project Leads</h4><p>Given the nature of our ambitious roadmap and the challenges ahead, it seemed natural to give everyone on the team a little more responsibility. Responsibility gives people a higher sense of commitment and motivation. With this in mind, we introduced the concept of Project Lead.</p><p>For each larger feature or User Story, an engineer was chosen to lead its design and implementation, and to coordinate its execution with other stakeholders (engineers, product managers, designers, marketing, etc). The size and complexity of each project can vary, but at a minimum they require a one-week effort involving more than one engineer. We believe that if it takes less than one week, then it’s probably too simple to take advantage of a Project Lead.</p><blockquote>Businesses with a strong learning culture enjoy employee engagement and retention rates around 30–50% higher than those that don’t. [<a href="https://www.roberthalf.co.uk/press/employers-fear-45m-workers-could-be-move-year"><em>Robert Half</em></a><em>]</em></blockquote><p>In addition to the design and implementation, each Project Lead also had to make sure their project was on the right track to be integrated into production, which lead us to come up with the acronym <strong>SFM</strong>:</p><p>Status updates: The Project Lead became the central point of communication for their designated project, which, from the EM and PM standpoint, made determining the current status of a project straightforward. This shifts the burden of piecing together the progress or delays of multiple tasks from each of their several contributors from the EM and PM to the Project Lead, who now also has the responsibility of understanding the entire scope of the project and to be well-informed at every step along the way.</p><p>Feature flags: The Project Lead makes sure every major feature is available through feature flags, so we can control how to roll out the feature to our customers, as well as how to roll it back if needed.</p><p>Metrics: To track the impact of each feature, Project Leads must add support for metrics (e.g., <em>statsd</em>, controller or user events, etc.). This will allow us, in future quarters, to understand which feature we should further work on, eliminate, or leave as-is.</p><p>We also provide the Project Leads with the necessary support and resources. At any point, they have the autonomy to schedule short 30-min meetings with anyone on the team to discuss any parts of the project. Preliminary brainstorming sessions with the EM and Team Leads are highly encouraged, as are meetings with any experts outside the team.</p><p>Furthermore, to ensure high quality standards, each Project Lead is granted a 30-min testing session with the entire team. This provides the Project Lead with very early feedback on large portions of the functionality and thus allows them to rollout a much more robust version for the internal release. Having a more stable first version allows CS to uncover harder-to-find bugs and avoids some of the frustration that comes from using a prematurely released feature.</p><blockquote>In the end, it was the experience of leading a project, any project, of being given a leadership opportunity and the responsibility that comes with it, that made this a successful growth experience.</blockquote><h4>Elect, Don’t Select</h4><p>Picking the right Project Lead for a given project is no trivial task. Everyone has their own interests, which could lead to some pretty strong opinions about who should lead which project. We aim to be as democratic as possible, but we also know that we can’t accommodate everyone’s first choice.</p><p>At first, I asked each team member to privately share with me their top choices, so I could try to match Projects with Project Leads. I would then ask them (not tell them) if they would like and agree to lead a particular project. If the project they were elected to lead was their first choice, it was a plus, not a requirement.</p><p>Having a wide variety of projects to choose from (8–10 projects for 6 Project Leads) certainly helps, but ultimately, I think what made this a success was that everyone on the team, from Junior to Senior, was a Project Lead of at least one project. In the end, it was the experience of leading a project, any project, of being given a leadership opportunity and the responsibility that comes with it, that made this a successful growth experience.</p><blockquote>Failures can be partial successes, but only if we learn from them.</blockquote><h4>Project Retrospectives</h4><p>At Entelo, we foster an engineering culture that encourages experimentation with new approaches to achieve ambitious goals (even if they end up failing). This safe environment, together with our exciting roadmap and increased responsibilities, makes the team feel both supported and eager to see what they can accomplish.</p><p>Naturally, success is the ultimate goal, but saying that a project succeeded or failed may be too simplistic. Failures can be partial successes, but only if we learn from them. And even successful projects can hide partial failures, which, if not reviewed and understood, may reoccur in future projects.</p><blockquote>“By asking why five times and answering it each time, we can get the real cause of the problem.”<br>–Taiichi Ohno (Architect of the Toyota Production System)</blockquote><p>A popular tool from the Agile methodology used to review past actions and learn from them are Retrospectives. A week after the project is released, the Project Lead schedules a team meeting to review and discuss the project’s implementation and results. These meetings are also lead by the Project Lead, who walks through the project’s timeline, important decisions, and outcomes. After all the facts are laid out, the team discusses what went well (and should be repeated in future projects) and what didn’t go so well and could have perhaps been prevented. Sometimes, when we need to drill into the root cause, we might even employ the <a href="https://en.wikipedia.org/wiki/5_Whys"><em>Five Whys</em></a> strategy. Information and transparency is key in leading a good retro.</p><p>It is crucial to keep in mind that Project Retros are not performance review hearings. They can provide valuable feedback and constitute one of the best learning tools, but only if everyone is candid, respectful and checks their egos at the door.</p><h3>A Quarter Full of Promising Results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zZx4w0TzAHsUWhwC" /><figcaption>Photo by <a href="https://unsplash.com/@japhethmast?utm_source=medium&amp;utm_medium=referral">Japheth Mast</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Project Leads have an increased responsibility to lead the design and implementation of the solution, but they are also empowered with a great deal of autonomy. They decompose the project into smaller tasks, choose who should collaborate on it and even assign those tasks. They are the key figures who know the status of the project at all times. When the Project Leads take on a project, they are owning it and committing themselves to its success.</p><p>There’s also an implicit trust placed in them, which further drives their engagement. They don’t want to let anyone down, especially themselves. The project they lead becomes part of them and this is a very powerful motivator.</p><blockquote>Let them fail. But be there by their side when that happens to help them get back up.</blockquote><h4>Growth Opportunity</h4><p>Being a Project Lead can be more or less challenging, depending on the complexity of the project and the engineer’s experience. In some cases, it could really bump the engineer out of their comfort zone. For instance, junior engineers, accustomed to taking on smaller tasks during Sprint Planning, might find it hard to scope the project and decompose it into smaller tasks. Even a more seasoned engineer might struggle with other parts of the role, like cross-team collaboration or communication. And even if you’ve managed a Sprint or a project before, the more times you do it, the better you’ll get at it.</p><blockquote>42% of employees say learning and development is the most important benefit when deciding where to work. [<a href="https://about.udemy.com/ideas-and-opinions/2018-millennials-at-work-research-report/">Udemy</a>]</blockquote><p>It’s important to note that having an accepting and supportive culture is paramount. Depending on the Project Lead’s experience, their new role may be overwhelming, so it’s important to provide them with the necessary support and understanding. This includes checking-in on them periodically and allowing them to ask for help at any point. And, as long as it doesn’t negatively impact the company or their career, let them fail. But be there by their side when that happens to help them get back up.</p><h4>Recognition</h4><p>A project carries the weight of a larger, independent feature. With the responsibility of being the one in charge of its execution, the Project Lead also feels a sense of pride and gratification in delivering it. At Entelo, every contribution to the product is recognized in many ways, from an email from the Product Team to all employees announcing the newly released features, to a mention by the CEO in the company-wide Week-In-Review presentations on Fridays. The Project Lead is always at the head of the list of contributors that made that project come to life.</p><p>At the end of Q4, we couldn’t be happier with the results. We successfully completed our roadmap, including seven Projects (lead by their respective Project Leads). It might be a bit unfair to compare the productivity of different quarters as many different factors are at play and roadmaps can vary greatly, but in the end, the team considered this one of the most productive quarters to date.</p><p>Project Leads have been highly motivated, engaged and committed. They have learned how to scope and plan the execution of a Project, as well as how and when to collaborate with other stakeholders to get results. From a management point-of-view, delegating some of these responsibilities to the Project Leads was a very efficient reallocation of resources and alleviated our work. From a Project Lead perspective, it was a fulfilling experience in which they felt more involved and learned more than in previous quarters.</p><p>Have you used a similar strategy with your team? What other ways to motivate and grow your teams have you used? Let us know in the comments below.</p><p>Also, if you’d like to know more about Entelo or our Engineering Team, please visit <a href="https://sourcecode.entelo.com/">SourceCode</a>, our blog about engineering in the recruiting industry.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f167472b580d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/entelo/why-you-should-make-everyone-a-project-lead-f167472b580d">Why You Should Make Everyone a Project Lead</a> was originally published in <a href="https://medium.com/entelo">Entelo Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ROC Curves]]></title>
            <link>https://medium.com/@joao_antunes_/roc-curves-d3c0a9e5fb24?source=rss-68fe095ef711------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3c0a9e5fb24</guid>
            <category><![CDATA[statistics]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[João Antunes]]></dc:creator>
            <pubDate>Tue, 10 Aug 2010 00:00:00 GMT</pubDate>
            <atom:updated>2019-02-15T07:24:28.097Z</atom:updated>
            <content:encoded><![CDATA[<p>Receiver Operating Characteristic (ROC) curve analysis is a statistical test that evaluates different cut-off points and their impact on the results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*GwYofhQR9adEgfDj.gif" /></figure><p>Imagine a population of positive and negative elements, such as for example a diagnostic of a disease, the identification of malicious traffic passing through an IDS, or messages accepted or refused by a language automaton. The <em>Reference</em> circle represents all positive elements and the <em>Inferred</em> represents the system we are testing. The closer the overlap between the inferred and the reference circles, the better the system is in recognizing positive and negative elements.</p><p>The amount of overlap or disjointness gives a measure of how good the system was trained. To test the impact of a particular training parameter, ROC curves can be used to plot the true positive rate (recall) in function of the false positive rate for different training parameter values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*tHS5bmcqOOHp1ft_.jpg" /></figure><p><em>Originally published at </em><a href="https://jasantunes.blogspot.com/2010/08/roc-curves.html"><em>jasantunes.blogspot.com</em></a><em> on August 10, 2010.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3c0a9e5fb24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recall and Precision]]></title>
            <link>https://medium.com/@joao_antunes_/recall-and-precision-2ffe78e8441d?source=rss-68fe095ef711------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ffe78e8441d</guid>
            <category><![CDATA[statistics]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[João Antunes]]></dc:creator>
            <pubDate>Mon, 09 Aug 2010 00:00:00 GMT</pubDate>
            <atom:updated>2019-02-15T07:21:52.473Z</atom:updated>
            <content:encoded><![CDATA[<ul><li><strong>Recall</strong>: measures the coverage of the inferred automaton, i.e., how much of the protocol specification has been captured by the FSM. Recall is calculated as the probability that a randomly selected set of <em>valid</em> protocol messages (or protocol sessions) is accepted by the inferred automaton.<br> Recall = #accepted messages (or sessions) / #messages (or sessions)</li><li><strong>Precision</strong>: determines the soundness of the automaton, i.e., if the inferred automaton is not overly-generalized. We calculate precision as the probability that a randomly selected (<em>valid</em> or <em>invalid</em>) set of protocol messages (or sessions) accepted by the inferred FSM is in fact <em>valid</em>.<br> Precision = #accepted valid messages (or sessions) / #accepted messages (or sessions)</li></ul><p>Typically, it is very simple to have a recall of 1 (with a low precision) by having a very generic automata, which accepts all messages (or sessions). Therefore, the objective is to have a both a high recall and precision [Manning08].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*0NWFwMtwTZIkMMhQ.gif" /></figure><p>To calculate the recall and precision of an inferred (trained) system we use the following:</p><ul><li><strong>Recall</strong> = TP / (TP+FN)</li><li><strong>Precision</strong> = TP / (TP+FP)</li></ul><p>[Manning08] C. Manning, P. Raghavan, and H. Schütze. An introduction to information retrieval. Cambridge University Press, 2008.</p><p><em>Originally published at </em><a href="http://jasantunes.blogspot.com/2010/08/recall-and-precision.html"><em>jasantunes.blogspot.com</em></a><em> on August 9, 2010.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ffe78e8441d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>