Over two decades leading product, design, and engineering organizations — from building web publishing systems at Knight Ridder to leading PDE at the Wall Street Journal, The New York Times, Hearst, Conde Nast, and Reddit — I have developed and refined frameworks for organizing technology teams, growing careers, and operating as a technology executive. I use the term PDE — product, design, and engineering — to describe the three disciplines that should operate as one integrated organization under a single leader.
This page collects those frameworks into a reading guide. The articles are organized by theme. Within each theme, they build on each other chronologically. Start wherever matches your current need.
Career Frameworks
How to structure career progression so that brilliant technologists can grow without being forced into people management.
| Article | Year | What It Covers |
|---|---|---|
| Management & Technical Career Growth Tracks | 2008 | The foundational dual-track framework: management and technical paths with equivalent levels |
| Some Pathways for Career Development in Product Engineering | 2011 | Non-linear career trajectories across engineering, product, QA, and systems |
| Career Growth Tracks (v2) | 2012 | Adds product management track, C-level band, and minimum direct-report guidelines |
| HR Classification and Discretionary Job Titles | 2013 | The system for separating HR classification titles from business-use titles, with policy guidelines |
| Career Growth Tracks (v3) | 2017 | The most comprehensive version: 4 levels with sub-levels, salary ranges, covers engineering, product, project management, data science, and design |
Employee Evaluation
| Article | Year | What It Covers |
|---|---|---|
| CAREER-CLEAR: Employee Evaluation and Career Development | 2010 | A 5-category evaluation system (Caliber, Leadership, Expertise, Role, Discretionary) that maps scores to career levels and compensation |
Organizing PDE Departments
How to structure a product, design, and engineering department at different scales.
| Article | Year | What It Covers |
|---|---|---|
| Organizing a Medium-Size Technology Department | 2009 | The 3-department model (Site Engineering, Platform Engineering, Technology Operations) for 20-100 person teams |
| Organizing by Functional Areas for Larger Companies | 2011 | Seven functional areas for 50-250 person departments, with detailed CTO org chart and program/project team model |
| 3 Dimensions of a Technology Team | 2014 | Balancing Products, Partners, and Professions — how to integrate product-aligned teams with professional departments and stakeholder relationships |
The CTO Role
What a CTO does, how to do it well, and how to start in a new CTO role.
| Article | Year | What It Covers |
|---|---|---|
| 3 Roles of a CTO: Culture, Technology, Operations | 2014 | The C/T/O framework as a 1:1 meeting template between a CTO and their direct reports |
| CTO Mind Map | 2015 | A visual job description for the CTO role, organized by Culture, Technology, and Operations |
| 90 Day Plan for a CTO in a New Job | 2016 | Seven areas to address in your first 90 days: understand the org, define measurements, articulate vision, organize people, build culture, revise processes, upgrade technologies |
| How to be an Effective CTO | 2016 | Culture/Technology/Operations in practice, with 5 lessons from leading technology at major media companies |
The CPTO Role and PDE Organizations
The evolution from separate CTO and CPO roles into a unified Chief Product and Technology Officer leading a PDE (product, design, and engineering) organization.
| Article | Year | What It Covers |
|---|---|---|
| IT Culture vs. Product Culture | 2017 | The fundamental shift from IT as a service organization to product as a core capability |
| The Role of a CPTO | 2018 | Why product, design, and engineering should be under one leader, with practical guidance on the CPTO-CEO relationship and organizational structure |
| How Stakeholders and PDE Should Work Together | 2019 | The collaborative model between business stakeholders and the PDE organization |
| A CEO’s Guide to Working with CTOs and CPOs | 2022 | Written for CEOs who want to get the most from their technology and product leaders |
Hiring for PDE Organizations
| Article | Year | What It Covers |
|---|---|---|
| Interviewing By Putting To Work | 2007 | Evidence-based hiring through work samples: three models (contractor-to-hire, work sample exercise, abbreviated assessment) with practical implementation guidance |
Human-AI Collaboration and Agentic AI
The articles above cover the human dimensions of leading PDE organizations. As AI becomes integral to how product, design, and engineering teams work, I write about the discipline of human-AI collaboration on two dedicated sites:
Synthesis Engineering covers the professional practice of human-AI collaboration for complex work — thinking frameworks, context management, project management redesigned for AI capabilities, and the principles that make human-AI teams effective rather than just fast.
Synthesis Coding covers the specific discipline of building production software with AI while maintaining human architectural authority, code quality, and system understanding. This is the methodology for engineering teams that need to ship reliable software with AI assistance without losing control of their codebase.