<?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 Kaiho Pasu on Medium]]></title>
        <description><![CDATA[Stories by Kaiho Pasu on Medium]]></description>
        <link>https://medium.com/@kaihopasu?source=rss-3017878454bb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Kaiho Pasu on Medium</title>
            <link>https://medium.com/@kaihopasu?source=rss-3017878454bb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:34:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kaihopasu/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[Why we think Translation is the primary objective of Product Management]]></title>
            <link>https://medium.com/@kaihopasu/why-we-think-translation-is-the-primary-objective-of-product-management-37d8c112c6f5?source=rss-3017878454bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/37d8c112c6f5</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Kaiho Pasu]]></dc:creator>
            <pubDate>Sun, 25 Jun 2017 07:30:16 GMT</pubDate>
            <atom:updated>2017-06-25T07:34:55.342Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*Hn4qJdklSIVrP-5BwQVrkA.jpeg" /></figure><h3>So, what is this Product Management thing?</h3><p>I don’t know. Do you? As someone who’s aspiring to build products, I keep reading up on Product management. So far, the most I’ve learnt is from David Cancel, Drift’s CEO talking about it on his blog <a href="https://medium.com/the-mission/this-is-why-i-never-hire-product-managers-c321ca96505b">“This is why I never hire Product Managers”</a>. David says:</p><blockquote>“Product management is a role that is very unique to a specific company.”</blockquote><p>I totally believe him. That’s why we set out on a journey to define what Product Management means to our organisation, Kaiho Pasu.</p><p>Like most of our important discussions, this one was happening inside our <a href="https://www.linkedin.com/in/prashanth-balasubramanian-44245214/">Creative Energizer’s </a>Ford Figo driving around the roads of Chennai. We were trying to define the role of Product Management (a role that I could play) within Kaiho Pasu. Actually, we were defining two roles: Product Management and Project Management but more on that later.</p><p>In that conversation, I blurted out my thoughts on Product Management:</p><blockquote>“Understanding what needs to be built and imaging the world where the product is being put to use. Bringing this imagination to life by working with whomsoever required to deliver tangible outcomes”</blockquote><p>The conversation slowly evolved and this is what we arrived at.</p><p>There are a lot of teams working on a lot of interesting at Kaiho Pasu.</p><p><strong>Kyoki Chimu</strong> — the core content team. They’re researching on the a lot of things like curriculum building and learning methodologies. They’re going to deliver pieces of amazing content. The language they speak is education.</p><p><strong>Vanakkam Alexa</strong> — The technologists who are trying their hands at different technology and learning how to build apps and websites. They’re developing frameworks that can hold the content Kyoki team sends their way. The language they speak is technology.</p><h4>Where does Product Management fit in?</h4><p>Now, Product Management has to translate one language into the other. They participate in conversations at both teams. They understand content from the Kyoki team and feed that into the tech team and shape how the product is delivered to our users.</p><p>So this requires someone who understands technology but needn’t know how to code; understands education and how people learn at a high level; also can easily articulate information in a way that the target audience understand. And here I was, ready made ;) A Computer Engineer who spent a few years teaching and now delivers product demos that are easy to understand (A little self promotion never hurt)</p><p>Product Management always have the users in mind. Everything they do, they think about the user base and think at a level on how users feel about the product. But, where do they get user inputs from? Well, I’m glad you asked :)</p><p><strong>Ichibachosa — </strong>Our social intelligence team is busy building a Voice of Customer program. Once we have a prototype ready, we will have a user group who can test it out for us. Now Product Management can use data collected from these user groups to validate product decisions.</p><h4>Rome wasn’t built in a day. Products can’t be built alone.</h4><p>By the end of that conversation, the role seemed pretty clear to me. Our Creative Energizer also sneakily highlighted that I need to turn extrovert for at least 4 days in a week to be successful. I have a natural aversion to conversations and prefer to operate alone. But in a role like Product Management, the more conversations we’re part of; the higher chances of success.</p><p>Products cannot be built alone and Product Management definitely cannot sit alone. I need to be part of every conversation and can’t wait for information to get to me. I need to get there first.</p><p>Get it raw. Get it unfiltered. Cuz it’s really annoying to translate information that’s already half ‘lost in translation’</p><p>P.S Watch out for another blog on how we’re going to use Project Management techniques to build great things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37d8c112c6f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we enable multi-doers through a Project approach]]></title>
            <link>https://medium.com/@kaihopasu/how-we-enable-multi-doers-through-a-project-approach-4969c7ae7cf2?source=rss-3017878454bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4969c7ae7cf2</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Kaiho Pasu]]></dc:creator>
            <pubDate>Wed, 31 May 2017 17:51:55 GMT</pubDate>
            <atom:updated>2017-05-31T17:51:55.821Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s first define the above said multi-doers. They are different from multi-taskers. Multi-taskers do many things at the same time. Multi-doers just do many things.</p><p>Also, multidoers aren’t people whose interests jump from one thing to another. Multidoers manage to stay focused and interested on multiple things at the same time. “How can one be interested in different things at the same time” you ask?</p><p>What if a sales person who’s passionate about the product they sell wants to build a small module in product? What if a product manager wants to spend time supporting customers on a regular basis? What if a support person wants to be involved in monthly marketing meetings? What if a marketer wants to sell?</p><p>Even if they show interest towards an activity happening in a different team, it’s quite a challenge for them to contribute actively. Modern organisational structure forces an individual to pick a function, pick a vertical and stick with it. Their day to day job is defined by the job description and it is really hard for them to pick up skills outside their function.</p><p>In the current system, even expressing interest to do other activities will send out a really strong signal to your manager — “You’re not interested in your current role”. Resistance follows and usually the conversation is brushed aside to be revisited later. This can also result in a team change which again doesn’t solve the problem for the multi-doer.</p><h3>Why the team approach doesn’t work for us?</h3><p>In this approach, the focus is usually on the team and the team defines what task the members get to work on. No one bothers checking with all the team members if they’re interested in the task. The scope of the task remains within the team. This presents two problems:</p><ol><li>There could be someone in the team who doesn’t like working on the task but they’re obliged to</li><li>There could be someone outside the team who wants to work on the task but they’re not allowed to.</li></ol><p>We can’t live with either of the above.</p><p>We have a lot of multi-doers in our organisation and we’d hate to deny them the opportunity to pick up the skills they want to. We feel that giving anyone in the organisation the freedom to do anything they want is paramount to a happy workforce. As long as the work they’re doing is aligned with the organisation’s vision and helps us all move forward, they can do it.</p><p>Hence, KP operates on a Project approach rather than a team approach.</p><h3>Project above team. Always.</h3><p>In a project approach, the focus is on the project and the outcome. Every project has clear goals and objectives. The project is open to anyone in the organisation as long as they have the necessary skill set (or willing to learn them) and the bandwidth. This approach renders any “team” irrelevant and puts the project above the team all the time.</p><p>This also lets us be nimble and quickly regroup whenever we want. We don’t have any problems with cross team communication as almost everyone works with each other on some project or the other. And also, how do you break silos when they don’t even exist?</p><p>Keeping true to the title, this also lets multi-doers pick up any number of projects they want provided they have the bandwidth to work on it. Time is like a superpower and we trust them to use it responsibly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4969c7ae7cf2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>