<?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 Product Cracks on Medium]]></title>
        <description><![CDATA[Stories by Product Cracks on Medium]]></description>
        <link>https://medium.com/@productcracks?source=rss-ac17f311daf0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dYVT9jdeyhjh_6zP.jpg</url>
            <title>Stories by Product Cracks on Medium</title>
            <link>https://medium.com/@productcracks?source=rss-ac17f311daf0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:48:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@productcracks/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 lead an agile transformation as a PM at Bitso]]></title>
            <link>https://productcracks.medium.com/how-to-lead-an-agile-transformation-as-a-pm-at-bitso-89844ec45515?source=rss-ac17f311daf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/89844ec45515</guid>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Product Cracks]]></dc:creator>
            <pubDate>Mon, 10 May 2021 14:12:58 GMT</pubDate>
            <atom:updated>2021-05-10T14:12:58.182Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>How to lead an agile transformation as a PM: lessons learned at Bitso </em>with <strong>Alejandro Romo</strong></h3><p>When Alex joined Bitso as one of their first real <strong>Product Manager</strong> a year and a half ago, the company started its <strong>digital transformation</strong>. The founders and the Tribe leads heard about the <strong>Spotify model</strong>. Consequently, they noticed their ways of ideations and planning were not <strong>scalable</strong>. The pandemic hit, crypto boomed. Bitso had to adjust and be ready for the <strong>new normal</strong>. And numbers show the company did it pretty well as they just announced a new funding, making their valuation increase to 2.2 billion dollars! Let’s have a look at the behind-scene, narrated by their employee number 90.</p><p><strong><em>How I met Alex</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jC_RXtri10YttLln3LEOg.jpeg" /></figure><p>Alex is one of the few that tries to build the Product Management <strong>community</strong> in Mexico City. I met him through one of the Product School <strong>meetups</strong> he organized a couple of years ago. Alex is always ready for a new challenge and isn’t afraid to roll up his sleeves to reach his objectives. When you see him, he seems calm, very meticulous, and listens well to others. NDLR: Product Management is still a <strong>new concept</strong> for Mexico City. Start-ups are flourishing, and you can find great engineers. But good, seasoned product managers are still scarce. However, people showing up to the meetups are hungry and want to learn, which is a great point. It wouldn’t be a surprise if, in the years to come, <strong>Mexico City </strong>becomes the number one spot in <strong>Latin America</strong> for <strong>Product</strong>.</p><h3><strong>The interview: tell me about your move to Bitso and what it’s like to transform your ways of working.</strong></h3><p><strong><em>JL: Could you start by giving us some context on your company and what was it like when you joined?</em></strong></p><p>AR: With their seven years in the market, Bitso has become the largest <strong>cryptocurrency</strong> fintech start-up in Latam. The company enables crypto transactions via its website and applications. While business is flourishing in Mexico, they opened the Argentinian market recently and targeted Brazil as their next challenge. I think we can explain the company’s success with several factors:</p><ul><li>The <strong>right profile</strong> mix between their founders: design, business, and engineering. Each of them contributes on day-to-day to the excellence for their respective area</li><li>Their desire to put the <strong>customers</strong> at the center of their decisions</li><li><strong>Regulation</strong>: the company follows Gilbratar’s and Mexico’s regulations, an important point in the Fintech environment. <strong>** </strong>Actually, by focusing on regulations and offering high-security standards to their customers, it has been really hard for other startups to compete with Bitso.</li><li>The <strong>interest</strong> increase in cryptocurrency worldwide.</li></ul><p>These led the company to several series of investments. They raised 62 millions of dollars last year and just announced a new serie of investment of 250 millions of dollars, making it a company worth 2.2 B! (<a href="https://techcrunch.com/2021/05/05/latam-crypto-exchange-bisto-raises-250m-from-tiger-coatue-at-a-2-2b-valuation/">https://techcrunch.com/2021/05/05/latam-crypto-exchange-bisto-raises-250m-from-tiger-coatue-at-a-2-2b-valuation/</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*ZMS05rCV5VCjtatbA7TpHw.jpeg" /></figure><p><strong><em>JL: How exciting! Now, what role do you play at Bitso?</em></strong></p><p>AR: I joined them at the end of 2019, as their employee number 90. Since that moment, it’s been a rollercoaster! Being one of the first official PM to join the company, I have been in charge of several different projects, mainly on the user experience within the <strong>Account squad</strong>. Those projects include security, password management, but also regulatory products and settings in general. I have also worked on acquisition in the Onboarding squad. My customers’ journey’s goal is to get to their “<strong>AHA-moment</strong>” of buying their first crypto. To do so, the <strong>enablers</strong> are wire transfers.</p><p>After a year and a half in the company, I am proud to say that I have been supporting them in their <strong>digital transformation</strong>.</p><p><strong><em>JL: Thank you for the information, which helps me think of the following question: can you tell us a little more about the Product organization?</em></strong></p><p>AR: As we said before, Bitso took the <strong>Spotify model </strong>as a basis and adapted it to their needs: we have different <strong>tribes</strong>, in which we have several <strong>squads</strong> and <strong>chapter</strong> leads. I am part of the consumer tribe, leading the product for acquisition and growth.</p><p>We are now more than 280 people in the company and want to duplicate this number by the end of the year. So obviously, we had to adapt and adjust our <strong>expectations</strong> to scale our business. And to be honest, we still are! We are better than yesterday, but tomorrow we’ll be even better.</p><p><strong><em>JL: What a growth, impressive! How did this impact your day-to-day and transformation?</em></strong></p><p>AR: I joined a team that had the ambition to be more <strong>agile</strong>. Naturally, I felt compelled to participate in the effort. They were still using <strong>waterfall</strong> as a development framework. So with the help of the VP of engineering, who joined a few weeks before me, the Tribes’ leads, and the founders, our first challenge was to implement agile methodologies and the <strong>SCRUM</strong> framework. I helped in setting up the <strong>rituals</strong> and promoting them with the engineering teams: daily stand-up, retrospectives, demo, etc. In parallel, I configured all the <strong>tools</strong> we were using, such as JIRA. While we were still trying to define the agile roles in the company, we asked for help. Then, the HR team recruited someone to lead the agile transformation. Bitso has a <strong>Head of Agile</strong> in their teams. Thanks to that impulse, we could go to the next level and start designing our tribes, squads, and chapters.</p><blockquote>The founders already had a vision for the company for the next 10 years. From there, we defined our mission: make crypto useful.</blockquote><p>Bitso has been leveraging cryptocurrencies since their humble beginnings but is not closed to new financial products. Their vision has shifted towards completely revolutionizing the financial system.</p><p>Being at the center of this transformation and having my <strong>voice</strong> heard by the leadership has been a great feeling. With the <strong>pandemic</strong>, we knew we had to change our <strong>ways of working</strong>, and we had to experiment fast. That’s what the agile framework enabled us to do: with several iterations in the <strong>digitalization</strong> process, we kept getting better.</p><p><strong><em>JL: How about you, as a PM? How did this impact your perception of product development?</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aAoPYvsvXmQcUp9D" /><figcaption>Photo by <a href="https://unsplash.com/@mat_graphik?utm_source=medium&amp;utm_medium=referral">Jordane Mathieu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>AR: I have always thought of Product Management as creating your <strong>own</strong> <strong>business</strong> or making a physical product. You have to own it to make the best out of it. Internally, I always say that I cannot decide if I don’t have the full context. Research and thinking of your customer are keys to deliver the best quality in your products. The passion I have built around the job is what makes me being good at it. While I am not the <strong>CEO of the product</strong>, as people in the area are debating, I am giving my best to polish it as it was my own business. Bitso is still looking at ways to improve that <strong>ownership</strong> feeling, following Amazon or Netflix’s examples.</p><p>I always feel like a baker who needs to adjust his recipes to sell to more customers and retain the existing ones. <strong>Internal and external feedback</strong> are keys to my growth! Selling is important, but the process of baking, the way you promote your final product, the way you maintain healthy finances on your purchases, will help you build your success. I guess it should be natural for a PM to feel bad when someone discovers a bug in your workflow. You think of ways to have avoided it and new ways of working to detect issues early. Not to voice in the debate of being the CEO of your product, the discipline itself is still in a <strong>grey area</strong>. That’s why I am not surprised when I see that numerous PMs have side projects and become <strong>entrepreneurs</strong> after all.</p><p><strong><em>JL: Inspiring. With that said, any tips on how to maintain a healthy backlog between new projects, technical debts, bugs for our readers?</em></strong></p><p>AR: The key is to communicate clearly on the <strong>benefits</strong> and the problems to be solved. You have to include the team bandwidth in the scale too. Our prioritization process is a combination of those 3. I said it before, it is never easy to say no, to a stakeholder or even someone from the product team. But, if we share common objectives, and support them with <strong>data</strong> it is easier to understand a decision. My role is to communicate what we cannot do and the reasons why. While Bitso gives full power to Product Managers to make those <strong>informed</strong> decisions, we are trying to work on engineering <strong>empowerment</strong> to decide as a team, including designers too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bfw2FkVA2nZsIIMCNonhbw.jpeg" /><figcaption>Example of a demo session in Bitso</figcaption></figure><p>A tool that helped us improve in that area is the <strong>demos</strong>. We open them to anyone in the company: product, business, finance, etc. We collect a lot of feedback. We take follow-up actions that help us refine our backlog. I also attend other product demos to adjust my backlog if needed and see dependencies.</p><p><strong><em>JL: Wow, demos open to the entire company, these are making an impact for sure! Thank you for this tip. Apart from rituals, you also mentioned frameworks, anything drastic that Bitso implemented recently?</em></strong></p><p>AR: Let’s talk about <strong>OKRs</strong>. When I joined, there was a roadmap meeting with the entire company to pitch in new ideas for each quarter. While I found this process interesting because it involved all the company, it was not <strong>scalable</strong>. With the curiosity and interests of our founders, and the coordination between Tribe leads and the Strategy department, we came across the OKR framework. We thought: how can we implement that at Bitso?</p><p>Implementing OKRs was a <strong>product-led</strong> approach to make sure we were keeping our customers in the center of our decisions. We set up objectives at the Tribe and Squad levels.</p><p>To do so, Product Managers and leaders met with the different business areas and shared the needed data to agree on common objectives. What is the right number of objectives to set up? How are we reviewing them? To be honest, it is still in process, but it has shown increasing interest from everyone at the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UuET6jfrXJlS6glOyL4r0g.jpeg" /><figcaption>Brainstorming and prioritization</figcaption></figure><p>We still have our <strong>roadmap</strong> meetings each quarter, and that’s where we perform our OKRs <strong>review</strong> at the company level. The focus is more on how we’ve moved the needle on some specific objectives and how we can adjust for the following quarters. Of course, we mention projects linked to these, but we don’t spend much time on the project list. Instead, we focus on the objectives and problems. And then, it is up to the different squads to work on the solution approach. Inside the squad, we also do several OKR check-ins to make sure we are on track or not. And PMs have the responsibility to communicate with the <strong>stakeholders</strong> how we are doing, and why we cannot include more initiatives in a given period. Saying “no” is the most <strong>crucial</strong> part of our job.</p><p><strong><em>JL: What did the stakeholder think about it?</em></strong></p><p>AR: <strong>Timing</strong> has been the key. The pandemic hit, and we all started to work from home, so we needed a common objective, our <strong>North-star</strong> metrics. While at some companies, it might be hard for stakeholders to give up controls on what’s next, it hasn’t been such a challenge at Bitso. All employees are committed to set up the right objectives and reach them. Of course, it is hard to say no to a specific project. If you back up your decision with <strong>data</strong>, and put it into the <strong>global perspective</strong>, it is easier to agree on a strategy.</p><p>I am not saying that everything we propose as <strong>frameworks</strong> or ideas is always going in the right direction. We’ve embraced <strong>experimentation</strong>: if it makes sense at the company level, then we are trying it! Bisto employees are trusting the process and actively participating in it.</p><p><strong><em>JL: That is great to hear! After all those changes and following the questions you already answered, would you think that Bitso is a product-centric company?</em></strong></p><p>AR: I can clearly say that we are on the <strong>right path</strong>. It wasn’t the case when I joined the company, but the market moved so fast that we needed to adapt. Crypto and Fintech are booming markets. How can we acquire more customers and retain the ones we have? Competition is hard. At first, the teams focused on delivering the promises made to investors to make sure they could raise more money. Also, they had to work on some regulatory aspects that enable your company to survive. Once we completed these initiatives, and Bitso raised enough money, we wanted to make good use of it. With the OKR <strong>interactive</strong> process, and by including more <strong>UX research</strong> and <strong>discoveries</strong>, we started thinking and acting “customer-first”. We needed to use time wisely, and be more flexible in our thought-process. Again, the company helped us by hiring UX agencies to walk us through the Discovery and Research processes. As a result, objectives are shared and set up by several areas, backed by Product and Design data. Product leads initiatives and projects. Leadership validates if they fit into the <strong>global mission</strong> and OKRs set up. Don’t get me wrong, we are not one of these <strong><em>empowered</em></strong> teams mentioned by Marty Cagan, but we surely are on the right way to become one!</p><p><strong><em>JL: For sure, that’s an exciting moment for any company. What was the support you received from the HR department in all this?</em></strong></p><p>AR: They have been learning and adapting with us! I must say that they did a pretty good job to capture what the company needed to go the <strong>extra mile</strong>. First, they attracted new talents with key roles. I already mentioned the VP of engineering, the Head of agile for instance. But they also included specific profiles in their team. Someone <strong>dedicated</strong> to recruiting the best PM joined the team recently. Our collaboration with that person helped us ace our interviews and “profiling”. We’ve recruited more than 10 PMs in total and reviewed the whole hiring process thanks to that new person. As Reed Hastings from Netflix would say:</p><blockquote>To make the right product and features, you have to get the best talents and retain them.</blockquote><p>They also helped us share more transparency and implement a <strong>feedback</strong> <strong>culture</strong>. 1:1 meetings are becoming a habit between managers and employees. Assessments are done quarterly. <strong>360 interviews</strong> and surveys are provided to anyone in the company, to help them improve at their current role. We design and review frequently the <strong>career paths</strong> from there. Finally, the HR team is ready to finance any <strong>training</strong> that will help anyone get to the next level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r2Xw8TgQld6wk9oD" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_source=medium&amp;utm_medium=referral">Christina @ wocintechchat.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong><em>JL: HR people, please take notes… <br>Before closing the interview, I would like to ask you some general questions: any interesting book or article on this subject you can recommend to us?</em></strong></p><p>Recently, I read a lot of <strong>Product Operations Manager</strong> articles. I find them very interesting! A new role is coming to the product world, and we have to embrace it. I guess this type of position will be more interesting for big organizations.</p><p>Also, I am still reading <em>Empowered</em> by Marty Cagan. We all know Marty. We all wish we had him to drive the product <strong>mindset</strong> in our companies. <em>Inspired</em> was already a success, but what makes Empowered great is that it is full of clear actions for leaders to make Product Managers and their organizations <strong>thrive</strong>.</p><p><strong><em>JL: And if you had to choose a couple of «cracks» that have inspired you in your journey, who would they be?</em></strong></p><p>AR: First, I follow the Miro, Airbnb, and Spotify PM leads on LinkedIn and other social networks. Their focus on <strong>design</strong> is what has always inspired me. Similarly, I have been a fan of Gibson Biddle, ex-CPO at Netflix. His way of speaking of <strong>Product strategy</strong> is inspiring. Our scope inside Product Management is so vast! And he made the best of one part of the product journey: how to set up the right strategy. It is amazing to see that he left Netflix more than 10 years ago but still shares incredible anecdotes and content from his time over there.</p><p><strong><em>JL: To finish, what are the subjects you would like ProductCracks to address in the upcoming articles? How can we make our content valuable to you and your teams?</em></strong></p><p>AR: I would love to discover more on new Product <strong>roles</strong>, different from the original PM: Product Marketing Manager, ProductOps, Product Data Manager, etc. Share the value of their job and when a start-up needs to hire those profiles, and why.</p><p>As an <strong>agile</strong> advocate, I am a sucker for new <strong>methodologies</strong> and <strong>frameworks</strong>, specifically if we can get a deep-dive into the implementation and challenges.</p><p>Finally, I am always interested in how new PMs got into Product Management and how they are doing.</p><p>Huge thanks to <strong>Alex, </strong>always eager to help the Product <strong>community</strong> grow locally. It’s been great to deep dive into his journey at <strong>Bitso</strong>. Anyone in a company can help to get to the next level!</p><p>You have an interest in crypto and want to participate in what could be the future of finance, make sure you check out the open positions at Bitso on <a href="https://bitso.com/jobs">https://bitso.com/jobs</a></p><p><em>— Written by Jonathan Leonardo, based on video interviews with Alejandro.</em></p><p><strong>** </strong><a href="https://blog.bitso.com/bitso-ahora-es-la-primer-plataforma-de-am%C3%A9rica-latina-regulada-d8e6b63132ad">https://blog.bitso.com/bitso-ahora-es-la-primer-plataforma-de-am%C3%A9rica-latina-regulada-d8e6b63132ad</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89844ec45515" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cómo liderar una transformación digital como PM: la historia de Bitso con Alejandro Romo]]></title>
            <link>https://productcracks.medium.com/c%C3%B3mo-liderar-una-transformaci%C3%B3n-digital-como-pm-la-historia-de-bitso-con-alejandro-romo-f7e756d2ed9c?source=rss-ac17f311daf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7e756d2ed9c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[latam]]></category>
            <category><![CDATA[okr-framework]]></category>
            <dc:creator><![CDATA[Product Cracks]]></dc:creator>
            <pubDate>Thu, 06 May 2021 15:59:20 GMT</pubDate>
            <atom:updated>2021-05-06T15:59:20.914Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cómo liderar una transformación digital como PM: la historia de Bitso por Alejandro Romo</h3><p>Alex se sumó al equipo de Bitso como su primer <strong>Product Manager</strong> oficial hace un año y medio. En aquel momento, la compañía empezó su <strong>transformación digital</strong> siguiendo el interés y la curiosidad de sus fundadores. Ellos leyeron acerca del modelo de <strong>Spotify</strong>, y notaron que sus procesos de ideación y planeación no eran escalables. El Covid-19 intervino, el mercado de las criptomonedas explotó, así que Bitso tuvo que ajustarse y enfrentar la <strong>nueva normalidad</strong> como cualquiera persona o empresa. Veremos las razones de su éxito y como llegó a levantar tanto dinero en un par de años. En este articulo descubriremos lo pasó detrás de la escena gracias al testimonio de su empleado número 90.</p><p><strong><em>Cómo conocí a Alex</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jC_RXtri10YttLln3LEOg.jpeg" /></figure><p>Alejandro siempre ha querido hacer crecer la <strong>comunidad </strong>de Product Managers en la Ciudad de México. Lo conocí gracias a un <em>meetup </em>que organizó hace un par de años con ProductSchool. Alex no le tiene miedo ni al <strong>cambio </strong>ni a los <strong>desafíos</strong>, siempre se esforzará y dará el mejor de sí mismo para empujar ideas y/o proyectos. Cuando lo ves, es alguien muy tranquilo. Sientes su atención por los detalles y sabes que escucha activamente lo que uno está contando. <em>NDLR</em>: Producto sigue siendo un concepto bastante nuevo en la Ciudad de México. Se crearon un montón de startups y puedes encontrar a muy buenos ingenieros pero todavía no hay muchos PMs con el buen <em>mindset </em>y la experiencia adecuada. Sin embargo, la gente que atiende esos <em>meetups </em>quiere aprender y se ve muy animada. Lo cual me hace decir que no sería una sorpresa que la CDMX se convierta en el lugar número 1 en <strong>Latinamerica </strong>para <strong>Producto </strong>en los siguientes años.</p><h4>La entrevista: cuéntame de tus primeros pasos en Bitso y cómo te adaptaste a esta transformación digital.</h4><p><strong><em>JL: Alex, podrías empezar con un poco de contexto sobre tu empresa y tus primeras impresiones al sumarte a su equipo por favor?</em></strong></p><p>AR: En siete años, Bitso se convirtió en la mayor startup <em>fintech</em> de <strong>criptomonedas </strong>en Latinoamérica. La empresa, vía sus aplicaciones y su sitio web, permite la compra, venta y envío de cripto activos. Después de haber crecido localmente en México, la empresa decidió abrir los mercados argentinos y brasileños también. Creo que podemos explicar el éxito de Bitso con varias razones:</p><ul><li>El balance perfecto entre los <strong>perfiles </strong>de los fundadores: diseño, negocio e ingeniería. Cada uno de ellos contribuye de manera diaria a lograr excelencia en su respectivo dominio.</li><li>Su deseo de poner al <strong>cliente </strong>al centro de las decisiones</li><li>La <strong>regulación</strong>: Bitso sigue oficialmente la regulación de Gibraltar y de México, lo cual les da una ventaja importante en el ecosistema <em>fintech </em>y de criptomonedas. ** (NDLR: este enfoque les permite trabajar con estandares de alta seguridad, lo cual no está tan sencillo para sus competidores).</li></ul><p>Así, la empresa ha podido levantar 62 millones de dólares el año pasado, y justo acaban de levantar otros 250 millones esta semana. Bitso ya se convirtió en un <strong>unicornio </strong>y tiene una valuación de 2.2 mil millones de dólares. (<a href="https://www.elfinanciero.com.mx/opinion/de-jefes/2021/05/05/la-fintech-bitso-se-convierte-en-unicornio/">https://www.elfinanciero.com.mx/opinion/de-jefes/2021/05/05/la-fintech-bitso-se-convierte-en-unicornio/</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*ZMS05rCV5VCjtatbA7TpHw.jpeg" /></figure><p><strong><em>JL: Qué emoción! Y cuál es tu papel en Bitso?</em></strong></p><p>AR: Llegué a finales del año 2019 como empleado número 90. Desde entonces, ha sido una aventura increíble, como un día en <em>SixFlags</em>! Fui el primer PM oficial en aquel momento y he podido trabajar en diferentes áreas y proyectos, sobre todo en la experiencia del usuario adentro del <strong><em>squad </em>de Account y OnBoarding</strong>. Trabajé en proyectos de parámetros de cuenta, productos regulatorios y seguridad, posicionando a Bitso como una de los <em>crypto</em> <em>exchanges</em> más seguros en el mundo (número 6 actualmente <a href="https://cer.live/">https://cer.live/</a>). El objetivo de<em> </em>mi usuario es llegar al <strong>momento “AHA”</strong> en que compra por primera vez criptomonedas. Para lograrlo, primero tiene que transferir dinero a su cuenta.</p><p>Después de un año y medio en Bitso, estoy muy orgulloso de haber podido participar y apoyar en su <strong>transformación ágil</strong>.</p><p><strong><em>JL: Gracias por esta información. Me hace pensar en mi próxima pregunta: nos puedes contar acerca de la organización del Producto adentro de la compañía?</em></strong></p><p>AR: Nos inspiramos del modelo de <strong>Spotify </strong>y lo adaptamos a nuestras necesidades: tenemos diferentes <strong>tribus</strong>, en las cuales operan diferentes <strong>squad </strong>y <strong>chapters</strong>. Por ejemplo, yo formo parte de la tribu de Consumer, liderando la parte de producto para adquisición, retención y <em>growth</em>.</p><p>Ahora, somos más de 280 en Bitso y tenemos el objetivo de duplicar nuestra plantilla hasta el final del año. Obviamente tuvimos que adaptarnos y ajustar nuestras <strong>expectativas </strong>para poder escalar nuestro negocio. Siendo honesto, todavía estamos en el proceso! Somos mejores que ayer, y mañana seremos aún mejores.</p><p><strong><em>JL: Un crecimiento impresionante! Cómo te impactó en tu día-a-día y en la transformación?</em></strong></p><p>AR: El equipo tenía la ambición de ser más ágil. Sin duda, quise apoyarles en este esfuerzo. En aquel momento, seguían con un <em>framework </em>de desarrollo de <strong>tradicional</strong>. Junto con los lideres de Tribus y los fundadores, nuestro primer desafío fue implementar la metodología ágil y<strong> SCRUM. </strong>Organizamos los diferentes rituales y trataba de promover los beneficios con los diferentes equipos de desarrollo: daily standup, retrospectivas, demo, etc. En paralelo, configuramos las <strong>herramientas</strong> que teníamos, sobre todo JIRA. En medio de esta transformación ágil, pedimos el apoyo de del departamento de <em>People</em>. Bitso cuenta con un <strong>Head of Agile</strong> ahora. Gracias a este empuje, pudimos ir al siguiente nivel y empezamos a diseñar las <em>tribus</em>, los <em>squads </em>y <em>chapters</em>.</p><blockquote>Los fundadores ya tenían una visión para los siguientes diez años. De ahí, definimos nuestra misión: make crypto useful.</blockquote><p>Bitso se enfocó en criptomonedas desde el inicio pero tampoco está cerrado para su futuro. Ahora, el objetivo es revolucionar por completo el sistema financiero.</p><p>Tengo que admitir que al estar en el centro de esta transformación, y sentir que mi <strong>voz</strong> cuenta por parte de la dirección, me sentí muy orgulloso. Con la pandemia, sabíamos que teníamos que cambiar nuestras <strong>maneras de trabajar. </strong>También necesitábamos experimentar nuevas ideas y hacerlo rápido. Desde entonces entendimos el poder del <em>framework </em>ágil: después de varias iteraciones en digitalizar nuestros procesos, seguimos mejorándonos.</p><p><strong><em>JL: Y qué cambió por tu parte: viste alguna diferencia en tu percepción del desarrollo de producto?</em></strong></p><p>AR: Desde el inicio, comparo el desarrollo de Producto a <strong>crear un negocio</strong> propio o crear un producto físico. Tienes que sentirte como un dueño para sacarle el mejor provecho. En Bisto, siempre digo lo mismo: si no tengo o no entiendo el contexto, no puedo tomar una decisión. Hacer <strong><em>Reseach </em></strong>y pensar en tu <strong>usuario </strong>son elementos claves para entregar calidad en tus productos. Pude construir una verdadera pasión acerca de la profesión y pienso que esto me ayuda a formar parte de los buenos PMs. Sé que hay un debate en el área, y no puedo decir que soy el <strong>CEO de mi producto</strong>, sin embargo siempre me esfuerzo en mejor mi producto como si fuera mi propio negocio. Además, Bitso está pensando en empujar esta idea de <strong><em>ownership </em></strong>al siguiente nivel, como lo hacen Amazon o Netflix por ejemplo.</p><p>Me siento como un panadero que tiene que ajusta sus recetas para poder vender más: tener a nuevos clientes y hacer que los clientes actuales regresen. Para crecer, valor cualquier tipo de <strong><em>feedback</em></strong>. Vender es importante, pero el proceso de ideación, la promoción de tu producto, mantener tus finanzas saludables también te ayudan a llegar al éxito. Es normal si uno se sienta mal cuando alguien descubre un defecto en el flujo de producto. Piensas en maneras de cómo lo hubieras podido evitar, o qué nuevo proceso podrías implementar para descubrirlo antes. No quiero estar a favor o en contra del debate de sí un PM es el CEO de su producto o no, pienso que la profesión tal cual sigue en un <strong>área gris</strong>. Pero, tampoco me sorprende que muchos PMs se conviertan en <strong>emprendedores</strong>.</p><p><strong><em>JL: Me encanta. Dado este contexto, tendrías algún consejo para mantener un balance en tu backlog, entre nuevos proyectos, defectos, deuda técnica, para nuestros lectores?</em></strong></p><p>AR: La clave es comunicar claramente sobre los <strong>beneficios </strong>y los problemas que están solucionando. Deben de incluir el nivel de esfuerzo o al menos la banda ancha del equipo de ingeniería también. Nuestro proceso de priorización es una combinación de estos 3 factores. Ya lo platicamos, nunca ha sido fácil decir no, ya sea a un <em>stakeholder </em>o a alguien del equipo de producto. Pero, si compartimos una dirección y objetivos en común, y que soportamos nuestras palabras con <em>data</em>, ya se vuelve más fácil hacer un compromiso y tomar una <strong>decisión informada</strong>. Mi papel, como PM, es compartir con los demás equipos lo que no podemos desarrollar y las razones de por qué no. En Bitso, los PMs tienen toda la confianza de la compañía en general para tomar estas decisiones. Sin embargo, seguimos trabajando en empoderar los equipos de <strong>ingeniería </strong>y <strong>diseño</strong> también para poder participar en este proceso.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bfw2FkVA2nZsIIMCNonhbw.jpeg" /><figcaption>Un ejemplo de sesión de demo en Bitso</figcaption></figure><p>Una herramienta que nos ayudó para mejorar es las <strong>demos</strong>. Las abrimos a cualquier contribuyente de la compañía que quiere y puede asistir: producto, negocio, finanzas, etc. Recibimos mucho <em>feedback</em>. Tomamos acciones para ajustar nuestro backlog. Yo, por ejemplo, asisto a las demos de los demás equipos de productos para ver dependencias sobre mi área y cambiar prioridades si es necesario.</p><p><strong><em>JL: Abrir las demos a toda la empresa, se me hace una idea increíble para generar impacto! Gracias por el consejo. Aparte de estos rituales, también mencionaste la palabra framework: nos puedes compartir uno que cambió sus maneras de trabajar en Bitso?</em></strong></p><p>AR: Vamos a tomar el ejemplo de los <strong>OKRs</strong>. Cuando empecé con Bitso, teníamos unas juntas para definir el <em>roadmap </em>con toda la compañía. Cada uno podía proponer sus ideas para el trimestre. Lo veía muy interesante, y que bueno que las voces de cada empleado podían contar. Pero al ser realista, este proceso no es <strong>escalable</strong>. De nuevo, con las curiosidad de los fundadores y la coordinación entre las diferentes tribus y el área de estrategia, nos enteramos de los OKRs. Cómo podíamos ocupar este <em>framework </em>en Bitso?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UuET6jfrXJlS6glOyL4r0g.jpeg" /><figcaption>Sesión de brainstorming y priorización</figcaption></figure><p>El <strong>Producto</strong> tuvo que liderar dicha implementación de los OKRs para guardar al cliente en el centro de todas las decisiones. Llegamos a tener objetivos al nivel de cada tribu<em> </em>y cada <em>squad</em>.</p><p>PMs y lideres se juntaron con las diferentes áreas de negocio, compartieron los datos necesarios y todos juntos se acordaron en objetivos comunes. Cuál es el número correcto de objetivos? Cómo los revisamos? La verdad es que seguimos en el proceso de aprendizaje pero demostró un interés creciente por cada empleado.</p><p>Seguimos con nuestras sesiones de <strong><em>roadmap</em> </strong>cada trimestre y ahí <strong>revisamos </strong>los performances de nuestros OKRs. El enfoque está más en los <em>outcomes </em>que entregamos y cómo necesitamos ajustarnos para los próximos trimestres. Por supuesto, mencionamos unas iniciativa que ayudan a lograr estos resultados pero no pasamos mucho tiempo en la lista de los diferentes proyectos. Al contrario, nos enfocamos en los objetivos y problemas por solucionar. Después, cada <em>squad </em>toma el <strong><em>ownership </em></strong>de diseñar soluciones adecuadas. Al nivel de cada <em>squad</em>, también hacemos <strong><em>check-ins</em></strong> durante un trimestre para ver como vamos en nuestros OKRs. Los PMs se encargan de comunicárselo al resto de los <strong><em>stakeholders </em></strong>y de la misma manera pueden explicar por qué no se va a trabajar en unas iniciativas especificas en el periodo definido. Decir “no” es la parte más crucial de nuestro trabajo.</p><p><strong><em>JL: Qué pensaron los stakeholders al respeto?</em></strong></p><p>AR: El <strong>tiempo </strong>nos ayudó. Llegó la pandemia, empezamos a trabajar desde casa entonces de verdad necesitábamos un objetivo común, nuestro “<strong>Norte</strong>”. Sé que en unas empresas a los <em>stakeholders </em>les cuesta abandonar el control de lo que sigue para la estrategia, pero no ha sido tan difícil en Bitso. Cada empleado se compromete en tener y cumplir con los buenos objetivos. Claro que sigue siendo difícil rechazar una idea de proyecto. Pero si soportas tu decisión con <strong>data</strong>, y lo pones en el <strong>contexto global</strong> de la empresa, es mucho más fácil acordarse sobre una estrategia.</p><p>Tampoco estoy diciendo que todos los <strong><em>frameworks </em></strong>o las ideas que propusimos van en la buena dirección. Aceptamos <strong>experimentos</strong>, entonces si hace sentido al nivel global compañía, lo probamos! Los empleados de Bitso confían en los procesos y de participan de manera activa en definirlos.</p><p><strong><em>JL: Me agrada escuchar esto. Después de todos estos desafíos y las preguntas que contaste, piensas que Bitso es una empresa con enfoque al producto?</em></strong></p><p>AR: Puedo decir sin dudas que estamos en buen camino. Y no fue el caso cuando llegue. El mercado mueve tan rápido que tuvimos que adaptarnos. Las criptomonedas y <em>fintech </em>en general están explotando, sobre todo en Latinoamérica! Cómo podemos adquirir nuevos usuarios y retener a nuestra base existente? La competencia se vuelve más y más seria. Al principio, se trataba de cumplir con las promesas que habíamos hecho con nuestros inversionistas para seguir levantando dinero. También tuvimos que trabajar en aspectos de regulación para seguir operando. Una vez que completamos dichas iniciativas, Bitso levantó bastante dinero entonces queríamos usarlo de manera justa y correcta. En paralelo a los OKRs, incluimos más <strong>Research </strong>por parte de UX y <strong>Discoveries </strong>para poner el cliente al centro. Tuvimos que usar el tiempo de manera inteligente y ser más flexible en nuestro proceso de ideación. De nuevo, la empresa decidió apoyar esta ida y contrató a una agencia de UX para promover los nuevos procesos de <em>discovery</em>. Resultó que los objetivos que fijamos se comparten entre diferentes áreas y se validan por parte de Producto y Diseño. Producto lidera las iniciativas y los proyectos. La dirección valida que éstas iniciativas concuerden con la <strong>misión global </strong>y los OKRs definidos. Seguimos lejos de los equipos “empoderados” mencionados por Marty Cagan, pero sí estamos en buen camino!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1CfOjtIPgqFDfgaknyFxHQ.jpeg" /><figcaption>Ideación y junta de Roadmap antes de implementar los OKRs</figcaption></figure><p><strong><em>JL: Por supuesto, qué momento tan importante para una empresa! Cuál fue el soporte de RR HH en todo esto?</em></strong></p><p>AR: Aprendieron y se adaptaron con nosotros. Hicieron un muy buen trabajo en entender lo que la empresa necesitaba para conquistar el mercado. Primero, atrajeron a nuevos talentos en roles claves. Ya mencioné el VP de ingeniería, el Head of Agile por ejemplo. Pero también incluyeron a perfiles espaciales en su equipo: alguien <strong>dedicado </strong>a reclutar los mejores PMs recién llegó a Bitso. Nuestra colaboración con esta persona nos permitió mejorar nuestros procesos de entrevistas y selección de candidatos. Reclutamos más de 10 PMs en total y revisamos todo el proceso de reclutamiento. Como Reed Hastings de Netflix diría:</p><blockquote>Para crear el producto y las funcionalidades correctas, necesitas atraer a los mejores talentos y guardarlos.</blockquote><p>También nos apoyaron en compartir más <em>feedback </em>y generar una <strong>cultura de transparencia</strong>. Juntas 1:1 ya se convirtieron en un hábito entre empleados. Entrevistas anuales llegaron a ser entrevistas trimestrales. Se organizan entrevistas y encuestas 360 para seguir mejorando. Diseñamos y revisamos de manera frecuente el <strong>plan de desarrollo </strong>de cada empleado a partir de estas herramientas. Falta mencionar que el equipo de RR HH finanza cualquiera formación que permite a un empleado llegar al siguiente nivel en su carrera.</p><p><strong><em>JL: Equipos de RR HH, por favor tomen notas… <br>Antes de cerrar la entrevista, te quería hacer unas preguntas más generales: nos puedes compartir algún articulo o libro que nos recomiendas?</em></strong></p><p>AR: Últimamente, estuve leyendo muchos artículos acerca del nuevo papel de <strong>Product Operations Managers</strong>. Me interesa mucho! Pienso que este nuevo papel aplica más para empresas de gran tamaño.</p><p>También estoy por terminar el ultimo libro de <strong>Marty Cagan</strong>, <em>Empowered</em>. Todos conocemos a Marty y todos desearíamos tenerlo en nuestra empresa para empujar las mentalidades acerca del rol de un equipo de Producto. <em>Inspired </em>ya fue un gran éxito pero lo que me gusta de <em>Empowered</em> son los diferentes accionables para los lideres para mejorar sus organizaciones.</p><p><strong><em>JL: Y si tuvieras que elegir algunos “cracks” que te inspiraron en tu carrera, quienes serían?</em></strong></p><p>AR: Primero, sigo los lideres de Producto de Miro, Airbnb y Spotify en LinkedIn y otras redes sociales. Me inspira su enfoque en el <strong>diseño</strong>. De la misma manera, soy un aficionado de Gibson Biddle, ex-CPO de Netflix. Su manera de hablar de estrategia de Product me encanta. Nuestro alcance en Product Management es enorme, y Gibson logró especializarse en una parte importante de la carrera de un PM: cómo tener la estrategia correcta. Imagínate que se fue de Netflix desde hace más de 10 años y sigue compartiendo anécdotas increíbles y contenido interesante de su estancia ahí.</p><p><strong><em>JL: Para terminar, cuáles son los temas que quisieras leer en el blog de ProductCracks? Cómo podemos tener contenido de mucho valor para ti y tus equipos?</em></strong></p><p>AR: Me encantaría saber más de otros roles de Producto: Product Marketing Manager, ProductOps, Product Data Manager, etc. Compartir el valor de su misión y cuando una startup necesita estos perfiles y por qué?</p><p>Siendo un líder ágil, me gustan todos los artículos acerca de nuevas metodologías o <em>frameworks</em>, sobre todo cuando podemos conocer los detalles de la implementación y los desafíos de dichos cambios.</p><p>Finalmente, siempre me interesa saber cómo cada uno de los PMs llegaron a esta profesión y que tal les van.</p><p>Muchísimas gracias a Alex, que siempre quiere ayudar al crecimiento de la <strong>comunidad </strong>de Producto de manera local. Me gustó mucho poder descubrir más sobre su rol en Bitso y ver como cada quien puede participar en cambios importantes adentro de una compañía!</p><p>Si te interesan las criptomonedas y quieres participar en el futuro de <em>fintech </em>en Latinoamérica, dale clic en la siguiente liga y únete a Bitso: <a href="https://bitso.com/jobs">https://bitso.com/jobs</a></p><p><em>— Escrito por Jonathan Leonardo, a base de entrevistas videos con Alejandro.</em></p><p><strong>** </strong><a href="https://blog.bitso.com/bitso-ahora-es-la-primer-plataforma-de-am%C3%A9rica-latina-regulada-d8e6b63132ad">https://blog.bitso.com/bitso-ahora-es-la-primer-plataforma-de-am%C3%A9rica-latina-regulada-d8e6b63132ad</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7e756d2ed9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How revamping our logistics boosted us: lessons learned at mobile.club by Grégoire Segretain]]></title>
            <link>https://productcracks.medium.com/how-revamping-our-logistics-boosted-us-lessons-learned-at-mobile-club-by-gr%C3%A9goire-segretain-d22209a63cfc?source=rss-ac17f311daf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d22209a63cfc</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[logistics]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[smartphones]]></category>
            <dc:creator><![CDATA[Product Cracks]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 13:36:45 GMT</pubDate>
            <atom:updated>2021-03-01T13:36:45.636Z</atom:updated>
            <content:encoded><![CDATA[<h3>How revamping our logistics unlocked our growth: lessons learned at mobile.club by <strong>Grégoire Segretain</strong></h3><p>The month is <strong>November 2019</strong>, 18 months after <a href="https://www.mobile.club/"><strong>mobile.club</strong></a> shipped its first device to its first customer. They had an incredible partnership with their #1 supplier:</p><ul><li>it promises constant <strong>sourcing</strong> and availability of all the products</li><li>it takes charge of <strong>stocking</strong> and <strong>shipment</strong> to the final customers</li><li>it has the relationship and manages the contracts with <strong>transporters</strong></li></ul><p>Everything seems perfect, the startup was building its business stress-free of all things logistics. Until one decision changed the story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wg4tYkFBuqYfJiLmb-Uk9Q.jpeg" /></figure><p><strong><em>How I met Grégoire</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QbjWG3q37jbUX9tDwff25g.jpeg" /></figure><p>JL: I joined <strong>Save.co</strong> (Save my Smartphone) in 2016. Greg was the <strong>Head of Design</strong>. Everyone was pretty young at Save so I wasn’t surprised that Greg, <strong>23 years old at the time, </strong>had so many responsibilities and achievements: he was managing a team of 3 people, already traveled the world, co-founded a company (<strong>Flatchr</strong>), and launched an iOS app in high school,… how did you get the <strong>time</strong> for all this? Despite his young age and <strong>creativity</strong>, Greg is one of the Design “Cracks” who knows when to be <strong>optimistic</strong>, <strong>realistic, </strong>or even <strong>pessimistic </strong>when needed. We have worked on several projects through which we challenged ourselves to be <strong>better</strong> at our job. Today, he is Head of Product and Co-founder at <strong>mobile.club</strong>, a transition that didn’t surprise me.</p><h4>Tell me about the time you and your partners had to review the whole logistics of your company to see a brighter future.</h4><p><strong><em>JL: Greg, thank you for contributing to ProductCracks. Could you start by describing what mobile.club is, and we’ll focus on the logistic later to get everyone on the same page.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tMzkTE2EBTz2G-0NZbInpw.jpeg" /><figcaption>Welcome to the club!</figcaption></figure><p>GS: <strong>mobile.club</strong> is transforming smartphone ownership with a month-to-month, anytime upgradable, insurance-included, and low-price rental service. It was launched in 2018 by 4 ex-co-workers of <em>Save.co </em>who wanted to take their revenge on their past failures.</p><p><strong><em>JL: Great, now let’s focus on your role: what lines of product are you in charge of, how big is your team?</em></strong></p><p>GS: In short, I am Head of Product &amp; Design in our small Product team of 3 engineers and a wonderful CTO (who is part of the co-founders too). I don’t manage anyone <strong>directly. </strong>I am focusing on anything <strong>product, </strong>including designs. Being the only PM means I am in charge of:</p><ul><li>our entire information system or <strong>back office,</strong></li><li>our <strong>eCommerce </strong>presence: website, customer platform, emails, BI,</li><li>but also the <strong>packaging</strong> and the branding E2E (with my designer hat).</li></ul><p><strong><em>JL: Multiple hats, that should be something our startuppers would understand! Do you consider mobile.club “product-focused” and why?</em></strong></p><p>GS: We debated this at the beginning. We came up with the following agreement: we are <strong>not</strong> <strong>tech-driven.</strong> Our value proposition is the <strong>service </strong>we offer to our customers.</p><blockquote>That said, the product team is at the <strong>origin</strong> of all decisions. Our motto is “Humans don’t thrive and don’t deserve repetitive and low-added-value tasks”. So that, we always prioritize the features from which big “operational” value can be <strong>automated</strong>.</blockquote><p>2 out of the 4 co-founders are in the Product team, which makes our <strong>innovation culture </strong>pretty strong. We decided to <strong>stay small</strong> to be more effective and improve our velocity: whatever we launch is based on our <strong>operations struggles</strong>. That’s not diminishing the rest of our priorities, such as our <strong>marketing investments </strong>and <strong>website conversions</strong>.</p><blockquote>We improve everything we can <strong>internally</strong> to make sure we deliver the <strong>best customer experience</strong> at the end.</blockquote><p>I cannot say that we follow a specific <strong>framework </strong>or use <strong>OKRs </strong>in our day-to-day. We have a roadmap. We prioritize features based on their outcome and the <strong>general health</strong> of the company. We also use SCRUMs and its agile processes.</p><p><strong><em>JL: Thanks for the transparency, it will help everyone understand the context of the main problem we want to discuss here. Let’s transition to your logistic issues. Can we start with the description of the problem?</em></strong></p><p>GS: First, getting back to the introduction of this article, you have to understand that our <strong>highest season</strong> was coming. A large American corporation <strong>acquired</strong> our partner’s company right before our deal. While we didn’t see any impact during 6 or 8 months of a fully-automated partnership, in <strong>3 days</strong>, we had no access to any of the inventory. No packages were being sent to our customers anymore. They simply ceased their activities because their acquirer decided to “change the strategy”. December was at the door, and we started wondering how we could keep up with our growth…</p><p><strong><em>JL: What a turnover in less than a week! How did your team react?</em></strong></p><p>GS: Surprisingly, the atmosphere was pretty <strong>calm</strong>. For your information, a year before, we had the logistics inside our <strong>apartment</strong>. Everything started in one of our co-founder’s apartment, not a garage but almost the same! We all learned our lessons working at Save.co; this time, we wanted to c<strong>ontrol our growth </strong>while focusing on our budget. So it wasn’t a surprise to see the CTO or even the CEO preparing packages to ship, answering to customers, and/or testing devices from our suppliers.</p><p>However, when the news hit us, we started wondering:</p><ul><li>How can we keep sourcing our devices?</li><li>What can we do to keep shipping phones to end-customers?</li><li>How can we keep growing in the long-term?</li></ul><p>We had to bounce back with another partnership the fastest way possible to make the best of the holiday season. In parallel, we had to <strong>pause </strong>our investments on growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OJQq05VytnLgZ8M9eMYtKA.jpeg" /><figcaption>Our team at its origin, working from an apartment.</figcaption></figure><p><strong><em>JL: That’s a pretty realistic approach… Talking about it, what were the figures like then?</em></strong></p><p>GS: What I can tell you is that we sold more devices in November (2019) than we did in December and January combined. December and January being our best months in a regular year.</p><p><strong><em>JL: Another reason why you had to find a solution pretty fast. Walk us through the “solutioning” please.</em></strong></p><p>GS: So our CEO, <a href="https://medium.com/@damienmorin">Damien Morin</a>, started searching for a new logistic partner on the business side. Within its network, he found a partner in Portugal, smartphone repairers with logistics expertise: Tamet. They found an agreement pretty fast. While Damien found this quick turnaround, the <strong>bottleneck </strong>was now on the Product side! We had to review our stock management system and put the financial controls needed to run our business smoothly.</p><p><strong><em>JL: Big challenge coming! What was the “discovery process” like?</em></strong></p><p>GS: Realistically, Tamet has an incredible and efficient system but <strong>repairs-focused</strong>. We needed to integrate the <strong>forward logistics</strong> on our side.</p><p>Before even talking about Product or IT impacts, we had to focus on specific parts of the<strong> E2E journey</strong>. The business proposal was as follows:</p><ul><li>mobile.club would own the <strong>sourcing </strong>and keep its supply contacts</li><li>this would also enable the startup to generate <strong>automated supply models</strong> based on forecast, demand, inventory, and return rate</li><li>and we would trust Tamet for shipping, returns, and repairs.</li></ul><p>The discussion was <strong>open. </strong>So were our new partners at Tamet. It boosted the integration and operations.</p><p>Once Tamet agreed to our conditions, we jumped on the first plane to perform what I would call an “<strong>express discovery</strong>”. We validated our first hypothesis: time-wise, we couldn’t integrate with Tamet’s system and logistics. We needed to bring the mobile.club DNA to Portugal. This included developing a homegrown system to create and print transporter labels, and ship the packages to our final customer. Operationally we also needed to create new spaces to adapt to our specificities: our packaging and additional accessories sold on each order.</p><p>Being on-site with <a href="https://medium.com/@othierry_">Olivier Thierry,</a> the CTO, we worked with the local team in Portugal to define the requirements and document them. It looked like a <strong>design sprint</strong>: we stayed 3 days there and returned to Paris, ready to deep dive. The trust and the openness of the Tamet team were keys to <strong>facilitate </strong>the discovery and the E2E process up to the release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wgdWTleNPikpTUwpm8d7NQ.jpeg" /><figcaption>Designing the E2E device journey and presenting it to the Tamet team.</figcaption></figure><p><strong><em>JL: Interesting “express discovery” as you say. So back in Paris, with a first draft of what could be your solution. Did you keep up with the agile processes and planning?</em></strong></p><p>GS: At this moment, the atmosphere went from pretty calm to excitement! We knew we could build a long-lasting solution and didn’t want to shoot for a quick-and-dirty MVP. We finished the <strong>specifications </strong>(including the technical discoveries) in two weeks and yes, we respected our Product vision and processes. We created the user stories, put everything on our <strong>SCRUM </strong>board, and went ahead with the development. The team worked without counting the hours, so I cannot say that these 3 sprints of development and testing reflected our actual <strong>velocity</strong>.</p><blockquote>That’s right, in 5 weeks we developed an enhanced solution and tested it from our Parisian office, which was still operating and selling a few devices while we were at it (souvenirs of our humble beginnings).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nU2nTi903JhsSQ0i8FF0Sw.jpeg" /><figcaption><em>In the logistic world: you need two documents, the PO with the order content and the transport label on two different sheets. We knew from our previous experiences that we could print everything on the same sticky paper: 1 order = 1 sheet.</em></figcaption></figure><p><strong><em>JL: Wait, you also tested these in a matter of five weeks in total?</em></strong></p><p>GS: That is correct, we enabled the possibility of having several warehouses to manage orders. We implemented the logic with the few units left in Paris. We even pushed the <strong>FIFO (First In First Out) </strong>rule to take the first device entered in stock, wherever it was physically. The goal was to empty the stock in Paris first and move forward with the Portugal operations as fast as possible.</p><p><strong><em>JL: I am impressed, even if I know how you guys work. What happened next? Tell us more about the official “release”.</em></strong></p><p>GS: We organized an on-site kick-off in Porto to train operators on our system and operational specificities (packaging and additional accessories). As we passed the Paris <strong>crash-test</strong> before, we were confident to release exactly what we had specified at Tamet. I repeat: not an MVP! In short, a real big bang <strong>rollout</strong>: the partners were excited about this launch. They loved to have something new to <strong>challenge </strong>their day-to-day. It wouldn’t have been a success without their attitude, <strong>culture, </strong>and eagerness to learn. Quickly, they even started giving us feedbacks on possible enhancements. Humanly, I loved it! I told myself, this is why I am doing this job!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*ufhVlj2KFkyz-1mHPUF-Fw.jpeg" /><figcaption>Demo time! This photo was taken in June 2020.</figcaption></figure><p><strong><em>JL: Congratulations, it looked like a great hit! Speaking of success, what KPIs or metrics were you addressing?</em></strong></p><p>GS: While specifying the project, we didn’t have the time <strong>luxury</strong> of defining specific operational or customer metrics. As I said before, we are not yet OKR-friendly and didn’t set up a <strong>milestone</strong>. We needed a working logistic, a little bit of intelligence, and we needed it to be available <strong>fast</strong>. The only deadline we had was the packaging delivery and the contracts with the transporter to respect. <br>A year later, we just started thinking of metrics and KPIs to follow this project’s success. Maybe I will tell you positive things about OKRs in a future article!</p><p><strong><em>JL: You bet. How about the results: even if you didn’t set up KPIs, how’s the business going now?</em></strong></p><p>GS: Sorry to disappoint the readers, but operations have been running smoothly: <strong>not a major issue or bug</strong> to share after several months! Our biggest win.</p><p>The quality we delivered enabled us to scale the business and get to <strong>numbers </strong>we are proud of, not only sales-wise but internally, for the <strong>E2E operations</strong>. If tomorrow we would have to rent 10x more devices than we do today, both our system and Tamet’s operations wouldn’t block this growth. We, the Product team at mobile.club, were also able to shift our focus on other priorities such as <strong>marketing, our website, </strong>and let the business think about<strong> </strong>our <strong>sourcing </strong>options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K0QT-_nORTkD0r88fFGWrA.jpeg" /><figcaption><a href="http://www.tametgroup.com/entreprise">Tamet</a> is one of the largest <strong>repairers </strong>of smartphones in Europe.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8UD1nvTaJtMJKnviinsNnQ.jpeg" /><figcaption>An example of a preparation bench.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ls9K0OX_7cHfbxLVXjNrcQ.jpeg" /><figcaption>An operator preparing an order with our original packaging.</figcaption></figure><p>Since then, we have integrated <strong>new streams </strong>with Tamet: supplier returns at testing (<a href="https://en.wikipedia.org/wiki/Return_merchandise_authorization"><strong>RMA</strong></a><strong> </strong>for those who know the processes) and repairs at testing. This helped us with running a healthier financial system. All returns and repairs are now redirected to Tamet’s operations, not in Paris anymore. Our next project is integrating system-wise those repairs (adding spare parts and quotations for instance). This time, we chose to <strong>integrate </strong>with their system for data exchanges and not develop a homegrown solution. They already have their expertise, and we inspired ourselves from what their operations and systems were capable of.</p><p><strong><em>JL: Again, really helpful: your decisions also changed based on the time you had and the urgency of the project. In retrospect, what feedback would you give yourself about this incredible project?</em></strong></p><p>GS: Having both Product and Design hats helped us gain <strong>velocity </strong>in setting up the ground rules. The mobile.club force is to deliver <strong>quality </strong>on the operational side, with very few team members. However, with the experience, after 2 or 3 big initiatives like this, any human being starts feeling its limits in the long term!</p><p><strong><em>JL: That is a pretty interesting story! Thank you for sharing. Before we finish, I like to ask this question: do you recommend any book or article that has inspired you in your Product career?</em></strong></p><p>GS: Not really… Unfortunately, I am not taking enough time to read what’s new in the Product world. I have been focusing on what is happening in <strong>real life</strong> for mobile.club. I know I should open to more people and keep up with new articles, but mobile.club is a baby (as co-founders) we need to give its <strong>full attention</strong>. That said, I do <strong>exchange</strong> with other fellow entrepreneurs and Product guys on their real <strong>experience</strong> towards some <strong>problems</strong> they had to solve.</p><p><strong><em>JL: And if you had to choose a couple of «cracks» that you look up to, who would they be?</em></strong></p><p>GS: Spontaneously, I don’t have a <strong>role model</strong>. It’s part of my introverted behavior, I do enjoy people’s success and love exchanging on everyone’s quality and opportunities. Still, I changed my view on all <strong>entrepreneurs</strong> (small or big): working on mobile.club transformed my opinion on them, and I always try to <strong>relate</strong> to them while creating products. This is my favorite persona to address!</p><p><strong><em>JL: Last but not least: what subjects would you like ProductCracks to cover in future articles?</em></strong></p><p>GS: I would like to know what it’s like in a company where a simple feature can change everything in their day-to-day or operations, especially for SaaS companies, like <strong>Slack</strong> or <strong>Superhuman</strong>. For me, these are 100% <strong>dependent</strong> on their product: whether it is a success or a failure.</p><p>And to do a parallel with mobile.club, I would also love to read about a PM that works on a <strong>subscription-based</strong> product. The challenge is always how do you keep delivering value to <strong>retain</strong> your customers in the long run.</p><p>JL: I enjoyed speaking with <a href="https://www.linkedin.com/in/gregoiresegretain/">Greg</a> about Product Management. I wish we had more time to do so. Big thank you to the whole mobile.club team for their feedback and their help on this article.</p><p>After a first article on the inaction towards the environmental changes, if you want to go greener, <a href="https://www.mobile.club/"><strong>mobile.club</strong></a> offers you the perfect refurbished phones and insurance for a fixed monthly fee: <a href="https://www.mobile.club/">https://www.mobile.club/</a> (France only)</p><p><em>— Written by Jonathan Leonardo, based on conference calls with Gregoire Segretain.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d22209a63cfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a new B2B line of product for a 100% B2C company: lessons learned at Carbo]]></title>
            <link>https://productcracks.medium.com/how-to-create-a-new-b2b-line-of-product-for-a-100-b2c-company-lessons-learned-at-carbo-3a9bd3bfb1b8?source=rss-ac17f311daf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a9bd3bfb1b8</guid>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Product Cracks]]></dc:creator>
            <pubDate>Wed, 02 Dec 2020 14:50:06 GMT</pubDate>
            <atom:updated>2020-12-08T15:34:03.748Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to create a new B2B line of product for a 100% B2C company: lessons learned at Carbo by <strong>Julien Janson</strong></h3><p>A couple of months after a major <a href="https://www.linkedin.com/posts/carbo-fr_partenariat-carbo-x-bridge-de-bankin-activity-6637693099722321921-5Q4i">press release</a> in the early days of 2020, the team at <strong>Carbo </strong>was expecting to get closer to <strong>Product Market Fit</strong>. The PR enabled the company to attract new customers and enjoy a good visibility for a small startup with only a few months of existence. Then, February 2020, March 2020, the <strong>world </strong>was about to change drastically… was it going to impact Carbo’s <strong>strategy</strong>?</p><p><strong><em>How I met Julien</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dndjDjnTa9fjTDN7" /><figcaption>Photo by <a href="https://unsplash.com/@yirage?utm_source=medium&amp;utm_medium=referral">Andriyko Podilnyk</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>JL: Julien joined Viadeo to work in the same team I was part of, and oversee any revenue generation from the social network. He reminds me a lot of Jimmy Neutron: he always has a million ideas and is passionate about each single one of them. It was not surprising at all when I saw Julien moving away and taking a leadership role but also when he decided to create his own company: Carbo. Julien is committed in his personal life and always wants to make an impact. <strong>Carbo</strong> is the perfect baby for him, mixing his interests and his professional life.</p><p><strong><em>In his own words..</em></strong></p><figure><img alt="Julien Janson, CPO @ Carbo IRL and soccer manager in his free time." src="https://cdn-images-1.medium.com/max/600/1*SPfSGMHyX6yqmTDOd0b3rg.png" /><figcaption>Julien as a wannabe soccer manager #nofilter</figcaption></figure><p>JJ: I discovered <strong>product management </strong>by accident when I joined a pre-launch startup after my engineering studies. My role was to fill the gaps between the engineering team, a business-oriented founder, and our soon-to-be users.</p><p>Since then, I’ve become obsessed with finding the right <strong>problems</strong> to solve and solve them right. I’ve added a <strong>UX</strong> and <strong>customer discovery</strong> flavor to my very data &amp; technical-oriented mind by working with tremendous product guys &amp; girls at Viadeo and Captain Contrat before finding the problem I wanted to solve by myself with <strong>Carbo</strong>.</p><h3>The interview:</h3><h4>Tell me about the time you and your partners decided to go for B2B at Carbo</h4><p><strong><em>JL: Julien, thank you for taking the time for the first article of ProductCracks. Could you start by giving us some context on what Carbo is and your role in the organization?</em></strong></p><p>JJ: We all know that <strong>global warming </strong>and <strong>environmental issues</strong> are in most people’s heads, but there are so many things to change that almost nobody can affirm they know <strong>where to start</strong>. In other words, the problem is identified (in general), there are tons of movements and actions but, if you’re not a “green” superhero, you’re a regular person like you and me, what can you actually do about it? That’s when Carbo came to our mind: how to fight against everyone’s “<strong>inaction</strong>” and how could we activate some simple actions for common people to start “acting” and not just reading or speaking about the environmental concerns. Of course, you have questionnaires and websites that are trying to fight against that, but, to my opinion and knowledge, these are too long, boring, and difficult for the average citizen to complete and feel committed. So when in early 2019, <strong>European banks</strong> decided to <strong>open their data</strong> to the engineering world, enabling tech companies to work on <strong>APIs</strong> to connect to one’s account and <strong>build financial products</strong>, we saw it as a great opportunity. We, my 2 partners and I decided to found Carbo. Our first idea was using people’s <strong>expenses</strong> to <strong>measure their carbon print</strong> and start a gamification/advisor relationship with our users. Basically, we knew people didn’t know how to select between their <strong>possibilities to make a positive green impact</strong> on the world, we attacked the issue by helping them to <strong>quantify their actions,</strong> without frictions and a long list of information needed from them: whatever small steps that you can do to save on carbon consumption and wastes, we intended to let you know and reward you. In short, we followed <strong>Nike+</strong> or similar apps that help <strong>people create habits </strong>and make them <strong>feel better about themselves. </strong>You’re not “losing your time” in toxic habits such as scrolling on your Instagram feed all day, but making an impact: on you, and on the world!</p><blockquote>Carbo doesn’t fight against global warming. It is intended to fight against the <strong>inaction</strong> towards the climatic changes.</blockquote><p>So who are we? and how did we organize ourselves? Well, I met my 2 partners in school years ago… <strong>Emmanuel</strong>, our <strong>marketing</strong> guy and serial <strong>entrepreneur</strong> who had success building co-working spaces and leveraged the social media power to do so, and <strong>Simon</strong>, the <strong>sales</strong> force of Carbo but also the one with the best professional experience in the <strong>environmental</strong> issues among us. And finally, there is me, wearing the Chief Product Officer and Chief Technical Officer hats in the company. I am an engineer (from my education) with a business mindset. I’ve loved my journey as a PM to test things and now I can do it in my own company, being my own boss and the only one (obviously with my partners backing me) that can block myself.</p><p><strong><em>JL: So I understand the model at first is directed to people like you and me, caring for the environment, B2C so-to-says. How did you envision monetization in the long term?</em></strong></p><p>JJ: That is correct. So we started by<strong> proving our concept</strong> of measuring everyone’s carbon print with the amount and type of their expense. From there, we could enable you to compare your “<strong>performances</strong>” with others. We gathered <strong>a lot of data</strong>, behaviors and this helped us discover new important things to keep building our product.</p><p>Since the beginning, as the profile of the <strong>founders </strong>is pretty <strong>complimentary</strong>, we focused on <strong>saving </strong>on <strong>costs</strong>: bootstrap, free stuff, and homemade solutions. Still, to start earning money, on the B2C side as you say, we implemented a model linked to your carbon print and again, <strong>gamification</strong>:</p><blockquote>in short, the most postive impact you make on the planet, the less you will pay for your subscription.</blockquote><p>This was part of our MVP, we had this <strong>subscription </strong>running for our early users. Before you ask me how are the results, let me tell you that it wasn’t the only monetization angle we wanted to have. Of course, we knew that people already had to make efforts for the <strong>environment</strong>, so <strong>not the majority</strong> of our users were willing to pay an extra amount to do so. And frankly, our first hypothesis on <strong>conversion </strong>wasn’t met. But it has enabled us to run our operations: hosting the website, paying for the different tools we have for instance. Heavy users are obviously super proud of this, and share their accomplishments with their network!</p><p><strong><em>JL: That’s pretty interesting, even if it sounds risky in the long-term I guess. Quick one: did you guys pay yourself a salary with this model?</em></strong></p><p>JJ: Hmm not yet… We want to reach <strong>Product Market Fit</strong> and validate our model first, but also pay for our infrastructure or freelance needs.<br>Again, this <strong>business model</strong> was part of our first hypothesis, and within the DNA of the company, but we couldn’t survive only with B2C users.</p><p><strong><em>JL Great transition thank you, so yes tell us more about pivoting to B2B, please!</em></strong></p><p>JJ: Actually, since the beginning, we knew that we would create a <strong>B2B </strong>line or at least B2B2C. In retrospect, it was a <strong>mix of a few factors</strong>:</p><ul><li>The problem we are trying to solve, <em>following and reducing one’s carbon print on the Earth</em>, isn’t important enough for one single person. Like I said before, everyone knows it is a problem but few people are actually ready to act, and moreover, pay for it.</li><li>Our target <strong>market </strong>in France isn’t big enough to only consider people like you and me.</li><li>Our <strong>distribution strategy</strong> didn’t enable us to address the problem correctly, especially on the banking connection.</li></ul><p>I suppose, if we had only suffered from one or 2 of the above factors, we might have chosen to <strong>iterate </strong>on our existing solution instead of <strong>pivoting</strong>…but we quickly came to the agreement that B2B was a must to survive, keep growing, and gain <strong>legitimacy</strong>.</p><p>The original idea was to apply the same feature to a company to measure its carbon print and their employees’. Rapidly, we also thought of selling our algorithm directly to the banks inside their own products and get paid through an API usage (i.e: based on the number of calls they would make). Why did we think about it? Well, in our <strong>user researches</strong>, we felt <strong>frictions </strong>on the customer side to share their bank information with us. So if we couldn’t grow our proper user base as fast as we wanted, at least we wanted to have a <strong>backup</strong>, and a “monetized” one, to make sure our “baby” will be useful. Remember two things: first, we are in France, with its own market limits and strong culture, and also, even if we were not directly impacting the environment, we had a shot to do so indirectly.</p><p><strong><em>JL: At what stage are you now? Do you have any figures or achievements that you can share?</em></strong></p><p>JJ: I can share a few figures yes of course:</p><ul><li>On the B2C side, we have around 1500 <strong>Monthly Active Users</strong>, for a total of more than 8000 accounts created. We also noticed a 20% rate in <strong>retention </strong>after using the app for 2 months</li><li>On the B2B and B2B2C, we counted more than 2 million bank transactions using our API and with our first <strong>MVP </strong>(launched in less than 2 months), we signed 10 customers.</li></ul><p>Overall we have an <strong>NPS </strong>between 45 and 50, depending on the customer type.</p><p>What is interesting this year, is obviously the<strong> impact of the pandemic </strong>on our users! While a lot of companies are seeing their activities slowing down, ours is pretty steady or actually increasing. But, the impact on the planet is the one that counts and we saw a reduction of 65% of the carbon consumption in our users in the last months.</p><p><em>For more details, you can read the blog post we published on our site: </em><a href="https://www.hellocarbo.com/blog/calculer/confinement-et-impact-carbone-des-pistes-pour-un-apres-moins-carbone/"><em>https://www.hellocarbo.com/blog/calculer/confinement-et-impact-carbone-des-pistes-pour-un-apres-moins-carbone/</em></a><em> (article in </em><strong><em>French</em></strong><em>)</em></p><p>HR-wise, fun fact, apart from help from people we know and some interns, the team hasn’t really grown yet.</p><p>What is difficult on a personal level is that when you launch a product, you expect to reach<strong> Product-Market fit</strong> in order to be able to recruit operation people and start dealing with higher priorities on your side. We realized pretty quickly, all 3 of us, that it didn’t happen yet. Of course, we were disappointed but there was no way we were about to give up!</p><p>Good news though, while pitching our B2B idea, we actually signed a big contract before the code was ready, so we estimate we are on our path to PMF… We could actually start to hire people, but now we are faced with a new challenge: meeting the deadline. So after having talked with my founders, we took the decision to stay as-is for now, because it would take us more time to train people and get them up-and-running and meet our deadline with our client. Again, we are going to double our efforts to keep on with our dream! And then, we’ll accelerate the business and we will be able to grow the team.</p><blockquote>For the French readers: On va retrousser nos manches et se remettre encore une fois au charbon!</blockquote><p><strong><em>JL: I know that you were a Product nerd, working with you at Viadeo, any specific framework that you applied to build on your ideas and roadmap and grow your team?</em></strong></p><p>JJ: Let me start with what hasn’t worked for us yet: <strong>OKRs</strong>… While I feel pretty comfortable with this logic and I have been using it in my different PM roles, my associates couldn’t adapt. Being <strong>outcome-focused</strong> cannot be taught in one day: my personal analysis from this is that they don’t have the right <strong>mindset </strong>and haven’t been <strong>trained </strong>on this outcome-based concept. Moreover, as we are in a really <strong>uncertain </strong>environment, we might pivot every other week. In short, it is hard to change the goals so often, and it makes OKR irrelevant for our company stage.</p><p>On the positive side, we are totally “<strong>Lean</strong>”. We gather the feedback from our users, we put this in a business canvas to define what is the <strong>value proposition</strong>. We review this with our users thanks to different tools: user <strong>interviews</strong>, closed-<strong>beta </strong>features, and public beta features. This really helped us launch our first versions with a good quality last year, and even get traction from the press. We were really hyped in December 2019! However, as I mentioned above, we didn’t get the retention we were looking after, and figures haven’t reached the likes of our launch yet neither.</p><p>In terms of tools, to get those feedbacks and have <strong>qualitative </strong>ones, we implemented <strong>Intercom </strong>as a survey/chat tool, but we also decided to publish a “public” <strong>roadmap </strong>where users could help us define and prioritize our next features. To do so, we implemented <strong>Userfeed</strong>, which basically enables the users to vote up and down for the next features. Obviously, I was the one filtering it and making sure it made sense. Also, my job was to highlight the <strong>problems </strong>and avoid going directly to the solutions, as every good PM should do!</p><p>We bundled all this in a newsletter and it proved we were right to be exaggerating our customer-centricity because <strong>retention </strong>increased. However, it took and it is still taking a lot of time: not only to gather the feedbacks and re-prioritize them but also to follow up with your power users who accepted to give feedback.</p><blockquote>If you claim to be user-centric and ask for feedback, it’s your job to get constant communication with your power users.</blockquote><p>Finally, on the <strong>delivery </strong>side, with my Product Owner hat, we decided to go for <strong>KANBAN</strong>. We like the <strong>flexibility </strong>of the framework and we re-prioritize the board constantly with my partners, reviewing user feedback. Same as OKRs, I don’t think we are ready to implement SCRUM and/or Sprints yet. Still, we perform retrospective and demo sessions every other week to keep agile rituals alive.</p><p><strong><em>JL: Thanks a lot Julien for sharing all this. Before we finish, I do have some more general questions for our audience: any interesting book or article on this or in general, that you can recommend us?</em></strong></p><p>JJ: A concept that inspired me a lot is <strong>Jobs-to-be done: </strong>developed at Harvard in the 80s or the 90s (if I’m not mistaken), it is about how to keep innovating in <strong>product</strong> in general. Intercom recently published a free eBook on this that I really liked, because it is accessible and inspiring.</p><blockquote>Intercom on Jobs to be done: <a href="https://www.intercom.com/resources/books/intercom-jobs-to-be-done">https://www.intercom.com/resources/books/intercom-jobs-to-be-done</a></blockquote><p>Another article that I can share with you is about how a startup called <strong>Superhuman </strong>reached Product Market Fit, their experience, problems, and solutions were very interesting, and the article as such got a lot of tractions.</p><blockquote>Rahul Vohra, CEO and Founder of Superhuman: <a href="https://firstround.com/review/how-superhuman-built-an-engine-to-find-product-market-fit/">https://firstround.com/review/how-superhuman-built-an-engine-to-find-product-market-fit/</a></blockquote><p><strong><em>JL: Great choices indeed, and if you had to choose a couple of «cracks» that have inspired you in your journey, who would they be?</em></strong></p><p>JJ: Again, on top of my list, I will put someone from <strong>Intercom</strong>: <strong>Paul Adams</strong>, their <strong>VP of Product</strong>. In general, I think he has a good ratio between being efficient, tracking and implementing stakeholders’ requirements while keeping a product approach in such a big company. I really liked his views on <strong>Jobs-to-be-done</strong> (to echo my previous answer).</p><p>Locally, in France, I will cite two people who are “<em>Product Cracks” :</em></p><ul><li><strong>Pierre Fournier, </strong>ex-CPO at <em>ManoMano</em> who published various articles on Medium too (see: <a href="https://medium.com/manomano-tech/how-we-turned-manomano-into-a-product-centric-organization-21882d395011">https://medium.com/manomano-tech/how-we-turned-manomano-into-a-product-centric-organization-21882d395011</a>)</li><li>and <strong>Boris Golden</strong>, with whom we had the chance to work at <em>Viadeo</em>, who despite his change of role (he went from Product to Venture Capitalist), is really inspiring and helping startups to grow.</li></ul><p><strong><em>JL: We have an Intercom fan here! Thank you for your transparency. And to finish, what are the subjects you would like ProductCracks to address in the upcoming articles?</em></strong></p><p>JJ: As far as I’m concerned, it would be interesting to know about a startup who had the same problem as us at Carbo: they created a product with a defined business model, it wasn’t getting the traction they wanted at first but they finally made it (reached PMF) by <strong>iterating </strong>on their solution, instead of pivoting like we had to.</p><p>Then, another subject I am curious about is what it is like to be a Product Manager for video games. I always wondered how they apply all the concepts that we can apply for our digital content for something so vivid as a video game.</p><p>JL: Big thank you to <a href="https://www.linkedin.com/in/julien-janson/"><strong>Julien</strong></a> for supporting ProductCracks while managing the daily life and struggles of his startup and being the first to take the time to answer my questions.</p><p>You can discover more about <strong>Carbo</strong>, and start acting for the environment by downloading their app: <a href="https://www.hellocarbo.com/">https://www.hellocarbo.com</a></p><p><em>— Written by Jonathan Leonardo, based on audio interviews with Julien.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a9bd3bfb1b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From 0 to 1]]></title>
            <link>https://productcracks.medium.com/from-0-to-1-475f7ab0bd1f?source=rss-ac17f311daf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/475f7ab0bd1f</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Product Cracks]]></dc:creator>
            <pubDate>Sat, 19 Sep 2020 03:31:33 GMT</pubDate>
            <atom:updated>2020-09-19T06:59:30.299Z</atom:updated>
            <content:encoded><![CDATA[<h3>From 0 to 1: ProductCracks is born!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RR86ZusT9fP8V-1_" /><figcaption>Photo by <a href="https://unsplash.com/@connor_jalbert?utm_source=medium&amp;utm_medium=referral">Connor Jalbert</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For years I have been wanting to write a blog of my own, share my views, learn from others and refer to their work, grow my network and exchange best-practices, well <strong>moment has come!</strong></p><p>My name is Jonathan, I have been working in Product Management for almost 10 years now and moved to different countries to keep on solving problems on a daily basis. I’ve been enjoying every part of the journey, especially meeting new faces and challenges. I would say I’m a risk-taker, both at my job and in my personal life. Life has brought me to Mexico and as I am writing this first article I am working for Walmart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mEj8-JWFg_y24fXh" /><figcaption>Photo by <a href="https://unsplash.com/@zoshuacolah?utm_source=medium&amp;utm_medium=referral">Zoshua Colah</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So, what is a “<em>crack</em>”? In Spanish a <em>crack</em> is a genius or at least someone that inspires others with their skills, ideas or influence. I like the image of a <em>glass-crack</em> also that sometimes symbolizes our life as <strong>PM</strong>: whether you’re the one fixing it for your customers, your organization, your friends and peers, or you feel like you’re on the verge of giving up, or probably everything at different times of your life, I am pretty sure that it will have an impact on you.</p><p><strong>ProductCracks</strong> is the name of my project, in which I am committed to share insights and real-life experiences of Product Managers all around the world. Not only will I try to focus on <strong>great successes</strong> but also on <strong>failures</strong> and all the problems that my interviewees have overcome in their Product journey. We all have mentors and models to which we aspire; but what I think is missing in this <em>Medium</em> world today is how everyone in the world who tries new things and/or existing ideas to solve real problems for their company, applying frameworks, techniques shared by the leaders of Product Management are actually adapting it to their <strong>real life</strong>, or their actual <strong>work</strong> <strong>environment</strong>.</p><blockquote>— “Nobody Knows Anything”.</blockquote><p>My hope is that the more I will move forward with this idea, the more <strong>feedbacks</strong> I can get from all of <strong>you</strong> and adapt the content for it to be a <em>win-win </em>situation for everyone. I don’t expect to be right every time and like all good PM’s, it’s a learning process.</p><p>Does that sound like something <strong>you</strong>’d be into? Do you think you have a lot to share on your side? Well, do not hesitate to drop me a line at <em>productcracks@gmail.com</em> and let’s discuss with an open-mind what you want and can tell to the whole world. If we can meet in person, coffee, coconut water or beer is on me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=475f7ab0bd1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>