Explore all content tagged with "CTO" across insights, frameworks, and resources.
RSS FeedIn a 50 person engineering org, a CTO with 8 direct reports can spend 4 hours a week in 1:1s. That is 200 hours a year per report if you meet weekly for 30 minutes.
In your first 90 days, it’s easy to burn weeks on work that feels responsible but quietly slows the company down.
Ward Cunningham technical debt and the quadrant model
TOGAF and ArchiMate for CTOs: Use Them as Decision Tools, Not Paperwork
Key Takeaways: Treat a tech-led selloff as a budget and risk reset, not a morale event. Reprice projects in weeks, not quarters.
Most CTOs I talk to have a fuzzy mental model of the CIO. Not because they're careless—because the CIO job shape-shifts depending on the company.
The CTO role is being redefined around AI: companies are hiring CTOs with generative AI pedigrees, expanding CTO scope into product and business operations, and contending with intense AI talent churn that can reshape execution risk and long-term strategy.
AI is rapidly becoming a regulated operational surface: CTOs are being asked to govern model behavior, third-party dependencies, and consumer outcomes with the same rigor as security and financial ...
CTO leadership is entering a “dual mandate” era: markets and boards are scrutinizing CTO moves like executive events, while the technical agenda is shifting toward AI system design, privacy control...
Agentic AI is moving from copilots to production control loops: vendors are pitching autonomous SRE and AI-native observability, investors are backing closed-loop remediation platforms, and boards are hiring AI-focused CTOs to operationalize these capabilities.
Have experience to share? We welcome contributions from technical leaders.
Learn how to contribute