Consulting that ships
Strategy is only real once it runs in production.
AslanWay advises boards on where digital value sits — then builds, ships and operates the systems that capture it. One team, one accountability line, from the first workshop to the first million users.
The problem, in published numbers
Most of this work does not land. Here is the evidence.
Rather than a curated set of our own success stories, we will show you the industry's own research. Every figure is external, sourced and dated — follow the link and check it yourself.
McKinsey surveyed 1,793 executives in January 2018. A further 7% said performance improved but the improvement did not hold — meaning roughly three quarters saw neither lasting gain nor a durable capability.
An analysis of 1,471 IT projects found an average cost overrun of 27%. But one in six ran 200% over on cost and almost 70% over on schedule. The risk is not the average; it is the tail.
Gartner attributes the abandonment to poor data quality, inadequate risk controls, escalating costs and unclear business value — none of which are model problems.
An automated scan found 56.1 errors per page on average, up 10.1% year on year. Six recurring issues — led by low-contrast text and missing alternative text — account for the great majority.
What we do
Six capabilities, one delivery model
Most firms hand you a deck and leave. We staff strategists, engineers and designers on the same team, under the same milestones, measured on the same outcomes.
Digital strategy & transformation
Value-led strategy that ends in a costed roadmap and a first release, not a maturity assessment.
Data & AI
Data platforms, ML systems and applied AI that clear risk review and survive contact with real users.
Product engineering & build
Cross-functional squads that ship customer-facing and internal products to production on a fortnightly cadence.
Cloud & platform modernization
Landing zones, migration programmes and platform engineering that reduce unit cost and unblock delivery.
Experience & design
Service design, product design and design systems grounded in evidence from the people who actually use the thing.
Managed delivery & operations
SLA-backed operation of the platforms we build, with a scheduled, contractual path to client ownership.
How we work
A build-first operating rhythm
Five phases, each ending in something you can test with real users, real data or real regulators — and each capable of stopping the programme.
- 01
Diagnose
2–4 weeks
Quantify where value actually sits, and what is genuinely blocking it.
- 02
Frame
2–3 weeks
Turn the diagnosis into a sequenced roadmap and a first release small enough to ship.
- 03
Prove
6–12 weeks
Ship a narrow vertical slice to production, with real users and real money moving.
- 04
Build & scale
3–12 months
Widen the slice on a fortnightly cadence, hardening as scope and load grow.
- 05
Transfer & run
Contractual, from month one
Hand over on a dated schedule, with our fee falling as your team takes over.
Industries
Depth where the constraints are hardest
Regulation, legacy cores and long asset cycles are not obstacles we route around — they are the reason clients call us.
Banking & capital markets
Modernising around cores that cannot be replaced, under supervision that does not pause for your roadmap.
Insurance
Underwriting, claims and servicing where the margin is decided by decision quality and cycle time.
Manufacturing & industrials
Connecting the plant floor to the planning system without betting the line on a pilot.
Retail & consumer
Commerce platforms and store operations that survive peak, promotion and a 90-day season.
Public sector
Services that have to work for everyone, including the people least able to work around them.
Telecom & media
Convergent propositions and subscriber platforms where churn is decided in the first thirty days.
Insights
What we are seeing in the market
Practical points of view from the people doing the work — no vendor pitch, no maturity-model bingo.
Operating model4 min read
Your architecture will look like your org chart whether you like it or not
Conway wrote this down in 1968. Sixty years on, most target architectures are still drawn without anyone checking who will be allowed to talk to whom.
Source: Melvin E. Conway, How Do Committees Invent?, Datamation, 1968
Programme risk6 min read
0.5%. That is how many big projects land on budget, on time and on benefits.
Flyvbjerg has the largest dataset on big projects anyone has assembled. The headline number should change how you plan, and usually does not.
Source: Bent Flyvbjerg & Dan Gardner, How Big Things Get Done, Currency / Penguin Random House, 2023
Legacy modernization4 min read
The alternative to a big-bang rewrite has had a name for twenty years
Fowler named the pattern after a plant that grows around its host and replaces it in place. Most failed replatforming programmes are ones that ignored it.
Source: Martin Fowler, Strangler Fig Application, martinfowler.com, 2004, rewritten 2024
Have a programme that has stalled between slideware and shipping?
Tell us where it is stuck. We will come back within two business days with a point of view — and an honest answer on whether we are the right partner.