Skip to content
MarketScale
Demo
Contributors›Tim Maitland
Tim Maitland photo

CRO · DisruptED

Tim Maitland

1 article
Contributor Brief·Tim Maitland · 1 article
Updated Jun 26, 2026

Design thinking, not code velocity, defines engineering's future value

Maitland argues through Wesley Pullin's perspective that engineering leadership must prioritize design thinking and problem-solving over raw coding speed and output metrics. The technology industry's obsession with developer productivity measures is fundamentally misaligned with what actually drives business impact and sustainable innovation.

55M

developers reached by Jenkins ecosystem at CloudBees

“Design thinking, not coding speed, is engineering's future.”

Ascendion's CTO: Design thinking, not coding speed, is engineering's future

Engineering leadership priorities shift from velocity to design

Coding speed / developer output metrics3
Design thinking and problem-solving approach9
Technical architecture decisions8
Team collaboration frameworks7

SHARE

11%Coding speed
Coding speed / developer output metrics
Design thinking and problem-solving approach
Technical architecture decisions
Team collaboration frameworks

34+ years

Wesley Pullin's experience spanning large software firms and infrastructure

When Ascendion co-founder Arun Varadarajan recruited him, it was not a familiar hire.

Ascendion's CTO article

Design thinking, not coding speed, is engineering's future.

Article title statement

“Problem-solving approach matters more than velocity metrics.”

Themes:Design thinking over developer velocityEngineering leadership transformation from metrics to mindsetInfrastructure ecosystem scale and impact measurement

What is MarketScale

These experts publish through MarketScale, a content platform that turns industry knowledge into articles, video, and audience. Want the same for your team?