As I start a new job tomorrow at ChampTitles, I took some time to reflect on what I learned at Patriot Software over the last 5 years.
I was struck by how different my experience was at an in-house company, versus my previous 11+ years at agencies.
While I was in a different role at agencies – UX, rather than product management – my time at Patriot Software showed me there are unique advantages to being in-house.
Working in-house, as opposed to an agency, allowed me to:
- š§āš»Get to know my stakeholders & team (dev/QA) and work with them over an extended period of time
- Communication is key to a PMās job; once you work with someone, itās easier to understand how best to communicate
- For example, when communicating async, some people prefer words while others prefer short video clips; some people like verbal communication where others want to be walked through a diagram
- I was also lucky enough to work with wonderful stakeholders and have fantastic teams ā¤ļø š„°
- š Create domain expertise
- I bounced around Patriot Software, so the longest time I was in any domain was a year; still, thatās far longer than most of my client projects
- While I always had āSMEsā (subject matter experts) to work with, having a deeper understanding made prioritizing and solving problems easier
- š„ Develop deep customer expertise by having direct and consistent access to the customers
- With some agency clients, we were able to do a formal study and talk to actual customers, but oftentimes we did not have access to customers
- At Patriot Software, I was able to recruit however I wanted to, including picking up the phone and calling a customer for input; I ended up with a better understanding of my customers which led to better prioritizing and improved features
- š¬ Be directly involved in any incidents, and solving / communicating about those incidents
- The Silicon Valley Bank incident was the biggest, by far
- Incidents are challenging, but also great opportunities for learning
- šļøMy biggest takeaway from that incident, along with others: communication, communication, communication
- Even saying āWe know parts of the system are down, not sure which parts and why, but weāre investigatingā is far better than silence when something goes awry and the calls are streaming in
- š¢ Have access to the data to do my own ādata diggingā
- I wrote over 600 SQL queries at my last job, plus created many āqueriesā in other tools
- I had an opportunity to learn a variety of tools over the years: MixPanel, Posthog, Google Analytics, Pendo, Redash (SQL query tool), Amazon QuickSight, and Oracle Analytics Cloud
- With these tools I was able to uncover insights like unusual ways customers were using our software that pointed to a missing feature, or dropoff points to rework in workflows; it also allowed me toā¦
- š See the outcomes of my work
- This was something I missed out on at agencies, outside of verbal feedback
- In-house, I could not only set the goals, but see how weāre doing towards those goals post-launch, which leads me toā¦.
- šIterate, iterate, iterate
- I had opportunities to get feedback – both qualitative and quantitative – and iterate towards our goals
- āļø Learn about our technology
- At agencies, I mostly used platforms such as Hybris, IBM eCommerce, and Adobe Experience Manager; while I understood those at a high level, thatās very different than understanding whether weāre using React or Vue and why, and how our different systems communicate
- This is directly relevant to iteration; I learned better tech = faster iteration
- ā³ Leverage feature flagging
- This wasnāt something I could control with agency clients, but here, I had my hands on the keyboard and could control rollouts to a much larger extent
- This goes back to the āsee outcomes and iterateā; we could see outcomes with a smaller group of customers, and iterate before a feature is fully rolled out
- For example, with one feature, after turning it on for California customers, we realized we need a ābulk moveā tool; we added that before final rollout
- š
Beyond individual projects: see the outcomes of my strategies and plans
- At agencies, I also created strategies and plans, but it was rare that I was with the client long enough to see how they played out
- š§ Work around the problem
- I learned how to work around obstacles in a way that I could not in an agency, such as working with operational teams on a solution
- As an example, one time the operations team wanted an analytics report built into our internal system, which would have been a fair amount of work; the compromise was for the devs to include a link to the analytics report built in another system
Other Lessons Learned: Coaching
Beyond the projects, I was also a manager for 3 and a half years. While I had coached before, it had mostly been in person; I improved my remote coaching skills, and my coaching skills in general.
ā³Both in terms of coaching meetings and for team meetings, I consciously allowed a few minutes of chit-chat before āgetting down to business.ā That isnāt my natural instinct, but itās extremely important anywhere, and more so in a remote environment.
šŖ I also learned about the importance of keeping high-performing team members challenged, and finding areas they should continue to improve on even if theyāre already strong; thereās always room for improvement for all of us.
šFor coaching purposes, I found value in working through books with team members. The books I shared most often were āProduct Management in Practiceā by Matt LeMay, and āHow to Win Friends and Influence People,ā by Dale Carnegie.
āProduct Management in Practiceā is great for those new to product management, and also for more experienced PMs when I needed to make sure we were aligned on what it means to be a PM; it helped gain alignment between my expectations and theirs better than any career framework.
āHow to Win Friends and Influence Peopleā is for anyone who wants to build stronger social and professional relationships. A manager gave the book to me early in my career, and it had a tremendous impact on my skills and career.
ā-
As I move into another in-house product role, I’m excited to apply these lessons and look forward to all the new ones that await me.
Really resonated with your point about having direct customer accessābeing able to āpick up the phone and call a customer for inputā is a luxury many in-house roles take for granted but can transform prioritization. For those of us working on outreach and link building, that same kind of direct audience connection happens through blog commenting, which is why I built a small tool (https://lincspider.kwverdit.com/en) to help streamline that process. Thanks for sharing such a grounded reflection.