<?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 Mehul Modha on Medium]]></title>
        <description><![CDATA[Stories by Mehul Modha on Medium]]></description>
        <link>https://medium.com/@mmodha_69827?source=rss-424dd271d72a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*FhJgxwLE1npd7IWglE262A.jpeg</url>
            <title>Stories by Mehul Modha on Medium</title>
            <link>https://medium.com/@mmodha_69827?source=rss-424dd271d72a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:31:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mmodha_69827/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[Returning back home: Platform Architecture]]></title>
            <link>https://medium.com/@mmodha_69827/returning-back-home-platform-architecture-242b2242974a?source=rss-424dd271d72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/242b2242974a</guid>
            <dc:creator><![CDATA[Mehul Modha]]></dc:creator>
            <pubDate>Mon, 13 Apr 2020 17:13:09 GMT</pubDate>
            <atom:updated>2020-04-13T17:23:12.061Z</atom:updated>
            <content:encoded><![CDATA[<p><em>If I told you the company that I work for lets me develop new product features, engage with customers to join our movement to transform how the world builds software, support them on keeping up to date and then pitch the platform of tomorrow today, all in one year, would you believe me?</em></p><p>Here’s what my year long adventure looked like and how I rotated throughout an organisation to go from a University Graduate, to Pivot.</p><p>After completing my R&amp;D, Labs and Support rotations, I returned back to the field as a Platform Architect. This was the opportunity to take all the learnings forward and articulate how Pivotal can move fast forever, with a combination of our products and services.</p><p><strong>Fast paced, tons of challenges and never a dull moment!</strong></p><p>As a Platform Architect, our days vary. It can be anything from pitching for new business, learning about the problems customers are facing with their status quo of delivering software, presenting demos and Proof of Concepts of our platform capabilities, to working with existing customers in prioritising and moving their workloads to the cloud.</p><p>Working alongside my experienced colleagues has given me a wealth of insights and traits in what makes a great Platform Architect at Pivotal. The essences of which boil down to some key skills:</p><p><strong>Empathy — it’s not one size that fits all</strong></p><p>Every customer is unique! While the problems we have seen over the years can be similar along customers, each resolution has its nuances and therefore we work alongside the customers to develop the best strategy and solutions to help them on their transformation journey. In taking the customers through the process of discovery, scoping and iteration, we see them take pride and ownership of the transformation project and confidence in executing on the plan.</p><p><strong>Forever curious — it’s not about knowing it all</strong></p><p>As Platform Architects, we are always learning about the various permutations of customer infrastructure and developer stacks. We are constantly hearing about new combinations of technologies and how they are being used together. For us, it’s not knowing about every possible technology in use. We use this opportunity to feed our curiosity to learn more about how customers consume services to deliver value, how we can leverage the current with the new and what alternatives we can provide if they benefit the customers deliver value faster. We have a broad range of knowledge across various domains and where necessary, we delve deeper into research and present back the best options to go forward.</p><p><strong>Thinking outside the box — it’s not always a technological problem</strong></p><p>During my time shadowing my team and working on accounts myself, I have learnt that in order to understand the customers problems, you must challenge their status quo in approaching new solutions. As organisations put their application estate through transformation, they find that their way of working and processes must change as well. In order to deliver faster improvements to their end users, the process in place, governance around releasing software, security and resource management must also be reviewed. Technology is just a single aspect for delivering software, as Platform Architects we also learn and help shape the pipeline to production with our customers to ensure they can deliver software fast forever.</p><p><strong>Doing what’s right — it’s always about doing what’s best for the customer</strong></p><p>Transformation doesn’t always mean an immediate overhaul, it can be about knowing where you want to reach and building the path toward the destination. While it may seem ideal to completely break away from an organisation’s norm, it can cause turbulence. Pivotal has always encouraged starting small and proving value before expanding a transformational movement across an organisation, a key to gaining confidence in a new way of working and developing software. For Platform Architects, we take great pride in presenting the vision to our customers of what tomorrow could look like in a cloud native world. It is then our job to work alongside teams to iterate on the path to success, find small projects to transform and articulate back the benefits gained in doing so and analyse where we can make further improvement for the next project. Adopting an agile methodology means the teams themselves learn the patterns and recipes to repeat these processes elsewhere. They gain deep insights of what works well within the organisation, where else these processes can be applied and what feedback could be applied for the next iteration. In working with the customers, we impart the skill sets to enable them to replicate the success at a larger scale across the organisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X1lS-UvdhOvwX1Pj9HRAMw.jpeg" /></figure><p><em>Special thanks to my fellow PAs who have mentored me and helped on my journey to where I am now (some are missing from the picture): David Pinto, Alan Hale, Arthur Viegers, Rob Edwards, Simon Rowe, Alessia Del Vecchio, Duncan McIntyre, Spencer Critchlow, Alex Guedes, Bill Glover, Chris Burgess, Declan McAleese, Adam Fowler, Denis Baltor, Donald Forbes, Stephen Midgley and Neven Cvetkovic</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=242b2242974a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rotation 3: Support]]></title>
            <link>https://medium.com/@mmodha_69827/rotation-3-support-51d6d1ae12d1?source=rss-424dd271d72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/51d6d1ae12d1</guid>
            <category><![CDATA[application-development]]></category>
            <category><![CDATA[pivotal]]></category>
            <category><![CDATA[support]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <dc:creator><![CDATA[Mehul Modha]]></dc:creator>
            <pubDate>Sun, 26 Jan 2020 21:52:25 GMT</pubDate>
            <atom:updated>2020-01-26T21:52:25.281Z</atom:updated>
            <content:encoded><![CDATA[<h3>A graduates path to being a Pivot</h3><p>By Mehul Modha</p><p><em>If I told you the company that I work for lets me develop new product features, engage with customers to join our movement to transform how the world builds software, support them on keeping up to date and then pitch the platform of tomorrow today, all in one year, would you believe me?</em></p><p>Here’s what my year long adventure looked like and how I rotated throughout an organisation to go from a University Graduate, to Pivot.</p><p>This rotation saw me travel and live in a new country surrounded by the friendliest of Pivots, fitting for the service they provided, full of empathy and guidance. I moved to Ireland, Cork to work with our EMEA support team.</p><p>During my time in support I learnt about how to manage customer pain points, how to make a smooth support journey for their day 2 operations and most importantly how to work with customers who are looking to adopt new technologies. Challenges in support vary from very simple problems such as getting started in configuring the platform, to more subtle challenges where outcomes and behaviour of the platform is unexpected based on a combination of misconfigurations. Therefore, the art of being a support engineer is being able to walk a customer through the debugging process, identify the issues and resolve in a timely manner. Similar to the skills of a doctor, they use their experiences and expertise of the platform to triage, identify where the issues are and what can be done to remedy them. During my time in Support, I paired and shadowed with senior support engineers. Support engineers logically map the components affected by a change in process and trace the root cause of problems with expedience.</p><p>At the beginning this was confusing to me, how do they manage to find the problem so quickly? Having completed the support rotation, here is what I learnt from it.</p><p><strong>Let the patient tell you what’s wrong.</strong></p><p>The first thing you learn is to listen to the customer, their stories and their pain points. Not only is it cathartic for them, but it also uncovers the journey and steps taken to get where they are and often, provide hints you need to understand how they got into a blocked state.</p><p><strong>Collect the vitals</strong></p><p>Now that we know where the customer is blocked, how did they discover the root cause? How do the support engineers know where to deep dive and what context they need to gather?</p><p>The support engineers at Pivotal have a deep understanding of the distributed system that is the Pivotal Platform and the interactions between the components. Furthermore, all the components are designed to give out as much information about their health as they can, in the form of logs. With this knowledge, they collect as much information as they can about the components, types of errors being outputted and what causes it to occur.</p><p><strong>Diagnose the problem</strong></p><p>Now with the full context of the situation and the behaviour of the system, they are quickly able to pin down a resolution. In seeing how the system is currently behaving compared to the desired behaviour, the support engineers are able to advise the operators what component is causing issues. The support engineers walk the customer through the steps required to make the system behave as expected and provide an explanation to what they are doing to remedy the situation. In this end to end support journey, not only are the customers satisfied that their problem gets resolved, but they are enabled to learn how to debug issues themselves.</p><p>In support, Pivotal philosophy really stands here. <strong>Always be kind! Do the right thing! </strong>Customers appreciate the kindness of the support staff and working together to provide them a direction back onto the right path of resolution and productivity.</p><p><em>Special thanks to Ciaren McGuiness, Eugene Bell, Eddie Murphy, Peter Ryan, Sinaed McDonnell, Cyrille Lebas, Stefan Stamov, Stephene Higgens, David Farrell, Faisal Ali Mark Nagle and the entire EMEA support team in Cork</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51d6d1ae12d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rotation 2: Labs]]></title>
            <link>https://medium.com/@mmodha_69827/rotation-2-labs-1795941af6cc?source=rss-424dd271d72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1795941af6cc</guid>
            <category><![CDATA[pivotal-labs]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[pivotal]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[application-development]]></category>
            <dc:creator><![CDATA[Mehul Modha]]></dc:creator>
            <pubDate>Wed, 04 Dec 2019 17:34:20 GMT</pubDate>
            <atom:updated>2019-12-04T17:39:11.696Z</atom:updated>
            <content:encoded><![CDATA[<h3>A graduates path to being a Pivot</h3><p>By Mehul Modha</p><p><em>If I told you the company that I work for lets me develop new product features, engage with customers to join our movement to transform how the world builds software, support them on keeping up to date and then pitch the platform of tomorrow today, all in one year, would you believe me?</em></p><p>Here’s what my year long adventure looked like and how I rotated throughout an organisation to go from a University Graduate, to Pivot.</p><p>It was in labs where I began interacting with customers for the first time, learning the art of taking them on a transformation journey and evolving their mindset along the way.</p><p>My time in labs showed me how the practices in R&amp;D are versatile, how they can be used to impact the work of all engineering teams, even outside of Pivotal. During this rotation I was able to learn about how we engage with customers, how we enable them to build software and deliver value quickly, the Pivotal way. Labs takes Pivotal’s pairing practices and enables the customers teams to operate as balanced teams. Their product manager pair with one of ours, their designers pair with ours, and their engineers pair as well. As the engagements progress, you see these teams adopt the practices, working in collaborative ways, enabling each other, sharing context of their days work, conducting meetings to plan the backlog for the weeks ahead and providing feedback to help each other achieve the outcomes set at the start. As I shadowed through these journeys, one thing I’ve always noticed, is how rewarding it is for the Pivots to watch these customers wholeheartedly adopt the methodologies taught to build sustainable delivery practices. Furthermore, these teams go on to create something of value that their customers are really happy with, which should be no surprise, as the end user is always brought in throughout the “Labs” process to provide feedback. All of this is delivered at a fraction of the time compared to their normal delivery cycles, from a couple of months to weeks!</p><p>Labs is more than just about the engineering of the product which makes the users happy. They help the customers identify key problems, define the business value, generate ideas to solve problems, the ways to test, iterate and define metrics to validate these solutions. In Labs they also enable the business to see why adopting an agile approach mitigates risk and enables a stable development cycle which validates hypothesis quickly and lets you pivot otherwise before too much is invested. In working with the customer along the entire journey, we see the result where the customers are now delivering more than functional, reliable feature. They are now looking at whether these solutions are also usable and joyful to use. What we see is how rewarding these projects become when the users of the software provide feedback on how they are able to link a positive experience to the tools that have been developed alongside our Pivots. The outcome of the Labs process goes beyond the software. It is about enabling a new train of thought, so once the engagement is finished, these autonomous teams become thought leaders in their own organisation, taking the practices they learnt to train more within their company to work the Pivotal way, going fast forever!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/0*p4KgeD4y_ohJBeE4" /></figure><p><em>Special thanks to Robbie Clutton, Nick Street, Erin Cobb, Denisse Zavala, Jennifer Lea, Gagandeep Kaur, Hannah Harrison and Nana Asiedu-Ampem</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1795941af6cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rotation 1: R&D]]></title>
            <link>https://medium.com/@mmodha_69827/rotation-1-r-d-bb75041cdc3c?source=rss-424dd271d72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb75041cdc3c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[graduate-program]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[pivotal]]></category>
            <dc:creator><![CDATA[Mehul Modha]]></dc:creator>
            <pubDate>Fri, 29 Nov 2019 16:04:14 GMT</pubDate>
            <atom:updated>2019-12-02T23:47:29.711Z</atom:updated>
            <content:encoded><![CDATA[<h3>A graduates path to being a Pivot</h3><p>By Mehul Modha</p><p><em>If I told you the company that I work for lets me develop new product features, engage with customers to join our movement to transform how the world builds software, support them on keeping up to date and then pitch the platform of tomorrow today, all in one year, would you believe me?</em></p><p>Here’s what my year long adventure looked like and how I rotated throughout an organisation to go from a University Graduate, to Pivot.</p><p>So here is the story about my first rotation in Pivotal, at the heart of the company. Research and Development is more than just developing products! It is a place where you learn about Pivotal culture, to feed your curiosity and to hit the ground running with a safe landing zone. It was here where I gained a deep understanding of working practices that allow Pivotal to deliver fast forever. At Pivotal, the collaborative environment is taken up a notch! Two screens, two keyboards, two mice, one computer! This is the true definition of pairing, where you learn by doing together and improve your skills by learning off one another in the process.</p><p>Through this rotation I learnt about what was meant by the following statements every Pivot knows and lives by to this day:</p><p><strong>Always be kind!</strong></p><p><strong>Do the right thing!</strong></p><p>While these statements may seem ambiguous, these mantras play core to the interactions within the company driving the innovation and outcomes we strive to meet.</p><p>R&amp;D has a vast number of teams covering a range of products, from recovery, security, to open source teams. Product managers looking after each of the offerings we serve our customers, considering the product value. Designers who consider the users interaction and empathise with the users pains and engineers to execute the delivery of the product roadmap. These teams are autonomous and are truly empowered to steer the direction of these products. As engineers we pair together to code, using extreme programming (XP) practices. Every day you rotate pairs within the team to work on a backlog of work we collectively assign priority towards. Pairing ensures that the quality of code remains high! With pairing, you are working together to maintain great coding quality, spotting errors, validating the code with tests, having healthy discussions to how to write the implementations and sharing context of the code base. We are able to do what is right because the team has the autonomy to work on providing the best user features with the best experience. Deciding the direction as a team on what to deliver and when. As an engineer this is one of the most invigorating feelings, knowing we collaborate to deliver features we agree are worth developing. It is a joint effort and no one person has the weight of delivering all the value. We really do feel that we are doing what is right, and our customers feedback loop validates this!</p><p>Within all teams in Pivotal there is also continuous room for improvements and mechanisms to keep enabling individuals to strive to be better than they were yesterday. For this, we do an activity called a retro. It’s a chance to get feedback on the weeks work, what we felt went well and what we think can be better. It’s really a safe comfortable session conducted weekly allowing Pivots to learn about what it means to improve in the domains we practice, may it be an engineer, designer, even a field operator. We pair day in and day out and with this mutual respect and empathy for each other, we help each other advance and strive to be even better than we are. The rewarding bit of the process was watching my team during my time in R&amp;D continuously change and improve. The relationship built in pairing has a sense of intimacy which you simply cannot have ‘coding solo’, you learn what it truly means to Always be Kind! Whether you are working together delivering code, or providing feedback to help each other strive to greatness.</p><p>While leaving R&amp;D was hard, the culture, lessons and the friendships made remain with me. Not only did it help me improve as an engineer, it help me grow as a person. It was a great journey to understand what it truly means be empathetic, what it really means to make the right decisions and how to be inclusive in these processes, enabling people to express their concern in a productive way. It can be a humbling and rewarding experience to see how much you can improve, thanks to the courage of your peers to share valuable feedback to help you elevate yourself, because it is the right thing to do!</p><p><strong>Here is a mini-story from my time in R&amp;D</strong></p><h3>Deliver an Epic:</h3><p>While in the ‘BOSH Backup and Recovery’ team in R&amp;D, a long running customers request had been the ability to take backups frequently without having to wait long time to backup very large files. With the majority of files being the same in each iteration of the backup, they would end up with duplicates as the current solution take a whole copy. While is was a working solution there was an opportunity to improve the experience.</p><p>The team hypothesised that if we backed up in a “smart way” where we can reduce the toil on the operators and the developers (by freeing up the Command Line Interface quicker) if we can speed up the backup process. This could be done by copying only what is new between backup and then making a backup artefact by gluing together the old stuff that was copied previously with the new items. In doing so, customers could take more backups and it becomes a quicker experience on each run, as only a small difference is copied each time.</p><p>Now that we had the hypothesis, we kicked off by conducting research into some potential solutions and as pairs, began to investigate the problems with backup process of today. This meant actually going through the Operators journey of making a backing up, looking at the transfer speeds and duration elapsed between starting the backup its completion and identify the pain point today. This process is called a spike in which we learn about the problem domain.</p><p>To make sure we built our knowledge as a team, pairs rotated multiple times over this line of work, called a story. This way we manage to get everyone’s input during the story, with 7 engineers having the opportunity to work on suggesting potential solutions. As a result we manage to get 4 solutions. We used whiteboarding session to explain the technical aspects of the solutions, the complexities to implement and the processes required to make each of these solutions to work. After a 2 hour sessions in which we discussed as a team the pros and cons, we “dot voted” to come to a consensus on the solution we wanted to implement.</p><p>During the process, I got to experience how customer-centered design can be used to improve the experience of a product, how powerful it is when the team have the autonomy to understand the problem domain and develop solutions, and how a teams can collaborate to deliver successful outcomes to serve the customers.</p><p><em>With Special thanks to</em></p><p><em>George Lestaris, Emmanouil Kiagias, Sarah Connor, Chunyi Lyu, Jake Klein &amp; Glen Rodgers</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb75041cdc3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A graduates path to being a Pivot]]></title>
            <link>https://medium.com/@mmodha_69827/a-graduates-path-to-being-a-pivot-d7a96ed53cc5?source=rss-424dd271d72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7a96ed53cc5</guid>
            <category><![CDATA[pivotal]]></category>
            <category><![CDATA[graduates-jobs]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[Mehul Modha]]></dc:creator>
            <pubDate>Tue, 26 Nov 2019 09:39:44 GMT</pubDate>
            <atom:updated>2019-11-26T09:39:44.786Z</atom:updated>
            <content:encoded><![CDATA[<p><em>If I told you the company that I work for lets me develop new product features, engage with customers to join our movement to transform how the world builds software, support them on keeping up to date and then pitch the platform of tomorrow today, all in one year, would you believe me?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*EzYFsvjhXSul3K4QIznCIQ.jpeg" /></figure><p>Here’s what my year long adventure looked like and how I rotated throughout an organisation to go from a University Graduate, to Pivot.</p><h3>Day 1: A new chapter, a new challenge</h3><p>November 19th, 2018, the day finally arrived to start at Pivotal! Couldn’t wait to get going, so I grabbed my work bag and began my commute in an oddly ghost like train to Old Street in the dark. <strong>But never mind those details</strong>, I needed to focus on what the first week at work would be like.</p><p>Is this a place I will thrive? What does it mean to be successful?</p><p>Is this a place where I can achieve my potential? What impact do I want to have with my team in a week, month, years time?</p><p>Will my team even like me? What does mean to fit into the company culture?</p><p>All these questions seemed daunting at the time and I hoped that the sounds of commuters joining me on their way in work would drown out these thoughts rattling around, yet there were no signs of the mob in question. <strong>But never mind all those details</strong>, How am I going to introduce myself?</p><p>I thought it would be a good use of my travel time to practice my introduction against my reflection of the empty train carriage and the hour long journey faded away feeling like 10 minutes. A myriad of scenarios playing in my mind of how I will be perceived on my first day by my follow Pivots. As I got out of the train, I look around and wondered where my fellow Londoners where hiding, why the station looked so baron. <strong>But never mind those details</strong>, I was here now at Old Street now and it was my time to make my entrance into the working world.</p><p>As I made my way through the building lobby and got into the elevator heading to the second floor, I took a deep breath and prepared myself to meet my peers. The elevator door opened and I stepped out to face the door of the reception and then I thought, maybe I should have considered those details, I looked at the time on my phone and realised I arrived an hour before breakfast started.<strong> But never mind those details</strong>, I was glad to be in early and ready to start my day, I was excited to be having breakfast with my peers!</p><p>It’s really a lovely relaxing way to start your day. Pivots providing a warm welcome to new employees, guests and clients, breaking bread together. It is a testament to the energy within the company, but I realised that there’s more to it. Breakfast gives us an opportunity to cross pollinate with other team members, share some challenges we are tackling in day to day work, ask for help, and above all else just have a chat and share stories.</p><p>Everyday at 9:06AM we conclude breakfast with a “standup”, a ceremony in which a soft chuckable microphone is passed around the canteen for people to introduce themselves, ask for help, let Pivots know of any events which we can get together for, and also a chance to share some “interestings” both work, and non work related. So the time came for standup and I kept thinking to myself “do it just like you practiced on the train”. <strong>But never mind those details</strong> because I was already holding the mic and introducing myself. I was so relaxed having already spoken to the Pivots around me that I was just doing what needed to be done instead of overthinking it. That’s when it became apparent to me, <strong><em>“don’t worry about those details”</em></strong>, everyone at Pivotal is here to help you figure them out as you go along. It is a culture which encourages you to collaborate, be agile and iterative on what you do, to be comfortable with yourself in order to get the best out of you.</p><p>In the next weeks blog, I will be talking about my first rotation, my learnings and experiences at the heart of Pivotals innovation, Research and Development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7a96ed53cc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>