Running a technology function: what to delegate, what to insist on, and how to tell whether the work is any good.
52 articles, most recent first within each group.
Fractional CTO
- How to Audit a Technology Estate You've Never Seen Before
- The Fractional CTO's AI Adoption Playbook: Four Strategies
- When to Build a Team and When to Buy Capability
- Working With an Existing Agency Without Becoming the Enemy
- Hiring Your First Engineer: What to Look For
- Handover: Designing an Engagement for Your Own Replacement
- The True Cost of a Fractional CTO, Measured Against the Real Alternatives
- AI Talent Strategy: Reskill, Augment or Replace
- The Evolving CTO Mandate: From Stack-Keeper to Agent-Fleet Architect
- Outsourced Technology Leadership for UAE Boards: How Boards Should Scope a Remote Engagement
- How Foreign Technology Leaders Work Effectively with Saudi Boards: A Remote Operating Model
- Fractional CTO, interim CTO, technology consultant: what's actually the difference
- The first 90 days: what a fractional CTO actually delivers
- Always fixing, never building: the IT capacity trap
- The five stages of technology maturity — and where most businesses actually are
- You've raised seed funding. Now what does your technology need to look like?
- What happens to a business's technology when the CTO leaves
- Your first developer hire changes more than the headcount
- What a technology roadmap looks like when it's actually working
- Your IT manager is excellent. Here's why that can be exactly the problem.
- Why your IT team is always flat out and nothing ever moves forward
- What technology mentoring actually delivers for a non-technical founder
Technology Leadership
- Why the Technical Problem Is Almost Never the Problem
- Remote Technology Leadership for Luxembourg Boards: How It Actually Works
- Remote Technology Leadership for UK-Regulated Firms: A Pragmatic Operating Model
- What happens to your technology when the founder steps back?
- When your board starts asking questions about technology you can't answer
Key-Person Risk
- How to know if your developers are doing good work without reading the code
- What investors actually look for when they review your technology
- Your only developer just resigned. What to do in the next 30 days.
- Technical due diligence: what it checks, what fails, and how to be ready
- The questions every non-technical CEO should be able to answer about their technology
Technical Debt
- AI as Amplifier: Why It Makes Good Engineering Orgs Better and Bad Ones Worse
- Why Reactive Task Queues Destroy Technical Strategy
- Cognitive Debt: The New Technical Debt Boards Need to Track
- The technology decisions that show up in your P&L
- What the acquirer will find in your technology. Know before they do.
- When technology stops feeling like an asset and starts feeling like a liability
More in this area
- Knowledge Concentration Is a Business Risk, Not Just an HR Question
- The AI Productivity Paradox: Individuals Speed Up, the System Slows Down
- The Cost of a Decision That Never Gets Made
- End-to-End Delivery vs Piecemeal Task Assignment
- Estimation: Why It's Always Wrong and What to Do Instead
- Golden Paths, Not Mandates: Designing Platforms Developers Choose to Use
- Platform as a Product: Applying Product Thinking to Internal Infrastructure
- Redesigning Work, Not Just Automating It
- Being Cited by AI Search: A GEO/AEO Reading for Executives
- Building for where you're going, not where you are
- How technology compounds productivity
- Why businesses outgrow their technology at predictable points
- How to develop your judgment on technology decisions when you didn't start as technical
- Why Coding Throughput Is a Dangerous Productivity Metric