Define Your Subtype Objectively
To answer what sub am I, focus on repeatable patterns in your skills, responsibilities, and outcomes rather than labels or short-term projects. A subtype is a distinct configuration of role, scope, and impact that tends to recur across organizations and industries. This profile breaks down how to identify your subtype using evidence, role behaviors, and verifiable outputs. The goal is clarity, not hierarchy, so you can align work, teams, and growth paths with the configuration that best matches your strengths and goals.
Core Principles of Subtype Identification
Subtype identification relies on consistent evidence over time, including role definitions, decision rights, and documented results. Three core principles guide a stable assessment: pattern recognition in responsibilities, clarity of scope and impact, and alignment with team needs. Avoid conflating temporary tasks with enduring role patterns; instead, track how you spend time, make decisions, and create outcomes across multiple contexts.
- Pattern recognition: Identify repeated responsibilities and decisions across projects.
- Scope and impact: Clarify what you own end-to-end and the outcomes you influence.
- Team and role fit: Compare your configuration to documented role models.
Common Subtype Clusters and Their Behaviors
While subtypes vary by organization, many map to recognizable behavioral clusters. These clusters help communicate expectations and calibrate contributions. Below are typical configurations, their focus areas, and the kinds of outcomes they tend to drive. Use these as reference points rather than strict boxes, since hybrid forms are common.
| Subtype Cluster | Primary Focus | Typical Outputs | Decision Authority |
|---|---|---|---|
| Execution Specialist | Delivery and optimization of defined workflows | Stable releases, process improvements, efficiency gains | Tactical within established scope |
| Product Orchestrator | Lifecycle ownership across discovery, build, and rollout | Roadmaps, metrics, prioritized backlogs | Scope and priority tradeoffs |
| Platform Engineer | Shared infrastructure, tooling, and reliability | Platform services, observability, standards | Architectural and service-level decisions |
| Data Insights Analyst | Evidence generation and measurement | Dashboards, experiments, narrative reports | Methodology and metric definitions |
| Customer Advocate | Experience coherence and retention drivers | Voice-of-customer synthesis, journeys, policies | Experience standards, escalation paths |
Evidence-Based Self-Assessment Steps
Use structured observation and data to identify your subtype. Collect at least four to six weeks of evidence across your recurring responsibilities and major initiatives. Map activities to role descriptors, quantify your outputs where possible, and compare them to target profiles within your organization and industry.
- Log your core activities for two to four weeks, noting time allocation and outcomes.
- Code each task to a role function, such as execution, design, or analysis.
- Summarize your decision rights and the types of problems you solve most often.
- Benchmark your outputs and scope against peers and documented role models.
- Synthesize findings into a concise subtype statement and development plan.
How Environment and Stage Shape Subtype Fit
Organizational stage, market dynamics, and team maturity influence which subtypes are needed and how they are structured. Early-stage companies often require hybrid profiles that span discovery, delivery, and operations. Growth and scale typically clarify role boundaries, enabling more specialized configurations and clearer ownership paths. Regulation, customer expectations, and technology platforms also redirect which capabilities are mission-critical.
Market Cycles and Demand
In expansion phases, demand grows for orchestration, platform reliability, and customer retention roles. In consolidation phases, execution optimization and disciplined measurement become more valuable. Track these cycles to understand how your subtype aligns with current needs and future positioning.
Organizational Maturity
Less mature organizations rely on generalists who wear multiple hats, while mature programs develop standards, tooling, and career paths for specific configurations. Assess where your organization sits on this spectrum to interpret your subtype within its current lifecycle.
Aligning Development with Your Subtype
Once you identify your configuration, design a development path that strengthens the skills and influence most relevant to your role cluster. This includes targeted projects, cross-functional exposure, and structured learning. Clear alignment between your subtype and growth investments increases both impact and satisfaction.
- Execution Specialists: deepen workflow expertise, automation, and quality practices.
- Product Orchestrators: build product management, metrics, and stakeholder communication.
- Platform Engineers: expand systems thinking, reliability engineering, and API design.
- Data Insights Analysts: grow SQL, experimental methods, and storytelling with data.
- Customer Advocates: master journey mapping, service design, and policy alignment.
Common Misinterpretations to Avoid
Confusing activity with impact, overemphasizing job titles, and copying others without evidence can skew your subtype understanding. Titles vary widely, and short projects rarely reflect enduring patterns. Stay grounded in behaviors, outcomes, and the context in which you operate to maintain an accurate view.
Next Steps and Ongoing Validation
Confirm your inferred subtype by comparing it to role descriptions, peer patterns, and documented expectations. Revisit your assessment every six to twelve months or after major role changes. Maintain a living record of responsibilities and outcomes to track evolution and ensure continued alignment with your goals.