Devendra Kumar
30+ years across technology, global delivery and enterprise transformation. Today I write about the decisions, disciplines and ideas behind transformation.
Experience → Thinking → Frameworks → Writing
Why I write
Three decades in technology taught me something simple.
Transformation rarely fails because technology is unavailable.
It fails when decisions, operating models, governance, leadership and value are not aligned.
This site is where I explore those ideas.
My Perspective
Technology
Where it genuinely changes the economics of work, and where it is being asked to carry weight it cannot hold.
Autonomy, boundaries and accountability — what has to be true before an agent is allowed near a real process.
Landing zones, cost discipline and the long tail of workloads nobody wants to touch.
The difference between removing effort and removing the reason the effort existed.
Architecture as a decision record, not a diagram — and how it earns its authority.
Resilience, migration sequencing and the unglamorous work that decides whether anything else lands.
Ownership, lineage and the quiet reasons reporting disagrees with itself.
How I read a new capability: what problem it retires, what cost it introduces, what it assumes about your organisation.
Leadership
What the role actually holds — mandate, budget, sequencing and the politics of a shared agenda.
Setting direction with incomplete information, and being clear about which bets you are making.
How decisions get made under pressure, and how to leave a trail your successor can read.
Forums that surface reality early rather than confirm the plan late.
Hiring, trust, succession and the conditions under which good engineers do their best work.
Time zones, handovers and the cultural translation that no operating model diagram captures.
Thirty years of choices — the ones that compounded and the ones I would make differently.
Reducing it where possible, absorbing it where necessary, and naming it honestly either way.
Journal
Journal · Enterprise Architecture
Technical debt is not automatically bad. The problem is technical debt that becomes invisible, unmanaged or disconnected from business decisions.
Field Notes
Field Note · Transformation Decisions
Every new transformation should create capacity somewhere by removing demand elsewhere.
Field Note · AI and Enterprise Control
If this works, who will operate it when the pilot team leaves?
My Journey
Close to the machine — writing, breaking and supporting systems. Where I learned that most outages are explained by something ordinary.
First responsibility for other people's work: estimates, standards, and the discovery that clarity is a leadership deliverable.
Programs spanning geographies and vendors. Delivery became as much about handovers and language as about engineering.
Modernisation at scale — migrations, platforms, operating models, and the organisational absorption that decides the outcome.
Portfolio-level choices: what to fund, what to stop, and how to keep a multi-year agenda intact through change.
Sitting where technology, operations and the business case meet — and translating between them without losing precision.
My consulting work is presented separately through DK Transformation.