As an independent consultant working across multiple projects, technical leadership doesn't mean managing a fixed team - it means being able to justify an architecture decision to different audiences: a developer who's going to implement it, a business stakeholder who's paying for it, and another architect who will inherit it a year from now.

"I learn best when I need to explain" isn't just a phrase - it's literally how I test whether a technical decision is solid or just seemed solid in my head. That requires a specific kind of discipline: documenting the why of a decision, not just the what.

Mentoring follows the same logic: I'd rather leave a team more capable of making the next decision on its own than solve everything personally. That's slower in the short term and cheaper in the long term - the kind of trade-off an outside consultant often sees more clearly than someone immersed in the day-to-day.

The path toward Certified Technical Architect (CTA) is, in practice, a formalization of this: the review board evaluates exactly the ability to defend architecture decisions under hard questions, not just make them.