<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team on Panji Gautama</title><link>https://panjigautama.com/categories/team/</link><description>Recent content in Team on Panji Gautama</description><generator>Hugo</generator><language>en</language><copyright>Copyright © Panji Gautama</copyright><lastBuildDate>Wed, 15 Nov 2023 17:37:11 +0000</lastBuildDate><atom:link href="https://panjigautama.com/categories/team/index.xml" rel="self" type="application/rss+xml"/><item><title>Thoughts on Developer Productivity</title><link>https://panjigautama.com/thoughts-on-developer-productivity/</link><pubDate>Wed, 15 Nov 2023 07:29:59 +0000</pubDate><guid>https://panjigautama.com/thoughts-on-developer-productivity/</guid><description>&lt;p&gt;&lt;img src="https://miro.medium.com/v2/resize:fit:512/1*nYbbM6V6ZJmlmUToZmLNTw.gif" alt="Color Cycling in Pixel Art | by Stephen Schroeder | Prototypr"&gt;&lt;/p&gt;
&lt;p&gt;I used to have a dream to work at a consulting giant until a few years ago. I worked with a bunch of them, as my parent company decided to hire one of the consulting companies, and they gave me nothing but a mess (Duh! 🙄). A while back, I stumbled upon this &lt;a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity"&gt;&amp;ldquo;Yes, you can measure software developer productivity&amp;rdquo;&lt;/a&gt; article from the consulting giant, and it sparked debate in a lot of tech blogs/newsletters.&lt;/p&gt;</description></item><item><title>Tech Debt Management</title><link>https://panjigautama.com/tech-debt-management/</link><pubDate>Tue, 08 Mar 2022 20:25:54 +0000</pubDate><guid>https://panjigautama.com/tech-debt-management/</guid><description>&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=n9BUA96ymC0"&gt;https://www.youtube.com/watch?v=n9BUA96ymC0&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;🔗 &lt;a href="https://www.slideshare.net/panjigautama/taming-technical-debt"&gt;https://www.slideshare.net/panjigautama/taming-technical-debt&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Software Fragmentation - The Golden Path</title><link>https://panjigautama.com/software-fragmentation-the-golden-path/</link><pubDate>Wed, 25 Aug 2021 09:29:07 +0000</pubDate><guid>https://panjigautama.com/software-fragmentation-the-golden-path/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/32f8ee1f68495231452451a2edfe9b7b.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;There is a direct correlation between teams that give their engineers autonomy to own their technical decisions and the team&amp;rsquo;s ability to hire and retain A-class or Senior talent. There is a tradeoff, but an acceptable level of chaos in exchange for a stronger sense of individual/team ownership is usually the right one and leads to higher performing teams in the long run - at least this is what I&amp;rsquo;ve been seeing if a couple of companies in Indonesia.&lt;/p&gt;</description></item><item><title>Engineering Growth Framework</title><link>https://panjigautama.com/engineering-growth-framework/</link><pubDate>Wed, 12 May 2021 13:56:50 +0000</pubDate><guid>https://panjigautama.com/engineering-growth-framework/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/1c1vsZe.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Growth Framework, Career Guideline, Career Ladder, whatever you call it, is essentially general expectations of each of the grade, sometimes people call it as career ladder, but we at Mekari wanted to take it further down into its philosophy: Framework. In general, a framework is a real or conceptual structure intended to serve as a support or guide for the building of something that expands the structure into something useful.&lt;/p&gt;</description></item><item><title>Manager Manifesto</title><link>https://panjigautama.com/manager-manifesto/</link><pubDate>Fri, 16 Apr 2021 11:41:27 +0000</pubDate><guid>https://panjigautama.com/manager-manifesto/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/200w.gif" alt=""&gt;&lt;/p&gt;
&lt;h2 id="manifesto"&gt;Manifesto&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Giving critical feedback or having difficult conversations&lt;/li&gt;
&lt;li&gt;Assessing whether a product is ready for launch&lt;/li&gt;
&lt;li&gt;Designing and executing a realistic roadmap&lt;/li&gt;
&lt;li&gt;Setting good goals with accountability&lt;/li&gt;
&lt;li&gt;Building viable new products&lt;/li&gt;
&lt;li&gt;Managing a team during “war time” versus “peace time”&lt;/li&gt;
&lt;li&gt;Defining quality&lt;/li&gt;
&lt;li&gt;Determining who to hire&lt;/li&gt;
&lt;li&gt;Understanding people’s skills, strengths, and growth trajectories&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="helping-people-reach-a-common-goal"&gt;&lt;strong&gt;Helping people reach a common goal&lt;/strong&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Listening and learning about people’s aspirations and frustrations.&lt;/li&gt;
&lt;li&gt;Mentoring and advising, generally in the form of providing frameworks rather than here’s-what-you-should-be-doing’s (which is a whole topic for another time).&lt;/li&gt;
&lt;li&gt;Designing better and more efficient ways for people to communicate, work, or learn.&lt;/li&gt;
&lt;li&gt;Context-switching often in your day-to-day.&lt;/li&gt;
&lt;li&gt;Playing a key role in the flow of communication (writing, sharing, meeting, presenting).&lt;/li&gt;
&lt;li&gt;Owning the outcome of the team’s successes and failures, even if you won’t make all the decisions yourself.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;note : not mine and nor I wanted to take credit on this points. I took this note awhile ago and unfortunately didn&amp;rsquo;t put the source link.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>On forming Technical Program Manager team at Mekari</title><link>https://panjigautama.com/on-forming-technical-program-manager-team-at-mekari/</link><pubDate>Sun, 03 Jan 2021 17:12:39 +0000</pubDate><guid>https://panjigautama.com/on-forming-technical-program-manager-team-at-mekari/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/0_v_qNjzpzTWJsFCtW.jpg" alt=""&gt;&lt;a href="https://medium.com/swlh/product-manager-vs-project-manager-vs-technical-program-manager-e45d0cf32e01"&gt;credit &lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As the company growing and more product verticals are coming in, and more competitors coming in not only from Indonesia but also big players from outside the country, there are needs from stakeholders and management (C/VP levels) to ensure we are delivering our initiatives more than ever. Hence, ensuring a team to be self-organized, transparent, and great visibility of ongoing and upcoming project progress are very critical. Spotting potential delays early and doing continuous improvement on how we structure the team and do communication within the team is also essential for us to achieve effective &amp;amp; efficient productivity.&lt;/p&gt;</description></item><item><title>Different types of 1:1 conversations visualised</title><link>https://panjigautama.com/different-types-of-11-conversations-visualised/</link><pubDate>Sat, 02 Jan 2021 13:50:43 +0000</pubDate><guid>https://panjigautama.com/different-types-of-11-conversations-visualised/</guid><description>&lt;p&gt;&lt;a href="https://twitter.com/thisisneer/status/1264537589031165952"&gt;Original Thread&lt;/a&gt;&lt;/p&gt;
&lt;h4 id="1-ping-pong"&gt;#1. Ping Pong&lt;/h4&gt;
&lt;p&gt;Both parties are equally engaged and curious about the other. Answers are thoughtful, and each participant always turns their answer back into a question for the other.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://panjigautama.com/images/conversation-1.png" alt=""&gt;&lt;/p&gt;
&lt;h4 id="2-interview"&gt;#2. Interview&lt;/h4&gt;
&lt;p&gt;One person takes the role of questioner, the other person takes the role of answerer. Conversations like these can have two implications:&lt;br&gt;
i) imbalance in interest in the other&lt;br&gt;
ii) perceived hierarchy or power dynamics&lt;/p&gt;</description></item><item><title>New Chapter of Kudo</title><link>https://panjigautama.com/new-chapter-of-kudo/</link><pubDate>Sun, 02 Apr 2017 09:33:00 +0000</pubDate><guid>https://panjigautama.com/new-chapter-of-kudo/</guid><description>&lt;p&gt;&lt;a href="https://medium.com/@rhapsodixx?source=post_page-----c9d3800ac568--------------------------------"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src="https://panjigautama.com/images/1_zuAi3_ycNGn6r1roM9Uz2g.jpeg" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Three years ago, I was working in my room to develop a prototype apps for these Indonesian guys who studied at Business School in US. It was a very fun project and I enjoyed the moment I spent to discuss the features with them.&lt;/p&gt;
&lt;p&gt;When they came back to Indonesia, they built this company called ‘KUDO’ and asked me to join them. Back then, I was worried that this company is just ‘another startup company’, but i decided to take a leap of faith and chose to believe that ‘KUDO’ is working to help underserved people in Indonesia through technology, which is pretty much my mission too coming from my computer science background.&lt;/p&gt;</description></item></channel></rss>