<?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 Nicolas Dupont on Medium]]></title>
        <description><![CDATA[Stories by Nicolas Dupont on Medium]]></description>
        <link>https://medium.com/@nidup?source=rss-da6e015fab0c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Pz9oDxmPOv9OYQpBSQpyIg.jpeg</url>
            <title>Stories by Nicolas Dupont on Medium</title>
            <link>https://medium.com/@nidup?source=rss-da6e015fab0c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:44:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nidup/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[How to Become a Lead Developer?]]></title>
            <link>https://medium.com/@nidup/how-to-become-a-lead-developer-c6cde2a4c36a?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6cde2a4c36a</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[senior-developer]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <category><![CDATA[lead-developers]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Sat, 15 Aug 2020 12:02:38 GMT</pubDate>
            <atom:updated>2020-08-15T12:02:38.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fs0US-Ylk0hZyMTnuc3rbQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@anniespratt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Annie Spratt</a></figcaption></figure><p>Starting in 2009, I’ve worked as a software engineer, lead developer, engineering manager, vice-president of engineering, and chief product officer. During this journey, I had the opportunity to support talented engineers in different career transitions, from individual contributor to lead developer, from lead developer to engineering manager. I found many shared struggles while mentoring them; that’s why I’m writing a series on how to get prepared to move into these positions.</p><h3>What is a Lead Developer?</h3><p>The Lead Developer is the technical leader of a team of developers. She’s in charge of the success of a project. She animates the delivery to build the right things, the right way, and on time.</p><p>She is responsible for advocating on best practices, communicating on the progress, mentoring other developers, providing technical guidance to the team, and deciding on technical trade-offs.</p><p>Depending on the organization, we can refer to a lead developer as a lead engineer, a team lead, a technical project manager, or a tech lead.</p><h3>Career Path</h3><p>In an <a href="https://nidup.io/garden/engineering-career-ladders">engineering career ladder</a>, the lead developer position often sits between the individual contributor track and the people manager track.</p><p>It’s not an engineering manager position as engineering management includes people management responsibilities. However, moving into a lead developer position is a solid first step in engineering management.</p><p>Moving into a lead developer role is also a significant progression in the technical leadership track. It’s an excellent way to get prepared to become a software architect, a staff engineer, or a principal engineer.</p><p>This role opens a lot of opportunities.</p><h3>Become a Lead Developer?</h3><p>If you want to become a lead developer, a critical aspect to consider is the shift of responsibilities.</p><p>A lead dev is responsible for the result of a team on a project. It’s not anymore about your own technical excellence, or what you individually build or contribute to building. It’s now about the success of the development team. Let’s discuss the main areas to work on to be prepared to move to a lead developer position.</p><h3>Technical guidance</h3><p>You can usually pretend to become a lead developer after a few years of experience as a developer or software engineer. These first years are critical to consolidate your technical skills and learn to be autonomous in your developments.</p><p>You start to have a solid sense of how to build things to answer the business needs, and you did it with success on several projects.</p><p>A useful exercise is to discover how to articulate larger pieces of software. You need to understand the technical decisions and the trade-offs regarding a given architecture. You can muscle your tech decision-making by reviewing existing projects and chatting with current tech leaders on how and why we build this way.</p><h3>Be a role model</h3><p>As for any leadership position, it’s critical to embody the excellence and the behavior that your organization expects for developers.</p><p>If you lead a team of developers, you become their representative, and they deserve to be well represented. To become a lead developer, you need to become first a great developer.</p><h3>Work organization</h3><p>A critical success factor is how the team collaborates.</p><p>Get interested in project management practices. How to prepare the work? How to slice the tasks? How to measure and communicate on the progress?</p><p>Get interested in each other skills. Who is comfortable doing what? What your teammates like or not like? What do they want to learn?</p><p>Any teamwork requires some upfront preparation and a proper animation to collaborate efficiently. Ask if you can contribute in a way or another in these aspects. Your tech lead or manager should be happy to delegate you some parts of it, and it will be an enjoyable exercise to train your leadership muscle.</p><h3>Be a mentor</h3><p>A lead developer contributes actively in helping her teammates to learn, to become better software engineers.</p><p>There are plenty of opportunities to strengthen your mentoring skills. You can improve by explaining an intricate part of the tech stack. You can also help to onboard a new developer on the team. You can mentor a junior developer or an intern.</p><p>The most important aspect is to have the proper attitude: be always willing to help. You can evaluate your progress by how often your teammates are coming to you to ask for your help or work with you.</p><h3>Communication</h3><p>The foundation of efficient teamwork is efficient communication. As a team, we need a shared understanding: why we do things, what’s our mission, what our goals are.</p><p>Frictions, duplicate work, or a waste of effort often come from a few misunderstandings between team members. To mitigate this inherent challenge, you’ll need to work on your communication skills.</p><p>You can improve by training yourself to be crystal clear when communicating. Listen carefully, ask genuine questions to ensure you understand correctly, re-phrase with your own words. Adapt your message to the audience’s knowledge and domain of expertise.</p><p>Contribute to helping the team communicate well, document the significant changes, and amplify the essential pieces of information.</p><h3>Earn Trust</h3><p>Last but not least, to move to a lead developer position, you will need to earn your teammates’ and manager’ trust.</p><p>We build trust by our actions and our behavior, by being consistent, by being reliable, by helping others.</p><p>A lot of small and concrete actions will contribute to building the strong grounds, the foundations of the team’s trust. And if you want to become a lead developer, you can start making these actions right now.</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/how-to-become-a-lead-developer"><em>How to Become a Lead Developer</em></a><em> story on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6cde2a4c36a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dig Into Problems With the 5 Whys]]></title>
            <link>https://medium.com/@nidup/dig-into-problems-with-the-5-whys-98cc734020ed?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/98cc734020ed</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[lean]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Thu, 30 Apr 2020 12:15:57 GMT</pubDate>
            <atom:updated>2020-08-15T10:51:49.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YIdiKq4-A0ttsk5xfImfOA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@maripotter?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mari Potter</a></figcaption></figure><p>We need to ship “you name it”; a pretty common request and situation when working as a product manager or software engineer.</p><p>It’s a natural tendency. We tend to talk first and more about solutions rather than discussing the underlying problem.</p><p><strong>A simple practice to re-frame the discussion is to ask Why.</strong></p><p>Ask it genuinely to grasp what problem we’re discussing. To understand what we’re trying to solve.</p><p>In the early 20th century, Sakichi Toyoda, an inventor working for Toyota, developed a root cause analysis concept. <strong>Known as Five Whys, the aim is to detect the root cause of a defect</strong>, by iteratively asking Why. In most of the cases, five iterations are enough to reach the root cause.</p><p>Since then, the Lean methodologies evangelized the use of this practice. Especially for problem-solving and for improving processes.</p><p>I find it very efficient when applied to product management.</p><p>First, to avoid to stick with our former solution. We tend to fall in love with a solution quickly. It allows us to step back and to discuss the problem.</p><p>Then, it prevents the second trap of staying at the surface of a problem.</p><p>We need to dig into the issue, persevering, checking data points, iterating to discover the root cause. Depending on the problem, it may be tricky to separate the causes and the symptoms.</p><p>Once we have a good grasp of the problem, we can look for patterns. Does this problem is an industry problem? Does it concern several customers? What is the opportunity? What are the potential outcomes of solving it?</p><p>Finally, we can go back thinking about potential solutions and figuring out the different possibilities; and their pros and cons.</p><p>In our organizations, we can mix the activities of studying a problem and defining a solution. When doing so, we reinforce the attachment to our former solution and don’t give to the problem the time it deserves.</p><p><strong>We should fall in love with the problem, not with the solution.</strong></p><p>Some practices or processes can support the split of these activities. For instance, write a one-pager talking only about the problem. And then, discussing the potential solutions into a dedicated one-pager.</p><p>I’m talking here about pretty big problems. The fine-tuning of an existing solution does not deserve so much effort. We get new learning or data points from the usage of this solution. In this case, small improvements are more a matter of increasing the adoption by enhancing the user experience, or by covering a new scenario.</p><p><strong>A product organization will never be able to answer all the problems its users are facing. We work into a constrained system; we need to invest our efforts in solving the right problem with a relevant solution.</strong></p><p>Our customers, our teams, our businesses (and our products) deserve it.</p><p>It’s now time to go back digging into problems. ⛏️</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/dig-into-problems-with-five-whys"><em>Dig Into Problems With the 5 Whys</em></a><em> story on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98cc734020ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nurture Your Product Backlog]]></title>
            <link>https://medium.com/@nidup/nurture-your-product-backlog-cb4b6f800d41?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb4b6f800d41</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-backlog]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Mon, 27 Apr 2020 15:21:01 GMT</pubDate>
            <atom:updated>2020-08-15T10:52:16.070Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WAlIryZDbzHvI58NFJbiow.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@b3njamin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Benjamin Combs</a></figcaption></figure><p>Last week, we were discussing some good practices around product backlogs with product folks.</p><p><strong>I tend to see a product backlog as a small garden. As a product manager, you need to take care of your garden. To nurture it regularly, to remove weeds, to grow promising seeds into nourishing plants.</strong></p><p>Here are a few thoughts and practices on backlog gardening.</p><p>The product backlog must be clear. It reveals an intention, what you want to achieve to solve a user pain point. A teammate should understand it in one blink.</p><p>Have you ever heard about “code smells”? The negative feeling you have, as a software engineer when you look at a codebase or piece of code.</p><p>Your gut feeling tells you something is wrong. But you need to dig a bit to understand what makes you uncomfortable. The same applies to a product backlog.</p><p>Huge backlog, hundreds of items, a patchwork of intentions, not well organized, no clear prioritization.</p><p>On the backlog size, more than a few dozen of user stories create a too big cognitive load. When working on one large product or several products, create several backlogs will help.</p><p>Camille F., product director in our team, has an excellent practice of naming a backlog with the expected goal. For instance, “Boost the adoption of YouNameIt”.</p><p>Using an explicit name creates a strong shared understanding with the team, reminding why we’re doing things.</p><p>Creating a dedicated backlog, we reduce the temptation to pile up hundreds of unrelated items. Then, the systematic use of Epics or Tags helps to describe smaller steps to reach the goal.</p><p>These Epics can relate to the scenarios of a user story mapping. This story map is a powerful and visual way to refine the appropriate scope to deliver business value to your users.</p><p>The backlog needs to be consistent. Whatever we’re using a format or another for user stories, it should be the same everywhere.</p><p>My favorite practice for the preparation and slicing of user stories is through regular review and collaboration with the tech team. Sitting on a weekly or bi-weekly basis and refining the stories together.</p><p>There are plenty of ways to slice some value. What matters here is to do it with one (or several) tech mates who will help to slice it conveniently for the team. It also helps to avoid under or over slicing. And it reinforces a common understanding.</p><p>In my definition, a strong slicing represents a few days of work for a story for the team (at max). Healthy slicing practice supports continuous integration, making everything easier.</p><p>We usually don’t need to have hundreds of detailed user stories in advance. But the next milestone scope must be clear and accurate enough. It allows the team to anticipate any potential difficulties. Or to figure out the amount of work to achieve.</p><p>Having at least the few upcoming weeks of prepared backlog content is critical for a product manager. Without this, you fall into reactive mode. It becomes challenging to have enough good time with the customers. You’re not available for other teams. You have not enough time to think about the next problems to tackle.</p><p>Last but not least, the prioritization must be crystal clear; it may evolve with the learning and user feedback. But, it should draw a clear path.</p><p>A <strong>product backlog is a communication and collaboration tool</strong>. It’s a living document. It requires <strong>regular grooming and cleans up</strong>, with a lot of discipline and attention.</p><p>My dear backlog gardeners, I wish you some pleasant gardening and harvesting sessions with your teams. 👩‍🌾</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/nurture-your-product-backlog"><em>Nurture Your Product Backlog</em></a><em> story on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb4b6f800d41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Benevolent RTFM]]></title>
            <link>https://medium.com/@nidup/benevolent-rtfm-e8a13e9cb388?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8a13e9cb388</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Sun, 26 Apr 2020 14:12:26 GMT</pubDate>
            <atom:updated>2020-08-15T10:52:38.858Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4aytm1qRTm5Eh7413ubRDw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@anete_lusina?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Anete Lūsiņa</a></figcaption></figure><p>The bigger the team, the harder the communication is.</p><p>Why?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*T0RQfWZHmI8jAbm59ONOJA.png" /><figcaption>Source <a href="https://getlighthouse.com/blog/developing-leaders-team-grows-big/">LightHouse</a></figcaption></figure><p>I was recently discussing with one of my mentors about the <strong>importance of some critical reference documentation</strong>. And also about the necessity of repetition in communication.</p><p>And an idea came while I was consolidating my meeting notes later on.</p><p>I slept on it, and it came back again, so I’m writing a short (or not) post on it.</p><p><strong>RTFM or Read The F*cking Manual</strong>. A pretty old, and standard answer you can get when asking for a question already documented. It initially comes from a LINPACK user’s manual in 1979.</p><p>Informing someone that the answer to his question exists in dedicated documentation is ok.</p><p>But the form is the worst we can find. It can make someone feeling guilty for asking something. It should never happen; any questions are right to ask; each answer brings value.</p><p>What about transforming this old RTFM thing by adding a critical missing aspect of it: be kind, be benevolent.</p><p>The <strong>Benevolent RTFM</strong> enters into the game with the following pseudo-framework.</p><p><strong>1/ Refine the need.</strong></p><p>Questions about What?</p><ul><li>What are the recurring questions? How often are they asked?</li><li>Who asks? Individuals, roles, teams. What are their needs?</li><li>Where are they asked? What’s the medium? Meetings, email, slack channel, calls, etc.</li><li>When are they asked?</li><li>Who answers, who can answer, who should answer?</li></ul><p>Any reference document?</p><ul><li>Does it exist? Is it known and easy to find?</li><li>What’s it’s goal or intention?</li><li>For which public?</li><li>Is it up to date? With an understandable format and content?</li><li>Who maintains it? How often?</li></ul><p>Answering these questions, we can define if there is a need to create or improve or better communicate on a piece of documentation. We specify its goal, for which public, for what expectations.</p><p><strong>2/ Make the documentation enjoyable</strong></p><p>It’s now time to make sure that the ownership of the documentation is clear, that the content answers the goal, that the format is pleasant, its title is self-explicit, that the doc is up to date, and available for the given public.</p><p><strong>3/ Make the documentation known</strong></p><p>We’re entering into the best part.</p><p>You can start answering questions with a kind message and a link to the specific section of the documentation.</p><p>Another critical point is to start to reference this documentation into as many other docs or decks you present and share (when it makes sense). Like if you were following a search engine optimization strategy. Make sure that this link will always be valid.</p><p><strong>4/ Measure the progress &amp; adapt the content</strong></p><p>A lot of documentation tools include some read statistics, to know who access the doc, and when. The number of accesses of the targetted public over time is a good measure of progress. The amount of positive feedback is an even better measure.</p><p>Use the feedback to refine the needs and update the content or format accordingly.</p><p>The real magic happens when the documentation starts to be openly shared, as an organization reflex, and this, totally out of your control or actions.</p><p>You created self-service documentation.</p><p><strong>Last words</strong></p><p>While growing, as a company or as a team, we need to shift our communication from oral to written. Knowledge sharing practices have to change; small chats at the coffee machine are not good enough anymore.</p><p>Building solid documentation practices and habits become a critical asset.</p><p>This Benevolent RTFM naming made me laugh. So much contradiction into these expressions.</p><p>The main point is we should <strong>share what we know, openly, kindly, and generously</strong>. And at a particular team scale, creating a referential is the most efficient way to reach this goal.</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/benevolent-rtfm"><em>Benevolent RTFM</em></a><em> story on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8a13e9cb388" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Error Messages Deserve Some Love]]></title>
            <link>https://medium.com/@nidup/your-error-messages-deserve-some-love-f70179ba9557?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f70179ba9557</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[error-message]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Mon, 20 Apr 2020 14:01:01 GMT</pubDate>
            <atom:updated>2020-08-15T10:51:15.763Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oVQfUxNbnGOZ_0j9Mjlbw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@dietmarbecker">Dietmar Becker</a></figcaption></figure><p>I recently attended a compelling presentation. 😍</p><p>In our distributed company, English is a second or third language for most of the teammates. We have a dedicated English teacher. Camille runs training and workshops to help us to improve.</p><p>Camille recently worked on our products’ error messages with our product management team.</p><p>The first goal was to ensure the correctness of these messages.</p><p>She pushed the exercise at a far more advanced level.</p><p><strong>Error messages</strong></p><p>When running into an error message, the experience is, most of the time, frustrating.</p><p>Something unexpected happened, and it breaks your productivity flow. You now have to understand why this piece of software does not work the way it’s supposed to. You have to figure out what to do to be able to move on. And you have more interesting to do.</p><p><strong>An error message has to be crystal clear</strong></p><p>Each message has to guide the user and must be self-explanatory, concise, and accurate.</p><p>When we write error messages, the temptation is high to detail as much as possible. What happened, what are the business rules. We should focus on helping the user to work around the issue and to move on.</p><p>Error messages don’t have to be boring or impersonal. An error message is a way to engage with your users. It can be user friendly, using “you” and “we” pronouns creates a more human feeling.</p><p>For instance:</p><blockquote>“Cannot remove this attribute used as a variant axis in a family variant.”</blockquote><blockquote>“You cannot remove this attribute because it is used as a variant axis in a family variant.”</blockquote><p>Our messages have to be consistent across your whole application. We can adapt their content depending on the user persona we’re talking too. But keeping a consistent tone of voice is essential.</p><p>Another good practice is to write them positively and to avoid negative sentences.</p><p>For instance:</p><blockquote>“This value should not be blank.”</blockquote><blockquote>“This value is required.”</blockquote><p>Conciliate these pieces of advice can be challenging, what to do when in doubt?</p><blockquote>“The Platinium rule, if you’re not sure, the rule overriding all the others, is your message has to be crystal clear.” (Camille B.)</blockquote><p><strong>Error messages are a critical part of the User eXperience</strong></p><p>Looking at most of the software I use, error messages appear to me as a second class citizen of the UX.</p><p>We can fix this in our industry. We can improve. We can craft great error messages. We can make them more engaging and as enjoyable as success messages.</p><p><strong>Last words</strong></p><p>Dear Camille, thank you! For pointing out this problem, for evangelizing and training our teams. Write great error messages is a step forward to deliver a more engaging experience to our users. 🦄</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/write-engaging-error-messages"><em>Your Error Messages Deserve Some Love</em></a><em> story on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f70179ba9557" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Small Automation, Big Impact]]></title>
            <link>https://medium.com/@nidup/small-automation-big-impact-ad3ede72adb7?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad3ede72adb7</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[community-engineering]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[customer-support]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Sun, 19 Apr 2020 09:47:35 GMT</pubDate>
            <atom:updated>2020-08-15T10:53:19.313Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJJKSUsxrkMBdWyQwTaUeQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@drscythe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dominik Scythe</a></figcaption></figure><p>Every single day, we spend quite a part of our work-time doing small, repetitive, and tedious tasks.</p><p>It has never been so easy to automate some parts of our work.</p><p>Some companies made their core business of making it easier to automate all the things. Looking at you, Zapier and IFTTT!</p><p><strong>Our time is our scarcest resource.</strong></p><p>Avoiding spending time on low added value tasks also means being able to dedicate more time to more important business.</p><p>Some projects that have a more significant impact on our business, on our products, on our teams.</p><p>This week, I discovered a couple of automation initiatives within our team.</p><p><strong>Community Engineering</strong></p><p>We do build an open-source product. For intellectual property reasons, we need to ask each contributor to sign a Contributor Licence Agreement (CLA). And for each code contribution, coming as a GitHub pull request, we need to make sure the author has signed the CLA.</p><p>A mate built the following automation as a GitHub status check.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*VNMzA1kdekqzIhQl-Cli_w.png" /></figure><p>He also added a command to be able to check directly from our slack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*z19pvH5Jj_y-8lw69H-KRA.png" /></figure><p>This automation creates a better experience for the contributor; he knows what he has to do. It allows the team to be more efficient, and it avoids mistakes, as it prevents any merge without a signed CLA.</p><p><strong>Support &amp; Maintenance</strong></p><p>Our support and maintenance teams observed that they spent quite some time assigning tickets to each other. Then accessing the progress, checking if they need to do something for the others.</p><p>For instance, support assigns to the maintenance once they qualified a product bug. The maintenance team re-assigns to the support team once they fixed and deployed on a test environment.</p><p>They reviewed the workflow of their respective ticket boards. And added some cross automation based on the status of these tickets.</p><p>This change comes with a re-configuration of some dashboards. It helps each mate to exactly knows what’s on his plate. And ensure the info is coming to the mate, no need to run after it through various boards.</p><p>It improves collaboration between teams, making the work easier for each mate. It decreases the lead time of a support ticket by reducing the time between actions. It results in faster answers to the problems of our users.</p><p><strong>Last words</strong></p><p>We can improve our daily routine. Reflect on our repetitive and tedious tasks. Automate these tasks to invest in more impacting projects. Automate to deliver a better service and experience to our customers.</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/small-automations-big-impact"><em>Small Automation, Big Impact</em></a><em> story on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad3ede72adb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Key Learnings From Game Jams]]></title>
            <link>https://medium.com/@nidup/8-key-learnings-from-game-jams-af62dd9f845e?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/af62dd9f845e</guid>
            <category><![CDATA[game-jams]]></category>
            <category><![CDATA[ludum-dare]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Thu, 16 Apr 2020 10:43:56 GMT</pubDate>
            <atom:updated>2020-08-15T10:54:43.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HfuKgls-H_EwmXoBg5XjyQ.jpeg" /><figcaption>Ludum Dare 38 (one of our first session as a crew)</figcaption></figure><p>The next Ludum Dare session is coming.</p><p>Ludum Dare, also known as LDJam, or LD, is one of the largest worldwide game jam events.</p><p>Within a few days, thousands of developers will release thousands of games. They can join in the jam mode, working as a team, with 72h to build a game, and being able to re-use some assets. Or they can choose to participate in compo mode, aka, making everything alone from scratch in 48h.</p><p>The announcement of the theme launches the event, and the clock starts, you have to submit your game before the clock stops.</p><p>I love game jams; it’s a demanding, messy, but always vibrant experience. I do prefer the jam mode. We regularly participate will a small crew, a few jam veterans, welcoming at least a new member at each session.</p><p>What can we learn from this kind of hackathon?</p><p>What can inspire us when getting back to our day to day work?</p><p><strong>Preparation and communication</strong></p><p>When starting, we dedicate the first morning of the jam to brain-storm on ideas to fit the theme. We draw on a whiteboard; we don’t touch a keyboard.</p><p>We’re looking for an idea, a concept, a game design we’re comfortable with as a team, that will keep us excited for the upcoming days.</p><p>Each teammate says what he’d like to do, game design, programming, graphics, sounds, etc. We can then pick a concept fitting what each of us we’ll enjoy doing during the upcoming days. We also write down our availabilities; someone can join for half a day, one day, or three days.</p><p>Once we picked our concept, we dedicate the rest of the first day to get a working prototype, validating our idea. And during the jam days, we’ll over-communicate on the progress. Doing a break together every few hours, to assess our progress, looking if someone needs help on a task.</p><p><strong>Energy management</strong></p><p>The exercise is very demanding. The first-time jammer often falls into the trap of coding 24h per day.</p><p>This desperate attempt to use each available minute to deliver value quickly burns you. The first day is ok. Then you struggle with even the most simple stuff.</p><p>Balancing your energy and doing proper breaks is critical. Sleep for real, make time to eat correctly. And for our summer sessions, the game jam barbecue became a tradition for our crew.</p><p><strong>Hard-core prioritization</strong></p><p>You have only a few days. Prioritization, hard-core prioritization is a must. But keep in mind that you need to deliver a great experience to your users. Storytelling. Game design. Mechanisms. Feedback.</p><p>You can quickly get trapped into something looking simple to do, but that will take far more time than expected, too much time. Not part of your core design?</p><p>Stop it, trash it. It’s an excellent scoping exercise.</p><p><strong>Be laser-focus</strong></p><p>Given the time frame, you’ll not be excellent at each aspect that makes a great game. Our very own trick is to pick one key point, one core aspect, and be laser-focus on it. We can choose the atmosphere, the narrative, the graphics, etc.</p><p>We often pick one aspect where the first-time jammer in our crew is comfortable with or can contribute. For instance, we made a game based on the audio atmosphere when we made a jam with a sound engineer. Or a game based on the narrative with a new jammer who is an actor.</p><p>By locking this constraint, we make sure everyone in the team will push on this key differentiator. You can’t be the best in all categories, but you can deliver an intense experience by picking your fights and being excellent on your differentiator.</p><p><strong>Collaboration &amp; team-work</strong></p><p>It can be very tempting to parallelize all the tasks, and for each mate to build a different piece. We noticed it’s far more efficient to do some pair programming, at least, on foundations. Or to have one mate being always available to join and give a hand to any other mates. It becomes easier to parallelize the work once the foundations have been built together, with a shared understanding.</p><p><strong>Polishing</strong></p><p>What makes a great experience is the level of polish. It seems counter-intuitive in a game jam, but we dedicate 30% of our time to polish the existing mechanisms and features, usually the third day of the jam.</p><p>Adding small user feedback, fine-tuning the sounds effects, the fonts, the graphics effects. Making sure the user onboarding is right, the difficulty well-balanced, that the game goals are clear.</p><p><strong>Technical debt</strong></p><p>You ever heard or suffered from technical debt? A game jam is a fertile context to experiment on tech debt. Your jam team will quickly turn into an efficient tech debt factory. While rushing to add capabilities, by cutting every single possible corner, you’ll soon suffer from your messy code.</p><p>And this, only after one or two days! Which is fine, you’ll never touch again this codebase (hopefully). The aim is to ship a game experience, a polished prototyped, not to build a game you could sell.</p><p><strong>Accidental successes</strong></p><p>Sometimes magic happens.</p><p>During a jam, we were building a platformer. Our hero wears eyeglasses, and a bug with sprites integration led to having only his glasses floating in the air. We had a lot of fun with this bug. And we discovered we could make something cool with it.</p><p>We changed our platformer to include sections in the dark where you see only the glasses of the hero. It was so good that we pivoted our concept entirely to make it the central aspect of our game, and we adapted the storytelling accordingly.</p><p>As in any project, unexpected things will happen, and a problem can become an opportunity. It could have been a boring game, and it became a unique concept, a blind platformer, on which we had great feedback. (here is the <a href="https://ldjam.com/events/ludum-dare/39/lionels-weekend">game</a>)</p><p><strong>Last words</strong></p><p>I highly encourage you to try to participate in a game jam once.</p><p>It’s an exceptional experiment. It gathers all the emotions you can feel when building a product but packed within a super short time frame.</p><p>The real reward is not into what you ship at the end but in the journey of trying to do it, especially when you do it as a team.</p><p>Cheers to my jam mates! 🎮</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/game-jam-key-learnings"><em>8 Key Learnings From Game Jams</em></a><em> on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af62dd9f845e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All models are wrong, but some are useful]]></title>
            <link>https://medium.com/@nidup/all-models-are-wrong-but-some-are-useful-d0d47663e198?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0d47663e198</guid>
            <category><![CDATA[conways-law]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[tuckman]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Tue, 14 Apr 2020 06:31:42 GMT</pubDate>
            <atom:updated>2020-08-15T10:56:19.743Z</atom:updated>
            <content:encoded><![CDATA[<h3>All Models Are Wrong, but Some Are Useful</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s3MWp5WI6MyD6PEZ4whwqw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sodacheese?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jouwen Wang</a></figcaption></figure><p>I love this quote from George Box.</p><p>The first time I heard about it, I felt like I discovered a small treasure. ✨ Something that will haunt me for years, coming back again and again.</p><p>The former context was:</p><blockquote>“… all models are approximations. Essentially, all models are wrong, but some are useful. However, the approximate nature of the model must always be borne in mind….”. (<a href="https://en.wikipedia.org/wiki/All_models_are_wrong">cf source</a>)</blockquote><p>Yes, all we perceive, all the mental models we’re building around our perception are approximations. Reality is always more complicated, fuzzy, chaotic than our representation. And it’s especially true when it comes to organization and human interactions.</p><p><strong>Conway’s Law</strong></p><p>A wrong but useful model I like is <a href="https://en.wikipedia.org/wiki/Conway%27s_law">Conway’s Law</a>, stating:</p><blockquote>“Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.”</blockquote><p>I found it often relevant. We copy the communication patterns into what we build as a team. When looking at some products or software architecture, I like to imagine the setup of the team(s) who built it.</p><p>A very strong decoupling between two features with a light integration between these in terms of UX/UI and navigation. A good chance that two different teams built these.</p><p>A very strong separation between frontend &amp; backend code that looks like two different applications into the code base, communicating through web API. I’d bet the team is organized with the backend team on one side, and frontend team on the other.</p><p>As a team, we look for autonomy and ownership of the things we’re working on. We do reproduce the communication constraints or the contracts we may have with other teams or other teammates.</p><p>When I craft a new organization or form a new team, I like to use Conway’s to try to predict or to guess the outcomes. It’s also known as Inverse Conway Maneuver. It’s a way to promote the desired architecture or expected result by shaping the organization upfront.</p><p><strong>Tuckman’s stages of group development</strong></p><p>Another wrong model I like is <a href="https://en.wikipedia.org/wiki/Tuckman%27s_stages_of_group_development">Tuckman’s stages of group development</a>.</p><p>Each time a teammate leaves a team, or each time a new member joins a team, it’s not the previous team +1 or -1, it’s a brand new team.</p><p>And this new team will cross different stages: Form, Storm, Norm, Perform to learn to collaborate efficiently. Each member has to find his own place within the new group. The group has to find its own way to operate.</p><p>This model can help to get prepared for the upcoming impacts when a team onboards a new teammate. It can also be used to trigger a change in the dynamic of a group. To help a team to change or re-invent their way to collaborate.</p><p>The reality is always far more complex.</p><p>These models are wrong (by definition).</p><p>But they can be useful (or not) in your context.</p><p><em>I formerly published the </em><a href="https://nidup.io/blog/all-models-are-wrong"><em>All Models Are Wrong, but Some Are Useful</em></a><em> story on my blog. I write a couple of articles per month; about product management, software engineering, and work organization. Don’t want to miss the next one?</em><strong><em> </em></strong><a href="https://twitter.com/duponico"><em>Follow me on Twitter</em></a><em> 🐦</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0d47663e198" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kanban boards sanity check]]></title>
            <link>https://medium.com/@nidup/kanban-boards-sanity-check-481868c50040?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/481868c50040</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[visual-management]]></category>
            <category><![CDATA[experiment]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Wed, 20 Mar 2019 08:55:36 GMT</pubDate>
            <atom:updated>2019-03-20T08:55:36.640Z</atom:updated>
            <content:encoded><![CDATA[<p>In our team, we have <strong>numerous Kanban boards</strong>. Boards for product squads on ongoing projects, boards for activities like support, maintenance, quality assurance, SRE. Boards for initiatives, board for internal toolings like continuous integration system and even boards for recruitment or onboarding processes. <strong>Dozens of boards</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QsMQfNNrHOTrLiiriSt1w.jpeg" /><figcaption>Kanban Board of Raccoons Squad</figcaption></figure><p><strong>Kanban</strong> has a powerful property by nature, it <strong>makes visible the work</strong> and allows to <strong>point out bottlenecks</strong> into the represented process. 🔮</p><p>I’m currently experimenting a new practice, the “<strong>Kanban boards sanity check</strong>”. Once a week, I <strong>pick</strong> <strong>randomly a</strong> <strong>couple of Kanban boards</strong>. <strong>I look at each board a few minutes</strong>, and I write down the glitches I observe, not digging into the diagnosis, <strong>only listing symptoms</strong>.</p><p>Being a software engineer, I’m trying to get the same feeling I have when I encounter a “code smell”. This instinct or experience to see in a few seconds there is something problematic here.</p><p>A generic “code smell” in Kanban looks like a bunch of cards stacked into a column, a mate working on several cards in parallel or unclear card titles. There is also more specific “code smells” depending on the context. For instance, a product squad board with very heterogeneous topics in progress.</p><p>Then, <strong>I share my observations</strong> with the team owning the Kanban. The goal is <strong>not to come with a solution but to start a discussion and ask questions</strong>.</p><p>Each observation is the <strong>opportunity of a rich organization story</strong>. The CI system slows us down, the product manager is overloaded, we wait for code review because the expert of this area is on vacation, we depend on other team or another mate, we underestimated the complexity of this card, etc.</p><p>The <a href="https://en.wikipedia.org/wiki/5_Whys">5 Whys</a> technique is a good complement to discover the root cause(s) before to discuss improvements with the team.</p><p>Bringing an external point of view is valuable to identify symptoms that are sometimes more complex to see on your own board or workflow. It’s also a great opportunity to <strong>learn, to teach and to discuss organizational glitches</strong>.</p><p>It may be useful (or not) in your context, don’t hesitate to open comments or ping me to share your thoughts and feedback if you give it a try. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=481868c50040" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers (Book Review)]]></title>
            <link>https://medium.com/@nidup/the-hard-thing-about-hard-things-building-a-business-when-there-are-no-easy-answers-book-review-aaa2fa12b974?source=rss-da6e015fab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaa2fa12b974</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[book-review]]></category>
            <dc:creator><![CDATA[Nicolas Dupont]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 08:09:24 GMT</pubDate>
            <atom:updated>2018-11-13T08:09:24.014Z</atom:updated>
            <content:encoded><![CDATA[<p>A masterpiece by <a href="https://medium.com/u/be9da4c4955">Ben Horowitz</a>, the inside story of the founding and scaling companies or how to survive this permanent roller coaster.</p><p>This book can be read like a novel, navigating through the career story of Ben Horovitz. From his early stage being an engineer at Silicon Graphics before to found Loudcloud and transform his company into Opsware, before to sell it to Hewlett-Packard.</p><p>This whole story delivers rock-solid advice all along the way, and especially around intricated issues where you need to make critical and tough decisions.</p><p>It also exposes something less visible, what is behind his start-up success story, a succession of struggles with all the hard things he had to face as a co-founder and CEO.</p><p>Poignant. Warmly recommended to any company co-founder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/1*mhLgrLw3nQkuDrvtx2_HxQ.jpeg" /><figcaption>The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers by Ben Horowitz</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaa2fa12b974" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>