First things first: PMs and TPMs

As a PM, your job is to “make a business impact by mobilizing team resources to solve our customers’ most painful problems.” Sounds fancy, right? But let’s be real — this role is like an all-you-can-eat K-BBQ of skills: communication, execution, data analysis, collaboration, product sense, technology understanding, strategic thinking, business savvy… and the list goes on. No PM can be a rockstar at everything, which is why we’ve split the role into non-technical PMs and technical PMs (TPMs).

Non-technical PMs are the “big picture” folks, the visionaries who handle strategy and market fit. They’re all about the “what” and the “why,” using their superpowers in communication, data analysis, and business acumen. Think of them as the idea banks. On the flip side, TPMs are the “executioners,” focusing on the “how” and “when” of technical projects. They ensure smooth execution and act as “translators for developers”. Both roles need basic PM skills, just like game characters with different stat allocations.

In the Age of AI: What Does a PM Need to Know About Tech?

However, with generative AI like ChatGPT shaking things up, the game has changed. The “what” and “why” are easier to nail down with AI’s help. Struggling with verbal or written skills? Let AI handle the data analysis. Need a crash course in business acumen? AI’s got your back with summarized articles. AI can assist non-technical PMs with many of their traditional duties.

So, does this mean non-technical PMs now need to master the “how” and “when”? Absolutely. Technology literacy is crucial to making the right business impact. To leverage AI effectively, you need to ask smart questions, and that requires a solid grasp of basic tech concepts and principles.

Why Bother with Tech Basics?

Here’s the deal. A strong technical understanding can do wonders for you:

• Communicate with Developers: You’ll anticipate roadblocks, set realistic timelines, and make convincing arguments during feature trade-offs. Talk is cheap, but informed talk is gold.

• Stay on Top of Tech Trends: Knowing the latest trends helps you spot opportunities and risks. Analyze competitors’ tech moves and adapt new technologies to your company.

• Manage Technical Debt: Reduce unintentional technical debt by anticipating errors. Don’t saddle your future self with the consequences of avoidable mistakes.

My goal = To help you become a “PM that engineers love”

Alright, just like I toss treats to my pup, I’m gonna break down this tech stuff for you.

My goal is to help you master the tech basics so you can communicate effectively with engineers and earn their respect. I’m not a comp sci major nor did I start my career in tech, but I’ve educated myself and gained recognition as a developer’s favorite non-developer. I want to share what I’ve learned in a way that’s so clear even your golden retriever could get it. As they say in the movie Margin Call, “Explain it like you’re talking to a kid or a golden retriever.”

I’m here to help you become a “PM that engineers love,” not a “PM that is an engineer.” My tech knowledge will be naturally shallow — if you want deep dives, treat your developers to a meal or coffee and pick their brains directly. Or consult specialized resources and AI. Once you have the basics down, everything else will make more sense.

Tech Basics Every PM Should Know

Me trying to figure out tech during my career pivot.

Let’s dive into the essentials. The tech wizards will be casting spells with this stuff, but you just need to know enough to sneak in and feed it the right info without causing a meltdown.

Here’s a list of tech basics for PMs, which I’ll be elaborating on in future posts:

1. Project Planning & Design Phase

• System Architecture: The front-end is all business in the front (what you, the user, get to see), while the back-end is a party in the back (where the magic happens, but you don’t need to know all the details).

• Software Development Lifecycle: From planning to deployment. Methodologies like waterfall and agile.

• Tech Stack: This is the stuff developers nerd out on. It’s their version of arguing over whether Star Wars or Star Trek is better. Just nod and smile.

• Database: Imagine a giant filing cabinet for your data. SQL is like neatly labeled folders, NoSQL is like a junk drawer where you throw everything in and hope you can find it later.

• Data Model: This is the blueprint for your data, like a map showing where everything is. Focus on the big picture, like how you’re going to use your data to send and receive messages in JSON and XML (the languages of data).

• Network Architecture: How devices and systems are connected — server-client, peer-to-peer, IoT, etc. Think of this like a party: Server-client is like a formal dinner with assigned seating, peer-to-peer is a potluck where everyone brings a dish, and IoT is like a wild house party where every appliance is invited.

• Cloud Infrastructure: Basics of cloud computing, major providers, scalability, elasticity, and serverless concepts. It’s like renting a digital apartment for your data. You can scale up or down depending on how much stuff you have. Just remember to pay your rent (aka your cloud bill)!

• Security: Authentication, permissions, encryption. Essential for protecting your data.

2. Development Phase

• APIs: Rules for easy data exchange. APIs are like ordering food from a menu at a Korean restaurant. You don’t need to know how the chef cook the Kimchi Jjigae or Gejang, you just tell them what you want (the request) and they bring it to you (the response).

• SDK (Software Development Kit): SDKs are like pre-made Lego sets for developers. They provide all the tools and instructions you need to build cool stuff according to the API’s rules, so you don’t have to start from scratch.

• Debugging: The art of catching errors.

• Web Development: It is like building a digital cat tower. You start with a simple foundation (HTML), add some style and flair (CSS), and then bring it all to life with interactive elements (JavaScript).

• Mobile Development: This is like the Pepsi (Android) vs. Coke (iOS) rivalry, but for tech. Both platforms have their die-hard fans, swearing by their favorite’s taste (or in this case, user experience), and each comes with its own secret recipe (or development tools).

• Git: Version control for tracking code changes. Git is like a time machine for your code. It lets you track changes, go back in time to fix mistakes, and even collaborate with other developers without creating a chaotic mess.

3. Testing & Quality Assurance Phase

• Types of tests and tools: Think of software testing like a stress test for your code: You’re basically poking, prodding, and even intentionally breaking things to see how it holds up. It’s the tech equivalent of seeing how many licks it takes to get to the center of a Tootsie Pop (and yes, developers hate it almost as much).

• Continuous Integration/Deployment (CI/CD): Automated testing and deployment. It’s like having a personal assistant for your code. It automatically runs tests, catches errors, and even deploys your updates, freeing you up to do more important things.

4. Deployment & Maintenance Phase

• Monitoring & Logging: Think of this as your software’s health tracker: It’s the FitBit for your code, constantly monitoring its vital signs and sending out alerts when something’s not quite right. It’s also the reason developers sometimes wake up in a cold sweat at 3AM.

• Patching & Updating: Fixing bugs and adding features. It’s like training sessions for your pup. Regular training keeps them well-behaved, helps correct any unwanted habits (bugs), and sometimes even teaches them new tricks (like playing dead or fetching the newspaper). Just like a well-trained dog, your software will be happy, healthy, and always ready to impress with its new skills.

• Scalability: Enhancing system performance for sudden user influx. Scalability is like planning a party. You want to make sure you have enough food and drinks for everyone, even if a few unexpected guests show up. It’s the difference between a fun night and a total disaster (or in this case, a crashed website).

• Refactoring: Improving code quality behind the scenes. Refactoring is like giving your code a makeover. You’re not changing the functionality, but you’re making it look better, smell better, and maybe even perform a little better. It’s like cleaning your room — your mom (or your product team) will be so proud.

5. Additional Considerations & New Technologies

• UX Design: Basics for collaborating with designers.

• Data Privacy Laws (GDPR, CCPA): Compliance to avoid fines and bans.

• Generative AI: Understanding LLMs, fine-tuning, RAGs, common AI mistakes, and more.

I brainstormed this list, and it might evolve over time (I’ll keep you posted if it does). I’ve skipped the super-specific stuff that varies from company to company and focused on the core concepts you actually need to know. I’ve roughly grouped them by software development cycle to make your search easier, but there’s bound to be some overlap.

Maybe this list is triggering some tech PTSD, or maybe you’re thinking, “Dang, that’s it?” Well, either way, AI is the hot topic right now, so I’m thinking of tackling that first. If there’s something specific you want to know first, let me know.

That’s it for today’s introduction — stay tuned for more and I’ll catch you in the next one.