Insights
Notes on business-led technology.
Short, practical writing from the consultants and engineers doing the work — delivery lessons, points of view and the occasional contrarian take. No content team, no thought-leadership machine.
Why our first recommendation is usually the smallest one
Clients often arrive expecting a platform. More often the fix is a process change and two weeks of work. Here is how we decide — and why under-scoping the first engagement tends to earn the second.
Read the article-
The questions we ask before writing a line of code
A short checklist we run on every brief, and what each answer changes about the plan.
Read -
Staff augmentation or managed delivery: a practical test
Three questions that tell you which model fits — before the contract, not after it.
Read -
What “accountable delivery” means when a project slips
Every firm promises accountability. This is what ours looks like on a bad week.
Read -
Reading an RFP for what it doesn’t say
The requirements list is rarely the real requirement. Where to look instead.
Read -
Legacy systems aren’t the problem. The seams are.
Most modernization budgets are spent at the integration points. A case for mapping them first.
Read -
How we size an engagement honestly
Fixed price, time and materials, or capped — and the questions that decide it.
Read
Article pages in progress
Written by the people delivering the work.