<?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 Lainne Capili-Renard on Medium]]></title>
        <description><![CDATA[Stories by Lainne Capili-Renard on Medium]]></description>
        <link>https://medium.com/@lainnecapilirenard?source=rss-4954deedbc69------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KAqxFCsIwg7oqtHTOVEwAw@2x.jpeg</url>
            <title>Stories by Lainne Capili-Renard on Medium</title>
            <link>https://medium.com/@lainnecapilirenard?source=rss-4954deedbc69------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:14:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lainnecapilirenard/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 I fell in love with Product]]></title>
            <link>https://medium.com/@lainnecapilirenard/how-i-fell-in-love-with-product-2c0dd6e7a193?source=rss-4954deedbc69------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c0dd6e7a193</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-culture]]></category>
            <category><![CDATA[product-management-skills]]></category>
            <dc:creator><![CDATA[Lainne Capili-Renard]]></dc:creator>
            <pubDate>Tue, 22 Jul 2025 21:10:51 GMT</pubDate>
            <atom:updated>2025-07-23T21:45:11.493Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cnIOl46F0GZYx0oy6qCslQ@2x.jpeg" /><figcaption>Photo by <a href="http://www.paypal.me/benkolde">Ben Kolde</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Finding meaning beyond the features: My (un)expected path to Product</h3><p>Little did I know, in my early twenties, as I was finalising my dissertation at university, I was already being moulded into rationalising why product culture exists. My research was about «Fire fighting in IT», sounds catchy, I might say, and even my mentor thought so!</p><p>My paper was specifically around both project and business-as-usual change requests, and why we have to deal with user issues and system breakdowns like firefighters, always reacting quickly to problems that pop up without warning.</p><p>The change management mentioned here is the process of dealing with our so-called backlog and not your change management linked to handling digital transformation or reorganisation, etc.. Nevertheless, whatever change you’re about to bring onboard, it has a goal, and you must aim to understand the “why” that change is needed and who it’s for.</p><p>By the end of the noughties (or 2000s in some regions;-)), yes, the separation between IT and business was very rife. Cross-functional teams and collaboration were not the norm. However, I would be lying to say that it isn’t the case anymore, because I’m still in that environment. I’m not that old, so maybe we’ve been left behind by what’s going on and missed the train millions of times, or it’s just that some cultures are hard to break.</p><p>Going through my final report, everything I have written still resonates well with me today, and it gives me chills about where I stand now. It was not by chance, but by the pure logic of the idea to put the user at the centre and nourish that very thing that provides value to that user (the product).</p><p>Below is an extract of my report about three of the many challenges we faced back then, which still ring true today!</p><h4>Let’s estimate the work without understanding the problem</h4><blockquote>‘Attention is still too heavily focused on the technical questions and not enough on the main obstacles: the “management” and “people” issues’.</blockquote><p><em>In a previous field study, Weiss &amp; Anderson Jr. (2004) supported Murchison’s views that analysis should be focused on the ‘human’ factors of the project or change and not much on the detailed analysis based on capital expenditure on hardware and software. McManus &amp; Wood-Harper (2007) supported this argument wherein tools and methodology alone are insufficient to achieve success because they isolate the IT practitioners from the issues, risks, and ambiguity of engagement with people. A good understanding of these management issues will likely result in a successful systems change.</em></p><p>This approach of estimating work, which is what I take from “capital expenditure” on software (more in my line of work), is something I’m not so drawn to. It’s much harder in software as there are so many things that could arise, and just so many things that we don’t know, which could totally make the estimations so pointless. It gives the wrong focus, which is solely on the delivery side rather than the discovery.</p><p>What I like about this extract is the fact that we’re so much into the solution space without even taking a step into the problem space and working with people who will benefit from the product. This creates, as explained, a lot of ambiguity and assumptions that are not tested because we think we know our users more than they think, and our intuitions are the way to go. Unfortunately, it just raises the risk of user engagement and, at worst, having a product with features that do not address any need or solve any pain points.</p><h4>User involvement is close to none</h4><blockquote>In reality, the involvement of everyone, such as representatives, users, and business process owners, cannot be achieved all the time. However, it is still highly desirable to include as many as possible because it is critical in the analysis and design of the system (Bocij, et al., 1999). It has also been suggested that focus must be on the participation of ordinary business users as opposed to the power users (experts of the system), as they are more difficult to manage, and if involved right from the start, there will be less change management issues once the system goes live (Fuchs, 2004).</blockquote><p>There goes empathy, I hear Design Thinking ringing in the background. Involving our end users from the start and humanising the product we’re creating.</p><p>This mirrors well the personas we create to understand the characteristics of our target users. If our product is designed in a simple way, and you manage to bring on board the least likely to use your product (the newbies), then you’ve hit the right spot! The goal is to make it accessible, understandable, and convert as many users as possible.</p><p>The change management issues described here are the results of the change requests, most likely not fully understood by the so-called “IT practitioners” delivering the system change or the feature. That change itself constitutes our product.</p><h4>Low quality of interaction with the users</h4><blockquote>On the other hand, user participation alone does not seem to be compelling enough. Involvement of users driven by a good quality of interaction with the system developers is a way that can largely affect the outcome of the system change (Amoako-Gyampah &amp; White, 2003).</blockquote><p>Outcome, wow it’s me talking 18 odd years ago, and yes it’s me evangelising outcome over output now! The quality of interaction as we know it today is usability testing, interviews, observation, focus groups, or simply putting your product live in production with your alpha, beta testers, or even your real users, for those who are more advanced in the Product space. It simply means having direct access to your potential users or a panel that represents your personas well, helps you gain that understanding of what to build, and directly impacts the outcome you’re aiming for. Whether you aim to onboard your users in less than a minute, with your sleekest design, or encourage users to save regularly for their retirement using your platform.</p><p>Not having the space to explore problems and solutions to these problems, before diving into development with close access to your users, can bring a lot of costly surprises, as would a traditional Waterfall project. Even being agile on the fact that you iterate every 2, 3, or 4 weeks (make your choice), but you’re building with a lack of feedback or a non-representative panel of end users, then you’re just reiterating on the wrong things.</p><h4>The product love story</h4><p>Just as when you love something, the motivation comes naturally. You’re driven by passion, and what you do just manifests through your actions.</p><p>I haven’t found anything more rewarding than learning in action and observing users fulfil their jobs and alleviate their problems through something I contribute to produce and co-design.</p><p>I guess this motivation comes from the fact that having a product culture embedded in the way I work serves as an anchor to remind me that my job is to create an impact and a positive outcome. I’m delivering something with a purpose. Even more, it makes my job meaningful.</p><h4>Long road to happily ever after</h4><p>Even love, like product culture, requires more than passion; it demands perseverance, adaptability, and a healthy dose of patience. There’s no fairy godmother in sight, just a continuous path toward what matters most.</p><p>I strive to champion this mindset, even among those most resistant to change.</p><p>Communication is a powerful tool that kickstarts the journey; just raising awareness to pass the message across already makes a difference.</p><p>Setting goals grounded in real problems, reinforced by meaningful metrics, is already a big step forward. Even if getting those metrics seems like a battle in the field, when your backlog resembles a game of survival and data takes a backseat to urgency, progress feels like an uphill battle.</p><p>So I say, be resourceful, do usability testing through your network, everyone is a user one way or another. We’re intelligent enough to find the right panel and get that «learning» engine started, as Eric Ries would say. Some say Lean Start-Up has had its moment. I say learning without excessive cost or premature development is still our sharpest tool (our biggest ally), especially in sales-driven landscapes, where resources are guarded and we don’t have the modern tools others use to develop and experiment quickly.</p><p>The road to happiness isn’t paved with grand gestures. It’s carved by small, intentional steps within your sphere of control, grounded in what you value and who you are. That’s how meaningful change begins ; and where product love truly lives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c0dd6e7a193" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rolling out Agile Transformation]]></title>
            <link>https://medium.com/@lainnecapilirenard/rolling-out-agile-transformation-2a901f3a6eee?source=rss-4954deedbc69------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a901f3a6eee</guid>
            <dc:creator><![CDATA[Lainne Capili-Renard]]></dc:creator>
            <pubDate>Wed, 11 Oct 2023 20:12:52 GMT</pubDate>
            <atom:updated>2023-10-11T20:12:52.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxAhjpkTRroDkONNF7if4A@2x.jpeg" /><figcaption>Photo by Ian Schneider on Unsplash</figcaption></figure><h3>4 key things that will make or break it</h3><h4><strong>Culture</strong></h4><p>This is the classic but indispensable first step into transformation. But sadly we still get it wrong. It’s all about the value that we uphold as humans that drives our actions and behaviours. There’s this saying that if you share the same values with someone, together you can do wonders!</p><p>If the cultural shift is not driven by value and where the agile mindset is not embedded, then there will be no shift ever.</p><p>We could call it a transformation but only on paper and not in action. As I’ve witnessed in my experience, this is what’s happening.</p><h4>Motivation (WIIFM)</h4><p>What’s in it for me?! If there is no tangible or intangible effect, then why would I do it?</p><p>From a personal perspective, I believe that motivation comes from within. It’s something that you are passionate about and no matter how tough it gets, you persist.</p><p>So the question to ask is, if the organisation doesn’t literally share the same values like each of the individuals working inside it, then the chances are that, the motivation to transform will likely be a challenge or even close to a failure.</p><p>Yes, we can talk about motivational speeches, but if people are not interested or not into it, then it’s likely going to be a battle. Like in the old management principles, we talk about “Change Management”. More often than not, it’s imposed by the top and not really a bottom up approach. Now that makes it harder.</p><p>Although it still does work sometimes, once we’ve enlightened our people and have given them the benefit of the doubt and guide them through this daunting unknown world of “change”.</p><h4>Infrastructure</h4><p>Let’s say you have the ideal culture and people are motivated, then you are one lucky ghost! It’s a dream team!</p><p>You’ve done the hard part, now it’s time to equip your team. Yes it’s about the behaviour, more than the process, but if you are not ready to break the old architecture, and look into the future, you will just demotivate these bunch of people who are hungry to make it work! You will leave them frustrated, because they don’t have the technical environment to discover, deliver and experiment those outcomes with the product or service they’re offering!</p><h4>Tools</h4><p>Last but not the least, are the tools! Like a handyman, we need our toolkit to solve problems or even make something entirely new. I like this analogy, as we call it a toolkit in our industry just for that very obvious reason. People need to be in continuous learning mode to keep up and produce or deliver valuable products and services. So tools mean, the support for learning, room for innovation, product discovery, which all lead us to specific techniques to apply to specific problems and situations.</p><p>The idea is to really champion this and encourage people to learn, to grow, to fail and to learn again. Give them the tools they need to produce something wonderful.</p><p>The usual training process, should be more around creating that community of practice, rather than ticking boxes on the number of trainings provided, which could be or not be relevant at all to the overall outcome they are trying to work on.</p><p>The 4 key things I’ve highlighted are from my experience, at the very least, the factors that we must address in high priority. It’s not exhaustive and I’m sure that a total transformation entails more than this, especially if you’re starting from scratch.</p><p>Evangelising people to something totally alien to them or out of their comfort zones is not an easy task. We need to listen and work on a collaborative approach, whilst leveraging on the benefits it could bring to your people, your business and most importantly your customers.</p><p>To wrap things up, it’s a journey and not a race. We must keep our eye on the goal and know the essence of why we’re doing it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a901f3a6eee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to survive in a non-agile environment and keep your agile mindset]]></title>
            <link>https://medium.com/@lainnecapilirenard/how-to-survive-in-a-non-agile-environment-and-keep-your-agile-mindset-a69fd223544d?source=rss-4954deedbc69------2</link>
            <guid isPermaLink="false">https://medium.com/p/a69fd223544d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile-mindset]]></category>
            <dc:creator><![CDATA[Lainne Capili-Renard]]></dc:creator>
            <pubDate>Mon, 08 May 2023 19:34:28 GMT</pubDate>
            <atom:updated>2023-05-08T21:07:07.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1nOzJlOzY1Vf8YZ1" /><figcaption>Photo by <a href="https://unsplash.com/@paulfiedler?utm_source=medium&amp;utm_medium=referral">Paul Fiedler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You may probably be able to relate if you work for large organisations notably in financial institutions (banks, insurance, etc..) for example, where the agile way of working is still not yet the norm.</p><p>The organisation itself is constructed in such a way that everyone has specific tasks that they have to deliver, boundaries are set, rules are written in black and white and crossing these boundaries, will make you feel like you are doing something wrong or that oops you’ve crossed the line!</p><p>It may feel alien in this day and age but it still does exists. So how do you survive it?</p><p>From a personal perspective I have listed 6 things that kept me going and most importantly how I have used the values and Agile mindset engraved in me to perform my role effectively without losing my agility.</p><h4>Context</h4><p>First, try to understand why the organisation is setup in such a way. Look at it from a global perspective to see the big picture. Financial institutions to name a few are highly regulated and very information intensive. My 9 years experience in the industry has taught me that producing high quality deliverables, rigorous reporting are mandatory, otherwise you are subject to fines and will not pass audit inspection. The stakes are indeed high and so there are specific departments who have specific tasks for producing certain reports and deliverables for that very reason.</p><p>But does that qualify to keep the silos? Of course not! The more the stakes are high, the more we could benefit from the Agile state of mind as the shorter the cycles, the lesser the risks! But then why? Well, a former manager once told me, if there’s no pain then there’s no reason to change. I was searching for answers and there I have it!</p><p>What she said, totally explained in simple terms the situation, why change is not imminent and the organisation is content as it is. So even within this highly regulated environment, we could still do things the same way and producing data intensive reports doesn’t call for much digital advancement and the manual way of doing things still does the job. After all, there’s still a bit of a hesitation on the back office side and report generation for that matter, because you can’t easily demo a report or how you have calculated the value in that particular field, as opposed to front end we you can actually see the impact of what you have done through user experience. So if you’re on the former, it’s harder to penetrate this area.</p><p>So <strong>context</strong> means, <em>what</em> (the origin of such structure) and <em>why</em> (is there a reason for changing?)</p><h4><strong>Keep your eye on the goal (Value)</strong></h4><p>Yes you have the context, now is the time to decide whether to persist or not. In my case I did! Now as for my job, I know what my goal is, it is to deliver value!</p><p>How the value is delivered is equally important as it can affect the fact whether you can actually deliver that value or not! So I focused on the means of delivering by adapting myself to the environment I found myself in and worked in thorough collaboration with siloed teams in order to get the job done. I learned the ins and outs from lengthy specifications, to complicated business rules (people validating almost every sentence that you’ve written!) and even writing the solution myself (as opposed to the requirements!) but what came out of this daunting exercise is, in the end, everyone had the same understanding of what’s required (transparency) Although there were still some surprises in the end, as we can never predict the outcome, we could only improve based on feedback!</p><h4><strong>Champion the change (Agility has no end, it is as constant as change)</strong></h4><p>They don’t want to change but why insist?!</p><p>But change is good and taking small steps at a time is healthy. So that’s what I did! I introduced a change in the way we collaborate from internal siloed teams to involving stakeholders up front, keeping them in the loop of all communication. This has eliminated redundant meetings to refine requirements, as we could answer most questions when we are with a diverse set of people having different domains of expertise, bringing valuable input together. Again this is linked to the second point which is “Keeping your eye on the goal” and to get the buy-in, you have to explain the fact that you’re all in this together (same objective)!</p><p>There’s a caveat here though, because in most non-agile teams (BA, DEV and TEST in the olden days) their objectives are limited to the tasks they are set to do (delivering specification, developing and testing) and not driven by result of the overall cross functional team effort.</p><p>But then again it’s that cross functional team effort that provides the personal satisfaction of making your stakeholders happy and delivering value, which in fact is the real goal! Who wouldn’t want that piece of satisfaction? I do!!</p><p>As our job is to deliver service through enhancing existing applications, I have also aligned with my stakeholders on what matters most in terms of business and operational effectiveness. I oriented them into defining these values in concrete terms in order to help them set their priorities right and give them a reality check on what we could possibly do in the short term.</p><p>Challenging the existing ways calls for a change!</p><p>I have always worked in this manner, although I could have given up with all the obstacles I have encountered (infrastructure is not ready, teams are built in a specific way, there is a standard process, etc..) but I didn’t because I kept highlighting the issues and also the benefits of changing!</p><h4><strong>Don’t be afraid to say “No”</strong></h4><p>Having an agile mindset also means not overcommitting. The goal is to deliver what we could within a set timeframe and quality is not a side goal but rather a natural part of the increment. Once you overcrowd your backlog to please your stakeholders, the chances are you’re likely to deliver a mediocre increment that is unlikely to be releasable nor acceptable. This is due to the fact that your team is stretched and quality decreases if you focus on that <strong><em>deadline</em></strong> with everything in it, rather on the <strong>value</strong> you’re suppose to deliver!</p><p>To do this, I have said “No” several times and not a single bit did I regret it!</p><p>Stakeholder will always put everything on top of the priority list but keep your eye on the goal “what’s the value”, what is it for? What if we don’t do it in the time they expect, what’s at stake?!</p><p>By not putting pressure on myself and the team, we were able to deliver better features with a piece of mind and enough margin for error.</p><h4><strong>Share your knowledge</strong></h4><p>Coming from the UK and moving to France, shifting work culture from a radical change driver to a more cautious one, may seem to be mission impossible! But in the end, not at all! I’m not generalising here and this is all based on my personal experience in the organisations I have worked with in the UK and in France, but I have seen the total opposites!</p><p>So the point is to pick and choose the learnings you have gained along the way, adapt them to your context and SHARE! This is where you can add value. Share the benefits of this cultural shift and share your knowledge on best practices.</p><p>The objective is to enrich the team and to improve. We are in a fast paced environment and we have to keep up. The least thing we could do is to share new insights and discover together better ways of working to better deliver our service or our products.</p><p>Agility means keeping up with the pace and to do so we must keep learning. Team and organisations always discover new ways of tackling a problem or dealing with a complex situation based on their experience. The industry is wide ranging, projects and products are nothing but simple so there will always be failures, but the beauty from it all is that we could benefit from others sharing their stories.</p><p>So I keep up by joining the internal Agile community, and sharing with the team new knowledge and techniques which I’ve learned (new ways of ordering the backlog/prioritisation, focusing on short term planning, not wasting time on estimation but using complexity and size as factors, changing the way we evaluate ourselves through new Retrospective concepts, etc…). I find the community making its impact as it does source its useful learning content looking beyond the company and exploring how competitors and those external to us have done their bit of transformation. Medium is also a good place to get a real feel of what’s happening on the field, with our peers sharing their experiences. Lastly, LinkedIn Groups such as Scrum.org, Scaled Agile, to name a few keeps me up to date on new tips and insights how to tackle everyday problem.</p><h4><strong>Practice it!</strong></h4><p>Last but not the least is practice it, it may sound mundane, but no!</p><p>Agility to me is a state of mind, where I share the same values described in the Agile Manifesto and live by it.</p><p>I keep reminding the team that nothing is constant but change, we could only plan so much, but in a fast paced world everything is changing. Priorities change, requirements get obsolete so we must embrace change.</p><p>We must focus on value adding priorities but of course, taking into account risks and dependencies.</p><p>The reminder that we can never predict the future and we must accept to learn from what we know now and also that we have limited capacity (humans doing the work) and we could only take on so much.</p><h4><strong>So where are we now?</strong></h4><p>Well at some point the benefits of an Agile culture will inevitably manifest itself through evidence based outcomes and so 3 years ago my hallelujah moment has come!</p><p>The strategy has changed its course and it was now fully understood that we have to go “Agile” well slowly but surely… there’s still a lot of work to do but I can feel the effort getting into the process of this transformation (speaking of that Agile Transformation that’s another topic!).</p><p>So today I’m part of a Feature Team delivering services across our subsidiaries in the EMEA, and in parallel a Proxy Product Owner working in Kanban mode with a focus on standardising and processing data so we can offer better products to our clients and analyse potential risks.</p><p>My team’s behaviour has changed throughout the years and I feel the openness (an important Scrum value) to their approach, which has provided a real positive impact to the way we do things today. As for my other team, their Agile culture is more pronounced and are more willing to drop things (deprioritise) and re-order the backlog in the smoothest fashion without losing their eye on the goal! It’s a pleasure to work with them, as even though we are still limited in terms of infrastructure (Continuous integration, delivery and automated testing, are all still our target for the future), the team itself is Agile!</p><p>But it’s fine, because to wrap things up, it’s all about the behaviour and not the process (I quote <em>Gunther Verheyen</em>, author of “Scrum — A Pocket Guide”). Once that mindset is embedded, everything else will come naturally as that is what drives our behaviour, and the necessary tools must be deployed to fit in to this new culture, not vice versa.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a69fd223544d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>