<?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[Convelio Insights - Medium]]></title>
        <description><![CDATA[Discover our way of working within the product team at Convelio. From improving tech velocity to making more data-driven decisions and doing continuous discovery, learn about what we do and how we do it. Concretely. - Medium]]></description>
        <link>https://medium.com/convelio-insights?source=rss----32fcc132d003---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Convelio Insights - Medium</title>
            <link>https://medium.com/convelio-insights?source=rss----32fcc132d003---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:42:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/convelio-insights" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Stop shipping new features, improve what you currently have]]></title>
            <link>https://medium.com/convelio-insights/stop-shipping-new-features-improve-what-you-currently-have-97868f1bad30?source=rss----32fcc132d003---4</link>
            <guid isPermaLink="false">https://medium.com/p/97868f1bad30</guid>
            <category><![CDATA[features]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Matthieu Harder]]></dc:creator>
            <pubDate>Tue, 29 Dec 2020 11:24:27 GMT</pubDate>
            <atom:updated>2020-12-29T11:24:27.317Z</atom:updated>
            <content:encoded><![CDATA[<p><em>It has been 9 months since I joined Convelio’s Product Team. During this 9 month period, the company has grown across every department and we have doubled our client base — we now work with more than 1,400 companies worldwide. From a Product perspective, when we were faced with this challenging growth, mistakes were made that led to crucial learnings.</em></p><blockquote><strong><em>How can we reach product excellence: is it by building new features or by getting the basics perfect?</em></strong></blockquote><h3>Race to feature: from euphoria to disappointment</h3><p>Convelio’s vision is to provide the leading art ecosystem to ship valuable goods worldwide. At its core, our vision relies on technology, and consequently the product team to drive it. To do so, we have been building a fluid and modular digital service experience, from quoting, booking and tracking shipments of artworks.</p><p>Obviously, it was a lot. Our roadmaps bursting at the seams, we had endless lists of customer needs, but fuelled by a palpable enthusiasm on the large range of products to grow… At this moment, we were in a race to feature and were pushing hard to deliver new features, regardless of the cost. With hindsight this was a mistake, and a good way to consider the pitfalls and learnings is through the <strong>metaphor of the Formula 1 racing world</strong>.</p><p>To start out, we saw ourselves as a <a href="https://www.formula1.com/en/latest/article.a-beginners-guide-to-f1-slang.1Pg6tvGZ2y7u4KAnc8WXGl.html">Formula 1</a> racing team dealing with better than <strong>optimal conditions</strong>:</p><ul><li><em>A full season of sun and a dry road, bringing with it a confidence that each race will be finished without any stop — the flag will be green, the track will be clear</em></li><li><em>A bunch of sexy fast cars available, with unbeatable engines and strong adhesive tyres</em></li><li><em>A dedicated and unlimited crew to help build and improve each car so as to win as many points as possible</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J-EeFzEdFEA4Lfmk.jpg" /><figcaption>Convelio’s product team : sponsored by Red Bull to deliver by night</figcaption></figure><p>In fact, the reality was a bit different. If we consider the <strong>F1 car to be the product and the pilot to be the user</strong>, then here are my top findings when trying to compare it with my daily routine as a Product Manager (to preface, yes, I spent a few hours binge watching F1 races, and have been hugely influenced by both seasons of Netflix series “Drive to Survive”. I thoroughly recommend it):</p><blockquote><strong>The weather was fickle, making the road slippy and pieces of debris would get lodged in the car. </strong>At this point, the yellow flag is waved, the safety car steps in and every driver must slow down with overtaking prohibited.</blockquote><p>Technical debt to fight, hidden impacts, cross-product interdependencies… Focusing exclusively on releasing new features usually means introducing uncertainty and/or complexity. Although the result is user delight, which is cool, but does this bring real, long term value? Every new feature is a new race and there is no insurance you will get points at the end — which means no insurance to deliver instant value to the user.</p><blockquote><strong>The car remains the same but it is constantly being adapted</strong> (regulations say only 3 engines for the full season meaning that you have to work on them, and 3 ranges of tyres that play a significant role in the performance of the car — hard, medium, soft — depending on the weather’s conditions).</blockquote><p>Does the data show that your wheel is blistering and so it is negatively impacting your performance? Box, switch, adapt. Working on the existing core features before adding new ones will be more impactful for the customer, who was probably aware of what was wrong. <strong>At Convelio, our experience shows that adding new features can permanently harm the product, as this strategy centralises quantity at the expense of quality.</strong> The lifecycle of a feature starts in conception (with ideation, business and tech scoping, identification and implementation of tagging events that will drive and justify further adjustments) and it ends in post-production with analytics and user feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/0*I1EUnbYCY0F5_AJH.jpg" /><figcaption>The undercut strategy can be applied to Product too, where you need to balance risk and research</figcaption></figure><blockquote><strong>The pit crew is not extensible</strong> (you only have up to 20 mechanics) so on race day everyone must be super reactive, as every second matters when pitting for a pilot.</blockquote><p>CPOs/CTOs have a dream: <strong>to build independent squads for each product of the ecosystem</strong> with dedicated resources in UX research, Design, Product and Tech. The problem is that in most cases, we have to make the most out of limited resources. The primary resource is the team and we have to figure out how to maximize everyone’s time/capacities to deliver instant value for the company (and the users). Putting the pilot in the best conditions is all about strategy. And strategy starts with prioritization.</p><p>Here is what happened at Convelio.</p><h3>Under the dome</h3><p>When Q3 2020 came to an end, it was time to draw harsh conclusions: <strong>too many initiatives had been started, but not so many closed</strong>. It appeared that we had grown too far from our users, and had been giving less interest to interviews and collecting feedback. The so-called “feature factory” mentality took over while we already had a performant backbone of core features to keep alive.</p><p>So we took a U-turn.</p><p>The next OKR session saw the team being aligned on 2–3 main objectives per product with <strong>1–2 big features to ship and a few candidates</strong> if we were faster than expected. Better launch a few important ones than nothing!</p><p>That’s how we entered Q4 2020, also by taking advantage of a newcomer within the Product Team. We directly had him perform a full UX/UI audit of<a href="https://web.convelio.com/get-a-price"> our customer platform</a>: quoting, booking and billing steps, saved quotes and order lists, and document management… Every single section has been combed through his fresh eye! <strong>From this audit, we identified quick wins and more impactful changes to implement</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfBeEm2IYgz4T2iCRcH_Vw.png" /><figcaption>Full audit of our quoting platform with 1st prioritisations</figcaption></figure><p>Meanwhile, we made a new structure to drive change:</p><ul><li>Implementation of <strong>weekly Design Reviews</strong> to better identify and prioritize features, as well as quick wins</li><li>Set-up of a<a href="https://www.productboard.com/"> <strong>Productboard</strong></a><strong> as our insight collection tool</strong>, so as not to lose any user feedback, whatever the product</li><li>At least <strong>3 user interviews a week</strong> to make sure we stay on track, and stick to our clients needs</li><li>Development of a <strong>data-layer</strong> that will give us accurate and insightful data to help us drive product decisions</li></ul><p>That’s how we realized that a huge part of user questions were linked to existing features and could be easily tackled with quick improvements <strong>to eliminate confusion &amp; reduce friction</strong>. Sometimes, developing a quick fix can be done in a single day… For example, by reducing the number of basic questions posed to our Operations team with valuable fixes/wins, we can save them a lot of time so they can process more order requests, which in turn generates more revenue, so contributes to support the company’s vision (scroll up if you forgot the Convelio one). And that is an example of one isolated quick win.</p><p><strong>Sometimes, sexy doesn’t mean worthy</strong>. Think about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sYeczzN9KcCTJ2sD.jpg" /><figcaption>Cocorico, the What’s New section is full of valuable fixes!</figcaption></figure><p><em>2020 has been a pretty challenging year: the company’s growth forced us to reduce our ambition, and rethink our organization. Within the Product team, our objective is to bring 50% of clients online by the end of 2021. Although this is still ambitious, we are moving forward with a renewed strategy and I have the feeling that we’ve never driven better before.</em></p><p><strong><em>Feel free to comment below. </em></strong><em>If you enjoyed this article, please hit that clap button to help others find it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97868f1bad30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/convelio-insights/stop-shipping-new-features-improve-what-you-currently-have-97868f1bad30">Stop shipping new features, improve what you currently have</a> was originally published in <a href="https://medium.com/convelio-insights">Convelio Insights</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product rituals : don’t force to fit in, find your own ones]]></title>
            <link>https://medium.com/convelio-insights/product-rituals-dont-force-to-fit-in-find-your-own-ones-2cefc12e09d7?source=rss----32fcc132d003---4</link>
            <guid isPermaLink="false">https://medium.com/p/2cefc12e09d7</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ritual]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Matthieu Harder]]></dc:creator>
            <pubDate>Thu, 06 Aug 2020 10:00:23 GMT</pubDate>
            <atom:updated>2020-08-06T09:50:38.873Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product rituals : don’t force to fit in, find your own ones</h3><p><em>As each product team has its own size, composition, resources and mentality, product rituals must be adapted to reach efficiency. Raising money to enter the scale-up companies family doesn’t mean that you will instantly be able to build fully fledged feature team and that’s why most of the time, frameworks we are learning in books are utopias. It just depends on the stage you’re at!</em></p><p><em>Consider this short article as a PM testimonial who has freshly jumped from a restrictive environment to a more flexible (though rocky) one.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*xC08uN9buGtQorVY" /><figcaption>Starting a PM career as a consultant is definitely the best springboard you can dream of</figcaption></figure><p>After 3+ years working as a product guy in a consultancy firm, I have spent most of my time learning theoretical stuffs in books and videos, trying to concretely apply them on mid-term missions. To become the next PM rockstar (I prefer rap music though), I’ve been pretty much advised to learn complex models that needed to be crossed with an endless list of frameworks/workshops, without even looking at how the team was set to behave. Among them : product rituals.</p><p>The reality is that 80% of what I’ve learned turned to be non-applicable/suitable/pertinent to the concrete situations I’ve faced (I feel you Pareto). And when it came to weekly product ceremonies (daily stand-up, scrum of scrum, project synch, retros), people were often complaining : “time-consuming and productivity killer” (1h daily foosball games weren’t that frowned upon though).</p><p><strong>Look around you and don’t force to fit in</strong></p><p>Then, early in 2020, I had the incredible opportunity to start something new. Same job but in a fast growing startup, amidst a freshly built out product team, with the possibility to run experiments in the discovery and delivery areas.</p><p>After a bunch of mistakes and trials while working on releasing new features/products, we came to rely on specific rituals to pave us the way through the uncertain road of Product Development. As a team, we decided to get rid of the common ones to explore ours, with this particular context :</p><ul><li>The COVID-19 pandemic was spreading worldwide and forced people to spend most of their time behind their screens (so the “less is more” motto when it comes to meetings became even more true)</li><li>We are a pretty small Product team — 1 head of Product, 2 Product Managers, 2 Product Designers, 1 UX Researcher and 1 Data Manager— working on 4–5 products at once (both internal and external), and trying to optimize the strength of each people</li><li>We implemented some affordable tools for analytics (Hotjar, Intercom, Mailjet or Google Analytics to name a few) and Product Management purposes (Miro, Notion) to both understand how to remain customer-centric and better organize ourselves</li><li>We all are on the same wavelength (and it’s crucial)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*W2amxyLN52tFfJmm.jpg" /><figcaption>Jeff Sutherland and his devoted theoretician Scrum Masters (or Maharishi Mahesh Yogi with four talented insects)</figcaption></figure><p><strong>Let’s play a “pick and choose” game</strong></p><p>Product rituals are deeply rooted into your organization mentality and resources. Here is an overview of what we implemented at <a href="https://www.convelio.com/fr/accueil/">Convelio</a> to be as efficient as possible in both Discovery and Delivery, involving internal (OPS ans Sales team) and external (end users) stakeholders :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CFWw1LuXm9rL8-Szan_gRQ.png" /></figure><p>As you can see, we don’t do meetings such as daily stand up, feature-scoring or any sprint relative one because we don’t feel that we need it right now (we don’t have sprint, actually). If the company keeps growing fast and the product/tech teams get bigger, we’ll probably reconsider it but for now, we simply stick to our needs (and we survived yet). Other thing to keep in mind : don’t hesitate to often ask for tech guys too at the conception stage, as matching user needs starts with technical feasibility.</p><p>Of course, all of those rituals need to be regular to reach efficiency, but they can be completed by more punctual ones, such as monthly 1-to-1 team members meetings (to get 360° feedbacks) or bi-weekly all-hands not to miss context across all departments.</p><p><strong>You’ll never walk alone</strong></p><p>You might not be a Celtic or a Liverpool fan (both champions this year, clap clap!), this sentence is still applicable for you. If you try to talk to some Product Guys who work in booming/hot companies (I did ask some friends of mine, PMs in startup of similar stages, for advices about their product habits), you’ll see that a huge part of them won’t follow basic routines as it will just slow them down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*gLgVMilc1munbyBN" /><figcaption>Old firm game excitation. Almost the same when it comes to turn user data into something tangible.</figcaption></figure><p>Don’t fear customizing your own rituals : it will help you build empathy and appreciation within your multidisciplinary team, with each member of the team owning one. Focus on those that will bring the most value to better gauge feedbacks and help you adjust your product roadmaps consequently.</p><p>Pretty easy to implement, so try at least!</p><p><strong><em>Feel free to comment below. </em></strong><em>If you enjoyed this article, please hit that clap button to help others find it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cefc12e09d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/convelio-insights/product-rituals-dont-force-to-fit-in-find-your-own-ones-2cefc12e09d7">Product rituals : don’t force to fit in, find your own ones</a> was originally published in <a href="https://medium.com/convelio-insights">Convelio Insights</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to conduct market and user research — the “series A startup amidst a pandemic” version]]></title>
            <link>https://medium.com/convelio-insights/how-to-conduct-market-and-user-research-the-series-a-startup-amidst-a-pandemic-version-26057749089c?source=rss----32fcc132d003---4</link>
            <guid isPermaLink="false">https://medium.com/p/26057749089c</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[paris]]></category>
            <category><![CDATA[logistics]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Yi Zhang]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 13:59:45 GMT</pubDate>
            <atom:updated>2020-07-02T14:08:24.251Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How to conduct market and user research — the “series A startup amidst a pandemic” version</strong></h3><p>In my four short months working in Paris in product and strategy at <a href="https://www.convelio.com/">Convelio</a>, a digital freight forwarder for fine art, I’ve learned three important things:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gk3VdfPWeEGPpvgP" /><figcaption>Photo by <a href="https://unsplash.com/@dnevozhai?utm_source=medium&amp;utm_medium=referral">Denys Nevozhai</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Lesson #1: </strong>The best baguette in the world is from Boulangerie Emmanuel Martin</p><p><strong>Lesson #2: </strong>Simplifying transport and logistics is actually quite complex, product and operation wise</p><p><strong>Lesson #3: </strong>Strangers can be incredibly helpful (and no, I don’t mean Parisiens. I already knew they were nice, which is why I chose to live here!)</p><p>When my colleague, Rita, and I were first tasked with our “New Segment” project, where we were in charge of finding a new market for our company to enter and then building a product for it, we weren’t entirely sure where to start. All we knew was that a huge portion of our work was going to involve interviews with relevant experts and customers in each industry. Some of these interviews were designed to better understand the markets we were looking at to assess which one made sense to enter. The rest revolved around user research and user testing.</p><p>User research, as I had learned, is the understanding of your audience’s behavior, pain points, and motivations in order to create the most suitable product for your user, together with your user. The information from user research helps to build personas and craft user journeys so that we can truly empathize with the person we are building for and what the process he/she is going through for each use case. With that, we then have an idea of the greatest problems to solve, and can then ideate on solutions and features that would then be prototyped, tested, and iterated upon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sEZqY4-0shFaul7E" /><figcaption>Photo by <a href="https://unsplash.com/@dtravisphd?utm_source=medium&amp;utm_medium=referral">David Travis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We had no clue how to get all the industry and user research we needed to get done — we were in the midst of the COVID-19 pandemic, where budgets were tight and schedules were even tighter, both internally and externally. However, three months, a set of market and user research, and a round of user testing later, I think we finally found a rhythm to recruiting candidates… and it all ties back to strategic sourcing, building rapport, and letting Paris lesson #3 do its thing.</p><h4><strong>Strategic sourcing</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Eq9eZG0I-d-cC2q" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine you’re trying to get experts in the medical device field who can speak to logistics. What do you do?</p><ol><li>Search “medical device logistics” on LinkedIn and send the same generic connection note to every individual that shows up. After all, it’s a numbers game, so the more messages you send, the higher chances you have of getting a response!</li><li>Curate a list of medical device companies and specific roles at each that are of interest to you. Then, with that list, ask your network for connections and, in parallel, sift through relevant profiles on LinkedIn. Choose the top results from your network and LinkedIn to reach out to with a well-thought out message based on their experiences.</li></ol><p>If it isn’t obvious, choice #2 is the best approach here. Being deliberate with who you reach out to and thoughtful about your messaging will help increase your chances of getting a response. After all, you wouldn’t yell at the janitor in a grocery store for a refund on an expired purchase. You would politely go to the customer service desk and explain the situation and that you would like to be reimbursed. The same applies here — people are more than happy to help if they find they are well-positioned to do so and are asked thoughtfully, especially if part of helping means being able to rant about pain points!</p><h4><strong>Building rapport</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0-nehCdpTJ71prBt" /><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>Great, after all your hard work sourcing candidates, you’re finally entering your first interview! Now what?</p><ol><li>Thank the interviewee for taking the time before bombarding them with your seemingly endless list of questions. After you’ve gotten all the information you were looking for, you find a way to amicably end the call.</li><li>Thank the interviewee for taking the time and provide context on why they are speaking with you today. Conversationally ask questions and read the interviewee, making sure you aren’t overstepping any boundaries or creating an uncomfortable atmosphere. Finally, at the close of the interview (and if it seems appropriate), ask if they would be interested in keeping in touch.</li></ol><p>Once again, #2 is the right choice here! We found that candidates tended to be much more helpful with our research when we were conversational and tried to truly connect with them. In fact, if the conversation turned out to be unfruitful, they often suggested connecting us with more relevant colleagues of their own accord, or dug around to relay to us information via a follow-up email. Building rapport also helped us throughout our project — we encountered many individuals who were interested in the work we were doing during our research phase and voluntarily raised their hands to participate in our user testing a few weeks down the line.</p><h4><strong>Letting helpful strangers… help</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L4Yn3sCjUeaazd9i" /><figcaption>Photo by <a href="https://unsplash.com/@tyler_milligan_visuals?utm_source=medium&amp;utm_medium=referral">Tyler Milligan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a type A/ENTJ/Achiever-Challenger/Virgo (the list goes on), I understand how unnerving it feels to rely on others to take your work to the next step. In fact, I would much rather have full control of every component involved in a project, so that I can direct where it goes. However, when it comes to getting the right candidates for industry and user research or testing, this isn’t possible. What is reassuring, however, is that if you’ve set yourself up by sourcing suitable candidates strategically and building rapport with well-connected individuals, you’re already more than halfway there. Now, you just have to be patient as your interviewee base grows. After all, you’ve already done your best on your side, now trust in the best in people to do their part. Strangers are much more helpful than they may seem at first.</p><p>And the best part? After all this, those strangers will no longer be strangers anymore. 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26057749089c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/convelio-insights/how-to-conduct-market-and-user-research-the-series-a-startup-amidst-a-pandemic-version-26057749089c">How to conduct market and user research — the “series A startup amidst a pandemic” version</a> was originally published in <a href="https://medium.com/convelio-insights">Convelio Insights</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>