Becoming “more technical” refers to gaining specialized knowledge, expertise, and practical skills in a particular field, allowing individuals to understand deeply how systems work, communicate effectively with specialists, and perform complex tasks. It is considered a continuum rather than a binary state, where increased technical depth often correlates with higher-level roles and increased impact. 1. Core Characteristics
Specialized Expertise: Possessing deep knowledge of specific tools, technologies, or subjects.
Practical Application: Focusing on doing, not just knowing, to ensure knowledge sticks and is effective.
Systemic Understanding: Understanding the infrastructure stack, system architecture, or the “behind-the-scenes” mechanisms of products.
Technical Communication: Being able to speak the language of engineering, data, or science to bridge the gap between technical and non-technical teams. 2. Key Areas to Develop Technical Skills
Software & Coding: Learning programming languages (e.g., Python, JavaScript), API configuration, or software development life cycles.
Data Analysis & Science: Understanding data structures, statistics, and machine learning techniques.
Infrastructure & DevOps: Familiarity with cloud services, server management, and automated deployment processes.
Technical Writing/Process Documentation: Documenting complex workflows and technical specs. 3. Actionable Ways to Get More Technical
Do Technical Work: Apply technical skills directly through projects, such as building an app, analyzing a dataset, or configuring a tool.
Deepen Product Knowledge: Move beyond high-level product understanding to understand the architecture, API, and data flow.
Shadow Engineering Teams: Engage in conversations with technical team members to learn their processes and tools.
Engage in Self-Study: Use educational resources to learn technical concepts from the ground up.
Being more technical is crucial for roles that require optimizing product efficiency and, in fields like product management, it allows for more productive conversations with engineering teams.
To help me tailor this information for you, could you tell me: What is your current role?
What specifically do you want to learn? (e.g., coding, understanding APIs, cloud computing)
What is your goal? (e.g., switching careers, leading technical teams)
Leave a Reply