<?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 Venita G on Medium]]></title>
        <description><![CDATA[Stories by Venita G on Medium]]></description>
        <link>https://medium.com/@venita.mobile?source=rss-f5a127676be9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6spHAeYkrJRqCeDMANWaUA.png</url>
            <title>Stories by Venita G on Medium</title>
            <link>https://medium.com/@venita.mobile?source=rss-f5a127676be9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:05:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@venita.mobile/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[Automation vs Human Dynamism.]]></title>
            <link>https://medium.com/@venita.mobile/automation-vs-human-dynamism-a26503e09e52?source=rss-f5a127676be9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a26503e09e52</guid>
            <category><![CDATA[piano]]></category>
            <dc:creator><![CDATA[Venita G]]></dc:creator>
            <pubDate>Sun, 30 Apr 2023 16:48:07 GMT</pubDate>
            <atom:updated>2023-05-01T05:13:05.138Z</atom:updated>
            <content:encoded><![CDATA[<p>Automation vs Human Dynamism.</p><p>“Automation vs Human Repetition” — If you ask the technologist in me to choose one, I’ll choose the former. But, when it comes to piano music and my newfound interest in ragtime piano, I’d go the other extreme.</p><p>One of the classic examples of automation is the pianola. Pianolas were at their peak in the 1920s, before radio technology was perfected and when ragtime music was at it’s heights. Pianolas operate using the concept of a punch card — where paper rolls with perforations corresponding to the music pass over a tracker bar. Air sucked through the perforations into pneumatic devices set the piano keys in motion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xtm-0GDBGLBhOKyFydeo1w.jpeg" /><figcaption>At an Antique Store on the I-90 west in South Dakota</figcaption></figure><p>The amateur pianist in me was enamored when I saw firsthand a working pianola at an antique store in South Dakota on one of my family roadtrips through the US. I recognized the music as ragtime piano. On returning home from my road trip, I sought out the ragtime books available at my local town library. Scott Joplin was easy to find — a clear cut difference in style from the Baroque, Romantic and Neo-Classical styles I was used to while practicing for my ABRSM piano exams.</p><p>I started out by playing Scott Joplin’s The Entertainer <em>without</em> the octaves in the right hand. Once the right hand moves were simplified, I found the left hand “strides” easier to practice and after extended sittings at the piano, I was able to memorize the music. There I reached a plateau and the only ragtime piece in my repertoire was this one piece for a good 5 years.</p><p>Recently, I broke my right hand and after surgery, no amount of physiotherapy could help me regain flexibility in my wrist. I turned to playing the piano looking for exercises that would stretch my right hand and decided to try my hand at Maple Leaf Rag by Joplin. It’s been a struggle for months — maintaining left and right hand independence, all the while playing octaves with the right hand and stretching the fingers with an inflexible wrist.</p><p>While searching for techniques to strengthen my right wrist, I happened to find the music of Winifred Atwell. Her <a href="https://www.youtube.com/watch?v=vmDHkwtAins">adaptation of George Botsford’s Black and White Rag</a> encouraged me to look for the sheet music. (if you happen to watch the video, don’t miss the 35 second mark where Winifred stops to engage with her audience for that split second)</p><p><a href="https://en.wikipedia.org/wiki/Black_and_White_Rag">The Black and White Rag</a> (in the key of G Major) is much less complex than <a href="https://en.wikipedia.org/wiki/Maple_Leaf_Rag">Maple Leaf Rag</a> (in the key of A Flat Major). Watching Winifred Atwell play it has enforced my conviction of how musicality expressed by an artist cannot be replicated by an automated machine, no matter how sophisticated the machine.</p><p>A technologist will always marvel at how ingenuity can be automated, but can automation replace human dynamism and charisma?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a26503e09e52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You don’t need a master mind — you need cross pollinators.]]></title>
            <link>https://medium.com/@venita.mobile/you-dont-need-a-master-mind-you-need-cross-pollinators-e54d3a6605a4?source=rss-f5a127676be9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e54d3a6605a4</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Venita G]]></dc:creator>
            <pubDate>Sat, 22 Apr 2023 19:50:05 GMT</pubDate>
            <atom:updated>2023-04-23T02:26:34.919Z</atom:updated>
            <content:encoded><![CDATA[<h3>You don’t need a master mind, you need cross pollinators</h3><p>Having built enterprise software for two decades, I’ve come to realize that innovation exists in everyone, and great products get built when collaborators meet to increase impact.</p><p>“3-in-a-box” is an oft used term in Product Management — It stands for a collaboration model that brings together Business, Users and Technologies. The Business is represented by the Product Team, Users are represented by UX Team, Technology is represented by the Engineering Team. Unfortunately, this model fails to acknowledge the participation of so many other important players in the Product Discovery Process.</p><p>For example, at our Product Management team, we’ve had collaborators who are as important as the other three — Our Data Scientists — They were able to unearth so many meaningful patterns in our data, build predictive models that forecasted trends that enabled us to call our product a “cognitive analytic engine”. The product would not be what it is today without them. At one point, I rallied to change our internal Slack channel name to 4 in a Box, but other steadfast purists were not inclined to change it.</p><p>Thinking further, I ruminated “Why even limit the number in the box?”. And that’s when I happened to chance on the term “Cross Pollinators” in the book by Tom Kelly from Ideo, <a href="https://www.ideo.com/post/the-ten-faces-of-innovation">The Ten Faces of Innovation</a>. We were not “3 or 4 in a box” — we were Cross Pollinators in a Box. Innovation in our product team is robust because of the extensive cross pollination of ideas between these individuals in the team. In the book, the author goes on to list “seven secret ingredients” for any company that wants to bump up its level of cross-pollination. Check it out and you will realize that there is no rocket science to building a greenhouse for cross pollination.</p><p>How does one build cross pollination within self? History is full of luminaries who have gone beyond the bounds of their thinking and there’s no better person to exemplify this than Henry David Thoreau. Thoreau’s reading and life itself involved vibrant and unending cross-pollination. Each subject he studied led him to insights about others, and the creation of these rich intellectual chains is what ultimately made him one of the most original and fruitful minds of his era.</p><p>As for us who work with teams, we just need to remember “There’s no mastermind”. It’s time to get out of silos and instead take the team approach to cross-pollinate and commingle the required skillsets. When we bring together diverse skills and backgrounds from within the organization to achieve a common goal, we can create amazing products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e54d3a6605a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Encouraging minds of the next generation]]></title>
            <link>https://medium.com/@venita.mobile/encouraging-minds-of-the-next-generation-5e80a69750a9?source=rss-f5a127676be9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e80a69750a9</guid>
            <category><![CDATA[mentoring]]></category>
            <dc:creator><![CDATA[Venita G]]></dc:creator>
            <pubDate>Sat, 01 Apr 2023 16:34:58 GMT</pubDate>
            <atom:updated>2023-04-01T16:34:58.362Z</atom:updated>
            <content:encoded><![CDATA[<p>LinkedIn’s Workforce Confidence <a href="https://www.linkedin.com/pulse/gen-z-boldest-generation-its-job-hunt-priorities-off-charts-anders/?trackingId=pwWrCQQ1SiG9Yds3hH8gUg%3D%3D">report</a> found 80% of Gen-Z employees (people born in 1997 or later) are looking to work for companies whose values better align with their own. Gen Z and millennials are still in the earlier stages of sampling what’s available in the world of work.</p><p>As a Product Architect and Engineering Manager, I’ve had the chance to work with many Gen-Z employees on my team. As a parent to a Gen Z kid, I know they’re curious, they’re go getters, they’re inquisitive and they want to make a difference.</p><p>In September of 2017, I had an opportunity to network with a group of Gen Z students from Massachussets Institute of Technology at the MIT@Cambridge event hosted at the IBM Cambridge office. Opening them to a world of how AI could be infused into Supply Chain applications in a mission to improve Order Management systems, I received many questions — Some said “Wow, this is real. What I learn in my college can really be used to make a difference”. Some wanted to delve into “How does this work?”.</p><figure><img alt="Inspiring curiosity in the minds of Gen Z — MIT@Cambridge student networking event." src="https://cdn-images-1.medium.com/max/884/1*O3F5aeH3Mt6-Udj6wHVMPA.jpeg" /><figcaption>Curiosity in the minds of Gen Z — MIT@Cambridge student networking event.</figcaption></figure><p>It’s now 2023, Gen-Z promises to continue disrupting the workplace and driving the evolution of the future of work. By bringing their aspirations to life, investing in thoughtful technology, and building healthy and inclusive cultures, we all stand to reap the benefits of a stronger next generation in the workforce.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e80a69750a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on my 900 days in Product Management after 20 years in Product Engineering]]></title>
            <link>https://medium.com/@venita.mobile/reflections-on-my-900-days-in-product-management-after-20-years-in-product-engineering-4dec6d1283d3?source=rss-f5a127676be9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dec6d1283d3</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Venita G]]></dc:creator>
            <pubDate>Sat, 01 Apr 2023 12:02:46 GMT</pubDate>
            <atom:updated>2023-04-03T07:24:34.688Z</atom:updated>
            <content:encoded><![CDATA[<p>900 days into my role in Product Management deserves some introspection. Many of you may wonder why I choose to define the subject of this article in terms of days and not in terms of months or years (300 days equals 30 months or nearly three years, and it’s amazing how much can happen in that window — the pace was such!). I’ve had countless learnings and experiences during this period, so it is only befitting that I retrospect in terms of days and it was by living each day to its fullest, that I’m able to look back and put all my learnings together.</p><p>Before transitioning into Product Management, I spent 20 years in Engineering. During that time, I’d built new products, re-engineered old products, got my hands dirty, my feet wet, set up agile scrum processes, led geographically dispersed teams, filed patents, worked with UX designers and data scientists to bring products to life. There is so much I learned on the job. During that phase of my career, my mantra was “Deploy or Die”. Given an idea, given a problem, I would gear my team and myself to find a solution, we would build it and ensure it got deployed and “productionized”.</p><p>Fast forward to 2020, I was at one of my quarterly checkpoint meetings with a Tech Vitality Development Manager discussing how I would fast track my Senior Technical Career Path, when I received a phone call from my Engineering Director who quickly got to the point. “Venita, there is an opportunity in Product Management for a Product Owner. You will report to the Director of Product Management and your role would be to bridge the gap between the Product Management and Engineering Management and bring the voice of our customers into the product”. Since Product and Engineering teams report into different organizations, I was very intrigued with the chance to take up this lateral job rotation in another organization within the same company while continuing to apply my skills. The answer was very clear to me, “Yes, I can do it”.</p><p>The transition had extraordinary highs and lows. I read voraciously, I listened to customers and stakeholders, I asked questions, learned a huge amount — about both product management and new schools of thought — how to do things and how <em>not to</em> do things. Most importantly, I learned the importance of “Delivering Value”.</p><p>-</p><p>It takes a Product Management team to bring in aspects that ensure that everything we build ties into strategic imperatives. Without a strategy, execution can continue, but culture takes over and rather than being Product Led, a team could become Sales Led, Marketing Led or even Engineering Led. It takes strategic thinking to ensure that we build the right thing for our customers. To quote <a href="https://www.walkerdunlop.com/insights/2023/03/01/unleashing-greatness-workplace-frances-frei/">Francis Frei, “Whenever strategy is silent, culture fills the space”</a>.</p><p>-</p><p>The difference between Delivery and Discovery. As a Product Engineering Lead, I was fanatical about delivery. We were measured by the top quality features we delivered on time and within budget. On transitioning into the Product Management team, I started discovering the importance of “outcome” vs. “output”. Marty Cagan’s book, Inspired, and his article about the difference between <a href="https://www.svpg.com/discovery-vs-delivery/">Delivery and Discovery</a> further enforced my experience that Engineering Managers, Release Managers, Program Managers <em>deliver</em>, but it takes a Product Manager to <em>discover</em>.</p><p>-</p><p>After learning the importance of delivering value, I was tough on my team — consciously trying to steer the UX designers, Engineers, Content Writers for the product to keep on the path to delivering value. I am as proud of the ideas we implemented, and I am equally proud of the ideas we did not implement. As <a href="https://www.lennysnewsletter.com/p/how-to-create-a-winning-product-strategy#details">Melissa Perri</a> puts it, a Product Manager is a <em>Good Idea Generator</em> and at the same time a <em>Bad Idea Terminator</em>. While I might have ruffled a few feathers along the way, I learned that it is a Product Manager’s role to keep the team focused on building value.</p><figure><img alt="One of the many Design Thinking Exercise we Product Managers Perform to Discover Value" src="https://cdn-images-1.medium.com/max/1024/1*PBhA1fPLk6cL5bR0WHjVFw.jpeg" /><figcaption>One of the many Design Thinking Exercise we Product Managers Perform to Discover Value</figcaption></figure><p>What else have I done in these 900 days besides build product as a Product Owner? Well, it wouldn’t be right if I left out some other key accomplishments — I’ve grown with my family, road tripped to amazing places putting 20000 miles on the speedometer with my adventure loving husband and son, learnt to ski, re-located from Boston to Bangalore, broken my hand in a road accident and nurtured it back to strength. The parallel phases of my life continue.</p><p>My one mantra through this transition has been “Make Every Moment Count” — for myself, my family, my team and my customers. Leaving you with a quote from one of my favorite authors that keeps reminding me to stay in the moment.</p><p><em>“With the past, I have nothing to do; nor with the future.</em> <em>I live now.”</em> <em>— Ralph Waldo Emerson</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dec6d1283d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>