<?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 Joseph Burns on Medium]]></title>
        <description><![CDATA[Stories by Joseph Burns on Medium]]></description>
        <link>https://medium.com/@josephrobertburns?source=rss-d8aa204e4695------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-yAxeErHjXf_O7Y5TR2JtQ.png</url>
            <title>Stories by Joseph Burns on Medium</title>
            <link>https://medium.com/@josephrobertburns?source=rss-d8aa204e4695------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:09:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@josephrobertburns/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[The 4 ‘culture rules’ of Rappi’s Search and Personalization team]]></title>
            <link>https://medium.com/@josephrobertburns/the-4-culture-rules-of-rappi-s-search-and-personalization-team-7a1e139564df?source=rss-d8aa204e4695------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a1e139564df</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Joseph Burns]]></dc:creator>
            <pubDate>Mon, 07 Mar 2022 15:15:41 GMT</pubDate>
            <atom:updated>2022-03-07T17:43:20.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*tbbSBcGOSwPsS91fazHkNQ.jpeg" /></figure><p><strong>How we built one of the most successful and impactful technology teams at Rappi</strong></p><p>During my 20s, I spent my work days in big companies and in team cultures that didn’t fit for me. I was always discouraged to question my leadership. There was no clearly defined path of what cultural fit meant, but I was always dinged for it in my performance reviews. Finally, I felt no control or predictability around the projects I was going to be involved with.</p><h4>One thing always played in my head: <em>“When I’m the boss, everything is going to be completely different”.</em></h4><p>After a move that found myself working for the first Colombian unicorn tech company and a promotion, I was suddenly a ‘boss’ and the time for something ‘different’ had arrived.</p><p>The ‘culture rules’ we’ve come to are a combination of (selfishly) the way I want to work and (maybe less selfishly) the way I think that my engineering teams want to work. I also had to keep in mind some things that are very different when working in a latin culture.</p><h4>There are a few main goals around ‘la cultura’:</h4><ol><li>We’re productive</li><li>We’re getting better</li><li>We’re happy</li><li>We stay together</li></ol><p>It can be a bit shocking for many folks to join our team and this new way of working, so it’s always something that I make sure to share in the interview process. For me (again maybe a bit selfishly), the most important thing is that no one quits. Training new people is expensive, costly, hurts team morale, and slows us down.</p><h4><strong>Rule 1</strong></h4><blockquote><strong><em>“Everything is open for debate by default, and those who debate will be rewarded”</em></strong></blockquote><p>For me, the main thing that I suffered with when I first joined Rappi was that everyone below me in the org chart would agree with me when I’d present a new idea. This is especially bad when you’re not really sure how to do what you’re supposed to be doing, which was often the case for me in Rappi.</p><p>There are techniques that I implement to relieve the pains of being in charge in a culture with high power distance, like asking everyone else what they’d do to solve a particular problem before I present my proposed solutions. However, this is by far the most important rule for me.</p><p><em>“But why is it so important, Joseph?”</em></p><p>Teams with a certain level of friction have shown to deliver much stronger results. Blindly agreeing to everything the leader says or always going along with your colleagues is sure fire way to be mediocre. Also, when people debate, they are required to think critically, and therefore get more involved and invested in the solution.</p><p>I want the type of people and culture where we’re coming up with ‘eureka moment solutions’ while we’re walking in the park or shampooing our hair (well, for those of us who have hair). This shouldn’t be because we’re workaholics and overworked. It should be because we really care a lot about what we’re doing and want to nail it.</p><p>Look around in your workplace. The ones who are debating (not to be confused with complaining) are the ones who really care.</p><p>A great forcing mechanism for caring to be the default is for debate to be the default.</p><h4><strong>Rule 2</strong></h4><blockquote><strong><em>“No hay horarios”</em></strong></blockquote><p>This loosely translates from Spanish to English as “we don’t have any fixed hours at work”.</p><p>Why this rule? Well, first of all, I don’t want anyone telling me when I need to show up to work and I don’t think anyone else wants that either. It’s 2022, people.</p><p>However, there is a lot more to this rule than meets the eye. The main ‘requirement’ (for those of you who also speak JIRA in addition to Spanish) is that we must also find the most optimized version of ourselves.</p><p>I’ll say it again for emphasis: We must find the most optimized version of ourselves.</p><p><em>“But what do you mean by ‘optimized version of ourselves’, Joseph?”</em></p><p>There is a huge difference between working a lot of hours and making those hours count. Everyone will be evaluated on the quality and quantity of their contribution to the team, not whether or not I see a green dot next to their name on Slack at 6pm. The best way to contribute is to find the best version of yourself as a colleague.</p><p>If you want to skip all your meetings on a Wednesday afternoon and meet your friends, do it. However, if you feel inspired to write down a new idea at 8pm on a Saturday, put on your noise cancelers and crack open a Google doc, amigo.</p><p>We should all be treating ourselves like an experiment, constantly A/B testing when is the best time to do the main things humans should be doing.</p><p>When should I eat? Sleep? Workout? Eat? Write documentation? Be creative? Code? Do the things I don’t like doing? Consume written information? Consume video content? Meditate? Get wasted with the boys? Call my mom? Cry?</p><p>If we aren’t asking ourselves these questions, we’re not focusing on the main goals of our culture: Be productive. Get better. Feel happy. Stay together.</p><h4><strong>Rule 3</strong></h4><blockquote><strong><em>“The no assholes rule”</em></strong></blockquote><p>The Search and Personalization team is tackling some of the most finicky and most difficult problems to solve in tech, not just algorithmically, but architecturally with millions of searches being run in tens of thousands of stores per day. There are going to be some tense moments.</p><p>If you know me, you know I’m passionate and probably the most guilty of anyone for breaking this rule. So, I always say a good barometer for the team is that I should be the biggest asshole of all of us (and I’m usually a pretty nice guy).</p><p><em>“But what do we do when we’re super mad, Joseph?”</em></p><p>I have one main mantra to remember in these tense moments. It’s not just a mantra to use at work, but one to apply in all frustrating situations in life: “Don’t get mad, get curious”</p><p>Again, for emphasis and this time chill on it for a second: Don’t get mad, get curious.</p><p>Of course there are going to be moments where we all think things like “How in the world did they put that garbage in production?” or “What kind of shameful excuse for a description of requirement for a ticket is this?”, but we need to use these moments to teach, understand and get better.</p><p>We must avoid building a culture where people are afraid to make mistakes, but we also can’t have a culture where we don’t understand why we mess up when we do mess up. If we’re afraid to fail, it’s impossible for us to work on the cutting edge.</p><p>Curiosity makes it so we all come out of the other side better off and requires us to treat each other with respect (even when maybe we’d rather rip someone’s head off), and most importantly, improve.</p><h4><strong>Rule 4</strong></h4><blockquote><strong><em>“If someone below you can do it, delegate it.”</em></strong></blockquote><p>If you’ve ever tried to schedule a meeting with leadership in your company, you’ll notice it’s never easy to find time on their calendar. The higher up in the organization you go, usually the more ‘time poor’ the person is when in reality, that person should be spending as much time as possible thinking, writing, recruiting, researching and scouting the competition.</p><p>Another problem you’ll often run into is that there are many middle managers or senior developers who are holding on to a certain area of ownership simply because that’s the way it’s always been. This doesn’t just make people bored and stop them from developing, it also makes it so that the people below them don’t have a chance to level up and take on new challenges.</p><p>Then, if you go to the bottom of any big company, you’ll typically find a large group of people who are doing the same menial tasks over and over. Any task that is done regularly can almost always be automated, even if it is only to a small degree.</p><p><em>“But if everything is delegated, doesn’t that just mean you won’t have to work since you’re the leader of the team, Joseph?”</em></p><p>Well, kind of, but not really. The goal for me as the leader of the team is to never do anything that I think anyone below me can do at an equal or near equal level. However, that doesn’t translate into less work for me.</p><p>There are certain things that only I can do the way I do them. Some examples are making sure all of the moving parts of the team are where they should be or finding the best talent on the planet to work with. There are also things that no one can do for me like expanding my knowledge base, having a 360 view of what the team’s capabilities are, and constantly revising our backlog.</p><p>Another byproduct of the delegation rule is that those who are below me are constantly having chances to level up their skillset. Do I think that this junior product manager can handle this meeting with our CEO? If yes, well then I have to delegate it and give him/her the exposure.</p><h4><strong>Wrapping things up</strong></h4><p>I’m super proud of the team and culture we’ve built. We’re not perfect, but we’re constantly adapting and striving to be a better version of ourselves.</p><p>And as always, and as rule #1 goes, everything is open for debate by default and I’d love to hear your feedback on our culture rules. I’d also love to know what rules of your own you might add.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a1e139564df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>