Field-tested perspectives on strategy, investment, architecture, sourcing and delivery for complex ICT projects.
Billing time encourages spending time. Billing an outcome aligns the provider's interest with the project's. Here's how we structure engagements around a deliverable, not a counter.
The costliest mistakes in a tender response are rarely technical: they come from an optimistic costing, undocumented assumptions, or an architecture under-sized for real-world operations.
An overly detailed HLD slows down decisions; an LLD done too early locks in choices you'll regret. Sequencing the two design levels is often what separates a schedule that holds from one that slips.
Most acceptance disputes are decided before the test itself — in how the acceptance criteria were (or weren't) defined and shared upfront with every stakeholder.
When the ICT scope touches security, industrial networks or critical systems, the absence of clear governance — roles, sign-offs, traceability — becomes a project risk in its own right.
IT, OT and building networks are increasingly converging onto a shared IP infrastructure. That convergence brings efficiency, but it also shifts the risk surface — and how you should design for it.
Starting from a solution before the need has been framed mechanically narrows the decision. Independent advice, free of any vendor relationship, changes the nature of the options actually on the table.
A convincing ICT investment case isn't just about technology cost: it has to demonstrate impact on risk, continuity and operational performance to win support at the leadership level.
The sourcing approach chosen shapes the outcome as much as the specification itself. Picking the right approach for the project's maturity and risk level avoids a lot of pain during execution.
These insights reflect how we frame projects — let's talk about yours.